Displaying 4 results from an estimated 4 matches for "vcpu_quota".
2014 Mar 05
5
cgroup for VM - does it work properly?
Hi
I tried to restrict usage of some running VM by cpu.shares (i.e. set to
10 from original 1024) on loaded system and it seem doesn't work as I
expected... all running processes has same CPU usage (by htop) :-/
Does anyone has same experience?
Fedora 19, libvirt-1.0.5.9-1.fc19.x86_64
Thanks a lot
Martin
--
Martin Pavlásek <mpavlase@redhat.com>
OpenStack QA Associate/Red Hat
2017 Nov 02
2
What global_quota option mean? What's its logic?
...fo options mean? Thanks.
[root@cpkvm ~]# virsh list
Id Name State
----------------------------------------------------
3 kvmtestvm running
[root@cpkvm ~]# virsh schedinfo 3
Scheduler : posix
cpu_shares : 154
vcpu_period : 100000
vcpu_quota : -1
emulator_period: 100000
emulator_quota : -1
global_period : 100000
global_quota : -1
iothread_period: 100000
iothread_quota : -1
[root@cpkvm ~]# virsh schedinfo 3 --set global_quota=25
Scheduler : posix
error: invalid argument: value of 'global_quota' is out of ran...
2014 Nov 01
0
quick question on schedinfo
...Can anyone explain the scedinfo parameters? I am wondering if I can use
this, (along with host side niceness scheduler tweaks) to cause vCPUs to
dominate the total time of the CPUs they are pinned to.
Here are the sched info parameters:
Scheduler : posix
cpu_shares : 0
vcpu_period : 0
vcpu_quota : 0
emulator_period: 0
emulator_quota : 0
The documentation (
http://libvirt.org/sources/virshcmdref/html/sect-schedinfo.html) is not yet
filled for this.
If anyone can explain these parameters, or point me to relevant code it
would be helpful!
Thanks
Yasser
2014 Feb 08
1
Failed to terminate process X with SIGKILL: Device or resource busy
Hi,
I'm using libvirt/kvm with openstack. When vm has CPU stall, the instance
can't be destroyed. I have asked the question on openstack user mailing
list and received no answers in weeks.
Here is one example:
# virsh destroy instance-00000085
error: Failed to destroy domain instance-00000085
error: Failed to terminate process 61222 with SIGKILL: Device or
resource busy