similar to: Xen hvm with qcow2

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root at test1 ]# virsh list Id Name State

I found guestfs_compress_out do the compression to gzip, bzip2, compress...etc. I want to compress qcow2, and I found details about qcow2 compression in https://people.gnome.org/~markmc/qcow-image-format.html The QCOW format supports compression by allowing each cluster to be > independently compressed with zlib. Can I do that with guestfs_compress_out?

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),

On 12/08/2014 03:03 PM, Laszlo Hornyak wrote: > Hi, > > I ran into a strange behavior with libvirt snapshots. I have some vms > running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora > 20). > * When I create a snapshot on the VM, the qcow file suddenly grows big, > somewhat bigger than the maximum size of the disk. The maximum (guest) size of a disk is

Il 30-01-2018 13:17 Gionatan Danti ha scritto: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file > is a qcow2 version 2 (compat=0.10) file. Example: > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol

Hi, I ran into a strange behavior with libvirt snapshots. I have some vms running with thin-provisioned qcow2 disk images (libvirt 1.1.3 with fedora 20). * When I create a snapshot on the VM, the qcow file suddenly grows big, somewhat bigger than the maximum size of the disk. * When I delete the snapshot, the allocated disk space is not freed up, the qcow image remains the same size. However, if

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

I want to add the following route command route add -net 192.168.2.0/27 gw 192.168.2.3 via the normal network setup. The result should be the following routing table (the first line): 192.168.2.0/27 via 192.168.2.3 dev xenbr1 scope link 192.168.2.0/27 dev eth2 proto kernel scope link src 192.168.2.4 192.168.2.0/27 dev xenbr1 proto kernel scope link src 192.168.2.3 192.168.1.0/24 dev xenbr0

I''ve got 2.0.7 running on a machine with 1 physical interface and two bridges, like so -- bridge name bridge id STP enabled interfaces xen-br0 8000.0040f4ce392f no eth1 vif5.0 vif9.0 xenbr1 8000.feffffffffff no

Hello techs, We used XL toolkit for Xen hypervisor for starting Windows hvm VMs and the option rtc_timeoffset worked perfectly with XL. It helped us to set correct Timezone time/offset for Windows HVM VMs from inside virtual_machine xen config. For example: Below option WORKS perfectly with XL toolkit. [root@hw12xen ~]# cat goillltawdlssq.xl.cfg | grep offset rtc_timeoffset = "7200"

On Wed, Nov 21, 2018 at 11:33:33AM +0800, Han Han wrote: > 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 This creates a 1GB virtual size qcow2 (real

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

I am not quite sure if this issue relates to iptables, routing or Xen virtual machines. Too many variables for my simple mind, so I'm asking some advice :) This is my network setup: Internet --- eth2 + CentOS dom0 / firewall / router + eth1 (xenbr1) --- LAN with private IPs --- separate file server and workstations + eth0 (xenbr0)

Hi all, on a fully patched CentOS 7.4 x86-64, I see the following behavior: - when creating a new volumes using vol-create-as, the resulting file is a qcow2 version 2 (compat=0.10) file. Example: [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 8589934592 --format=qcow2 --backing-vol /mnt/vmimages/centos6.img Vol zzz.qcow2 created [root@gdanti-lenovo vmimages]# file

Hi, we''re running 4 xen servers on our network with multiple network cards. During HighLoad we experince degeneration of inbound network traffic through our loadbalancer. I might found a reason for it, in Dom0 dmesg output looks as follows: [1157421.975910] eth0: received packet with own address as source address [1157421.975957] eth0: received packet with own address as source

Hey All I''m Using Xen 3.0.3-105 on CentOS 5.5. It Has to Nics: eth0 - Internet eth1 - Internal Lan ( where Dhcp , DNs , Cobbler - Kick Start Server Resides ) I''ve Set xend-config.xsp to create xenbr1 on eth1 and it looks well So Guest May Get Access TO ALl Resources via the Bridge. brctl show bridge name bridge id STP enabled interfaces xenbr1

Hello Everyone, I have set up a xen server with 10 physical network devices using the bridge mode of XEN. This is because I want to split and separate the network traffic for security reasons. Maybe the best way is to use pci back hide. But I want to understand what is going on here. For all testings I have only activated eth[0-3]. My first tests were successful. I have created a VM using

Hi Folks: I have a strange problem with multiple (2) NICs on a CentOS 5.5 dom0 setup running xen 3.4.3 and have been struggling to fix it for some time. I could not find anything by googling or searching through this list but that is probably because I couldn''t figure out the correct search terms. After I configure my bridges the command "system network restart" fails for eth1

I have a Xen DomU configuration that was made in the days before libvirt and virt-install. In this configuration I have: vif = [ ''mac=00:16:3e:05:06:01, bridge=xenbr0'', ''mac=00:16:3e:05:06:0a, bridge=xenbr1'' ] and then in xend-config.sxp I define (network-script my-network-bridge) where my-network-bridge is in the scripts directory and looks like this:

Hello, I am having a frustrating time trying to get bridge networking working. I''ve gone over the Wiki page on the topic, a few of the howtoforge pages and everything that I am doing is failing utterly. What I want to achieve is to have Dom0 be a stub running two DomUs. One DomU being a router/firewall and the other being the rest of what is on the current machine.