12:07 a.m.
Anyone ?
On Sun, 8 Dec 2019 at 2:00 AM, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com>
wrote:
What step I did was:
1. Used qemu-img to convert the vhdx to raw img
2. Created a blank disk and copied my converted disk to same location.
3. Renamed the converted drive with the name of blank disk.
4. Created a VM and attached my converted disk to VM.
Error: No bootable disk found
But when I attack this disk to another running VM, there I can see the
data. But noting booting as bootable.
Vijay Sachdeva
*From: *Vijay Sachdeva <vijay.sachdeva(a)indiqus.com>
*Date: *Sunday, 8 December 2019 at 1:48 AM
*To: *Strahil <hunter86_bg(a)yahoo.com>, users <users(a)ovirt.org>
*Subject: *Re: [ovirt-users] Hyper-V to KVM | v2v
One question, once disk is converted to KVM format.
What is the way to use that drive and run a VM from it within Ovirt
environment.
Vijay Sachdeva
*From: *Strahil <hunter86_bg(a)yahoo.com>
*Date: *Friday, 6 December 2019 at 8:57 PM
*To: *users <users(a)ovirt.org>, Vijay <vijay.sachdeva(a)indiqus.com>
*Subject: *Re: [ovirt-users] Hyper-V to KVM | v2v
Have you tried to power up and fully shutdown the VM ?
Best Regards,
Strahil Nikolov
On Dec 6, 2019 15:52, Vijay Sachdeva <vijay.sachdeva(a)indiqus.com> wrote:
Hello,
I am trying to convert a Hyper-V guest VM to run on KVM using virt-v2v
utility.
Getting below error:
[image: cid:image001.png@01D5AC6A.8B510030]
Any suggestions how to solve this.
Thanks
Vijay Sachdeva
1:16 a.m.
New subject: Hyper-V to KVM | v2v
Hi Vijay
Based on your initial post about using virt-v2v I don't know how
intelligent virt-v2v is in knowing and converting the VM machine type.
However the boot issue could be related to Hyper-V defaulting to "Gen 2"
VMs which are all UEFI based. Hence your current VMs
should have a FAT32 partition with an EFI loader. oVirt by default emulates
440FX Chipset and a legacy SeaBIOS.
Only so-called Gen 1 VMs were emulating a legacy BIOS on the Hyper-V side.
You should be able to check VM generation on Hyper-V using this PowerShell
command:
Get-VM | Format-List Name,Generation
If it is a Gen 2 VM, starting with oVirt 4.3 you could try booting a
converted disk on a VM with Q35 and OVMF (UEFI).
Keep in mind that 4.3 still has some rough edges in that area. For example
all settings written to the UEFI NVRAM get lost when turning off
and on the VM in oVirt. This affects the bootloader entries in OVMF that an
OS installer eventually created during setup.
Thus the OVMF only ever looks for an EFI loader bootloader in the path
boot/efi/bootx64.efi in that FAT32 partition.
However if that path is not present, OVMF should open the "BIOS settings"
and you should be able to "boot from file" and then
select the .efi file if the given operating system and make an attempt at
booting the guest OS.
The current workaround that seems to work now is to copy the OS's .efi
loader to the default location OVMF is looking for a bootloader
as described here: https://bugzilla.redhat.com/show_bug.cgi?id=1727987
Regards,
Mathieu
1:55 a.m.
New subject: Hyper-V to KVM | v2v
Hi.
Although if I add this converted disk as second disk..I could see the data
there.
But not booting as single disk..as windows 2016 OS data is kept and have to
deliver to one of my client. Bit of stuck here.
Thanks
On Sun, 8 Dec 2019 at 11:46 AM, Mathieu Simon <mathieu.simon(a)gymneufeld.ch>
wrote:
Hi Vijay
Based on your initial post about using virt-v2v I don't know how
intelligent virt-v2v is in knowing and converting the VM machine type.
However the boot issue could be related to Hyper-V defaulting to "Gen 2"
VMs which are all UEFI based. Hence your current VMs
should have a FAT32 partition with an EFI loader. oVirt by default
emulates 440FX Chipset and a legacy SeaBIOS.
Only so-called Gen 1 VMs were emulating a legacy BIOS on the Hyper-V side.
You should be able to check VM generation on Hyper-V using this PowerShell
command:
Get-VM | Format-List Name,Generation
If it is a Gen 2 VM, starting with oVirt 4.3 you could try booting a
converted disk on a VM with Q35 and OVMF (UEFI).
Keep in mind that 4.3 still has some rough edges in that area. For example
all settings written to the UEFI NVRAM get lost when turning off
and on the VM in oVirt. This affects the bootloader entries in OVMF that
an OS installer eventually created during setup.
Thus the OVMF only ever looks for an EFI loader bootloader in the path
boot/efi/bootx64.efi in that FAT32 partition.
However if that path is not present, OVMF should open the "BIOS settings"
and you should be able to "boot from file" and then
select the .efi file if the given operating system and make an attempt at
booting the guest OS.
The current workaround that seems to work now is to copy the OS's .efi
loader to the default location OVMF is looking for a bootloader
as described here: https://bugzilla.redhat.com/show_bug.cgi?id=1727987
Regards,
Mathieu
_______________________________________________
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/ESOPHINAYC3...
11:15 a.m.
New subject: Hyper-V to KVM | v2v
Hi Vijay
Although if I add this converted disk as second disk..I could see the
data there.
Yes, that is pretty much expected.
But not booting as single disk..as windows 2016 OS data is kept and
have to deliver to one of my client. Bit of stuck here.
Maybe I wasn't clear:
You first need to check whether your Hyper-V VM
in question is a Gen 2 UEFI-based VM or a legacy BIOS-based
Gen 1 VM. (It's quite likely Gen 2 since this has been the default
since Hyper-V on Server 2012 R2)
This defines the way on how the destination VM on the oVirt side needs
to be configured.
Once that is identified, try the according machine type on the oVirt
side there that converted disk is attached to:
- Hyper-V Gen 1 => oVirt 440FX + SeaBIOS (default in oVirt as of writing)
- Hyper-V Gen 2 => oVirt Q35 + OVMF
As written previously: There are still plenty of limitations in the
UEFI guest support and they sometimes
need workarounds until hopefully oVirt 4.4 closes most of these gaps.
Regards
Mathieu
1847
days inactive
1847
days old
3 comments
2 participants
participants (2)
-
Mathieu Simon -
Vijay Sachdeva