Re: How to stop QEMU punching holes in backing store

On Wed, Jun 19, 2024 at 2:18 PM Nir Soffer wrote: > On 19 Jun 2024, at 8:54, Justin wrote: > >I've run strace and I see calls to fallocate with these flags: >FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE > >I've tried passing these options: discard=off,detect-zeroes=off

Re: qemu-img convert: Compression can not be disabled when converting from .qcow2 to .raw

On Fri, Jun 21, 2024 at 5:48 PM Sven Ott wrote: > Hi, I want to mount a VM image to a loop device and give it some excess > space. > > To do so, I download a .qcow2 file, add some 0 bytes with truncate, and > then convert the image from QCOW2 to RAW format with qemu-img convert, > like so: > >

Re: How to stop QEMU punching holes in backing store

> On 19 Jun 2024, at 8:54, Justin wrote: > >>I've run strace and I see calls to fallocate with these flags: >>FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE >> >>I've tried passing these options: discard=off,detect-zeroes=off but >>this does not help. This is the full set of

Re: How to stop QEMU punching holes in backing store

On Wed, Jun 5, 2024 at 5:27 PM Justin wrote: > Hi. I'm using QEMU emulator version 5.2.0 on Linux. I am using > thick-provisioned RAW files as the VM backing store. I've found that > QEMU is punching holes in my RAW files (it's replacing some zero > blocks with holes), which means that the

Re: Export checkpoint/bitmap from image on qcow2

long backup (e.g full backup, or incremental backup with a lot of data) blocks usage of the vm during the backup. You can start/stop/migrate a vm while it is being backed up and the backup can run on another host in the cluster (if using shared storage). Nir > On 12/18/23 18:44, Nir Soffer

Re: Export checkpoint/bitmap from image on qcow2

On Thu, Nov 30, 2023 at 4:14 PM João Jandre Paraquetti wrote: > > Hi, all > > I recently started looking into how to create incremental backups using > Libvirt+Qemu. I have already found that, since Libvirt 7.6.0, we can use > the virDomainBackupBegin API to create incremental backups of live VMs

Re: Is it normal to get bigger qcow2 image after blockcopy?

On Fri, Nov 3, 2023 at 3:25 AM Fangge Jin wrote: > > > On Thu, Nov 2, 2023 at 5:13 PM Fangge Jin wrote: > >> Recently, I found that the disk size of qcow2 image get bigger(from 6.16G >> to 8G in my test) after blockcopy. ❓ ❓ >> > Sorry, it should be "from 6.16G to 6.64G in my test"here > >>

Re: how to improve qcow performance?

On Wed, Jul 21, 2021 at 3:20 PM Geraldo Netto wrote: > > Dear Nir/Friends, > > On Tue, 20 Jul 2021 at 11:34, Nir Soffer wrote: > > > > On Thu, Jul 15, 2021 at 2:33 PM Geraldo Netto > > wrote: > > > > > > Dear Friends, > > > > > &

Re: how to improve qcow performance?

On Thu, Jul 15, 2021 at 2:33 PM Geraldo Netto wrote: > > Dear Friends, > > I beg your pardon for such a newbie question > But I would like to better understand how to improve the qcow performance I guess you mean how to improve "qcow2" performance. If you use "qcow" format the best way is to

Re: how to change sector size using qemu-img

On Fri, Jun 25, 2021 at 7:40 PM Jiatong Shen wrote: > > Hello community, > > I have a disk with both logical and physical sector size being 4096. I have a > qcow2 image which is built from a virtual machine has legacy 512 bytes sector > size. > > when I do something like > > qemu-img convert -f

Re: resizing disk image in a raw file online possible ?

On Thu, Apr 15, 2021 at 7:13 PM Lentes, Bernd wrote: > > Hi, > > we have several qemu guests running on SLES 12 SP5 and pacemaker and a > two-node HA cluster. > The raw files for the disks for the guests reside on a OCFS2 Volume on a SAN. > We need to give more storage to a guest (several

Re: qemu-img measure

On Thu, Jul 23, 2020 at 7:55 PM Arik Hadas wrote: > > > > On Thu, Jul 23, 2020 at 7:31 PM Nir Soffer wrote: >> >> On Thu, Jul 23, 2020 at 6:12 PM Arik Hadas wrote: >> >> The best place for this question is qemu-discuss, and CC Kevin and Stefan >>

Re: qemu-img measure

On Thu, Jul 23, 2020 at 6:12 PM Arik Hadas wrote: The best place for this question is qemu-discuss, and CC Kevin and Stefan (author of qemu-img measure). > @Nir Soffer does the following make any sense to you: > > [root@lion01 8c98c94d-bc14-4e24-b89c-4d96c820056d]# qemu-img info &

Re: [ovirt-devel] [ARM64] Possiblity to support oVirt on ARM64

On Sun, Jul 19, 2020 at 5:04 PM Zhenyu Zheng wrote: > > Hi oVirt, > > We are currently trying to make oVirt work on ARM64 platform, since I'm quite > new to oVirt community, I'm wondering what is the current status about ARM64 > support in the oVirt upstream, as I saw the oVirt Wikipedia page

Re: [ovirt-users] [OT] Major and minor numbers assigned to /dev/vdx virtio devices

On Wed, Jul 1, 2020 at 5:55 PM Gianluca Cecchi wrote: > > Hello, > isn't there an official major/minor numbering scheme for virtio disks? > Sometimes I see 251 major or 252 or so... what is the udev assignment logic? > Reading here: >

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Mon, Jun 29, 2020 at 3:06 PM Kevin Wolf wrote: > > Am 26.06.2020 um 21:42 hat Nir Soffer geschrieben: > > On Tue, Jun 23, 2020 at 1:21 AM Nir Soffer wrote: > > > > > > I'm trying to export qcow2 images from ova format using qemu-nbd. > > > &

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Fri, Jun 26, 2020 at 11:34 PM Richard W.M. Jones wrote: > > On Fri, Jun 26, 2020 at 10:42:02PM +0300, Nir Soffer wrote: > > Can we have better support in qemu-img/qemu-nbd for accessing images > > in a tar file? > > > > Maybe something like: > > > >

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Tue, Jun 23, 2020 at 1:21 AM Nir Soffer wrote: > > I'm trying to export qcow2 images from ova format using qemu-nbd. > > I create 2 compressed qcow2 images, with different data: > > $ qemu-img info disk1.qcow2 > image: disk1.qcow2 > file format: qcow2 > virtual siz

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Tue, Jun 23, 2020 at 1:47 PM Richard W.M. Jones wrote: > > On Tue, Jun 23, 2020 at 01:14:43PM +0300, Nir Soffer wrote: > > On Tue, Jun 23, 2020 at 12:47 PM Richard W.M. Jones > > wrote: > > > Here you go: > > > > > >

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Tue, Jun 23, 2020 at 5:08 PM Richard W.M. Jones wrote: > > On Tue, Jun 23, 2020 at 08:47:52AM -0500, Eric Blake wrote: > > On 6/22/20 5:21 PM, Nir Soffer wrote: > > >And it works, but it exposes the qcow2 data. I want to raw data so I > > >can upload the guest &g

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

On Tue, Jun 23, 2020 at 12:47 PM Richard W.M. Jones wrote: > > > Here you go: > > https://github.com/libguestfs/nbdkit/commit/2d15e79f65764d9b0c68bea28ed6afbcbcc63467 Nice! But using qemu-nbd directly is much simpler and will perform better. Regardless, nbdit tar plugin is awesome. Is it

Re: Exporting qcow2 images as raw data from ova file with qemu-nbd

> On 2020-06-23 00:21, Nir Soffer wrote: > > I'm trying to export qcow2 images from ova format using qemu-nbd. > > > > I create 2 compressed qcow2 images, with different data: > > > > $ qemu-img info disk1.qcow2 > > image: disk1.qcow2 > > file format: q

Exporting qcow2 images as raw data from ova file with qemu-nbd

I'm trying to export qcow2 images from ova format using qemu-nbd. I create 2 compressed qcow2 images, with different data: $ qemu-img info disk1.qcow2 image: disk1.qcow2 file format: qcow2 virtual size: 200 MiB (209715200 bytes) disk size: 384 KiB ... $ qemu-img info disk2.qcow2 image:

Re: QEMU-img convert question

On Tue, Dec 3, 2019 at 7:27 PM Reuven Alvesson wrote: > > Hi. > > I can not create a VM in proxmox...I get all the time this message when > trying to create a Hard drive: > > > lvcreate 'pve/vm-100-disk-0' error: Aborting. Could not deactivate thin pool > pve/data. at

Re: [ovirt-users] Possible sources of cpu steal and countermeasures

On Wed, Dec 4, 2019 at 6:15 PM wrote: > > Hi, > > I'm having performance issues with a ovirt installation. It is showing > high steal (5-10%) for a cpu intensive VM. The hypervisor however has > more than 65% of his resources idle while the steal is seen inside of > the VM. > > Even when placing

Re: qemu-system-x86_64: -accel kvm:tcg: Don't use ':' with -accel, use -M accel=... for now instead

own set of suboptions, but that isn't implemented > yet. Anyway there's no plan to drop "-M accel=kvm:tcg", it will continue to > work and will be transparently converted to "-accel kvm -accel tcg". Makes sense, thanks! > > Thanks, > > Paolo > > Il lun 25

Re: qemu-system-x86_64: -accel kvm:tcg: Don't use ':' with -accel, use -M accel=... for now instead

On Mon, Nov 25, 2019 at 9:54 PM Nir Soffer wrote: > > We have automated tests running qemu like this: > > 19:22:55 DEBUG (MainThread) [qemu] Starting qemu ['qemu-kvm', > '-accel', 'kvm:tcg', '-drive', > 'file=/var/tmp/ovirt-imageio-common/test_full_backup_raw_tcp_0/d

qemu-system-x86_64: -accel kvm:tcg: Don't use ':' with -accel, use -M accel=... for now instead

We have automated tests running qemu like this: 19:22:55 DEBUG (MainThread) [qemu] Starting qemu ['qemu-kvm', '-accel', 'kvm:tcg', '-drive', 'file=/var/tmp/ovirt-imageio-common/test_full_backup_raw_tcp_0/disk.raw,format=raw', '-nographic', '-qmp',

Re: [Qemu-discuss] [ovirt-users] VM snapshot - some info needed

On Wed, Jul 3, 2019 at 8:11 PM Strahil Nikolov wrote: > I have noticed that if I want a VM snapshot with memory - I get a warning "The > VM will be paused while saving the memory" . > Is there a way to make snapshot without pausing the VM for the whole > duration ? > No, this is expected.

Re: [Qemu-discuss] [ovirt-devel] Query regarding copying and executing files inside guest OS

On Thu, Feb 21, 2019 at 2:42 PM Pravin Amin wrote: > Hi, > > > > We are looking for a way to copy files and execute scripts inside Virtual > Machines hosted on oVirt manager (Any supported guest OS) either through > REST API or using Guest Tools. Please let me know how we can achieve it. > I'm

Re: [Qemu-discuss] [ovirt-users] VirtIO in new upgraded 4.2.5 for FreeBSD is very poor (could not use)

On Sun, Aug 5, 2018 at 1:40 PM Paul.LKW wrote: > Dear All: > I just upgraded my oVIrt-4.2.4 to 4.2.5 and nightmare begin, FreeBSD VMs > hangs once the VM's VirtIO harddisk is some loading (eg. extracting a > big tar ball, portsnap extract, etc.), I tried to create a VMs using > back the IDE do

Re: [Qemu-discuss] [kubevirt-dev] Re: Converting qcow2 image on the fly to raw format

On Thu, Jul 19, 2018 at 10:24 PM Richard W.M. Jones wrote: > On Thu, Jul 19, 2018 at 09:50:00PM +0300, Nir Soffer wrote: > > On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé > > > wrote: > > ... > > > > > Recommendation is to run 'qemu-img inf

Re: [Qemu-discuss] [kubevirt-dev] Re: Converting qcow2 image on the fly to raw format

On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé wrote: ... > Recommendation is to run 'qemu-img info' to extract the metadata and sanity > check results eg no backing file list, not unreasonable size, etc. When > running 'qemu-img info' apply process limits of 30 secs CPU time, and 1 GB >

Re: [Qemu-discuss] [kubevirt-dev] Re: Converting qcow2 image on the fly to raw format

On Mon, Jul 16, 2018 at 11:56 AM Daniel P. Berrangé wrote: > On Wed, Jul 11, 2018 at 02:17:18PM +0300, Adam Litke wrote: > > Adding some kubevirt developers to the thread. Thanks guys for the > > information! I think this could work perfectly for on the fly conversion > > of qcow2 images to

Re: [Qemu-discuss] Converting qcow2 image on the fly to raw format

On Mon, Jul 9, 2018 at 8:06 PM Richard W.M. Jones wrote: > On Mon, Jul 09, 2018 at 07:02:50PM +0200, Kevin Wolf wrote: > > Am 09.07.2018 um 18:52 hat Richard W.M. Jones geschrieben: > > > On Mon, Jul 09, 2018 at 07:38:05PM +0300, Nir Soffer wrote: > > > > We are

[Qemu-discuss] Converting qcow2 image on the fly to raw format

We are discussing importing VM images to KubVirt. The goal is to be able to import an existing qcow2 disk, probably some appliance stored on http server, and and convert it to raw format for writing to storage. This can be also useful for for oVirt for importing OVA, since we like to pack disks

Re: [Qemu-discuss] [Qemu-devel] Supporting unsafe create when backing file is not accessible

On Wed, Jul 12, 2017 at 5:40 PM Eric Blake wrote: > On 07/12/2017 03:56 AM, Ala Hino wrote: > > Hi, > > > > We encountered a performance issue when creating a volume for a running > VM > > and we'd like to share the info with you. The root cause of the issue is > in > > our

Re: [Qemu-discuss] [Qemu-devel] Estimation of qcow2 image size converted from raw image

On Wed, Feb 15, 2017 at 5:20 PM, Daniel P. Berrange wrote: > On Wed, Feb 15, 2017 at 03:14:19PM +, Stefan Hajnoczi wrote: >> On Mon, Feb 13, 2017 at 05:46:19PM +0200, Maor Lipchuk wrote: >> > I was wondering if that is possible to provide a new API that >> > estimates the

Re: [Qemu-discuss] [Qemu-devel] Estimation of qcow2 image size converted from raw image

On Wed, Feb 15, 2017 at 5:14 PM, Stefan Hajnoczi wrote: > On Mon, Feb 13, 2017 at 05:46:19PM +0200, Maor Lipchuk wrote: >> I was wondering if that is possible to provide a new API that >> estimates the size of >> qcow2 image converted from a raw image. We could use this new

Re: [Qemu-discuss] Converting qcow2 image to raw thin lv

On Sat, Feb 11, 2017 at 12:23 AM, Nir Soffer <nir...@gmail.com> wrote: > Hi all, > > I'm trying to convert images (mostly qcow2) to raw format on thin lv, > hoping to write only the allocated blocks on the thin lv, but > it seems that qemu-img cannot write sparse imag

[Qemu-discuss] Converting qcow2 image to raw thin lv

Hi all, I'm trying to convert images (mostly qcow2) to raw format on thin lv, hoping to write only the allocated blocks on the thin lv, but it seems that qemu-img cannot write sparse image on a block device. Here is an example: Create a new thin lv: # lvcreate --name raw-test --virtualsize 20g