I also tried cpu hot plug for the following guest os: win7-x86_64/win8.1/win8.
The results are the same: The hot plugged cpus can only be found in Device
Manager, but they never appear in Task Manager, anyone please help to make some
comments? Thank you so much!
_
" ovirt (from 1*2*1 to 2*2*1) "
I mean change cpu count from 2(1*2*1) to 4(2*2*1)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of C
Hi there,
I am running ovirt engine 4.2.8.
I did cpu hotplug for windows 10 guest os, ovirt (from 1*2*1 to 2*2*1)
successfully, and the output of virsh vcpuinfo also shows now there are total 4
vcpus:
# virsh --readonly vcpuinfo 13
VCPU: 0
CPU:51
State: running
CP
Hi there,
I created a before_set_num_of_cpus hook:
# more /usr/libexec/vdsm/hooks/before_set_num_of_cpus/before.py
#!/usr/bin/python
import os
import sys
if os.environ.has_key('never_existed'):
sys.stderr.write('cantsetcpu: before_cpu_set: cannot set cpu.\n')
sys.exit(2)
else:
sys.stdo
Thank you, Paul !
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guideli
Hi Andrej,
Thank you for your quick response, as well as the RFE.
Thanks,
-Zhen
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Con
Hi there,
Here is my setup:
oVirt engine: 4.2.8
1. Create an affinity group as below:
VM affinity rule: positive + enforcing
Host affinity rule: disabled.
VMs: 2 VMs added
Hosts: No host selected.
2. Run the 2 VMs, they are running on the same host, say host1.
3. Change the affinity group's host
I designed test cases to cover the scenario that making snapshots for disks
including direct luns, if it is not a valid operation for oVirt, I can remove
these cases; If it is valid, I will add more cases, including VM export. Thanks.
> you don't need to remove, ovirt should exclude "unsnappable
Hi Benny,
Thank you so much for your quick response. Yes, oVirt indeed excludes direct
luns.
I have one more question, does oVirt support "Making snapshot without removing
direct lun disks", I mean, is this a valid operation for oVirt?
Thank you,
-Zhenchao
_
We know that now oVirt doesn't make snapshot for direct lun.
Please consider this scenario:
I have a VM with total 2 disks: the os image disk is created on the nfs domain,
while the other one is a direct lun disk.
Now I'd like to create a snapshot,
1. should I remove the direct lun disk first
Hi,
I'd like to try the memory hot unplug, refer to:
https://www.ovirt.org/documentation/vmm-guide/chap-Editing_Virtual_Machines.html:
"All blocks of the hot-plugged memory must be set to **online_movable** in the
virtual machine’s device management rules. In virtual machines running
up-to-
11 matches
Mail list logo