Re: Importing Hyper-V to Cloudstack 4.11.0 UEFI and GPT
Hi Adam,
Wonderful that you found a way to solve it !
If you have some spare time, please consider updating the ACS
administration pages on github :) - I do that from time to time (since
can't contribute any code really :) )
Cheers!
On Tue, Jul 10, 2018, 17:43 Adam Witwicki wrote:
> Fixed using this
>
>
> https://www.sevenforums.com/installation-setup/320700-boot-windows-7-8-gpt-bios-system-no-hybrid-mbrs-duet.html
>
> ROOT MBR disk,
> Attached GPT disk (imported windows partitions)
>
> select disk 0
> clean
> create partition primary [size=##]
> format
> select partition 1
> active
> list volume
> select volume 1
> assign
> list volume
> exit
>
> bcdboot C:\Windows /l en-us /s D:
> bootsect /nt60 D: /mbr /force
> bcdedit /store D:\boot\bcd /set {bootmgr} device boot
>
>
> Thanks Everyone
>
> Adam
>
> -Original Message-----
> From: Adam Witwicki
> Sent: 10 July 2018 15:09
> To: users
> Subject: RE: Importing Hyper-V to Cloudstack 4.11.0 UEFI and GPT
>
> Is there any way to get cloudstack to boot a GPT disk? This needs to be
> made clearer in the documentation, we have lots of hyper-v GEN2 boxes we
> need to import.
>
> I have found one bootloader on a CD that will boot the windows OS, but am
> having a nightmare getting this installed on the first HDD
> https://sourceforge.net/projects/cloverefiboot/
>
> Thanks
>
> Adam
>
> -Original Message-
> From: Andrija Panic
> Sent: 09 July 2018 14:09
> To: users
> Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
>
> ** This mail originated from OUTSIDE the Oakford corporate network. Treat
> hyperlinks and attachments in this email with caution. **
>
> Ah yes... if ti has anything to do with UEFI, than it's not possible.
>
> But if plain GPT - there should be a fix possible - check this one:
>
> https://forum.proxmox.com/threads/hyper-v-export-with-gpt-partition-table-will-not-boot.23716/
>
> Cheers
>
> On Mon, 9 Jul 2018 at 14:48, Adam Witwicki
> wrote:
>
> > Andrija
> >
> > It looks like we cannot boot a GPT disk, this will be a huge pain, as
> > most of the systems we want to migrate are GPT
> >
> > Thanks
> >
> > Aadm
> >
> > -Original Message-
> > From: Andrija Panic
> > Sent: 06 July 2018 14:27
> > To: users
> > Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
> >
> > ** This mail originated from OUTSIDE the Oakford corporate network.
> > Treat hyperlinks and attachments in this email with caution. **
> >
> > I would not be sure...
> >
> > Silly question, can you check (ps aux | grep VMNAME) or with virsh
> > dumpxml etc... that the volume is actually really attached to the VM ?
> > If so, then I would try to mount the volume on the hypervisor host
> > (there are ways to mount qcow2 and same with ceph, using rbd map,
> > etc...) to "enter" the volume and see if all fine.. or perhaps doing
> > qemu-img check... just from top of my head. I find it hard that
> > conversion produces damaged volume, but it;s possible,
> >
> > Actually, pay attention on the conversion process - not sure how/with
> > which tool you do conversion - but's it's good idea to export VM (from
> > HyperV) to get clean/single VHDX file, and then convert (check the
> > VHDX previously also with qemu-img check) Here there is a Windows
> > version, that should work (did NOT test it though):
> > https://cloudbase.it/qemu-img-windows/
> >
> > Let me know, really curious what is going on...
> >
> >
> >
> >
> > On Fri, 6 Jul 2018 at 14:49, Adam Witwicki
> > wrote:
> >
> > > Andrija,
> > >
> > > I used qemu-img to convert to qcow2 since I am using KVM with ceph -
> > > when I view the console I get the emulated BIOS saying no bootable
> > > device found
> > > - this must be before any IDE or VirtIO drivers.
> > > I have also tried with NFS storage and get the same boot error.
> > >
> > > This process worked on 4.9, I notice there are more template options
> > > on
> > > 4.11.0 do I need to do any thing different?
> > >
> > > Thanks
> > >
> > > Adam
> > >
> > > -Original Message-
> > > From: Andrija Panic
> > > Sent: 06 July 2018 13:45
> > > To: users
> > > Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
> > >
> > > ** This mail originated from OUTSIDE the Oakford corporate network.
> > > Treat hyperlinks and attachments in this email with caution. **
> > >
&
RE: Importing Hyper-V to Cloudstack 4.11.0 UEFI and GPT
Fixed using this
https://www.sevenforums.com/installation-setup/320700-boot-windows-7-8-gpt-bios-system-no-hybrid-mbrs-duet.html
ROOT MBR disk,
Attached GPT disk (imported windows partitions)
select disk 0
clean
create partition primary [size=##]
format
select partition 1
active
list volume
select volume 1
assign
list volume
exit
bcdboot C:\Windows /l en-us /s D:
bootsect /nt60 D: /mbr /force
bcdedit /store D:\boot\bcd /set {bootmgr} device boot
Thanks Everyone
Adam
-Original Message-
From: Adam Witwicki
Sent: 10 July 2018 15:09
To: users
Subject: RE: Importing Hyper-V to Cloudstack 4.11.0 UEFI and GPT
Is there any way to get cloudstack to boot a GPT disk? This needs to be made
clearer in the documentation, we have lots of hyper-v GEN2 boxes we need to
import.
I have found one bootloader on a CD that will boot the windows OS, but am
having a nightmare getting this installed on the first HDD
https://sourceforge.net/projects/cloverefiboot/
Thanks
Adam
-Original Message-
From: Andrija Panic
Sent: 09 July 2018 14:09
To: users
Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
** This mail originated from OUTSIDE the Oakford corporate network. Treat
hyperlinks and attachments in this email with caution. **
Ah yes... if ti has anything to do with UEFI, than it's not possible.
But if plain GPT - there should be a fix possible - check this one:
https://forum.proxmox.com/threads/hyper-v-export-with-gpt-partition-table-will-not-boot.23716/
Cheers
On Mon, 9 Jul 2018 at 14:48, Adam Witwicki wrote:
> Andrija
>
> It looks like we cannot boot a GPT disk, this will be a huge pain, as
> most of the systems we want to migrate are GPT
>
> Thanks
>
> Aadm
>
> -Original Message-
> From: Andrija Panic
> Sent: 06 July 2018 14:27
> To: users
> Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
>
> ** This mail originated from OUTSIDE the Oakford corporate network.
> Treat hyperlinks and attachments in this email with caution. **
>
> I would not be sure...
>
> Silly question, can you check (ps aux | grep VMNAME) or with virsh
> dumpxml etc... that the volume is actually really attached to the VM ?
> If so, then I would try to mount the volume on the hypervisor host
> (there are ways to mount qcow2 and same with ceph, using rbd map,
> etc...) to "enter" the volume and see if all fine.. or perhaps doing
> qemu-img check... just from top of my head. I find it hard that
> conversion produces damaged volume, but it;s possible,
>
> Actually, pay attention on the conversion process - not sure how/with
> which tool you do conversion - but's it's good idea to export VM (from
> HyperV) to get clean/single VHDX file, and then convert (check the
> VHDX previously also with qemu-img check) Here there is a Windows
> version, that should work (did NOT test it though):
> https://cloudbase.it/qemu-img-windows/
>
> Let me know, really curious what is going on...
>
>
>
>
> On Fri, 6 Jul 2018 at 14:49, Adam Witwicki
> wrote:
>
> > Andrija,
> >
> > I used qemu-img to convert to qcow2 since I am using KVM with ceph -
> > when I view the console I get the emulated BIOS saying no bootable
> > device found
> > - this must be before any IDE or VirtIO drivers.
> > I have also tried with NFS storage and get the same boot error.
> >
> > This process worked on 4.9, I notice there are more template options
> > on
> > 4.11.0 do I need to do any thing different?
> >
> > Thanks
> >
> > Adam
> >
> > -Original Message-
> > From: Andrija Panic
> > Sent: 06 July 2018 13:45
> > To: users
> > Subject: Re: Importing Hyper-V to Cloudstack 4.11.0
> >
> > ** This mail originated from OUTSIDE the Oakford corporate network.
> > Treat hyperlinks and attachments in this email with caution. **
> >
> > Hi Adam,
> >
> > havent done that myslef (but helped some customers) - if you are
> > running OS TYpe :"Windows XXX" - anything concrete version - this
> > means no VirtIO drives are needed, since all IDE, so no drivers
> > needed) If using "Windows PV" this means you need to have installed
> > VirtIO drivers inside the OS (I suggest, on HyperV VM, adding new
> > hardware via device manager and loading correct VirtIO drivers for
> > SCSI controller, or also for the network...up to
> > you) - and only then exporting VHDX to qcow2.
> >
> > Btw, I don't know if VHDX can be imported into ACS directly ? -
> > perhaps it needs previous conversion to QCOW2 format, and then
> > upload
> > qcow2 natively (again, not sure, so I might be wrong here).
> >
> >
> > Also please note that there is something re
RE: Importing Hyper-V to Cloudstack 4.11.0 UEFI and GPT
Is there any way to get cloudstack to boot a GPT disk? This needs to be made clearer in the documentation, we have lots of hyper-v GEN2 boxes we need to import. I have found one bootloader on a CD that will boot the windows OS, but am having a nightmare getting this installed on the first HDD https://sourceforge.net/projects/cloverefiboot/ Thanks Adam -Original Message- From: Andrija Panic Sent: 09 July 2018 14:09 To: users Subject: Re: Importing Hyper-V to Cloudstack 4.11.0 ** This mail originated from OUTSIDE the Oakford corporate network. Treat hyperlinks and attachments in this email with caution. ** Ah yes... if ti has anything to do with UEFI, than it's not possible. But if plain GPT - there should be a fix possible - check this one: https://forum.proxmox.com/threads/hyper-v-export-with-gpt-partition-table-will-not-boot.23716/ Cheers On Mon, 9 Jul 2018 at 14:48, Adam Witwicki wrote: > Andrija > > It looks like we cannot boot a GPT disk, this will be a huge pain, as > most of the systems we want to migrate are GPT > > Thanks > > Aadm > > -Original Message- > From: Andrija Panic > Sent: 06 July 2018 14:27 > To: users > Subject: Re: Importing Hyper-V to Cloudstack 4.11.0 > > ** This mail originated from OUTSIDE the Oakford corporate network. > Treat hyperlinks and attachments in this email with caution. ** > > I would not be sure... > > Silly question, can you check (ps aux | grep VMNAME) or with virsh > dumpxml etc... that the volume is actually really attached to the VM ? > If so, then I would try to mount the volume on the hypervisor host > (there are ways to mount qcow2 and same with ceph, using rbd map, > etc...) to "enter" the volume and see if all fine.. or perhaps doing > qemu-img check... just from top of my head. I find it hard that > conversion produces damaged volume, but it;s possible, > > Actually, pay attention on the conversion process - not sure how/with > which tool you do conversion - but's it's good idea to export VM (from > HyperV) to get clean/single VHDX file, and then convert (check the > VHDX previously also with qemu-img check) Here there is a Windows > version, that should work (did NOT test it though): > https://cloudbase.it/qemu-img-windows/ > > Let me know, really curious what is going on... > > > > > On Fri, 6 Jul 2018 at 14:49, Adam Witwicki > wrote: > > > Andrija, > > > > I used qemu-img to convert to qcow2 since I am using KVM with ceph - > > when I view the console I get the emulated BIOS saying no bootable > > device found > > - this must be before any IDE or VirtIO drivers. > > I have also tried with NFS storage and get the same boot error. > > > > This process worked on 4.9, I notice there are more template options > > on > > 4.11.0 do I need to do any thing different? > > > > Thanks > > > > Adam > > > > -Original Message- > > From: Andrija Panic > > Sent: 06 July 2018 13:45 > > To: users > > Subject: Re: Importing Hyper-V to Cloudstack 4.11.0 > > > > ** This mail originated from OUTSIDE the Oakford corporate network. > > Treat hyperlinks and attachments in this email with caution. ** > > > > Hi Adam, > > > > havent done that myslef (but helped some customers) - if you are > > running OS TYpe :"Windows XXX" - anything concrete version - this > > means no VirtIO drives are needed, since all IDE, so no drivers > > needed) If using "Windows PV" this means you need to have installed > > VirtIO drivers inside the OS (I suggest, on HyperV VM, adding new > > hardware via device manager and loading correct VirtIO drivers for > > SCSI controller, or also for the network...up to > > you) - and only then exporting VHDX to qcow2. > > > > Btw, I don't know if VHDX can be imported into ACS directly ? - > > perhaps it needs previous conversion to QCOW2 format, and then > > upload > > qcow2 natively (again, not sure, so I might be wrong here). > > > > > > Also please note that there is something related to Hardware > > Abstraction Layer in Windows (if Windows at all ?), when some of the > > changes (even installing VirtIO in some cases on existing KVM VM) > > will bring server down unable to boot - bcdedit /detecthal - google > > for this one - i.e. force OS to detect HAL again, for proper boot/fix. > > > > > > > > Hope that helps > > > > Andrija > > > > On Fri, 6 Jul 2018 at 12:39, Adam Witwicki > > wrote: > > > > > Hello, > > > > > > I wonder if anyone can help, I am having issues importing a > > > converted Hyper-V (VHDX) to KVM (qcow2). > > > After importing the template and starting the instance, the > > > instance will fail to find the boot device. > > > > > > This worked in 4.9 > > > > > > > > > Thanks > > > > > > Adam Witwicki > > > > > > > > > Disclaimer Notice: > > > This email has been sent by Oakford Technology Limited, while we > > > have checked this e-mail and any attachments for viruses, we can > > > not guarantee that they are virus-free. You must therefore take > > > full responsibility for virus checking. > > >
