Re: Debian 5.0 host, qemu-kvm 0.12.4, unable to use -smp > 1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Aug 11, 2010 at 7:29 AM, Freddie Cash <fjwcash@xxxxxxxxx> wrote:
> We just upgraded our KVM host system from KVM-72 to qemu-kvm 0.12.4
> (debian lenny backports).  We are now unable to start any VMs that use
> -smp option with values > 1 (-smp 1 works, -smp 2 doesn't).
> Everything else is the same (nothing in the guests was changed,
> nothing else on the host was changed).
>
> Hardware:
>  Tyan h2000M motherboard
>  2x dual-core AMD Opteron 2200-series CPUs @ 2 GHz
>  16 GB DDR2 SDRAM
>  3Ware 9550SXU-12ML RAID controller
>  12x 500 GB SATA harddrives in RAID6
>  Intel PRO/1000MT quad-port gigabit NIC (bonded into kvmbr0)
>
>  Debian 5.0 (Lenny) amd64
>
> Everything was working great with KVM-72 with the exception of virtio
> block device drivers (memory leak).
>
> We have several Debian/Ubuntu and Windows XP/2003 VMs running on here
> with various amounts of RAM.  And 1 VM that was running with -smp 2
> that is now running with -smp 1.
>
> I've tested -smp 1,cores=2 and it will boot, but only shows 1 CPU.
> Using any value other than 1 for -smp causes the kvm process to start
> (shows in ps output) but never run (no CPU usage in top, no VNC
> connection, no errors, just nothing).
>
> Not sure how to diagnose this one.  Any ideas?

Adding -no-kvm-irqchip to the command-line allows the VM to start, and
the extra virtual CPUs to appear.  No idea what this option does,
though, nor why it would be needed.  It's not listed in the qemu/kvm
man page.

The command fails:
/usr/bin/kvm -name radius -smp 2 -m 512 -vnc :12 -daemonize -localtime
-usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:12,model=e1000
-net tap,ifname=tap12 -pidfile /var/run/kvm/radius.pid -boot c -drive
index=0,media=disk,if=virtio,boot=on,file=/dev/mapper/vol0-radius

And this one works:
/usr/bin/kvm -name radius -smp 2 -m 512 -vnc :12 -daemonize -localtime
-usb -usbdevice tablet -net nic,macaddr=00:16:3e:00:00:12,model=e1000
-net tap,ifname=tap12 -pidfile /var/run/kvm/radius.pid -boot c -drive
index=0,media=disk,if=virtio,boot=on,file=/dev/mapper/vol0-radius
-no-kvm-irqchip

Anyone care to explain what -no-kvm-irqchip does, and/or why it's needed now?
-- 
Freddie Cash
fjwcash@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux