similar to: Re: Question about mounting QCOW2 files....

On Mon, Oct 15, 2018 at 10:28:25AM -0400, Raghuram Devarakonda wrote: > On Mon, Oct 15, 2018 at 3:54 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > [Adding libguestfs mailing list] > > > > On Sun, Oct 14, 2018 at 11:53:17AM -0400, Raghuram Devarakonda wrote: > > > Hi, > > > > > > In our project, we deal with quite large sparse

On Mon, Oct 15, 2018 at 3:54 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > [Adding libguestfs mailing list] > > On Sun, Oct 14, 2018 at 11:53:17AM -0400, Raghuram Devarakonda wrote: > > Hi, > > > > In our project, we deal with quite large sparse files whose total size > > runs into several hundred terabytes or even more, though actual > >

2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > > > > I'm curious about which performance is better? > > They do quite different things, they're not comparable. > > Can you specifically give the

2017-07-28 0:31 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > On Fri, Jul 28, 2017 at 12:23:04AM +0800, lampahome wrote: > > 2017-07-27 20:18 GMT+08:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Thu, Jul 27, 2017 at 06:34:13PM +0800, lampahome wrote: > > > > I can mount qcow2 img to nbd devices through guestfish or qemu-nbd > >

Hi, I would like to mount a device using NBD protocol on CentOS 7 but it looks like the module is not available by default in the kernel. Is there a way I can install it (like from a rpm somewhere)? I found instructions to build such a module but want to make sure that it is not already available in some repo before I go ahead with building. Any help is greatly appreciated. Thanks, Raghu

Hi, List, I''m trying xl create a pv guest with qcow/qcow2 image, it always fails at libxl_device_disk_local_attach. #xl create pv_config_file libxl: error: libxl.c:1119:libxl_device_disk_local_attach: cannot locally attach a qdisk image if the format is not raw libxl: error: libxl_create.c:467:do_domain_create: failed to run bootloader: -3 disk configuration is: disk=[

Hi All, I am unable to figure out the issue here, when I try to create a filesystem (ext4) on a virtual disk using qemu-nbd. This happens intermittently. Following is the sequence of commands:- $> qemu-img create -f qcow2 test.qcow2 30G $> qemu-nbd --connect=/dev/nbd0 test.qcow2 $> *mkfs.ext4 /dev/nbd0* * mkfs.ext4: Device size reported to be zero. Invalid partition specified, or*

Add support for qcow2 disk format, enabled by imageio NBD backend in RHV 4.3. To use this feature manually, you can run virt-v2v with "-of qcow2". Here is example run: Source disk: $ qemu-img info /var/tmp/fedora-30.img image: /var/tmp/fedora-30.img file format: raw virtual size: 6 GiB (6442450944 bytes) disk size: 1.15 GiB virt-v2v: $ ./run virt-v2v \ -v \ -i disk

Occasionally this test will choose a random seed which results in an all-zeroes disk. The test tries to convert this to a compressed qcow2 file, and fails because no compressed clusters are detected in the resulting file. This happens because qcow2 stores zero clusters with a special sparse representation, they are never stored compressed, so a disk with only zeroes in it will never contain

On 8/8/23 00:28, Richard W.M. Jones wrote: > Occasionally this test will choose a random seed which results in an > all-zeroes disk. The test tries to convert this to a compressed qcow2 > file, and fails because no compressed clusters are detected in the > resulting file. This happens because qcow2 stores zero clusters with > a special sparse representation, they are never stored

I can mount qcow2 img to nbd devices through guestfish or qemu-nbd I'm curious about which performance is better?

hello, I would only like to have guestmount in my toolkit to read-only vhd/vhdx images, so I try to compile libguestfs with a minimum of dependencies. I downloaded the 1.38-stable sources, installed the necessary dependencies and compiled them with the command : ./configure --disable-ocaml --disable-perl --disable-ruby --disable-haskell --disable-php --disable-erlang --disable-lua

Hi all. I have a few questions regarding the qcow2 format. 1/ Allocated size vs. file size When creating a VM, I indicated a size of 10 G. $ls -lsh 7,7G -rw------- 1 libvirt-qemu libvirt-qemu 11G oct. 14 10:04 prod.qcow2 The allocated size is lesser than max size. Alright. I think I more or less grab the difference between allocated size and file size, but I'm not sure I get the point

Hi Eric, I wonder if you have any thoughts about this build failure in tests/test-nozero.sh? https://koji.fedoraproject.org/koji/taskinfo?taskID=48259627 log: https://kojipkgs.fedoraproject.org//work/tasks/9762/48259762/build.log The error is “nozero6.img was trimmed by mistake”. I added “set -x” to the script earlier today so we can see exactly what's wrong, and it is that: ++ stat

On Wed, Nov 21, 2018 at 09:25:05AM +0000, Richard W.M. Jones wrote: > nbdkit: file.2: error: invalid request: offset and count are out of range: offset=196608 count=512 Actually what happens even more precisely is that the underlying file is not a multiple of 512 bytes (196624 ≡ 16 mod 512). qemu-img (the client) issues a request for the final "sector" of the file which goes beyond

Hi all, When I live migrate a vm using "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system tcp://192.168.1.3" I got the following error WARNING: Image format was not specified for 'nbd://node2:49155/drive-virtio-disk0' and probing guessed raw. 258 Automatically detecting the format is dangerous for raw images, write operations on

Hi, So I've been hacking together an nbdkit plugin (similar to the "file" plugin, but it splits the file up into chunks): https://github.com/pepaslabs/nbdkit-chunks-plugin I got it to the point of being a working prototype. Then I threw it onto a raspberry pi, which it turns out only has a 50/50 shot of fallocate() working correctly. I'm checking the return code of

These are my thoughts on adding a test harness to run tests instead of using automake. The aim of this exercise is to allow us to run the full test suite on an installed copy of libguestfs. Another aim is to allow us to work around all the limitations and problems of automake. The first patch makes an observation that since the ./run script sets up $PATH to contain all the directories

Hello, I face a problem on the nbdkit server: Version-Release number of selected component (if applicable): nbdkit-v1.9.1 qemu-utils-2.12+dfsg-3+b1 How reproducible: 100% Steps: 1. Create a qcow2 file # qemu-img create disk 1G -f qcow2 2. Export the qcow2 file then try to read it via nbd url # nbdkit file file=disk -e raw -v nbdkit: debug: TLS disabled: could not load TLS certificates nbdkit:

When using oVirt >= 4.3, we can enable the NBD based backend in imageio by specifying that we transfer raw data when creating a transfer. With the NBD backend, we can specify qcow2 disk format. I think we need a way to expose the capabilities of the output to the user. For example, can we use qcow2 format. Issues: - I hacked qemu-img convert command line to always use -O raw instead of