search for: overlay1

...her name that seems to be wrong based on the context. It doesn't have the same implication as my earlier example, as the name of the overlay file is not written in the command itself, but still: ------ $ virsh snapshot-create-as --domain vm1 guest-state1 \ --diskspec vda,file=/export/images/overlay1.qcow2 \ --disk-only --atomic Then: $ virsh domblklist vm1 Target Source ------------------------------------------------ vda /export/images/overlay.qcow2 Now that the backup is finished, perform active blockcommit by live mergning contents of 'overlay1' into base . . . .&qu...

...unt_bits=16 [root@singularity images]# qemu-img info base.qcow2 image: base.qcow2 file format: qcow2 virtual size: 8.0G (8589934592 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false # create overlay1.qcow2 via qemu-img; note how backing file format is autodetected ("-f qcow2" regards the overlay file itself) [root@singularity images]# qemu-img create -b /var/lib/libvirt/images/base.qcow2 overlay1.qcow2 -f qcow2 Formatting 'overlay1.qcow2', fmt=qcow2 size=8589934592 backing_...

...ot; "format:raw" "protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" libguestfs: creating COW overlay to protect original drive content libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: trace: disk_create "/tmp/libguestfs3pGMi6/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" "backingformat:raw" libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libgues...

...bguestfs: trace: add_drive >> "images/CentOS-7-x86_64-GenericCloud-1901" "readonly:true" >> "format:raw" "protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" > This is probably where it goes wrong: > >> "/tmp/libguestfs3pGMi6/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" >> "backingformat:raw" >> libguestfs: command: run: \ -o backing_file=rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[...

...protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" libguestfs: creating COW overlay to protect original drive content libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/root/libguestfs/tmp" libguestfs: trace: disk_create "/root/libguestfs/tmp/libguestfs9gclsg/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00\:\:cefc\:1]\:6789:auth_supported=none" "backingformat:raw" libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libgu...

...itional options (no-metadata and atomic). I want to use the generated XML to create a snapshot via a perl script, and Sys::Virt only seems to support snapshots using a XML description of the arguments. timos@cerberus:~$ sudo virsh snapshot-create-as --domain web guest- state1 --diskspec hda,file=overlay1.qcow2 --disk-only --atomic --no- metadata --print-xml <domainsnapshot> <name>guest-state1</name> <disks> <disk name='hda'> <source file='overlay1.qcow2'/> </disk> </disks> </domainsnapshot> timos@cerberus:~$...

...rive "/home/peterd/TVE/wer.qcow2" "readonly:true" "format:qcow2" libguestfs: creating COW overlay to protect original drive content libguestfs: trace: get_tmpdir libguestfs: trace: get_tmpdir = "/tmp" libguestfs: trace: disk_create "/tmp/libguestfsUIZbDK/overlay1.qcow2" "qcow2" -1 "backingfile:/home/peterd/TVE/wer.qcow2" "backingformat:qcow2" libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libguestfs: command: run: \ -o backing_file=/home/peterd/TVE/wer.qcow2,backi...

...gt; "images/CentOS-7-x86_64-GenericCloud-1901" "readonly:true" >>>> "format:raw" "protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" >>> This is probably where it goes wrong: >>> >>>> "/tmp/libguestfs3pGMi6/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" >>>> "backingformat:raw" >>>> libguestfs: command: run: \ -o backing_file=rbd:images/CentOS-7-x86_64-GenericCloud...

...fine to me: > libguestfs: trace: add_drive > "images/CentOS-7-x86_64-GenericCloud-1901" "readonly:true" > "format:raw" "protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" This is probably where it goes wrong: > "/tmp/libguestfs3pGMi6/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" > "backingformat:raw" > libguestfs: command: run: \ -o backing_file=rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::c...

On Wed, Jan 08, 2020 at 09:05:55PM +0800, 谢威 wrote: > &gt; libguestfs: trace: disk_create "/tmp/libguestfsHRQGUn/overlay1.qcow2" "qcow2" -1 "backingfile:/var/tmp/.guestfs-0/appliance.d/root" "backingformat:raw" > &gt; libguestfs: command: run: qemu-img > &gt; libguestfs: command: run: \ create > &gt; libguestfs: command: run: \ -f qcow2 > &gt; libguestfs:...

...k, is it just for external snapshots, or do > internal snapshots work? >From my quick test (for offline disks with `qemu-img`), it does seem to work: $ qemu-img create -f vmdk base.vmdk 1G $ qemu-img create -f qcow2 -o \ 'backing_file=./base.vmdk,backing_fmt=vmdk' ./overlay1.qcow2 $ qemu-img info overlay1.qcow2 image: overlay1.qcow2 file format: qcow2 virtual size: 1.0G (1073741824 bytes) disk size: 196K cluster_size: 65536 backing file: ./base.vmdk backing file format: vmdk Format specific information: compat: 1.1...

Does libvirt support snapshotting when the virtual disk comes from a vmdk file? http://wiki.libvirt.org/page/Snapshots#Desired_functionality seems to say no, since it says "'virsh snapshot', which requires all disk images to be qcow2". OTOH, man virsh, http://libvirt.org/formatsnapshot.html, and http://libvirt.org/formatdomain.html#elementsDisks seem to indicate more

...t strange is going on: > libguestfs: command: run: qemu-img > libguestfs: command: run: \ create > libguestfs: command: run: \ -f qcow2 > libguestfs: command: run: \ -o > backing_file=/home/peterd/TVE/wer.qcow2,backing_fmt=qcow2 > libguestfs: command: run: \ /tmp/libguestfsUIZbDK/overlay1.qcow2 > Formatting '/tmp/libguestfsUIZbDK/overlay1.qcow2', fmt=qcow2 > size=107374182400 backing_file=/home/peterd/TVE/wer.qcow2 backing_fmt=qcow2 > encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 > libguestfs: error: command: waitpid: No child processes &g...

...drive > >>"images/CentOS-7-x86_64-GenericCloud-1901" "readonly:true" > >>"format:raw" "protocol:rbd" "server:tcp:[fd00::cefc:1]:6789" > >This is probably where it goes wrong: > > > >>"/tmp/libguestfs3pGMi6/overlay1.qcow2" "qcow2" -1 "backingfile:rbd:images/CentOS-7-x86_64-GenericCloud-1901:mon_host=[fd00::cefc:1]\:6789:auth_supported=none" > >>"backingformat:raw" > >>libguestfs: command: run: \ -o backing_file=rbd:images/CentOS-7-x86_64-GenericCloud-1901:mo...

...other packages don't necessarily force a change to the relationship > metadata. Yeah, that part's all good. I look forward to your writeup though, because I think the problem space is a little different. Provides works as a synonym for Role, but how do you do Overlays? Content-ID: overlay1 Role: subtitle Overlays: video1 vs Content-ID: overlay1 Provides: subtitles Depends: video1 I guess it works to make depends a synonym for Overlays. I do like Suggests as a way to flag a default configuration. > In terms of skeleton, two tracks which provide the same thing (eg. > subtit...

...ml [**] NBD over TCP: (1) Run an NBD server locally: $ qemu-nbd -f qcow2 -p10809 \ /var/lib/libvirt/images/cirros-0.3.3-x86_64-disk.img -t (2) Create an overlay using the NBD server as backing file: $ qemu-img create -f qcow2 -F raw \ -o backing_file=nbd://localhost nbd-overlay1.qcow2 (3) Optionally, boot the overlay w/ a minimal CLI. $ qemu-system-x86_64 \ -nographic \ -nodefconfig \ -nodefaults \ -m 2048 \ -device virtio-scsi-pci,id=s...

On Wed, Mar 25, 2015 at 07:38:03PM +0100, Kashyap Chamarthy wrote: > On Mon, Mar 23, 2015 at 10:43:30PM +0000, Richard W.M. Jones wrote: > > [. . .] > > > > This makes a copy of the whole disk image. It's also not a consistent > > > (point in time) copy. > > > > Oh I see that you're copying the _snapshot_ that you created with > >

...-0/appliance.d.omlxj0zh/initrd' supermin: ext2: wrote 34 modules to minimal initrd supermin: renaming /var/tmp/.guestfs-0/appliance.d.omlxj0zh to /var/tmp/.guestfs-0/appliance.d libguestfs: [62773ms] finished building supermin appliance libguestfs: trace: disk_create "/tmp/libguestfsWmxUbv/overlay1" "qcow2" -1 "backingfile:/var/tmp/.guestfs-0/appliance.d/root" "backingformat:raw" libguestfs: command: run: qemu-img libguestfs: command: run: \ create libguestfs: command: run: \ -f qcow2 libguestfs: command: run: \ -o backing_file=/var/tmp/.guestfs-0/appliance....

...gt; libguestfs: command: run: qemu-img > > libguestfs: command: run: \ create > > libguestfs: command: run: \ -f qcow2 > > libguestfs: command: run: \ -o > > backing_file=/home/peterd/TVE/wer.qcow2,backing_fmt=qcow2 > > libguestfs: command: run: \ /tmp/libguestfsUIZbDK/overlay1.qcow2 > > Formatting '/tmp/libguestfsUIZbDK/overlay1.qcow2', fmt=qcow2 > > size=107374182400 backing_file=/home/peterd/TVE/wer.qcow2 > backing_fmt=qcow2 > > encryption=off cluster_size=65536 lazy_refcounts=off refcount_bits=16 > > libguestfs: error: command: waitp...