similar to: Unable to boot from a vdi image

Hi, I am using libguestfs 1.12.0 and I am facing a problem with it . I am using guestfs python bindings to "launch" a vdi image file . It works fine except immediately after a VM is stopped(which uses the same vdi file) i.e in normal conditions launch command works but when a vm (which uses the same vdi file) is started - stopped , a call to "launch" command hangs the

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

Yeswanth, I'm looking at: https://bitbucket.org/swamiyeswanth/pyti/src/2b3a7401eccf/diskhandler.py from this thread: http://librelist.com/browser//pyti/2011/6/13/disk-handler/ (1) I don't think the code you posted will work unless you move line 23 ('launch') up to just after you've added the drive (after line 12). (2) You probably don't want to use 'add_drive'.

On Sat, Aug 19, 2017 at 08:38:31AM -0600, stef204 wrote: > Hi, > > I am new to v2v/libguestfs. > I need to convert a 30 GB virtual machine running Windows7 64 bit (a > guest on a Linux system) from Virtualbox vdi format to qcow2 (or > raw/img--another debate in itself) so I can use libvirt/qemu/kvm to > run it and completely migrate away from Virtualbox. > > The vdi

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'

08.10.2017, 13:50, "Richard W.M. Jones" <rjones@redhat.com>: > [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

Hi, I am new to v2v/libguestfs. I need to convert a 30 GB virtual machine running Windows7 64 bit (a guest on a Linux system) from Virtualbox vdi format to qcow2 (or raw/img--another debate in itself) so I can use libvirt/qemu/kvm to run it and completely migrate away from Virtualbox. The vdi machine is a mission critical production environment and I cannot afford to mess it up, etc. Will keep

Only able to get to this now, but need additional help, if at all possible. See comments inline below. Thanks. 19.08.2017, 10:36, "Richard W.M. Jones" <rjones@redhat.com>: > On Sat, Aug 19, 2017 at 08:38:31AM -0600, stef204 wrote: >>  Hi, >> >>  I am new to v2v/libguestfs. > >>  I need to convert a 30 GB virtual machine running Windows7 64 bit (a

On Sun, Oct 08, 2017 at 02:41:30PM -0600, stef204 wrote: > The question is: What am I getting extra by using the -i libvirtxml option as opposed to the more plain: > > % virt-v2v -i disk Win7-convert.vdi -of qcow2 -o local -os /mnt/partition2 Guests consist of the disk images, plus copious metadata. When you give just the disk image to virt-v2v (‘-i disk disk.img’), it has to make

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

Hi all, i am trying to create virtual box using libvirt , following is xml i tried to use following xml (followed example in libvirt site . http://libvirt.org/drvvbox.html) <domain type='vbox'> <name>vboxtest</name> <os> <type>hvm</type> <boot dev='hd'/> <boot dev='cdrom'/> </os>

I'm using virtualbox with one of the tests I have for centos 6.4. I realized after creating the disk, the default was too small. I added more disk space with: VBoxManage modifyhd /Users/user/VirtualBox\ VMs/centos\ 6.x/centos\ 6.x.vdi --resize 25000 I then used this site to help me resize the lvm:

running windows vista: downloaded virtual machine and virtual rails cannot get virtual rails to mount to virtual machine after downloading virtual rails i attempted to extract it so i could convert it to vdi file and this is the result virtual_rails_1.1(1).7z i followed the tutorial at http://www.virtualrails.org/node/3 to create a new virtual machine, but when I start the machine i get the

08.10.2017, 13:50, "Richard W.M. Jones" <rjones@redhat.com>: > [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

[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'/>

Anyone have any idea on this. I wanted to separate out my VirtualBox VDIs so that I could activate compression on the rest of the parent directory structure so I created a ZFS filesystem under my user directory. mv .VirtualBox .VirtualBox_orig zfs create /export/home/user/.VirtualBox zfs create /export/home/user/.VirtualBox/VDI zfs set compression=off /export/home/user/.VirtualBox/VDI zfs set

> Hi, > > Didier Spaier wrote: > > The issue is the inability of booting of a *physical* (not virtual) optical > > media, like for instance a DVD or a CD, using syslinux.efi. > > Actually firmware cannot find any UEFI specified booting starting points > in an ISO 9660 filesystem that was created with mkisofs -b and > -hard-disk-boot, but without a boot image

Hello everyone, I have a corrupt .vdi file from a virtualbox installation (XP host, Mint 11 guest) which I recently broke. I wanted to allocate more space to it, so I ran this command:VBoxManage.exe modifyhd /path/to/YOUR_HARD_DISK.vdi --resize 17179869184 It only took a second to actually complete, so I think a header somewhere is broken. I need to get access to some files I had on there using

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

I am unable to mount a vdi image with virt-df. I get this error in the libvirt log. 2012-06-24 02:37:22.484+0000: 2364: error : qemuMonitorIO:583 : internal error End of file from monitor I don't really know from this output what the problem is and some assistance would be appreciated. I'm attaching the output of the libguest test program. Brian