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

2018-05-30 Thread Eric Blake
On 05/30/2018 09:16 AM, Kevin Wolf wrote: 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

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

2018-05-30 Thread Eric Blake
otocol (simplified to qcow2 format => NBD client protocol => (qcow2 bytes) => NBD server => raw format => file protocol) -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org __

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

2018-05-30 Thread Eric Blake
iting is a bit harder, but should work as long as you don't need resize and don't have any compressed sparse regions that need to be rewritten to non-sparse data) -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization

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

2018-05-29 Thread Eric Blake
#x27;: 'int' } } Yeah, it's a pity that "qemu-img create -o help -f raw" has forgotten to document them, the way "qemu-img create -o help -f qcow2" does for its options, so we should fix that. -- Eric Blake, Principal Software Engineer Red Hat, Inc.

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

2018-05-29 Thread Eric Blake
t the guest would see), by using an NBD export of volume V. Reading from that volume will then pull sectors from whichever portion of the chain you need. You can use either qemu-nbd (if no guest is writing to the chain), or within a running qemu, you can use nbd-server-start and nbd-serve

Re: [ovirt-users] [Qemu-block] import thin provisioned disks with image upload

2017-12-07 Thread Eric Blake
st filesystem didn't care about them) - but only insofar as you can preserve sparseness of the portions of the file that are holes in the source. You may also be interested in the virt-sparsify tool from libguestfs, which is very good at squeezing out unneeded space from an image in order to get a

Re: [Users] [libvirt] libvirt migration port configuration and virPortAllocator

2014-01-08 Thread Eric Blake
even on virt-preview > http://fedorapeople.org/groups/virt/virt-preview/fedora-19 (but it is on > http://fedorapeople.org/groups/virt/virt-preview/fedora-20 !) Again, virt-preview on F19 is dead. virt-preview on F20 tracks rawhide. And for the non-virt-preview packages, if you need p

Re: [Users] [libvirt] Starting VM Error

2013-09-18 Thread Eric Blake
On 09/15/2013 07:55 AM, Gianluca Cecchi wrote: > I'm using what stock f18 repo gives today: > [root@tekkaman ~]# rpm -q libvirt > libvirt-0.10.2.7-1.fc18.x86_64 Known bug: CVE-2013-4291. Downgrade to 0.10.2.6, or wait for 0.10.2.8 to be released. -- Eric Blake eblake redhat com

Re: [Users] [libvirt] VNC/Spice console connection failure

2013-09-18 Thread Eric Blake
On 09/11/2013 12:53 AM, Michal Skrivanek wrote: > > On Sep 11, 2013, at 00:11 , Eric Blake wrote: > >> On 09/10/2013 03:52 PM, Dan Kenigsberg wrote: >>> On Tue, Sep 10, 2013 at 05:31:23PM +, SULLIVAN, Chris (WGK) wrote: >>>> Hi Itamar, >>>&

Re: [Users] Online snapshot

2012-06-28 Thread Eric Blake
ing a different use of the API than what you did with your virsh command line. VDSM is attempting to do the equivalent of 'virsh snapshot-create --disk-only --reuse-ext', but because your qemu doesn't support the 'transaction' command, libvirt can't make qemu do wha