Re: [ANNOUNCE] kvm-52 release

david ahern
2007-11-12T17:09:41Z

Can you post the full qemu command that gets launched in each case?

david

Farkas Levente wrote:
> Izik Eidus wrote:
>> On Mon, 2007-11-12 at 17:07 +0100, Farkas Levente wrote:
>>> Izik Eidus wrote:
>>>> On Mon, 2007-11-12 at 16:29 +0100, Farkas Levente wrote:
>>>>> Avi Kivity wrote:
>>>>>> Small fixes and updates.
>>>>>>
>>>>>> Changes from kvm-51:
>>>>>> - fix efer reload host crash on T2600 and similar processors
>>>>>> - revert sleepy interrupt injection
>>>>>> - fixes "Fault when IDT_Vectoring"
>>>>>> - atomically inject real-mode interrupts
>>>>>> - wbinvd exiting on newer Intel processors (Eddie Dong)
>>>>>> - fixes real-time issues
>>>>>> - fix call/jmp instruction emulation (Izik Eidus)
>>>>>> - fixes Vista x64 installation
>>>>>> - fix save/restore/migrate with multiple nics
>>>>>> - fix build on i386 uniprocessor w/ no ioapic hosts
>>>>>> - fix smp_call_function_single() emulation on older hosts
>>>>>> - fixes smp guests not booting on RHEL 5 hosts
>>>>>> - make qemu/kvm memory allocation match plain qemu more closely (Izik Eidus)
>>>>>> - fixes issues with large memory guests
>>>>>> - libkvm compile fixes (Carlo Marcelo Arenas Belon, Jerone Young)
>>>>> still not working for us, there is even a small regression.
>>>> wow, what host kernel are you using?
>>> see bellow:-)
>>> are you think i manually create the screenshots?:-)?
>>>
>>>>> with smp:
>>>>> - centos 32bit guest hang during boot at different places (see screenshot).
>>>> work for me (2.6.23.1)
>>> there is no such kernel for redhat/centos! we use a clean upstream fully
>>> updated centos (ie. the kernel actually 2.6.18-8.1.15:-)
>>>
>> ok this is hard to catch, i tried to use centos 5 kernel 2.6.18-8.el5
>> and ran smp guest, (centos5 64 and winxp32) and it worked for me
>> you have any idea what i can do to make my system look more like your?
>> what could be diffrent?
>
> first of all fully update your centos (a bit newer kernel), then i use
> these packages:
> http://www.lfarkas.org/linux/packages/centos/5/x86_64/
> use libvirtd and virt-manager too and start the guests from there. and
> start them manually paralell (i used to reboot the host when i update
> kvm, the start virt-manager and start each guests). anyway may be a
> newer processor generate the same result as ours.
> or if you can send me any kind of debug kvm version i can run it which
> can print any additional debug messages etc...
>
> i can just repeat my setup:
> - host:
> - Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
> - Intel S3000AHV
> - 8GB RAM
> - CentOS-5
> - kernel-2.6.18-8.1.15.el5 x86_64 64bit
> - guest-1:
> - CentOS-5
> - kernel-2.6.18-8.1.15.el5 i386 32bit
> - guest-2:
> - CentOS-5
> - kernel-2.6.18-8.1.15.el5 x86_64 64bit
>
> packages on the host:
> # rpm -qa|egrep "virt|vnc|kvm"|sort
> gtk-vnc-0.2.0-4
> gtk-vnc-python-0.2.0-4
> kmod-kvm-52-1.2.6.18_8.1.15.el5
> kvm-52-1
> libvirt-0.3.3-2
> libvirt-python-0.3.3-2
> python-virtinst-0.300.1-3
> virt-manager-0.5.2-2
> virt-top-0.3.2.8-1
> virt-viewer-0.0.2-2
> vnc-4.1.2-9.el5
>
> the two guest config in libvirtd are the following:
> devel-i386.xml:
> -------------------------------------------------------------
> <domain type='kvm'>
> <name>devel-i386</name>
> <uuid>dee4ab98-363c-649f-4a02-fef25b17756b</uuid>
> <memory>2097152</memory>
> <currentMemory>2097152</currentMemory>
> <vcpu>1</vcpu>
> <os>
> <type>hvm</type>
> <boot dev='hd'/>
> </os>
> <features>
> <acpi/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>destroy</on_crash>
> <devices>
> <emulator>/usr/bin/qemu-kvm</emulator>
> <disk type='block' device='disk'>
>
> <target dev='hda'/>
> </disk>
> <disk type='block' device='disk'>
>
> <target dev='hdb'/>
> </disk>
> <disk type='block' device='disk'>
>
> <target dev='hdc'/>
> </disk>
> <!--
> <disk type='block' device='cdrom'>
>
> <target dev='hdcd?'/>
> <readonly/>
> </disk>
> -->
> <interface type='bridge'>
> <mac address='00:16:3e:58:66:7b'/>
>
> </interface>
>
> <graphics type='vnc' port='-1' listen='127.0.0.1'/>
> </devices>
> </domain>
> -------------------------------------------------------------
> devel-x86-64.xml:
> -------------------------------------------------------------
> <domain type='kvm'>
> <name>devel-x86-64</name>
> <uuid>9436bef1-aef9-2f5c-21cf-123e300fcd27</uuid>
> <memory>524288</memory>
> <currentMemory>524288</currentMemory>
> <vcpu>1</vcpu>
> <os>
> <type>hvm</type>
> <boot dev='hd'/>
> </os>
> <features>
> <acpi/>
> </features>
> <clock offset='utc'/>
> <on_poweroff>destroy</on_poweroff>
> <on_reboot>restart</on_reboot>
> <on_crash>destroy</on_crash>
> <devices>
> <emulator>/usr/bin/qemu-kvm</emulator>
> <disk type='block' device='disk'>
>
> <target dev='hda'/>
> </disk>
> <disk type='block' device='disk'>
>
> <target dev='hdb'/>
> </disk>
> <interface type='bridge'>
> <mac address='00:16:3e:2e:99:e2'/>
>
> </interface>
>
> <graphics type='vnc' port='-1' listen='127.0.0.1'/>
> </devices>
> </domain>
> -------------------------------------------------------------