similar to: Looking for feedback

On Tue, Jan 20, 2015 at 05:19:54PM +0200, Shahar Havivi wrote: > >From ff9261b201283f7bff16dc41721480e2e0a9f80f Mon Sep 17 00:00:00 2001 > From: Shahar Havivi <shaharh@redhat.com> > Date: Tue, 20 Jan 2015 14:41:23 +0200 > Subject: [PATCH] v2v: -o vdsm should assume data domain at -os path > > Unlike -o rhev which have only one data domin, -o vdsm can and usually >

Hi, I think that issue is due to the fact that my Guest is a transient domain. When shutting down it or migrating to another host , then virsh list --all doesn't show this Guest anymore. How may I make this Guest a persistent one ? ( i.e. this Guest has been created via RHEV-M GUI) Thx for hlep. Regards, J.P. -----Message d'origine----- De : libvirt-users-bounces@redhat.com

On Wednesday, 7 December 2016 10:02:49 CET Richard W.M. Jones wrote: > Support for RHEV with RHEL 6 nodes required us to output the old style > qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been > supported as a RHEV node type. Since RHV 4.1, compat=1.1 is > supported. (Support for compat=1.1 is uncertain in RHV 4.0 even on > RHEL 7 nodes.) > > There are

v3: Change the flag from --vdsm-compat-11 to --vdsm-compat=1.1 Also the --machine-readable output has changed. I have also added a test. Rich.

hi, i am getting this error below when i try to create a storage volume: ? ? libvirt.virStoragePool.CreateXML(storagepoolobject,xmldesc,0) AttributeError: class virStoragePool has no attribute 'CreateXML' my code is: xmldesc="xml description of storage volume which i got from sudo virsh vol-dumpxml" #get a storage pool object to use in creating a volume

On 20.01.15 14:48, Richard W.M. Jones wrote: > On Tue, Jan 20, 2015 at 04:25:20PM +0200, Shahar Havivi wrote: > > > > + let pos = (String.length os) - 36 in > > > > + let mp = String.sub os 0 (pos-1) in > > > > + let uuid = String.sub os pos 36 in > > > > > > What is the significance of 36 here? > > the length of uuid. >

v2: - Fix virt-p2v messages too. Rich.

On Tue, Feb 14, 2012 at 10:59:22AM -0500, Igor Lvovsky wrote: > > Hi, > I want to discuss $subject on the email just to be sure that we all on the > same page. > > So, today in 3.0 vdsm has two ways to create VM with cdrom : > 1. If RHEV-M ask to create VM with cdrom, vdsm just create it > 2. RHEV-M doesn't ask to create VM with cdrom, vdsm still creates VM with

On 11/21/2013 05:56 PM, Richard W.M. Jones wrote: > [Adding Itamar: Any suggestions on where Vitaly could get help on this > RHEV-M API problem?] > > On Thu, Nov 21, 2013 at 02:27:08PM +0000, Исаев Виталий Анатольевич wrote: >> Dear libguestfs developers, >> >> We are developing the protected enterprise system based on several >> Red Hat technologies (Red Hat

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

Support for RHEV with RHEL 6 nodes required us to output the old style qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been supported as a RHEV node type. Since RHV 4.1, compat=1.1 is supported. Support for compat=1.1 is uncertain in RHV 4.0 even on RHEL 7 nodes. There are significant downsides to using qcow2 compat=0.10 instead of the modern default (compat=1.1). Therefore this

Hi everybody, like in the subject: is there a way for telling libvirt to auto define an xml under /etc/libvirt/qemu? I mean, sometimes it happens to have the /etc/libvirt/qemu shared between nodes, say with a NFS share, since I can set a new xml on a node and I want o see the virtual machine on all the others, is there a way to automate this or am I obligated to launch virsh define <xml> on

On Wed, Oct 08, 2014 at 08:11:16AM +0000, VONDRA Alain wrote: > Hi, > I meet an amazing issue, when I convert a raw file to the oVirt environment using virt-v2v. > All seems to work fine, my VM is composed of 9 disks, the processes > finishes without any trouble, the files are well present in the > right import volume, but only the first system disk appear un my > oVirt Import

On Sun, Aug 6, 2017 at 4:42 AM, Jim Kusznir <jim at palousetech.com> wrote: > Well, after a very stressful weekend, I think I have things largely > working. Turns out that most of the above issues were caused by the linux > permissions of the exports for all three volumes (they had been reset to > 600; setting them to 774 or 770 fixed many of the issues). Of course, I >

----- Original Message ----- > From: "Richard W.M. Jones" <rjones@redhat.com> > To: "Исаев Виталий Анатольевич" <isaev@fintech.ru> > Cc: libguestfs@redhat.com > Sent: Tuesday, January 14, 2014 6:42:23 PM > Subject: Re: [Libguestfs] Libguestfs can't launch with one of the disk images in the RHEV cluster > > On Tue, Jan 14, 2014 at 02:57:35PM

Dear libguestfs developers, We are developing the protected enterprise system based on several Red Hat technologies (Red Hat Enterprise Virtualisation, the IdM server and so on). Our current goal is to prevent the booting of the virtual machine in case of integrity loss. So what we are trying to do Is to intercept the event of the VM's start (using the RHEV Manager hook scripts), mount the

On Tue, Oct 13, 2020 at 8:40 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > On Tue, Oct 13, 2020 at 07:56:29PM +0300, Nir Soffer wrote: > > On Tue, Oct 13, 2020 at 7:15 PM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > > > On Tue, Oct 13, 2020 at 06:45:42PM +0300, Nir Soffer wrote: > > > > I think this is the right solution - when

Hi, the following packages from oVirt 3.5.4 RC1 have been pushed to testing repositories: - qemu-kvm-ev-2.1.2-23.el7_1.4.1 - vdsm-4.16.21-1.el7 You're welcome to test them[1] and provide feedback. [1] http://wiki.centos.org/HowTos/oVirt Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

The first two patches implement the change discussed here: https://www.redhat.com/archives/libguestfs/2016-April/msg00178.html The third patch fixes the mapping of inspection data to OVF VmType which was inherited directly from old virt-v2v and had never been changed. It had a number of problems. The fourth patch is only slightly related to the others. It adds an extra slow test to ensure that