similar to: unable to execute QEMU command 'migrate': this feature or command is not currently supported

Valentin, Please check if the VM guest has vm-tools installed else the ?virsh migrate --live? parameter requirement is not fulfilled else you has to turn off the VM guest and do the offline ?virsh migrate? without ?--live? options. Hope that helps. Xlord From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Sandro Bonazzola Sent: Thursday, March 16, 2017 10:57 PM To:

Adding Paolo On Thu, Mar 16, 2017 at 1:50 PM, Valentin Guggiana <valentin at guggiana.ch> wrote: > Hi all > > I'm trying to do a live migration with non-shared storage on CentOS 7. It > was working > well doing it from CentOS 6 to CentOS 7 but not between to CentOS 7 > machines. I read > that this feature was removed in RHEL/CentOS 7 but should be available in >

Hi, Running on: $ cat /etc/redhat-release CentOS Linux release 7.3.1611 (Core) And: $ rpm -qa |grep libvirt libvirt-daemon-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-qemu-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-secret-2.0.0-10.el7_3.5.x86_64 libvirt-client-2.0.0-10.el7_3.5.x86_64 libvirt-daemon-driver-network-2.0.0-10.el7_3.5.x86_64

> On May 16, 2017, at 3:49 PM, Martin Kletzander <mkletzan@redhat.com> wrote: > > On Tue, May 16, 2017 at 06:41:05PM +0000, Innus, Martins wrote: >> Hi, >> >> Running on: >> >> $ cat /etc/redhat-release >> CentOS Linux release 7.3.1611 (Core) >> >> And: >> >> $ rpm -qa |grep libvirt >>

Hello! We tried to move Windows 2003 VM with e1000 driver from Centos 7 which runs qemu-kvm-0.12.1.2-2.491.el6_8.7.x86_64 to Centos 7 with qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 and we got problems- tcp sessions, namely smb connections, randomly drops. We didn't test previous qemu-rhev with this VM, so we don't know how it works in them. Could you tell me is this known problem? Any

Hi, just pushed to testing a new build of qemu-kvm-ev, here's the ChangeLog: * Thu Mar 2 2017 Sandro Bonazzola <sbonazzo at redhat.com> - ev-2.6.0-28.el7_3.6.1 - Removing RH branding from package name * Mon Feb 13 2017 Miroslav Rezanina <mrezanin at redhat.com> - rhev-2.6.0-28.el7_3.6 - kvm-cirrus-fix-patterncopy-checks.patch [bz#1420493] -

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory

Hum..if the live migration is not happening on a shared storage, then I think it is best to have offline migration copy to image and hook up to the destinated server instead, this is a short-cut path I suppose. Xlord -----Original Message----- From: CentOS-virt [mailto:centos-virt-bounces at centos.org] On Behalf Of Valentin Guggiana Sent: Monday, March 20, 2017 8:47 PM To: Discussion about the

hello, I am getting such error: libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp 00007f4930711740 error 4 in libvirt.so.0.2000.0[7f4940678000+353000] when I am trying to start VM with graphic spice/vnc console - in headless mode(without graphic console) it is running I noticed this after update oVirt 4.0 to oVirt 4.1 however I noticed that also libvirtd and related packages were upgraded

Sandro, Could you please enumerate the actual technical differences between stock qemu-kvm and qemu-kvm-ev? For example, what could one do with qemu-kvm-ev that cannot with qemu-kvm? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Sandro Bonazzola" <sbonazzo at redhat.com> > To: "Discussion about

Hello, All! virtio-win.iso contains two different Windows drivers. these Windows Server 2012 R2 drivers have different hardware IDs: \vioscsi\2k12R2\amd64\vioscsi.inf "Red Hat VirtIO SCSI pass-through controller" PCI\VEN_1AF4&DEV_1004&SUBSYS_00081AF4&REV_00 PCI\VEN_1AF4&DEV_1048&SUBSYS_11001AF4&REV_01 \viostor\2k12R2\amd64\viostor.inf "Red Hat VirtIO SCSI

Hi all, What are the real technical difference between qemu-kvm and qemu-kvm-ev packages? What are the advantages to use qemu-kvm-ev (if exists someone)? Or qemu-kvm-ev makes sense when is used with ovirt only?? Thanks.

Hi, qemu-kvm-ev-2.3.0-31.el7_2.10.1 has been tagged for testing. In order to test it, please enable centos-qemu-ev-test repository after installing centos-release-qemu-ev Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Wed, Oct 28, 2015 at 5:29 PM, Lamar Owen <lowen at pari.edu> wrote: > On 10/07/2015 07:07 PM, Karanbir Singh wrote: > >> hi, >> >> kvm-qemu-ev from virt7-kvm-common-release is now signed and available on >> buildlogs.centos.org for testing, the corresponding release file is >> available in the centos/7/extras/ location on buildlogs as well. >>

Note that qemu-kvm-ev is built within Virt SIG too in kvm-common-testing CBS repo On Wed, Jul 29, 2015 at 8:34 PM, Nux! <nux at li.nux.ro> wrote: > Yes, you can. In fact you can use the binaries from the ovirt repo itself, > no need to rebuild. > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message -----

2018-05-15 12:38 GMT+02:00 Gena Makhomed <gmm at csdoc.com>: > Hello, Sandro! > > On 15.05.2018 13:24, Gena Makhomed wrote: > > failure: repodata/repomd.xml from centos-qemu-ev: [Errno 256] No more >> mirrors to try. >> http://mirror.centos.org/altarch/7/virt/x86_64/kvm-common/ >> repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found >> > >

CentOS Errata and Bugfix Advisory 2017:0397 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-0397.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 458765621aa3f44cfe67ba67ff8410fe3a64b2433248a448970577daca0828dc libvirt-2.0.0-10.el7_3.5.x86_64.rpm

I see with the introduction of CentOS 7.5 there's a new qemu-kvm-ma package on ppc64le (which is actually newer than qemu-kvm-ev currently). Does anyone know what the difference is between these two packages? We currently use qemu-kvm-ev and we've run into this bug [1] which got me wondering if we should be switching to that package on ppc64le. Thanks! [1]

Hello, Sandro! On 11.05.2018 12:19, Sandro Bonazzola wrote: > Sadly, the new qemu-kvm-ev we prepared for CentOS 7.5 didn't get released ( > https://bugs.centos.org/view.php?id=14764) but the new build is ready. After installing CentOS 7.5 and installing package qemu-kvm-ev I can't install KVM on x86_64 arch: command "yum -y install perf qemu-kvm-ev qemu-kvm-tools-ev

The following transcript should provide all the necessary details: # yum install glibc-devel-2.17-157.el7.i686 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: mirrors.gigenet.com * epel: mirrors.xmission.com * extras: mirrors.gigenet.com * updates: ftp.osuosl.org Resolving Dependencies --> Running transaction check ---> Package