Yunfeng,
I'd like additional information to help narrow
the problem space and assure this isn't some type
of version skew problem. Please see my comments/
questions inline below.
Thanks,
-john
> Subject: [kvm-devel] [ kvm-Bugs-1941302 ] Cannot boot guests with hugetlbfs
> From: "SourceForge.net" <[EMAIL PROTECTED]>
> Date: Sun, 13 Apr 2008 04:21:08 -0700
> To: kvm-devel@lists.sourceforge.net
>
> Bugs item #1941302, was opened at 2008-04-13 19:21
> Message generated for change (Tracker Item Submitted) made by Item Submitter
> 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: Open
> Resolution: None
> 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:
What kvm-release and kernel version were you using here?
> ###########################################
> 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
> ##########################################
Were any diagnostics generated from qemu in the window it
was launched? Also could you try to launch it exactly
as you did before but trace the syscall progression as:
# script
# strace -f qemu <args..>
# exit
..and attach the resulting typescript log to this bug case?
> And I checked my system, hugepages has been enabled.
> [EMAIL PROTECTED] ~]# grep -i huge /proc/meminfo
> HugePages_Total: 500
> HugePages_Free: 496
> HugePages_Rsvd: 0
> Hugepagesize: 2048 kB
Is qemu hanging after printing out the above "could
not read the boot disk" message in the qemu console?
If so could you leave it hung while doing another grep
of /proc/meminfo to see if it did manage to acquire any
huge pages?
> [EMAIL PROTECTED] ~]# 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.
--
[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
