Xen users - Jun 2012 - Fwd: Problems migrating Windows guest from Virtualbox to xen

Hi,

First of all, sorry if I doublepost. I wasn''t subscribed first so
I''m not sure if the first post got through.

I am trying to make a script to convert a VirtualBox image to a xen hvm domU and
start it.
My problem now is that the xen domU starts, but hangs at "Booting from hard
disk..."
It''s state is r-----, and it is using 100% of one cpu all the time.
When connecting via VNC, I see the following: http://kuvaton.com/k/Yo1L.png

The .vdi image contains a clean Windows 7 installation, and it is working in
VBox.
I have converted the disk image from .vdi to raw image file with
"VBoxManage internalcommands converttoraw image.vdi image.img"
I have also tried to do it with "qemu-img convert -f vdi -O raw image.vdi
image.img" - but had the same results.

The raw image file seems to be OK and I can mount the two partitions in it, by
using the right offset.

I have also tried the same script with a clean Debian Squeeze installation. It
went a bit further, it displayed "Welcome to GRUB!" but hang there.

I have attached the domU config, xend log and qemu-dm log.
Please tell me if there is something else that might be helpful.

What am I possibly doing wrong?

I am running an old version, but I wasn''t able to find any related bugs
that have been fixed in more recent versions.
I am running Debian as dom0, and using a Debian packet
xen-hypervisor-3.2.1-amd64 version 3.2.1-2


Thank you,

Mikael Tuomisalo



_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users

On Thu, Jun 28, 2012 at 3:23 PM,  <tumik@tumik.eu>
wrote:
> What am I possibly doing wrong?
Simple: you tried to convert a windows guest. Microsoft have gone out
of their way to make SURE you can''t transfer windows installation from
one PC/server to another easily. And that affects V2V as well.

The general procedure would usually involve installing the driver for
storage controller of the new system (in this case, xen/qemu''s
emulated storage controller) on the old system. I''m not aware of any
steps to do this easily.

Another alternative would be to use sysprep /oobe /generalize on
windows (search Google for details) BEFORE you convert the storage.
IIRC I used this method (last year or so) to convert a windows7
installation on virtualbox to native. YMMV

-- 
Fajar

-----Original Message-----
From: Fajar A. Nugraha [mailto:list@fajar.net] 
Sent: Thursday, June 28, 2012 11:51
> Simple: you tried to convert a windows guest. Microsoft have gone out of
their way to make SURE you can''t transfer windows installation from one
PC/server to another easily. And that affects V2V as well.

Hi,

I don''t think it is because of Windows, as I have also tried the same
method
with a clean Debian installation and that didn''t work either.
(Mentioned
that on the last post.) The GRUB started loading, but didn''t get far
enough
to show the boot menu.

And I thought that having different drivers installed in Windows etc mostly
affects by creating a BSOD while booting, or can it also have some effect
this early, before the bootloader has printed anything on the screen?


Thank you,
Mikael Tuomisalo

On Thu, Jun 28, 2012 at 4:54 PM, tumik <tumik@tumik.eu>
wrote:
> -----Original Message-----
> From: Fajar A. Nugraha [mailto:list@fajar.net]
> Sent: Thursday, June 28, 2012 11:51
>> Simple: you tried to convert a windows guest. Microsoft have gone out
of
> their way to make SURE you can''t transfer windows installation
from one
> PC/server to another easily. And that affects V2V as well.
>
> Hi,
>
> I don''t think it is because of Windows, as I have also tried the
same method
> with a clean Debian installation and that didn''t work either.
(Mentioned
> that on the last post.) The GRUB started loading, but didn''t get
far enough
> to show the boot menu.
(shrug)

Not sure why I didn''t work for you.

In any case, debugging linux guests is easier. Start by using HVM
domU, and mapping both the converted image and a live CD (e.g.
sysrescuecd). And after booting into the live cd:
- mount the partitions (e.g. /mnt/root, /mnt/root/boot, etc)
- verify that the data is there
- run grub-install with the correct arguments (either chroot, or using
the live cd''s grub should be fine if they''re both grub2)
- reboot, but this time boot from disk

-- 
Fajar