Bug 998279

rich - iiuc, these should first be converted by v2v?

It depends if the disk image files contain operating systems or
just data disks.

If operating systems, converting them in virt-v2v is essential.

For data disks, perhaps oVirt could provide an easier way to just
attach them to existing guests (performance wouldn't be great however).
For now you can run the following:
  qemu-img convert -O qcow2 data-disk.vdi data-disk.qcow2
Make sure you've got a very recent version of qemu-img, because older
versions are known to silently corrupt certain types of disk.

(In reply to Richard W.M. Jones from comment #2)
> It depends if the disk image files contain operating systems or
> just data disks.
> 
> If operating systems, converting them in virt-v2v is essential.
> 
> For data disks, perhaps oVirt could provide an easier way to just
> attach them to existing guests (performance wouldn't be great however).
> For now you can run the following:
>   qemu-img convert -O qcow2 data-disk.vdi data-disk.qcow2
> Make sure you've got a very recent version of qemu-img, because older
> versions are known to silently corrupt certain types of disk.

The default behaviour of VirtualBox is to use only 1 disk image for the OS (as well as the data).

http://libvirt.org/drvvbox.html says that VirtualBox is supported? 

So can open I the OS stored inside a .VDI disk image file using oVirt? 
(i.e. without converting using virt-v2v or qemu-img convert)

(In reply to quickbooks.office from comment #3)
> The default behaviour of VirtualBox is to use only 1 disk image for the OS
> (as well as the data).

You need to convert it using virt-v2v, *if* that is possible.  When
I originally read this bug report I thought it was about VMware.
I don't know if anyone has tried converting VirtualBox images or
if virt-v2v supports them.

Matt ^^ have you ever thought about converting VirtualBox images
with virt-v2v or guestconv?

> http://libvirt.org/drvvbox.html says that VirtualBox is supported? 

This link is for libvirt controlling a virtualbox hypervisor.  It's
got nothing to do with oVirt support for vdi disk images.

(In reply to Richard W.M. Jones from comment #4)
> (In reply to quickbooks.office from comment #3)
> > The default behaviour of VirtualBox is to use only 1 disk image for the OS
> > (as well as the data).
> 
> You need to convert it using virt-v2v, *if* that is possible.  When
> I originally read this bug report I thought it was about VMware.
> I don't know if anyone has tried converting VirtualBox images or
> if virt-v2v supports them.
> 
> Matt ^^ have you ever thought about converting VirtualBox images
> with virt-v2v or guestconv?

The answer to this is that virt-v2v can remove virtualbox
agents, but it's unlikely that anyone has tested whether
it really works with virtualbox images end to end.

(In reply to Richard W.M. Jones from comment #5)
> (In reply to Richard W.M. Jones from comment #4)
> > (In reply to quickbooks.office from comment #3)
> > > The default behaviour of VirtualBox is to use only 1 disk image for the OS
> > > (as well as the data).
> > 
> > You need to convert it using virt-v2v, *if* that is possible.  When
> > I originally read this bug report I thought it was about VMware.
> > I don't know if anyone has tried converting VirtualBox images or
> > if virt-v2v supports them.
> > 
> > Matt ^^ have you ever thought about converting VirtualBox images
> > with virt-v2v or guestconv?
> 
> The answer to this is that virt-v2v can remove virtualbox
> agents, but it's unlikely that anyone has tested whether
> it really works with virtualbox images end to end.

Why would you need to run virt-v2v when you can just uninstall the VirtualBox Guest Additions after you load up the OS?

For example when I wanted to a virtualize a physical PC with Windows on it, I ran this tool: Disk2vhd v1.64 http://technet.microsoft.com/en-ca/sysinternals/ee656415.aspx

Then I opened the resulting VHD image file inside VirtualBox and uninstalled the graphics driver (Intel/Nvidia) using Add/Remove programs.

After that I installed VirtualBox Guest Additions to get 3D acceleration / full screen resize etc.

(In reply to Richard W.M. Jones from comment #2)
> For data disks, perhaps oVirt could provide an easier way to just
> attach them to existing guests (performance wouldn't be great however).

Well, how do you just attach a disk image (like .vdi, .vmdk, or .vhd) to an existing right now? Screenshots appreciated :)

setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.

I am able to open ViurtualBox .VDI disk image (which contains the OS) via virt-manager.

See Bug 952908:

(Martin Kletzander from comment #6)
> The problem is that virt-manager doesn't detect the VDI format properly. 
> This can be seen from the log output where the machine is being generated
> with:
> 
> <driver name='qemu' type='raw'/>
> 
> You can workaround this with clicking "Customize configuration before
> install" and select "VDI" as a format of the disk image.  The support for
> probing VDI files is not yet implemented, though.

IIUC this is about a non-system disk, just to be able to add/discover such a disk to a VM. I think you'd need to import it into the storage domain first. Moving to "storage" to consider

integration with v2v for whole VM import is a different matter

(In reply to Michal Skrivanek from comment #10)
> IIUC this is about a non-system disk, just to be able to add/discover such a
> disk to a VM. I think you'd need to import it into the storage domain first.
> Moving to "storage" to consider
> 
> integration with v2v for whole VM import is a different matter

Aren't we already integrating with v2v for 3.6.0?

my understanding is this is not about virt-v2v, as per comment #9 we should be able to use the .vdi directly.

Closing old bugs.
If needed please reopen and explain why.