[libvirt-users] How to set cpuset.cpus dynamically?
by Peeyush Gupta
Hi all,
I have been trying to run a VM on some particular cpu cores. Now the thing is I can set cpuset with virt-install and that will reflect in VM's XML and it will define the affinity. But what about cpuset.cpus? That is inherited directly from the parent. Is there any way to set it when launching the VM? Again, if I have given cpuset during virt-install, why doesn't cpuset.cpus reflect the value instead of inheriting it from parent?
Thanks.
~Peeyush Gupta
11 years
[libvirt-users] Not able to create two cpusets with exclusive access
by Peeyush Gupta
Hi all,
I am trying to set up exclusive cpu access for two different VMs. Now, in the hierarchy, the directories of both the VM's are inside /libvirt/qemu/$VM. I have 3 cpus on my machine. I have done echo 0 > cpuset.cpus and echo 1 > cpuset.cpu_exclusive for one VM. Now, I am launching another VM using virt-install and I have given the option --cpuset 1. There is no overlapping of cpus here, but still libvirt is showing error that it's unable to create cgroup for the new VM. Is it possible to have two exclusive cpusets inside a same hierarchy?
~Peeyush Gupta
11 years
[libvirt-users] cpuset attribute not working with virt-install
by Peeyush Gupta
Hi all,
I have been trying to use cpuset with virt-install. I am using the following command:
$ virt-install --virt-type kvm --name Ubuntu13 --ram 1024 --cdrom=/home/peeyush/Downloads/ubuntu-13.04-desktop-i386.iso --cpuset=0,2 --disk path=/var/lib/libvirt/guest.qcow2,size=10,format=qcow2
Now, according to virt-install man page, my VM's cpu affinity should be set to pcpu 0 and 2 . But when I did virsh vcpuinfo $VM, it shows that the affinity is to all cpus. I checked the xml file of my VM and it has the cpuset attribute, but still my VM is running on all cpus.
~Peeyush Gupta
11 years
[libvirt-users] nova-compute, libvirt and authentication
by Maciej Gałkiewicz
Hello
I have a question about live migration when libvirt requires sasl
authentication. I have managed to configure remote access for user nova
with sasl enabled (credentials stored in auth.conf -
https://review.openstack.org/#/c/12706/). It looks like live migration do
not use these credentials at all. What is more it thinks that sasl is not
not configured:
2013-07-01 09:49:09.317+0000: 17997: error :
virNetSASLSessionClientStart:484 : authentication failed: Failed to start
SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs
found)
2013-07-01 09:49:09.317+0000: 17997: error : doPeer2PeerMigrate:2527 :
operation failed: Failed to connect to remote libvirt URI
qemu+tcp://n12c1/system
I execute migration like this:
nova live-migration c923af69-4cb3-46dd-8bd2-871812d7d223 n12c1
Nova.conf:
live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE
Could you please let me know whether nova/libvirt support p2p live
migration with sasl and if so point out what might be misconfigured?
Disabling sasl solves all my problems but I have to configure some
authentication.
I would really appreciate your help.
regards
--
Maciej Gałkiewicz
Shelly Cloud Sp. z o. o., Sysadmin
http://shellycloud.com/, macias(a)shellycloud.com
KRS: 0000440358 REGON: 101504426
11 years
