Xen users - Dec 2011 - Xen 3.2-1 (Debian) migration Windows 2003 HVM from Intel to AMD and vice versa

Hi,

I need to migrate a Windows 2003 HVM from an Intel server to an AMD
server and another one the other way around. Both servers are running
Debian Lenny with Xen 3.2-1. The GPLPV drivers are installed on both
Windows 2003 HVMs and both are configured with two CPUs.

I''ve tried it straight (ie. without making any changes). I''ve
tried
updated the HAL from MPS to Standard PC then making the image backup and
restoring that on the other server. I''m still getting a BSOD when
starting the Windows 2003 HVM on the AMD server.

I''m using Acronis Backup & Restore with Universal Restore to make
and
restore the image backups.

Any ideas how I can proceed with this?

regards,
Jan

> 
> Hi,
> 
> I need to migrate a Windows 2003 HVM from an Intel server to an AMD
> server and another one the other way around. Both servers are running
> Debian Lenny with Xen 3.2-1. The GPLPV drivers are installed on both
> Windows 2003 HVMs and both are configured with two CPUs.
> 
> I''ve tried it straight (ie. without making any changes).
I''ve tried updated the
> HAL from MPS to Standard PC then making the image backup and restoring
> that on the other server. I''m still getting a BSOD when starting
the Windows
> 2003 HVM on the AMD server.
> 
> 
> I''m using Acronis Backup & Restore with Universal Restore to
make and
> restore the image backups.
> 
> Any ideas how I can proceed with this?
> 
So this is a one way migration right, nothing to do with migrating live?

What is the BSoD bug check code you are getting?

James

Hi James,
> So this is a one way migration right, nothing to do with migrating live?
Yes.
> What is the BSoD bug check code you are getting?
0x0000007B (0xF789EA94,0xC0000034,0x00000000,0x00000000)

Same thing happens when booting in Safe Mode; the progress bar at the
bottom fills up to 100%, then shortly after that BSOD.

kind regards,
Jan

> 
> Hi James,
> 
> > So this is a one way migration right, nothing to do with migrating
live?
> 
> Yes.
> 
> > What is the BSoD bug check code you are getting?
> 
> 0x0000007B (0xF789EA94,0xC0000034,0x00000000,0x00000000)
> 
> Same thing happens when booting in Safe Mode; the progress bar at the
> bottom fills up to 100%, then shortly after that BSOD.
> 
If you can install the debug build of GPLPV you should get some useful output in
/var/log/xen/qemu-dm-<domu name>.log

James

Hi James,

I was assuming it was AMD vs Intel as I couldn''t see any other
differences. It turned out not to be the case though.

What I did to fix the problem was to remove the default Intel IDE and
Realtek network drivers even those were not used (status: Device cannot
start) prior to making the image backup. These are the default drivers
for disc and network that are there before GPLPV takes over.

I would not expect that to be an issue as this virtual hardware was
present (but not used) on the source VM.

I trust there''s a perfectly logical explanation why this would be an
issue when the VM is moved to another server.

As always thank you for your quick response and willingness to help. It
makes a real difference knowing you''re out there!

kind regards,
Jan



On 23/12/11 11:43, James Harper wrote:
>> Hi James,
>>
>>> So this is a one way migration right, nothing to do with migrating
live?
>> Yes.
>>
>>> What is the BSoD bug check code you are getting?
>> 0x0000007B (0xF789EA94,0xC0000034,0x00000000,0x00000000)
>>
>> Same thing happens when booting in Safe Mode; the progress bar at the
>> bottom fills up to 100%, then shortly after that BSOD.
>>
> If you can install the debug build of GPLPV you should get some useful
output in /var/log/xen/qemu-dm-<domu name>.log
>
> James
>