Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1675721

Summary:	cannot import win 10 machine
Product:	[oVirt] ovirt-provider-ovn	Reporter:	Hetz Ben Hamo <hetz>
Component:	provider	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED DUPLICATE	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	1.0.4	CC:	bugs, danken, rbarry, royoung
Target Milestone:	ovirt-4.4.0	Flags:	rule-engine: ovirt-4.4+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-15 03:39:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Hetz Ben Hamo 2019-02-11 21:33:19 UTC

I'm using oVirt 4.3.0.

I'm trying to import Windows 10 machine from ESXi/vCenter to oVirt, and while it indicate it's initializing, it fails without showing why.

I'm enclosing engine log from the HE and vdsm from the node.

(I hope I selected correctly the component here in Bugzilla).

Comment 1 Hetz Ben Hamo 2019-02-11 22:50:56 UTC

Ok, I digged a bit deeper and according to the import log, it cannot import this machine because it's UEFI based, not BIOS based.

And I thought that oVirt 4.3.0 now supports UEFI, so why doesn't it imports UEFI? virt-v2v surely supports it (I tried to import to local libvirt, it works).

Comment 2 Ryan Barry 2019-02-11 23:45:32 UTC

Unfortunately, UEFI support is currently in a tech preview state, and it needs a little work before we can move v2v.

v2v support in RHV utilizes libguestfs, but there are some additions... We'll see if we can get this into a Z-stream if there's capacity once resolved

Comment 3 Ryan Barry 2019-05-15 03:39:57 UTC

Pending

*** This bug has been marked as a duplicate of bug 1693571 ***