similar to: question about backing file path of a qcow2 image

thanks . now i know qcow2 only store relative path. look at my error message, 6a3256bb-b247-4fb5-9f75-8ffa7151eeda i a symlink to a LV. it is the backing_file of several images(LV).. i have no idea of the reason of the error. # virt-win-reg 6a3256bb-b247-4fb5-9f75-8ffa7151eeda 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' 'Productname' hivex:

On Wed, Sep 11, 2013 at 10:33:06AM +0800, bigclouds wrote: > hi,all > images of qcow2 format with backing files, its backing files have > two path infos (absolute path and relative path), This is not true. The file format only contains the relative path. qemu-img info will print an absolute path, but it's not stored inside the file. > how to let > libguestfs use absolute path

hi,all i have a patch for netfilter, i want to talk with you, how to submit ? thanks

Hi， I used 'virsh snapshot-create' create an encrypted external snapshot, when I try to use 'qemu-img check' top file, found no entrance to pass backing-file's secret-id 1、Version centos-release-8.2-2.2004.0.1.el8.x86_64 libvirt.x86_64 6.0.0-17.el8 qemu-kvm.x86_64

On Mon, Dec 16, 2019 at 12:49:40 +0100, Jens John wrote: > Hello list, Hi Jens, > > upon upgrading from libvirt v5.9.0 -> v5.10.0, libvirt started calling > qemu differently causing the VM operating system to not be found. I'm > wondering whether I'm chasing a bug, or have to otherwise fix my domain > config (created by virt-manager). Yes, this change was done by

Hello list, upon upgrading from libvirt v5.9.0 -> v5.10.0, libvirt started calling qemu differently causing the VM operating system to not be found. I'm wondering whether I'm chasing a bug, or have to otherwise fix my domain config (created by virt-manager). To start with, I have a Windows 7 domain based on the following images: windows7-base.qcow2: QEMU QCOW2 Image (v3),

Hi, I'm experiencing weird things with the vbox driver when using multiple threads. Following is the snippet of code I experience problems with /*****************************************************/ #include <stdlib.h> #include <stdio.h> #include <pthread.h> #include <libvirt/libvirt.h> void *create_and_destroy(void *arg) { virDomainPtr dom = (virDomainPtr)arg;

Hello, I''m having some problems with hvm images and qcow2 under xen 3.4. The virtual machine won''t boot, and I ignore why. This is the template I''m using: ******** kernel = "/usr/lib/xen/boot/hvmloader" builder=''hvm'' name = "CentosMinimalkvm" memory = 1024 vcpus = 1 boot="c" on_poweroff = "destroy" on_reboot =

Hi, I want to know how the xen 4.1.2 source code read an qcow2/raw image that is used as a vdi.However I just know i should read some source code about the blktap and tapdisk.and don''t know where to begin. I need your help. hxk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Is there any benchmark or does anyone have tried which one is fastest? Regards, -- Thiago Vinhas de Moraes ________________________________________________________ SimpleWeb Tecnologia Inovativa Soluções em cloud computing e gerenciamento de TI Av. das Américas, 500 - Bloco 23 / Sala 215 - Rio de Janeiro - RJ Tel/Fax: 0800-8880-WEB / (21) 3002-0377 Celular: .(21)

The following two fixes by Jürgen Keil have been in qemu for a year now. They are still missing in ioemu. [Qemu-devel] PATCH: qcow2 image corruption http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00773.html [Qemu-devel] [PATCH] qcow2: release refcount table clusters of the old table, after growing the refcount table http://lists.gnu.org/archive/html/qemu-devel/2007-04/msg00043.html

I''m trying to create a pv guest with qcow/qcow2 disk image by xl, it always fails atlibxl_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 Does that mean we cannot create such a pv guest

hi?all, when I use Java library to create volume ,specified format "qcow2"?but when I check it use qemu-img info ,it show format is "raw".? I think it a bug,can you fix it .. thanks very much. the java library version?0.4.8 libvirt version?0.9.8 -------------- next part -------------- An HTML attachment was scrubbed... URL:

-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://et.redhat.com/~rjones/libguestfs/ See what it can do: http://et.redhat.com/~rjones/libguestfs/recipes.html -------------- next part -------------- >From 4d88a74532b20bcb60909c0d0983cdf7498aa08c Mon Sep 17

This question was asked on IRC: $ virt-builder centos-6 --output box.img --format qcow2 --size 40G # ... $ qemu-img convert -O qcow2 box.img box-qcow2.img $ ls -lAhs 1.6G -rw-r--r--. 1 james 41G Jan 2 21:53 box.img 1.1G -rw-r--r--. 1 james 1.1G Jan 3 18:54 box-qcow2.img $ file box* box.img: QEMU QCOW Image (v2), 42949672960 bytes box-qcow2.img: QEMU QCOW Image (v2),

Hi, I am having trouble configuring a virtual machine domain and its corresponding xml definition to use a qcow2 delta disk. The delta disk is backed by a qcow2 base disk. I am able to successfully start the guest OS with the delta disk at the command line using qemu. However, I am not able to start the guest OS using the libvirt tools including virsh and virt-manager. I am hoping that

Hello, I converted a W2003-Server to a vmdk-image, I didn't think too much back then ... Now I have 2 windows-drives C: and E: inside one vmdk-image-file, which was converted to qcow2. I have installed drivers and stuff into that VM already and would like to avoid to start over again with the vmdk-file -> Is there a way to split that one qcow2 into 2 separate files, one for each

Hello, I'm using libvirt to deploy a series of 7 KVM (in qcow2 format) sequentially. The base image of the qcow2 is an ubuntu server. The environment where i am doing this is a Live USB Ubuntu with a persistence file (so that changes made remain). So, my problem: * If the persistence file (i.e. free disk space in the live ubuntu) is up to around 1.5GB, the qemu process of launching the

Hello, I'm using libvirt to deploy a series of 7 KVM (in qcow2 format) sequentially. The base image of the qcow2 is an ubuntu server of around 1.6GB. The environment where i am doing this is a Live USB Ubuntu with a persistence file (so that changes made remain). So, the problem: * If the persistence file (i.e. free disk space in the live ubuntu) is up to around 1.6GB, the qemu process of

Good morning. I already tried: 1. http://michael.orlitzky.com/articles/resizing_a_kvm_or_qemu_disk_image.php Result: OS system can't see the disk space sudo qemu-img resize /var/lib/libvirt/images/mysql-1.qcow2 +8G ls -lath /var/lib/libvirt/images/mysql-1.qcow2 -rw------- 1 libvirt-qemu kvm 10G jun 1 15:35 /var/lib/libvirt/images/mysql-1.qcow2 # pvresize /dev/vda5