similar to: Virtualbox vdi Input Format and man pages

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

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

08.10.2017, 08:09, "Richard W.M. Jones" <rjones@redhat.com>: > However virt-v2v has its own parser for libvirt XML and only parses a > (very) small subset of these fields. Generally you only need to take > that template and change a few fields, name, memory size, number of > vCPUs, and make sure there is one <disk> section per disk and one > <interface>

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

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

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

08.10.2017, 08:09, "Richard W.M. Jones" <rjones@redhat.com>: > > I guess we should probably link to the real documentation: > >   https://libvirt.org/formatdomain.html > > However virt-v2v has its own parser for libvirt XML and only parses a > (very) small subset of these fields. Generally you only need to take > that template and change a few fields, name,

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

running with -v -x I see this just above the failure: guestfsd: main_loop: new request, len 0x3c commandrvf: stdout=n stderr=y flags=0x0 commandrvf: mount -o ro /dev/sda /sysroot/ mount: wrong fs type, bad option, bad superblock on /dev/sda, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. guestfsd:

On Sun, Oct 08, 2017 at 07:03:50AM -0600, stef204 wrote: > >   http://libguestfs.org/virt-v2v.1.html#minimal-xml-for--i-libvirtxml-option > > > > Please bear with me but I really don't have enough info as to HOW to > modify the xml template., beyond the obvious stuff, MAC address, > name of VM, etc. > > Might there bit a more detailed xml template in context of

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

On Sun, Oct 08, 2017 at 08:47:34AM -0600, stef204 wrote: > > > 08.10.2017, 08:09, "Richard W.M. Jones" <rjones@redhat.com>: > > > > > I guess we should probably link to the real documentation: > > > >   https://libvirt.org/formatdomain.html > > > > However virt-v2v has its own parser for libvirt XML and only parses a > >

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'

Hi, attached is an updated [1] patch for virt-v2v to support converting VirtualBox guests with VirtualBox Guest Additions [2] installed. With the patch applied a VirtualBox RHEL 6 guest with Guest Additions can be converted with the steps documented in the manual page. I've tested this patch on a RHEL 6.2 host running VirtualBox 4.1.8 using a RHEL 6.2 guest, the guest works as expected

Hi, I''m trying to migrate a VirtualBox virtual machine to Xen, but I haven''t been able to successfully boot it under xen (3.0.1 that comes with CentOS 5.5). Thinking that the problem was converting the disk format to a raw format, I tried converting the VDI disk with all these options: VBoxManage internalcommands converttoraw disk.vdi disk.raw VBoxManage clonehd disk.vdi

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

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

Hello, I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on Fedora 19 64bit via virt-v2v. The command I'm currently using is: virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd xxx.xxx.xxx.xxx:/usr/local/ovirt/exports --network ovirtmgmt /usr1/home/williams/Downloads/OpenAthens/VMs/OpenAthensLARuntime2.2.xml The exciting bit of the XML is: <devices>

I have a KVM (qemu-img raw) that I have attempted to convert to VirtualBox. I did the convertfromraw to convert to vdi. I was hoping it would be that simple but, no. When I try to boot the image, it does not boot. Is there something "extra" I need to do - or something different? Thanks, Jerry

Matt, On Fri, 2013-11-15 at 14:05 +0000, Matthew Booth wrote: > On Fri, 2013-11-15 at 10:47 +0000, Owen Williams wrote: > > Hello, > > I've trying to move a 32bit CentOS 6.4 on VirtualBox to oVirt on > > Fedora 19 64bit via virt-v2v. The command I'm currently using is: > > > > virt-v2v -i libvirtxml -of qcow2 -oa sparse -o rhev -osd > >