Re: [ANNOUNCE] kvm-51 release

[david ahern <daahern-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>]

I removed the kvm/kvm-intel modules. qemu command line was:

/usr/local/bin/qemu-system-x86_64 -boot c -localtime -hda /opt/kvm/images/rhel5.img -m 1536 -smp 4 -net nic,macaddr=00:0c:29:10:10:e8,model=rtl8139 -net tap,ifname=tap0,script=/bin/true -monitor stdio -no-kvm -name bldr-ccm89.cisco.com -vnc :2

I did *not* add 'noapic' to guest kernel boot. 

The VM boot went fine; the reboot did not. qemu process was showing 100% CPU. After a few minutes I hit ctrl-c, to terminate qemu and then restarted the exact the same command. Same result: boot went fine; shutdown did not, though it hung at a different spot.

If it matters, host for this test is an HP DL380 G5.

david


Avi Kivity wrote:
> david ahern wrote:
>> First boot has been working fine since your patch this past weekend.
>> It's been subsequent boots that hang.
>>
>> I added -no-kvm-irqchip to qemu command line and did not add the
>> noapic boot option: it's hung at 'Starting udev' again but this time
>> it's not consuming CPU. kernel stack traces for qemu threads:
>>
>>   
> 
> Ah okay.  I misunderstood.
> 
> How about -no-kvm?  Maybe it's a qemu problem.
> 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/