![]() ![]() ![]() Multiprocessor HAL), but with no success. Of course, I have read about changing the HAL within Windows and tried several things (Uniprocessor HAL vs. Now, I really need additional CPU power in one of the guests, so I am wondering what I am doing wrong. I am running several Windows guests (Server 2003 R2 (32 Bit), Server 2008 R2 (64 Bit), Windows XP Pro (32 Bit), Windows 7 Pro (64 Bit)) and Linux guests (Ubuntu 11.10 (64 Bit), Debian squeeze (32 Bit)), but all of these only report one processor / core, regardless of the -smp settings besides that, the setup works reliably. I also have tried -cpu host and -smp cores=1,threads=1,sockets=2 (amongst other things). qemu-garak.pid -boot c -k de -m 4096 -smp 1 -device pci-assign,host=01:05.0 -daemonize -usb -usbdevice "tablet" -name garak -net nic,vlan=0,model=virtio,macaddr=02:01:01:01:01:01 -net tap,vlan=0,ifname=virtnet1,script=/etc/qemu-ifup,downscript=/etc/qemu-ifup -vnc :1 I am using commands like this one: /usr/bin/qemu-system-x86_64 -M pc -cpu host -smp cores=2,threads=1,sockets=1 -drive file=/dev/sda6,if=virtio,cache=none,index=0 -drive file=/dev/sdb,if=virtio,cache=none,index=1 -cdrom /dev/cdrom -pidfile. Since virt-manager and the related tools were failing with unintelligible error messages when trying the very first basic action, I am starting the virtual machines by hand instead of using any wrappers / managers. I did not alter the other parts of the distribution notably, I am using the original qemu-kvm package which was included. I have compiled my own (newer) kernel 2.6.37 for Natty (since I had certain problems with PCI passthrough if I used the standard kernel). Host software: Ubuntu 11.04 (Natty) 64-Bit Host hardware: Xeon E5620 on a Supermicro mainboard ![]() Whatever I do, the guests only report one CPU / core. You will notice how interesting my system is numbering the cores.It seems that I am unable to pass multiple cores / CPUs to KVM guests. sys/devices/system/cpu/cpu do echo 0 > /sys/devices/system/cpu/cpu$fake_cpu/online done Here is an example from an SMP quadcore box with Hyperthreading: # grep. The /sys filesystem holds a nice overview of this information. But using this information you can associate which processors are from the same core. There is no distinction between "virtual" or "real" in hyperthreading. Note that there 8 siblings and 4 cores, so there is 2 virtual processor per core. You can use this information to correlate which virtual processor goes into a single core.Īpicid (and original apicid) show the number of the (virtual) processor, as given by the bios. Siblings show the number of processor attached to the same physical processor.Ĭore id show the identifier of the current core, out to a total of cpu cores. Unless you have a multiprocessor setup (having two separate, physical processor in a machine), it will always be 0. Physical id shows the identifier of the processor. You can know about each processor core by examining each cpuinfo entry: processor : 0
0 Comments
Leave a Reply. |