However, you mention that you have your VM pinned to CPU 1, while the command line is doing '-cpu 4'. When I run a VM with -cpu 4 locked to a single physical cpu, it definately does not do well. I'm not sure whether to call that a bug or mis-use.
Example: cgm create cpuset qemu cgm setvalue cpuset qemu cpuset.cpus 0 cgm movepid cpuset qemu $$ kvm -hda x.img -cdrom ubuntu-13.10-desktop-amd64.iso -m 1024 -realtime mlock=off -smp 4,sockets=1,cores=4,threads=1 -rtc base=localtime (resulting VM hangs; without the -smp 4,sockets=1,cores=4,threads=1' it runs fine.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307473 Title: guest hang due to missing clock interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1307473/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
