Re: Importing Hyper-V to Cloudstack 4.11.0
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
On Fri, 6 Jul 2018 at 12:39, Adam Witwicki <awitwicki@xxxxxxxxxxxxx> wrote:
> 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
> 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
> 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