kvm-52 release

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)

Hi Levente !

The only idea that I have for you is to: Try to run KVM on newer kernel. (2.6.21+)

I did all of what you said on Fedora 7/x64 host (2.6.21 default kernel) and it all worked ! (except Mandrake 9.0, which I don't have)

Quoted 7 lines · Alexey Eremenko

Hi Levente !

The only idea that I have for you is to: Try to run KVM on newer kernel. (2.6.21+)

I did all of what you said on Fedora 7/x64 host (2.6.21 default kernel) and it all worked ! (except Mandrake 9.0, which I don't have)

that's exactly which i'm not really want!
i really like to keep at a standard distributed upstream patched kernel. we never would like to use non redhat/centos kernel on servers. we all have fedora on our workstations, but (probably that's way) we all knows the stability of these kernels. ok currently kvm also bring the hosts and the guest to the same level or even worse, but i hope it'd change in the near feature (the only thing i want a stable smp guest kvm and probably won't update it for a while).
i can try a fedora kernel just for test but wouldn't like to switch the whole host os and it's not so trivial to change only the kernel under redhat/centos (there are udev and other dependencies).

Quoted 18 lines · Avi Kivity

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.

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

- centos 64bit guest boot but crash (or at least dump stack strace on

console) the other screenshot.
- winxp guest are hang during boot.

setup:
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:

- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
_

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 1 line

still not working for us, there is even a small regression.

wow, what host kernel are you using?

Quoted 2 lines

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

work for me (2.6.23.1)

Quoted 1 line

- centos 64bit guest boot but crash (or at least dump stack strace on

work for me

Quoted 2 lines

console) the other screenshot.
- winxp guest are hang during boot.

work for me

Quoted 19 lines

setup:
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-1:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 i386 32bit
- guest-2:
- CentOS-5
- kernel-2.6.18-8.1.14.el5 x86_64 64bit
- guest-3:
- Mandrake-9
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Windows XP Professional 32bit
_

Quoted 20 lines · Izik Eidus

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 3 lines

Quoted 1 line

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?:-)?

Quoted 3 lines

Quoted 2 lines

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:-)

Quoted 29 lines · Farkas Levente

Quoted 20 lines · Izik Eidus

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 2 lines

Quoted 1 line

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?:-)?

Quoted 3 lines

Quoted 2 lines

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

work for me (2.6.23.1)

Quoted 3 lines

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?

Quoted 29 lines · Izik Eidus

Quoted 28 lines · Farkas Levente

Quoted 20 lines · Izik Eidus

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 2 lines

Quoted 1 line

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?:-)?

Quoted 2 lines

Quoted 2 lines

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

Quoted 8 lines

Quoted 4 lines

Quoted 1 line

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'>
      <source dev='/dev/VolGroup00/centos-i386-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-i386-swap'/>
      <target dev='hdb'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/md2'/>
      <target dev='hdc'/>
    </disk>
<!--
    <disk type='block' device='cdrom'>
      <source dev='/dev/hda'/>
      <target dev='hdcd?'/>
      <readonly/>
    </disk>
-->
    <interface type='bridge'>
      <mac address='00:16:3e:58:66:7b'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <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'>
      <source dev='/dev/VolGroup00/centos-x86_64-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
      <target dev='hdb'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:2e:99:e2'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='127.0.0.1'/>

</devices>
</domain>
-------------------------------------------------------------

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

david

Quoted 166 lines · Farkas Levente

Quoted 29 lines · Izik Eidus

Quoted 28 lines · Farkas Levente

Quoted 20 lines · Izik Eidus

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 2 lines

Quoted 1 line

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?:-)?

Quoted 2 lines

Quoted 2 lines

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

Quoted 8 lines

Quoted 4 lines

Quoted 1 line

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'>
      <source dev='/dev/VolGroup00/centos-i386-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-i386-swap'/>
      <target dev='hdb'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/md2'/>
      <target dev='hdc'/>
    </disk>
<!--
    <disk type='block' device='cdrom'>
      <source dev='/dev/hda'/>
      <target dev='hdcd?'/>
      <readonly/>
    </disk>
-->
    <interface type='bridge'>
      <mac address='00:16:3e:58:66:7b'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <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'>
      <source dev='/dev/VolGroup00/centos-x86_64-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
      <target dev='hdb'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:2e:99:e2'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='127.0.0.1'/>

</devices>
</domain>
-------------------------------------------------------------

Quoted 1 line · david ahern

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

this is the current running one, the only difference when smp set is -smp 4:

root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35
/usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0

root 3299 0.7 6.6 636024 540116 ? Sl 16:20 2:19
/usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-x86_64-root -hdb /dev/VolGroup00/centos-x86_64-swap -net nic,macaddr=00:16:3e:2e:99:e2,vlan=0 -net tap,fd=14,script=,vlan=0 -usb -vnc 127.0.0.1:1

root 3459 0.4 5.0 639940 410684 ? Sl 16:21 1:23
/usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/mandrake-root -hdb /dev/VolGroup00/mandrake-swap -net nic,macaddr=00:16:3e:37:68:fd,vlan=0 -net tap,fd=18,script=,vlan=0 -usb -vnc 127.0.0.1:2

Quoted 170 lines

david

Quoted 166 lines · Farkas Levente

Quoted 29 lines · Izik Eidus

Quoted 28 lines · Farkas Levente

Quoted 20 lines · Izik Eidus

Quoted 19 lines · Farkas Levente

Quoted 18 lines · Avi Kivity

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)

Quoted 2 lines

Quoted 1 line

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?:-)?

Quoted 2 lines

Quoted 2 lines

with smp:
- centos 32bit guest hang during boot at different places (see screenshot).

Quoted 8 lines

Quoted 4 lines

Quoted 1 line

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'>
      <source dev='/dev/VolGroup00/centos-i386-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-i386-swap'/>
      <target dev='hdb'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/md2'/>
      <target dev='hdc'/>
    </disk>
<!--
    <disk type='block' device='cdrom'>
      <source dev='/dev/hda'/>
      <target dev='hdcd?'/>
      <readonly/>
    </disk>
-->
    <interface type='bridge'>
      <mac address='00:16:3e:58:66:7b'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <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'>
      <source dev='/dev/VolGroup00/centos-x86_64-root'/>
      <target dev='hda'/>
    </disk>
    <disk type='block' device='disk'>
      <source dev='/dev/VolGroup00/centos-x86_64-swap'/>
      <target dev='hdb'/>
    </disk>
    <interface type='bridge'>
      <mac address='00:16:3e:2e:99:e2'/>
      <source bridge='eth0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <graphics type='vnc' port='-1' listen='127.0.0.1'/>

</devices>
</domain>
-------------------------------------------------------------

One of my hosts is a DL380 G5 (Intel(R) Xeon(R) CPU 5140 @ 2.33GHz) with 4GB of RAM. At this time it is running the stock i386 version of RHEL5.1. I am building kvm from the tar balls, currently using kvm-52.

I have a stock RHEL5 guest (2.6.18-8.el5 kernel) and no added kernel boot options. The qemu command is:

/usr/local/bin/qemu-system-x86_64 -boot c -localtime -hda images/rhel5.img -m 1536 -smp 4 -net nic,macaddr=00:1a:4b:34:74:52,model=rtl8139 -net tap,ifname=tap0,script=/bin/true -monitor stdio -vnc :2

Starting with the Avi's patch over the weekend, all of my SMP guests (running stock RHEL 3.8, RHEL 4.4, and RHEL 5.0) now boot just fine.

Are you adding any kernel options to the guest boot? If not, try adding 'noapic'.

While debugging this issue, you might try downloading the kvm tar balls and building/installing from it -- removing the rpms first of course to make sure there are not conflicts -- and running qemu directly rather than through virtmanager.

david

Quoted 22 lines · Farkas Levente

Quoted 1 line · david ahern

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

this is the current running one, the only difference when smp set is -smp 4:

root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35
/usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0

root 3299 0.7 6.6 636024 540116 ? Sl 16:20 2:19
/usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-x86_64-root -hdb /dev/VolGroup00/centos-x86_64-swap -net nic,macaddr=00:16:3e:2e:99:e2,vlan=0 -net tap,fd=14,script=,vlan=0 -usb -vnc 127.0.0.1:1

root 3459 0.4 5.0 639940 410684 ? Sl 16:21 1:23
/usr/bin/qemu-kvm -M pc -m 512 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/mandrake-root -hdb /dev/VolGroup00/mandrake-swap -net nic,macaddr=00:16:3e:37:68:fd,vlan=0 -net tap,fd=18,script=,vlan=0 -usb -vnc 127.0.0.1:2

Quoted 2 lines · david ahern

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

this is the current running one, the only difference when smp set is -smp 4:

root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35
/usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0

Quoted 4 lines · Farkas Levente

Quoted 2 lines · david ahern

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

Quoted 9 lines

this is the current running one, the only difference when smp set is -smp 4:

root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35
/usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0

Well, you're not running kvm-52 userspace then. You're running Fedora's kvm package (unless you renamed /usr/local/bin/qemu-system-x86_64 to /usr/bin/qemu-kvm).

Quoted 18 lines · Avi Kivity

Quoted 6 lines · Farkas Levente

Quoted 3 lines · david ahern

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

Quoted 10 lines

this is the current running one, the only difference when smp set is -smp 4:

root 3270 10.3 25.8 2213976 2111868 ? Sl 16:20 30:35
/usr/bin/qemu-kvm -M pc -m 2048 -smp 1 -monitor pty -boot c -hda /dev/VolGroup00/centos-i386-root -hdb /dev/VolGroup00/centos-i386-swap -hdc /dev/md2 -net nic,macaddr=00:16:3e:58:66:7b,vlan=0 -net tap,fd=11,script=,vlan=0 -usb -vnc 127.0.0.1:0

Quoted 4 lines

Well, you're not running kvm-52 userspace then. You're running Fedora's kvm package (unless you renamed /usr/local/bin/qemu-system-x86_64 to /usr/bin/qemu-kvm).

i running kvm-52 userspace. i build the rpm based on centos and fedora spec file (which eventually rename it to qemu-kvm). belive me these rpm are the latest compiled by myself from the latest kvm-52.tar.gz on a fully updated centos x86_64.

is there any way how can i prove it? may be a command line option for qemu -version would be useful.

anyway how should i've test noapic? qemu command line -noapic or guest kernel param noapic or both?

Quoted 3 lines · Farkas Levente

anyway how should i've test noapic? qemu command line -noapic or guest kernel param noapic or both?

Add 'noapic' to guest kernel boot options. I've been adding it for a while to workaround a networking issue (see kvm-Bugs-1802082).

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).

Quoted 6 lines · Farkas Levente

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).

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

Quoted 9 lines · Avi Kivity

Quoted 7 lines · Farkas Levente

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).

Quoted 4 lines

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot the host (just to be sure).

Quoted 15 lines · Farkas Levente

Quoted 13 lines · Avi Kivity

Quoted 7 lines · Farkas Levente

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).

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

Quoted 4 lines

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot the host (just to be sure).

Installing the files means nothing. You also need to make sure all your tools use the right binaries (or use the command line directly).

Quoted 16 lines · Avi Kivity

Quoted 15 lines · Farkas Levente

Quoted 13 lines · Avi Kivity

Quoted 7 lines · Farkas Levente

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).

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

Quoted 7 lines

Quoted 4 lines

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot the host (just to be sure).

Installing the files means nothing. You also need to make sure all your tools use the right binaries (or use the command line directly).

ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0 (not rhel3) i do know how to install and use packages and which files are called. there is no any other kvm in the given machine. ok i understand that you try to find some kind of reason why it's works for you and not for me but that's not the reason.
anyway it'd be useful to if i can see which version of the userspace running ie. give a short message into the stslog on the host about the userspace version may be even a warning in case of the kmod and the userspace version are different, but currently that's all:
------------------------------------
[root@kvm ~]# rpm -qa|grep kvm kmod-kvm-52-1.2.6.18_8.1.15.el5
kvm-52-1
[root@kvm ~]# rpm -qf /usr/bin/qemu-kvm
kvm-52-1
[root@kvm ~]# rpm -V kvm-52-1
[root@kvm ~]# modinfo kvm_intel

filename:       /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
license:        GPL
author:         Qumranet
version:        kvm-52
srcversion:     F7E80D6C3124584F75EDAAF
depends:        kvm
vermagic:       2.6.18-8.1.15.el5 SMP mod_unload gcc-4.1
parm:           bypass_guest_pf:bool

Hi Levente,

Quoted 40 lines · Farkas Levente

Quoted 16 lines · Avi Kivity

Quoted 15 lines · Farkas Levente

Quoted 13 lines · Avi Kivity

Quoted 7 lines · Farkas Levente

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).

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

Quoted 6 lines

Quoted 4 lines

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot the host (just to be sure).

Installing the files means nothing. You also need to make sure all your tools use the right binaries (or use the command line directly).

ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0 (not rhel3) i do know how to install and use packages and which files are called. there is no any other kvm in the given machine. ok i understand that you try to find some kind of reason why it's works for you and not for me but that's not the reason.
anyway it'd be useful to if i can see which version of the userspace running ie. give a short message into the stslog on the host about the userspace version may be even a warning in case of the kmod and the userspace version are different, but currently that's all:
------------------------------------
[root@kvm ~]# rpm -qa|grep kvm kmod-kvm-52-1.2.6.18_8.1.15.el5
kvm-52-1
[root@kvm ~]# rpm -qf /usr/bin/qemu-kvm
kvm-52-1
[root@kvm ~]# rpm -V kvm-52-1
[root@kvm ~]# modinfo kvm_intel

Quoted 8 lines

filename:       /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko
license:        GPL
author:         Qumranet
version:        kvm-52
srcversion:     F7E80D6C3124584F75EDAAF
depends:        kvm
vermagic:       2.6.18-8.1.15.el5 SMP mod_unload gcc-4.1
parm:           bypass_guest_pf:bool

[snip]

perhaps you can try:

- "rpm -ql kvm-52-1"
- "rpm -qf /lib/modules/2.6.18-8.1.15.el5/extra/kvm/kvm-intel.ko"
- "find /lib/modules -name kvm.ko"
- "find /lib/modules -name kvm-intel.ko"
- "type qemu-kvm"

Just to be sure there is no garbage on your system...

Quoted 21 lines · Avi Kivity

Quoted 19 lines · Farkas Levente

Quoted 16 lines · Avi Kivity

Quoted 8 lines · Farkas Levente

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).

IIRC virt-manager uses /usr/bin/kvm as its qemu launcher. Maybe it is running the old userspace. Can you ensure that you are using the new userspace and new kernel modules at all times?

Quoted 8 lines

Quoted 5 lines

yes, it's sure. i always run rpm -Uvh kvm... kmod-kvm... and the reboot the host (just to be sure).

Installing the files means nothing. You also need to make sure all your tools use the right binaries (or use the command line directly).

ohh come on. i use linux since 94 and i use redhat/rpm since redhat 3.0 (not rhel3) i do know how to install and use packages and which files are called. there is no any other kvm in the given machine. ok i understand that you try to find some kind of reason why it's works for you and not for me but that's not the reason.

anyway it'd be useful to if i can see which version of the userspace running ie. give a short message into the stslog on the host about the userspace version may be even a warning in case of the kmod and the userspace version are different, but currently that's all:

Quoted 5 lines

anyway it'd be useful to if i can see which version of the userspace running ie. give a short message into the stslog on the host about the userspace version may be even a warning in case of the kmod and the userspace version are different, but currently that's all:

kvm is designed to support mismatched kernel/userspace versions, so that's inappropriate for production.