I let the host stay up for 90 minutes before loading kvm and starting a VM. On 
the first reboot it hangs at 'Starting udev'.

I added 'noapic' to the kernel boot options, and it boots fine. (Turns out I 
only added that to grub.conf in images that run a particular ap for which I am 
running performance tests.)

I would like to know why I need the noapic option to get around this and the 
networking problem. Are there performance hits as a side effect?

david

Avi Kivity wrote:
> david ahern wrote:
>> With kvm-52 my 32-bit host running RHEL5.1 can start an RHEL 5 SMP guest 
>> only once. Second and subsequent attempts hang. Removing kvm and kvm_intel 
>> modules have no affect; I need to reboot the host to get an SMP guest to 
>> start. My similarly configured 64-bit host does not seem to have this 
>> problem.
>>
>>
>>   
> 
> What happens if you boot a host, wait a while (say a couple of hours),
> and then start a guest?
> 
> (I'm suspecting unsynchronized tscs)
> 

-------------------------------------------------------------------------
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/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to