<p dir="ltr"><br>
On Dec 7, 2014 10:11 PM, Blaster <blaster@556nato.com> wrote:<br>
><br>
><br>
> On Sep 12, 2014, at 4:35 PM, Itamar Heim <iheim@redhat.com> wrote:<br>
><br>
>> On 09/12/2014 04:22 PM, Morten Stevens wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On 12.09.2014 14:22, Itamar Heim wrote:<br>
>>>><br>
>>>> With oVirt 3.5 nearing GA, time to ask for "what do you want to see in<br>
>>>> oVirt 3.6"?<br>
>>><br>
>>><br>
>>> An official supported way to import existing raw disk images would be nice.<br>
>><br>
>><br>
>> please review:<br>
>> http://www.ovirt.org/Features/virt-v2v_Integration<br>
><br>
><br>
> I don’t think that’s what we are looking for.  With this process, if I have an X size virtual disk, I have to come up with X+2X more storage to go through this silly import process. With ESXi, I just right click, add to inventory and I’m off.<br>
><br>
> Right now, I’m looking at moving my AIO configuration to a new host.  I’ll have to create the new AIO host, create a new storage domain on the old disks, create new VMs that look like the old ones, create new virtual disks, then go rummage around the storage, figure out what’s what in these user unfriendly UUID names, then move the old images onto the new ones.<br>
><br>
> With ESXi, I just reinstall the hypervisor, create the new VM, then right click, add to inventory on the old disk image, and I’m done.<br>
><br>
> https://bugzilla.redhat.com/show_bug.cgi?id=1049604<br>
><br>
> The concept of storage domains seems rather clumsy and limited to me.<br>
></p>
<p dir="ltr">If your existing raw images are from an ovirt storage domain you can keep it as is and import the entire storage domain or specific vms from it.<br>
That's a new 3.5 feature. Mind you yii must first upgrade the storage domain to 3.5 before reinstalling</p>