similar to: libguestfs support snapshot based virutal disk analysis?

I've used QEMU to read .vmdk snapshots. The VM directory layout in my case (Fusion, and I've seen Workstation do the same) created a .vmdk file per snapshot, and qemu-img could use that .vmdk file and the base .vmdk to convert the disk image to a raw image. IIRC there is a manifest file that ties .vmdk files to the snapshot they represent. So, from my experience, qemu does read disk

On Sun, Jun 09, 2013 at 03:40:42PM +0800, 雨居轩 wrote: > Hi dear all: > I have browsed almost all architecture of libGuestFs and use it on Fedora 18. It really seems greate! > However, > 1. No virtual disk (*.vdi, *.vmdk...) based snashot analysis code > Current LibGuestFs could recognize and virtual disk format > (e.g. *.VDI) and the file syste inside it (e.g. NTFS ), but

I''ve just pushed vdiskadm import/export/convert to the 3.3 vdisk and vbox repos. You can now import a disk image from a block device or file to a vdisk, convert (in place) to a different type of vdisk and export from a vdisk to a block device or file. I''ve also pushed the full vhd support (sparse and fixed) and the ability to import a vmdk 1.1 optimized stream file. An

I''ve just pushed vdiskadm translate to the 3.3 vdisk repo. You can now translate data from one virtual disk data type to another without creating a virtual disk. This allows the user to use a vmdk file and directly translate the data into a zvol without having to import it first to a vdisk and then export it to the zvol. # vdiskadm help translate translate - translate virtual disk data

Hello libvirt experts, I use libvirt (0.7.5-5ubuntu27.7) with KVM / qemu (0.12.3+noroms-0ubuntu9.2). Some machines use raw images but same use Virtualbox images (.vdi). Since last Ubuntu 10.04 LTS update I can not start the vdi-images. The "driver name= type=" option was new. <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file'

So I've gotten excluding paths to work as a standalone command. When I paste this into a script however, it ignores the exclusions. Any advice? rsync -aXvr --times --links --exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'} /home/path/ user at nas:/NAS/HOME/destination/ Are there supposed to be some kind of brackets around this?

(Sorry, Rich, I managed to miss reply-all.) These VMDK files are difference files from a baseline VMDK file. I'm not familiar with ESX's storage, but the size indicators on these tell me they aren't raw. For a virtual disk that has 3.2GB of data in its current state, against 3.0GB of data in its baseline, the current state's .vmdk file is 200MB. --Alex On Mon, Jun 10, 2013 at

Hi, I would like to backup my Virtual Box VM folder. I have VDI and VMDK files in there. I am told I have to shutdown those virtual machines first in order for rsync to copy them correctly. Is this correct ? Thanks, Dan

Hi, I'm using virsh to instance a VM in my environment, but I'm running on some issues. I created the following domain file: <domain type='kvm'> <name>demovm</name> <uuid>4a9b3f53-fa2a-47f3-a757-dd87720d9d1d</uuid> <memory unit='KiB'>4194304</memory> <currentMemory

Hi all, I have a Sun x2200 named Adra running OpenSolaris 2008.11 set up as a Dom0 per Levon''s instructions on this site. It hosts some production services and has been running nice and stable for a number of months now (with NetWare DomUs running GroupWise, believe it or not). The machine is pretty nicely speced out and there''s room for more virtualisation, so I was

If you use the libguestfs tools which open disk images read-only (eg. virt-df), with formats such as 'vdi', then you will see an error: error: invalid value for backingformat parameter 'vdi' This is because opening a disk image read-only will try to create a qcow2 file with the original image as a backing file. However the list of permitted backing formats was very restrictive

Just a quick fyi... We''ve recently added support for blktap along with support for managing virtual disks (disk file images). There are some difference from a linux dom0. This is available in b101 @ http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ This allows you to create and manage vmdk and vdi (Virtual Box) disk files. By default, virt-install will now use a vmdk vdisk when

On Sun, Jun 09, 2013 at 05:49:44PM -0400, Alexander Nelson wrote: > I've used QEMU to read .vmdk snapshots. The VM directory layout in my case > (Fusion, and I've seen Workstation do the same) created a .vmdk file per > snapshot, and qemu-img could use that .vmdk file and the base .vmdk to > convert the disk image to a raw image. IIRC there is a manifest file that > ties

If i will use a virtualbox image with xen Must ionly convert it to raw and copy the hole image to a lvm or harddisk Or are it more advanced? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

During some discussions and handwaving, including discussions with some experts on the Xenserver/XCP storage architecture, we came up with what we think might be a plausible proposal for an architecture for communication between toolstack and driver domain, for storage at least. I offered to write it up. The abstract proposal is as I understand the consensus from our conversation. The concrete

Good afternoon, I was wondering if anyone has any in site as to how to import a VMware vmdk into xVM on OpenSolaris 2009.06 (xVM 3.1). I have a VMware VM created on VMware Server 2.0 and would like to move it over to this xVM server. I appreciate any advice anyone may have. Cheers, -Chris -- This message posted from opensolaris.org

Hello, I?m using ZFS to export some iscsi targets for the virtual box iscsi initiator. It works ok if I try to install the guest OS manually. However, I?d like to be able to import my already prepared guest os vdi images into the iscsi devices but I can?t figure out how to do it. Each time I tried, I cannot boot. It only works if I save the manually installed guest os and re-instate the same

Hi, I''ve been touring XCP and making my way around it for the last few days, and am having problems with some reasonably straightforward actions. I''ve poured a several hours into different ways of resolving the issue, but am coming up short. Here''s the main issue. The following command (plugging in a VBD to the dom0 VM), when, run, hangs for several minutes, and then

[stef204 sent me the full log since it contains sensitive information] The log says that virt-v2v cannot see anything at all on the 34.1 GB disk (as if the disk is blank). However I think the actual problem is that you've given the wrong disk type in the XML: <disk type='file' device='disk'> <driver name='qemu' type='raw'/>

The current test for .vdi files is incorrect. It tries to detect the string "<<< Sun xVM VirtualBox Disk Image >>>". However this string is just free text and .vdi files often contain different strings (ref: [1]). The correct test in this patch looks for the magic number at offset 0x40 in the file (ref: [2]). Example: Upstream 'file' without the patch on an