similar to: qemu-guest-agent doesnt start

On 11/22/2013 12:02 AM, Исаев Виталий Анатольевич wrote: ... >> i may be missing something, but wouldn't vdsm hooks be a better fit: >> http://www.ovirt.org/VDSM-Hooks >> >> for example, I think the "checkimages" one would cover what you are >> trying to do already? > > Thank you, this hook was useful, but "gemu-img check" command is

Hi, I ran gemu-img on a VM thinking it was down but in fact it was live. I rebooted the VM and it does show the added space after running pv/lv etc to resize the disk, also the KVM server if you will, also shows the correct new size of that particular VMs raw file via du. However the virtual machine manager still shows the disk size of that VM as being before the resize. Is there a way that I

Hi, qemu-kvm-ev-2.9.0-16.el7_4.13.1 <https://cbs.centos.org/koji/buildinfo?buildID=21119> is now available for testing. I'm testing it right now in oVirt CI, if nothing shows up, I'll tag it for release in a few hours. Here's the changelog: * Thu Jan 04 2018 Sandro Bonazzola <sbonazzo at redhat.com> - ev-2.9.0-16.el7_4.13.1 - Removing RH branding from package name * Thu

CentOS Errata and Security Advisory 2018:0029 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:0029 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f1a6a43c10abfc52510f73c351cf175ee6489d55c7c9056cb39250a7a6789e9d libvirt-3.2.0-14.el7_4.7.x86_64.rpm

CentOS Errata and Security Advisory 2018:0260 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2018:0260 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a7ff6697cba768a37cfbf5b08cd4fea42887544e64fa81d652726fac42328c22 libgudev1-219-42.el7_4.7.i686.rpm

Hello, I have no queue configured on tap and veth devices, quest type is of course KVM and I’m using virtio model for VM’s NIC. What we found is that on Xenial (where performance is poor) during test ovs-vswitchd process is using 100% CPU and there are some messages in ovs logs: 2017-05-12T14:22:04.351Z|00125|poll_loop|INFO|wakeup due to [POLLIN] on fd 149

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Bugfix Advisory 2018:0165 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0165 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b88184d0561fe583defe5cd3583ccb40dd37d75dd537c34a30de928551d71e06 pacemaker-1.1.16-12.el7_4.7.x86_64.rpm

I am trying to make Qemu agent work with libvirt thanks to https://github.com/NixOS/nixops/pull/922 with libvirt 4.1.0. I've been trying to make it work for quite some time but I still haven't the slightest idea of what is wrong, I keep seeing "Guest agent is not responding: QEMU guest agent is not connected" as the program I use (nixops) calls the libvirt python API. I

CentOS Errata and Bugfix Advisory 2017:3305 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3305 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: cb59732fb41872863d49cde0a90a068404ebbe007048a3fece337a80ff642512 selinux-policy-3.13.1-166.el7_4.7.noarch.rpm

CentOS Errata and Bugfix Advisory 2018:0159 Upstream details at : https://access.redhat.com/errata/RHBA-2018:0159 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d03e7a330b75f15e7fa4c39da8416e42c24d42a7a9682781eca16877ba004ab5 kmod-20-15.el7_4.7.x86_64.rpm 3f81bf83cb7e26a84d6ef0627a7ad55d3fc891f8897bfb4c66b8e2ff5cf94ac8

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On 03/19/2018 11:46 AM, Dennis Jacobfeuerborn wrote: > Hi, > I'm trying to get some basic data from running guests on a libvirt HV > but one thing I'm missing is the name of the network interfaces of the > guests. I can get the MAC address from the XML but there seems to be no > function to actually get the name of the interface. > > The only function that comes close

On 5/12/20 1:41 PM, Dana Elfassy wrote: > if I understand correctly then I shouldn't have installed libvirt-daemon > on the guests VMs? > > Just a little background to Daniel's response. Libvirt and QEMU treat guests as black boxes, to some extent. There are some exceptions to this rule, when it comes to para-virtualization (that is when the guest knows it is running

Hi, I have a windows 10 guest with qemu-ga-x64.msi installed from the fedora virtio iso. qemu-ga version is 0.12.1 host qemu version is 2.1.0 (I know its older but in this version the active block commit works perfectly...) libvirt version 1.2.12 I have these lines in my xml: <channel type='unix'> <source mode='bind'

Thanks, Michal, On my laptop I do have libguestfs and libvirt-daemon-qemu. both libvirtd.service and libvirtd.socket are running ok on my laptop I just realized I haven't mentioned - my vms intend to serve as hosts themselves, and that's why they, too, need to have libvirtd.service running on them. up to recently I didn't have such a problem when I installed a vm on my laptop -

Dominique wrote: > -----Original Message----- > From: Dominique Ramaekers > [mailto:dominique.ramaekers@cometal.be] > Sent: Thursday, December 03, 2015 9:46 AM > To: Lentes, Bernd > Subject: RE: snapshot of running vm's > > > > > -----Oorspronkelijk bericht----- > > Van: Lentes, Bernd [mailto:bernd.lentes@helmholtz-muenchen.de] > > Verzonden:

Dominique wrote: > -----Original Message----- > From: Dominique Ramaekers > [mailto:dominique.ramaekers@cometal.be] > Sent: Thursday, December 03, 2015 9:46 AM > To: Lentes, Bernd > Subject: RE: snapshot of running vm's > > > > > -----Oorspronkelijk bericht----- > > Van: Lentes, Bernd [mailto:bernd.lentes@helmholtz-muenchen.de] > > Verzonden:

On 11/05/2014 10:50 AM, Thomas Stein wrote: > Am 04.11.14 17:55, schrieb Thomas Stein: >> Hello. >> >> Just a quick question. Is "setvcpus $windowsVM --guest 4" supposed to >> work? I have qemu-guest-agent (1.6.something) running inside a windows7 >> vm but all i get is: >> >> virsh # setvcpus windows7 --guest 4 >> error: invalid