Bugs item #1941302, was opened at 2008-04-13 14:21 Message generated for change (Comment added) made by avik You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1941302&group_id=180599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: yunfeng (yunfeng) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot boot guests with hugetlbfs Initial Comment: I meet problem to get hugetlbfs work on my test box. If i added "--mem-path" to qemu, the guest will always fail to boot with the error messages below printed on qemu console: ########################################### ata0 master: ATA-0 Hard-Disk ( 0 MBytes) ata1 master: ATAPI-0 Device Booting from Hard Disk ..... Booting from Hard Disk failed: could not read the boot disk ########################################## And I checked my system, hugepages has been enabled. [root@vt-dp8 ~]# grep -i huge /proc/meminfo HugePages_Total: 500 HugePages_Free: 496 HugePages_Rsvd: 0 Hugepagesize: 2048 kB [root@vt-dp8 ~]# mount /dev/sda1 on / type ext3 (rw) none on /dev/shm type tmpfs (rw,size=4G) nodev on /hugepages type hugetlbfs (rw) /dev/sda3 on /share type ext2 (rw) /dev/sda2 on /mnt/sda2 type ext3 (rw) The command i am using: qemu -m 256 -monitor pty -net nic,macaddr=00:16:3e:48:d4:aa,model=rtl8139 -net tap,script=/etc/kvm/qemu-ifup -hda /dev/sda --mem-path /hugepages/ If I remove "--mem-path", the guest can be booted up. ---------------------------------------------------------------------- >Comment By: Avi Kivity (avik) Date: 2009-08-10 15:24 Message: Should be fixed in kvm-88. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1941302&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
