Convert VirtualBox VM to Xen.

hack3rcon · 06-13-2016, 02:04 AM

Hello.
I used below command for convert my VirtualBox VM to Xen :

# VBoxManage clonehd vm.vdi vm.img --format RAW

And write my Xen config like below :

Code:

name = "Converted"
builder = "hvm"
uuid= "8ea234db-8ee0-46ff-bda1-71d95bd257c6"
memory = 1024
vcpus = 2
interface=['br0']
vif = [ "mac=00:16:3e:46:e6:fb,bridge=br0" ]
disk = [ "file:/home/jason/vm.img,xvda,w" ]
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"

I tested it for Linux and Windows and both OSs crashed and can't boot. Windows OS show me Blue Page and Linux...
How can I solve it?

Thank you.

jefro · 06-13-2016, 03:54 PM

Windows may not like it ever.

I assume that the conversion to raw may have been part of it. Guess you could try virtualbox with the raw hard drive file and see if it works. Qemu on the raw drive ought to work too as a first step test.

Guess you could use clonezilla or such too.

Habitual · 06-13-2016, 04:08 PM

https://www.serverstack.com/blog/201...rtual-machine/ may be of help.

hack3rcon · 06-14-2016, 01:49 AM

Quote:

Originally Posted by Habitual

https://www.serverstack.com/blog/201...rtual-machine/ may be of help.

As you see I used same steps.

TenTenths · 06-14-2016, 02:42 AM

Moving VMs between virtualisation platforms can be problematic due to the different ways different platforms "present" the hardware.

Windows is especially prone to this and also because as a "paid for" O/S it ties itself closely to the hardware it's installed on, knowing things like the bios settings, the motherboard / hard disk serial numbers etc. and if it sees significant changes it assumes that it's been copied on to a different machine and at best will require license re-activation and at worst (what you're probably seeing) is that the installed HAL doesn't work with the underlying virtualisation platform.

From experience I'd strongly suggest that you build new VMs on the target platform and then migrate your data accordingly.

Habitual · 06-14-2016, 08:43 AM

Quote:

Originally Posted by hack3rcon

As you see I used same steps.

No, I didn't "see" you used the same steps. I did not read the link.
You didn't specify what documentation you had read, or tried, so you got google's answer.
Why do we have to beat info out of folks?

jefro · 06-14-2016, 04:35 PM

Did you try to boot the raw file yet?

hack3rcon · 06-15-2016, 02:25 AM

Quote:

Originally Posted by jefro

Did you try to boot the raw file yet?

I got Blue page.

jefro · 06-15-2016, 05:30 PM

Then my guess so far is the conversion failed.

You can make a raw drive and dd it over in the vm if you want. Or use clonezilla/redobackup.

Windows won't like any system changes usually. Either fix the hal before move or after move with oem media.

hack3rcon · 06-18-2016, 02:06 AM

Quote:

Originally Posted by jefro

Then my guess so far is the conversion failed.

You can make a raw drive and dd it over in the vm if you want. Or use clonezilla/redobackup.

Windows won't like any system changes usually. Either fix the hal before move or after move with oem media.

As you see I choice "RAW" as format. Can you guide me about dd it?

WFV · 07-07-2016, 12:58 AM

Quote:

Originally Posted by hack3rcon

As you see I choice "RAW" as format. Can you guide me about dd it?

There are lots of helpful dd sites out there.

jefro · 07-08-2016, 04:13 PM

You did fix the hal before you tried this didn't you?

It should also be possible to fix hal after you migrated it. Boot to windows image and fix install. I believe MS suggested you make full backup with system state and then load new OS on VM then apply restore to correct hal if all else fails.