search for: backingfil

In the guestfs_disk_create API we have traditionally allowed you to set backingfile without setting backingformat. The meaning of this is to let qemu autodetect the backing format when opening the overlay disk. However libvirt >= 6.0 refuses to even pass such disks to qemu (see https://bugzilla.redhat.com/show_bug.cgi?id=1798148). For this reason, move the autodetection ear...

On Mon, Mar 09, 2020 at 11:07:20AM +0100, Pino Toscano wrote: > On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > > In the guestfs_disk_create API we have traditionally allowed you to > > set backingfile without setting backingformat. The meaning of this is > > to let qemu autodetect the backing format when opening the overlay > > disk. > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > https://bugzilla.redhat.com/show_bug.cgi?id=1798...

...46 CET Richard W.M. Jones wrote: > > On Mon, Mar 09, 2020 at 11:07:20AM +0100, Pino Toscano wrote: > > > On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > > > > In the guestfs_disk_create API we have traditionally allowed you to > > > > set backingfile without setting backingformat. The meaning of this is > > > > to let qemu autodetect the backing format when opening the overlay > > > > disk. > > > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > > &gt...

On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > In the guestfs_disk_create API we have traditionally allowed you to > set backingfile without setting backingformat. The meaning of this is > to let qemu autodetect the backing format when opening the overlay > disk. > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > https://bugzilla.redhat.com/show_bug.cgi?id=1798148). > > For this...

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

...9 March 2020 11:40:46 CET Richard W.M. Jones wrote: > On Mon, Mar 09, 2020 at 11:07:20AM +0100, Pino Toscano wrote: > > On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > > > In the guestfs_disk_create API we have traditionally allowed you to > > > set backingfile without setting backingformat. The meaning of this is > > > to let qemu autodetect the backing format when opening the overlay > > > disk. > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (see > > > https://bugzilla.redhat...

Hi,guys, During a HVM''s running which take a qcow format image file as its own virtual disk, the qcow image file will be always read.In the situation that its qcow format image is based on a raw format image, if nesethe backingfile ,just that raw format image file,would be read .my purpose is to cache the data that is read from the backingfile when the hvm is running . Now what I concern is the following (which is in the /xen-4.1.2/tools/ioemu-qemu-xen/block-qcow.c) : static void qcow_aio_read_cb(void *opaque, int ret) { ......

...Jones wrote: > > > On Mon, Mar 09, 2020 at 11:07:20AM +0100, Pino Toscano wrote: > > > > On Thursday, 6 February 2020 18:20:19 CET Richard W.M. Jones wrote: > > > > > In the guestfs_disk_create API we have traditionally allowed you to > > > > > set backingfile without setting backingformat. The meaning of this is > > > > > to let qemu autodetect the backing format when opening the overlay > > > > > disk. > > > > > > > > > > However libvirt >= 6.0 refuses to even pass such disks to qemu (se...

...;rhev_disk_create" () in - (* For qcow2, override v2v-supplied compat option, because RHEL 6 - * nodes cannot handle qcow2 v3 (RHBZ#1145582). - *) - let compat = if format <> "qcow2" then compat else Some "0.10" in g#disk_create ?backingfile ?backingformat ?preallocation ?compat ?clustersize path format size; (* Make it sufficiently writable so that possibly root, or diff --git a/v2v/output_vdsm.ml b/v2v/output_vdsm.ml index 7cd94c0..92ce5c0 100644 --- a/v2v/output_vdsm.ml +++ b/v2v/output_vdsm.ml @@ -145,16 +145,6...

Libvirt >= 2.1.0 now allows you to open files which have a "json:" QEMU pseudo-URL as backingfile, whereas previously it would fail hard in this case (RHBZ#1134878). When virt-v2v performs conversions from Xen (over SSH) or vCenter (over HTTPS) it uses these pseudo-URLs as backingfiles. We had to tell people to use LIBGUESTFS_BACKEND=direct to avoid libvirt in this situation. This commit na...

..._builder_guest "$guestname" + +# Build a guest (using virt-builder). +virt-builder "$guestname" --quiet -o "$disk" + +# Test #1: relabel with the default configuration works. +rm -f "$disk_overlay" +guestfish -- disk-create "$disk_overlay" qcow2 -1 backingfile:"$disk" +virt-customize -a "$disk" --selinux-relabel + +# Test #2: relabel with no SELINUXTYPE in the configuration. +rm -f "$disk_overlay" +guestfish -- disk-create "$disk_overlay" qcow2 -1 backingfile:"$disk" +virt-customize -a "$disk"...

...ycle，and by virsh blockcommit merge snapshot chain，but when VM offline， the virsh blockcommit will fail， someone suggest me：when VM offline，may use qemu-img commit to submit snapshot turn，but qemu-img can't modify snapshot chain backing relation，it need we use qemu-img rebase amend snapshot‘s backingfile， the main question is when we use qemu-img rebase modify snapshot's backingfile, if someone start the VM, it will may lead to VM filesystem readonly。 we should how to solve the question? thanks! justlibvirt@gmail.com

...; "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 libguestfs: command: run: \ -o backing_file=rbd:images/Cen...

...for backingformat parameter ‘%s’"), backingformat); return -1; } } so this hunk can just be omitted. > @@ -321,7 +322,7 @@ disk_create_qcow2 (guestfs_h *g, const char *orig_filename, int64_t size, > CLEANUP_FREE char *p = guestfs_int_qemu_escape_param (g, backingfile); > guestfs_int_add_sprintf (g, &optionsv, "backing_file=%s", p); > } > - if (backingformat) > + if (backingformat && STRNEQ (backingformat, AUTODETECTION_FORMAT)) > guestfs_int_add_sprintf (g, &optionsv, "backing_fmt=%s", backingfo...

...s of the commands will be considered as guestfish +options if they start with a dash (C<->): you can always separate the +guestfish options and the rest of the commands (with their arguments) +using a double dash (C<-->). For example: + + guestfish -- disk_create overlay.qcow2 qcow2 -1 backingfile:image.img + =head1 USING launch (OR run) As with L<guestfs(3)>, you must first configure your guest by adding -- 2.14.3

...cycle，and by virsh blockcommit merge snapshot chain，but whenVM offline， the virsh blockcommit will fail， someone suggest me：when VM offline，may use qemu-img commit to submit snapshot turn，but qemu-img can't modify snapshot chain backing relation，it need we use qemu-img rebase amend snapshot‘s backingfile， the main question is when we use qemu-img rebase modify snapshot's backingfile, if someone start the VM, it will may lead to VM filesystem readonly。 we shoule solve the question? thanks!

...cycle，and by virsh blockcommit merge snapshot chain，but whenVM offline， the virsh blockcommit will fail， someone suggest me：when VM offline，may use qemu-img commit to submit snapshot turn，but qemu-img can't modify snapshot chain backing relation，it need we use qemu-img rebase amend snapshot‘s backingfile，* the main question* is when we use qemu-img rebase modify snapshot's backingfile, if someone start the VM, it will may lead to VM filesystem readonly。 we should how to solve the question? thanks!

...cycle，and by virsh blockcommit merge snapshot chain，but whenVM offline， the virsh blockcommit will fail， someone suggest me：when VM offline，may use qemu-img commit to submit snapshot turn，but qemu-img can't modify snapshot chain backing relation，it need we use qemu-img rebase amend snapshot‘s backingfile，* the main question* is when we use qemu-img rebase modify snapshot's backingfile, if someone start the VM, it will may lead to VM filesystem readonly。 we should how to solve the question? thanks!

...chain，but > when VM offline， the virsh blockcommit will fail， someone > suggest me：when VM offline，may use qemu-img commit to submit > snapshot turn，but qemu-img can't modify snapshot chain backing > relation，it need we use qemu-img rebase amend snapshot‘s > backingfile， As you note there's the 'qemu-img commit' primitive that allows you to commit the changes in an overlay back into its base image: If you have: base.qcow2 <-- overlay1.qcow2 <-- overlay2.qcow2 And, if you do: $ qemu-img commit overlay2.qcow2 It'll commit the conten...

Hi, all, I have a really big matrix that I want to run k-means on. I tried: >data <- read.big.memory('mydata.csv',type='double',backingfile='mydata.bin',descriptorfile='mydata.desc') I'm using doMC to register multicore. >library(doMC) >registerDoMC(cores=8) >ans<-bigkmeans(data,k) In system monitor, it seems only one thread running R. Is there anything I did wrong? Thanks in advance for any suggestion...