[ovirt-users] Re: What is this error message from?

Am 17.02.2020 um 16:16 hat Nir Soffer geschrieben: > On Mon, Feb 17, 2020, 16:53 wrote: > > > I have seen this error message repeatedly when reviewing events. > > > > VDSM vmh.cyber-range.lan command HSMGetAllTasksStatusesVDS failed: low > > level Image copy failed: ("Command

[ovirt-users] Re: max number of snapshot per vm

Am 25.11.2018 um 19:55 hat Nir Soffer geschrieben: > On Fri, Nov 23, 2018 at 1:01 PM Nathanaël Blanchet wrote: > > What are the best pratices about vm snapshots? > > > > I think the general guideline is keep only snapshot you need, since every > snapshot has a potential performance cost. > >

[ovirt-users] Re: [Qemu-block] Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 30.05.2018 um 18:14 hat Arik Hadas geschrieben: > On Wed, May 30, 2018 at 6:33 PM, Kevin Wolf wrote: > > I think the problem is that we're talking about two different things in > > one thread. If I understand correctly, what oVirt does today is: > > > > 1.

[ovirt-users] Re: [Qemu-block] Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 30.05.2018 um 17:05 hat Eric Blake geschrieben: > If I understood the question, we start with a local: > > T (any format) <- S (qcow2) <- V (qcow2) > > and want to create a remote tar file: > > dest.tar == | header ... | qcow2 image | > > where we write a single collapsed view of the

[ovirt-users] Re: [Qemu-block] Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 30.05.2018 um 15:44 hat Eric Blake geschrieben: > On 05/29/2018 04:18 PM, Nir Soffer wrote: > > > You CAN get a logically collapsed view of storage (that is, what the > > > guest would see), by using an NBD export of volume V. Reading from that > > > volume will then pull sectors from

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 29.05.2018 um 11:27 hat Richard W.M. Jones geschrieben: > On Mon, May 28, 2018 at 01:27:21PM +0300, Arik Hadas wrote: > > Let me demonstrate briefly the flow for OVA: > > Let's say that we have a VM that is based on a template and has one disk > > and one snapshot, so its volume-chain would be:

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 28.05.2018 um 16:06 hat Tomáš Golembiovský geschrieben: > > On Mon, 28 May 2018 13:37:59 +0200 > Kevin Wolf <kw...@redhat.com> wrote: > > > Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben: > > > On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf <kw...@redhat.c

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

Am 28.05.2018 um 12:27 hat Arik Hadas geschrieben: > On Mon, May 28, 2018 at 11:25 AM, Kevin Wolf <kw...@redhat.com> wrote: > > > [ Adding qemu-block ] > > > > Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben: > > > On Thu, May 24, 2018 at 6:13 PM

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

[ Adding qemu-block ] Am 27.05.2018 um 10:36 hat Arik Hadas geschrieben: > On Thu, May 24, 2018 at 6:13 PM, Nir Soffer wrote: > > > On Thu, May 24, 2018 at 6:06 PM Vrgotic, Marko > > wrote: > > > >> Dear Nir, > >> > >> Thank you for quick reply. >

Re: [ovirt-users] [Qemu-block] qcow2 images corruption

Am 07.02.2018 um 18:06 hat Nicolas Ecarnot geschrieben: > TL; DR : qcow2 images keep getting corrupted. Any workaround? Not without knowing the cause. The first thing to make sure is that the image isn't touched by a second process while QEMU is running a VM. The classic one is using 'qemu-img

Re: [ovirt-users] [Qemu-block] slow performance with export storage on glusterfs

Am 07.12.2017 um 23:45 hat Nir Soffer geschrieben: > The qemu bug https://bugzilla.redhat.com/713743 explains the issue: > qemu-img was writing disk images using writeback and fillingup the > cache buffers which are then flushed by the kernel preventing other > processes from accessing the

Re: [ovirt-users] [Qemu-block] Scheduling daily Snapshot

Am 07.12.2017 um 23:19 hat Nir Soffer geschrieben: > On Wed, Dec 6, 2017 at 6:02 PM Jason Lelievre > wrote: > > > Hello, > > > > What is the best way to set up a daily live snapshot for all VM, and have > > the possibility to recover, for example, a specific VM to a

Re: [ovirt-users] [Qemu-block] Enabling libgfapi disk access with oVirt 4.2

Am 15.11.2017 um 23:05 hat Nir Soffer geschrieben: > On Wed, Nov 15, 2017 at 8:58 AM Misak Khachatryan wrote: > > > Hi, > > > > will it be a more clean approach? I can't tolerate full stop of all > > VMs just to enable it, seems too disastrous for real production > >

Re: [ovirt-users] Performance of cloning

Am 28.09.2017 um 12:44 hat Nir Soffer geschrieben: > On Thu, Sep 28, 2017 at 12:03 PM Gianluca Cecchi > wrote: > > > Hello, > > I'm on 4.1.5 and I'm cloning a snapshot of a VM with 3 disks for a total > > of about 200Gb to copy > > The target I choose is on a different

Re: [ovirt-users] VM get stuck randomly

Hi Christophe, Am 30.03.2016 um 13:45 hat Christophe TREFOIS geschrieben: > Another host went down, so I have to prepare info for this one. > > I could not SSH to it anymore. > Console would show login screen, but no keystrokes were registered. > > I could “suspend” the VM and “run” it, but

Re: [ovirt-users] VM get stuck randomly

Am 27.03.2016 um 22:38 hat Christophe TREFOIS geschrieben: > Hi, > > MS does not like my previous email, so here it is again with a link to Dropbox > instead of as attached. > > —— > Hi Nir, > > Inside the core dump tarball is also the output of the two gdb commands you > mentioned. > >