If you've created the XP machine in VBox it's easy that it has been
configured with IDE channel. So it's a matter of controller if BSOD, not
matter of QCOW2 or RAW image.
to boot in ONE just set DEV_PREFIX="hda" in the template or in the image
of your xp machine.
if still not booting check if you uninstalled the VBoxTools before
converting it.
if you want (and you better do so if you want a bit of performance)
switch to virtio controller for storage you have to do the following
steps (in order to let the "poor" xp load correctly the drivers)
- boot xp using DEV_PREFIX="hd" in order to test if it works correctly
- shutdown and add any image (eg: a cdrom) with virtio "DEV_PREFIX=vd"
- when it loads XP will find a new hardware and ask you for drivers:
load them from the virtio cdrom
http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/ this will
let XP know how to access a VirtIO SCSI drive in boot phase
- shutdown after installing drivers, remove the "fake image" you used
with vd prefix, and change DEV_PREFIX=""vd" for the WinXP System drive image
- instantiate and enjoy xp with virtio
bye
(this works for win 7 too)
Il 30/11/2013 02:15, M Fazli A Jalaluddin ha scritto:
Hi,
I also have deployed Windows 7 qcow2 format on OpenNebula without the
any problem.
which I used VirtualBox to create the image first and convert it from
.vdi to .qcow2 using qemu-utils.
May I know how to use IDE instead?
PS: I have tried using both qcow2 and raw format but still blue
screen. The Blue screen appears shortly after the Windows XP loading
bar splash screen.
Best regards
On Fri, Nov 29, 2013 at 10:40 PM, Shankhadeep Shome
<[email protected] <mailto:[email protected]>> wrote:
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
<[email protected] <mailto:[email protected]>> 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
<[email protected]
<mailto:[email protected]>> 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
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Lorenzo Faleschini
Responsabile Sistemi Informativi
skype: falegalizeit
mobile: +39 335 6055225
tel: +39 0427 807934
fax: +39 0434 1820145
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
