Hi Nir -
in my case these VMs were migrated from VirtualBox to oVirt using some of
the VMWare provided tool
and then virt-v2v to convert images. Here's the example of the meta file -
DOMAIN=92be9db3-eab4-47ed-9ee9-87b8616b7c8c
VOLTYPE=LEAF
CTIME=1529005629
MTIME=1529005629
IMAGE=f0d0b3b3-5a31-4c9f-b551-90586bf946a5
DISKTYPE=1
PUUID=00000000-0000-0000-0000-000000000000
LEGALITY=LEGAL
POOL_UUID=
SIZE=41943040
FORMAT=RAW
TYPE=SPARSE
DESCRIPTION=generated by virt-v2v 1.36.10rhel_7,release_6.el7_5.2,libvirt
EOF
These disks worked fine on 4.2.3.8 but I wasn't able to import them into
4.3.4.3 unless I changed DISKTYPE line manually.
Fil
--
Dmitry Filonov
Linux Administrator
SBGrid Core | Harvard Medical School
250 Longwood Ave, SGM-114
Boston, MA 02115
On Tue, Jun 25, 2019 at 5:41 AM Nir Soffer <nsoffer(a)redhat.com> wrote:
On Mon, Jun 24, 2019 at 7:47 PM Dmitry Filonov <
filonov(a)hkl.hms.harvard.edu> wrote:
>
> Take a look at the corresponding .meta file for the disks you can not
> import.
> I had the very same problem and it was caused by
> DISKTYPE=1 in .meta.
>
I want more info on this. We think that the only value ever used for
DISKTYPE is 2.
Do you have any info on how these disks were created? Maybe by some
ancient version?
Nir
> When changed to
> DISKTYPE=DATA I was able to import disks correctly.
> Not the whole VM though..
>
>
> --
> Dmitry Filonov
> Linux Administrator
> SBGrid Core | Harvard Medical School
> 250 Longwood Ave, SGM-114
> Boston, MA 02115
>
>
> On Sun, Jun 23, 2019 at 4:29 AM m black <mblack0(a)yandex.ru> wrote:
>
>> Hi.
>>
>> I have a problem with importing some VMs after importing storage domain
>> in new datacenter.
>>
>> I have 5 servers with oVirt version 4.1.7, hosted-engine setup and
>> datacenter with iscsi, fc and nfs storages. Also i have 3 servers with
>> oVirt 4.3.4, hosted-engine and nfs storage.
>>
>> I've set iscsi and fc storages to maintenance and detached them
>> successfully on 4.1.7 datacenter.
>> Then i've imported these storage domains via Import Domain in 4.3.4
>> datacenter successfully.
>>
>> After storage domains were imported to new 4.3.4 datacenter i've tried
>> to import VMs from VM Import tab on storages.
>>
>> On the FC storage it was good, all VMs imported and started, all VMs in
>> place.
>>
>> And with iSCSI storage i've got problems:
>> On the iSCSI storage some VMs imported and started, but some of them
>> missing, some of missing VMs disks are showing at Disk Import, i've tried
>> to import disks from Disk Import tab and got error - 'Failed to register
>> disk'.
>> Tried to scan disks with 'Scan Disks' in storage domain, also tried
>> 'Update OVF' - no result.
>>
>> What caused this? What can i do to recover missing VMs? What logs to
>> examine?
>> Can it be storage domain disk corruption?
>>
>> Please, help.
>>
>> Thank you.
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>>
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MF5IUXURKIQ...
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BMXCPVIHKKQ...
>