On Oct 24, 2011, at 4:46 PM, Eric Blake wrote: > On 10/24/2011 02:39 PM, sethuraman subbiah wrote: >> Hi, >> >> >> >> When i use "[root@hgcc11 ssubbiah]# virsh schedinfo rubis_ws --cap 50" , I dont see the cap value being set and I am able to see only cpu shares. > > schedinfo --cap is obsolete (it's xen-only). Rather, you want: > > virsh schedinfo domain > > to list the current settings, and > > virsh schedinfo domain --set vcpu_period $value --set vcpu_quota $value > > I haven't used it myself; I'm only going off the documentation provided by Wen Congyang, who oversaw the addition of the features. Sorry, I noticed it late about using a xen command here. I tried virsh schedinfo domain. I dont think I have the capability to set quota : [root@sbc11 ssubbiah]# virsh schedinfo rubis_ws Scheduler : posix cpu_shares : 1024 [root@sbc11 ssubbiah]# virsh schedinfo rubis_ws --set vcpu_quota=50 Scheduler : posix error: invalid scheduler option: vcpu_quota=50 I get the same error for "virsh schedinfo rubies_ws --set vcpu_quota 50" . I find that my version is 0.9.4. [root@sbc11 ssubbiah]# virsh --version 0.9.4 Should I do some modifications,enable options or add some patch to get the capability to set cap ? Thanks for all your help. > > -- > Eric Blake eblake@xxxxxxxxxx +1-801-349-2682 > Libvirt virtualization library http://libvirt.org
