Re: can hotplug vcpus to running Windows 10 guest, but not unplug

On 2/14/20 11:17 AM, Gianluca Cecchi wrote: On Fri, Feb 14, 2020 at 4:54 PM Lentes, Bernd > wrote: qemu-kvm-2.11.2-5.18.1.x86_64 [...] I found a table on https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html/virt

RE: can hotplug vcpus to running Windows 10 guest, but not unplug

Thanks! Will compare it this weekend! -Original Message- Cc: libvirt-ML Subject: Re: can hotplug vcpus to running Windows 10 guest, but not unplug - On Feb 15, 2020, at 12:47 AM, Marc Roos m.r...@f1-outsourcing.eu wrote: > Would you mind sharing your xml? I have strange high h

Re: can hotplug vcpus to running Windows 10 guest, but not unplug

- On Feb 15, 2020, at 12:47 AM, Marc Roos m.r...@f1-outsourcing.eu wrote: > Would you mind sharing your xml? I have strange high host load on idle > windows guest/domain pathway 8235e5ae-0756-4286-5407-9fa02d372046 Pathway Studio Dietrich 16146944 4147456 4

RE: guest-fsfreeze-freeze freezes all mounted block devices

Hmmm, using 'virsh domfsinfo testdom' gives me a crash in win2008r2 (using software from virtio-win-0.1.171.iso) Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: qemu-ga.exe P2: 100.0.0.0 P3: 5c473543 P4: KERNELBASE.dll P5: 6.1.7601.24545 P6:

Re: guest-fsfreeze-freeze freezes all mounted block devices

On Mon, Feb 17, 2020 at 10:03:27 +0100, Marc Roos wrote: > Hi Peter, > > Should I assume that the virsh domfsfreeze, does not require the > qemu-agent service in the guest? No. That's the official way how to drive the "guest-fsfreeze-freeze" agent command via libvirt, thus you must have the gues

RE: guest-fsfreeze-freeze freezes all mounted block devices

Hi Peter, Should I assume that the virsh domfsfreeze, does not require the qemu-agent service in the guest? PS. I couldn't find the result. Afaik it looks like it is returning the amount of frozen/thawed filesystem's -Original Message- Cc: libvirt-users Subject: Re: guest-fsfreeze-fr