From: Binarus <lists@binarus.de>
To: kvm@vger.kernel.org
Subject: Re: Unable to pass multiple cores / CPUs to guests
Date: Sat, 04 Feb 2012 10:03:21 +0100 [thread overview]
Message-ID: <4F2CF459.9010302@binarus.de> (raw)
In-Reply-To: <20120130174445.GA23238@psychosis.jim.sh>
Jim,
I just don't know how I could thank you! I have put multiple days into that problem and didn't remember nor see that I already have put -smp 1 later in the command. I think it would have cost me some more days or I would have been unable to solve the problem at all if you didn't give me that hint.
It's working like expected now; the guest sees and uses the additional CPU core, and the backup from encrypted drives to other encrypted drives is running much faster and with lower CPU load now.
An amusing aside: During my experiments, I had a set of parameters which made the Windows guest think it runs at 7.2 GHz (3 x 2.4 GHz where 2.4 GHz is the real clock rate of the host's CPU). Unfortunately, I can't remember the exact command, but I believe it roughly looked like ... -cpu qemu64 -smp2 ... -smp 1 ...
Regards,
Binarus
On 30.01.2012 18:44, Jim Paris wrote:
> Binarus wrote:
>> Dear all,
>>
>> it seems that I am unable to pass multiple cores / CPUs to KVM
>> guests. Whatever I do, the guests only report one CPU / core.
> ...
>> /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 ./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
>
> Remove the "-smp 1".
>
> -jim
>
prev parent reply other threads:[~2012-02-04 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 8:05 Unable to pass multiple cores / CPUs to guests Binarus
2012-01-30 17:44 ` Jim Paris
2012-02-04 9:03 ` Binarus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F2CF459.9010302@binarus.de \
--to=lists@binarus.de \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).