[one-users] BSOD when deploy Windows XP VM in OpenNebula 4.2

[Shankhadeep Shome]

For windows VMs you need to make sure the correct virtio block drivers are
installed, you might get lucky with using ide instead. Remove the
virtualbox guest tools before moving the vm over.


On Fri, Nov 29, 2013 at 6:25 AM, André Monteiro <andre.monteir at gmail.com>wrote:

> Hi,
>
> I have some experience on Windows machines, and all are running on qcow2
> without problems. When does exactly the VM blue screen appears? While not
> discarding a qemu problem, Windows OS is very sensible to hardware changes
> and the problem can be at the loading drivers step, which are not part of
> the new system.
>
> I have two suggestions:
> - Try to replicate Virtualbox hardware as close as possible on OpenNebula
> and boot in Safe Mode
> - Try to install a clean image on OpenNebula to check XP compatibility
>
> Regards,
>
>
>
> --
> André Monteiro
>
>
>
> On Fri, Nov 29, 2013 at 10:34 AM, M Fazli A Jalaluddin <
> fazli.jalaluddin at gmail.com> wrote:
>
>> Dear All,
>>
>> I was trying to install Windows XP in VirtualBox and convert it to qcow2.
>>
>> After I upload the qcow2 image to OpenNebula and instantiate the template,
>> the image goes BSOD while in Virtualbox, the VM works fine.
>>
>> I done some google and found out that there was some bug in qemu which
>> cause this [1].
>> Is there any possible solutions to this? Please help advise.
>>
>> Thank you
>> Best regards
>>
>> [1] http://ubuntuforums.org/showthread.php?t=1437758
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20131129/9a2079c7/attachment-0002.htm>