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 <[email protected]> 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 <[email protected]> > Sent: 06 July 2018 14:27 > To: users <[email protected]> > 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 <[email protected]> > 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 <[email protected]> > > Sent: 06 July 2018 13:45 > > To: users <[email protected]> > > 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 <[email protected]> > > 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. > > > This message and any attachments are confidential and should only be > > > read by those to whom they are addressed. If you are not the > > > intended recipient, please contact us, delete the message from your > > > computer and destroy any copies. Any distribution or copying without > > > our prior permission is prohibited. > > > Internet communications are not always secure and therefore Oakford > > > Technology Limited does not accept legal responsibility for this > message. > > > The recipient is responsible for verifying its authenticity before > > > acting on the contents. Any views or opinions presented are solely > > > those of the author and do not necessarily represent those of > > > Oakford > > Technology Limited. > > > Registered address: Oakford Technology Limited, 10 Prince Maurice > > > Court, Devizes, Wiltshire. SN10 2RT. > > > Registered in England and Wales No. 5971519 > > > > > > > > > > -- > > > > Andrija Panić > > 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. > > This message and any attachments are confidential and should only be > > read by those to whom they are addressed. If you are not the intended > > recipient, please contact us, delete the message from your computer > > and destroy any copies. Any distribution or copying without our prior > > permission is prohibited. > > Internet communications are not always secure and therefore Oakford > > Technology Limited does not accept legal responsibility for this message. > > The recipient is responsible for verifying its authenticity before > > acting on the contents. Any views or opinions presented are solely > > those of the author and do not necessarily represent those of Oakford > Technology Limited. > > Registered address: Oakford Technology Limited, 10 Prince Maurice > > Court, Devizes, Wiltshire. SN10 2RT. > > Registered in England and Wales No. 5971519 > > > > > > -- > > Andrija Panić > 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. > This message and any attachments are confidential and should only be read > by those to whom they are addressed. If you are not the intended recipient, > please contact us, delete the message from your computer and destroy any > copies. Any distribution or copying without our prior permission is > prohibited. > Internet communications are not always secure and therefore Oakford > Technology Limited does not accept legal responsibility for this message. > The recipient is responsible for verifying its authenticity before acting > on the contents. Any views or opinions presented are solely those of the > author and do not necessarily represent those of Oakford Technology Limited. > Registered address: Oakford Technology Limited, 10 Prince Maurice Court, > Devizes, Wiltshire. SN10 2RT. > Registered in England and Wales No. 5971519 > > -- Andrija Panić
