KVM Vm will not start on another node

[eislon]

I have the following issue:

I got a KVM Windows 2008 64-bit (the one who caused the system shutdown with a compressed backup) which I migrate from an AMD to an Intel server.
The migration goes well (also the online migration) but the KVM VM will not start on the Intel node.

I tried to change some settings, just in case for memory, network. But nothing works. I start the vm from the webinterface, it says starting..running and very quickly stopped.

I see no errors what so ever. The KVM image is made on the AMD server.

 

[tom]

I have the following issue:

I got a KVM Windows 2008 64-bit (the one who caused the system shutdown with a compressed backup) which I migrate from an AMD to an Intel server.
The migration goes well (also the online migration) but the KVM VM will not start on the Intel node.

I tried to change some settings, just in case for memory, network. But nothing works. I start the vm from the webinterface, it says starting..running and very quickly stopped.

I see no errors what so ever. The KVM image is made on the AMD server.

any logs (see also the web interface: Administration/Logs: Command results of the start process).

 

[nick]

Maybe it's a hardware protection! As many administrators know when on Windows Server change the CPU, sometimes a BSOD appear and system stop.

Try to move back on AMD and test if the machine it's OK.

 

[eislon]

Migrating back to the AMD is no problem, it even starts. how should a hardware protection be lifted? I find it strange that this is possible, cause the processor is seen as a QEMU virtual processor.

 

[nick]

No, QEmu proprieties change when change the VE. So, Windows will recongnize as a different CPU with different parameters. For example, on XEON Qemu see 16 CPU...on Core 2 Duo see only 1 (I give him only 1 core).

 

[BitRausch]

Hi Eislon,

Maybe this will help?:

- On my WS08 x64 the virtio driver only works when I set:

BCDEDIT -set testsignin on

otherwise it crashes.
VIRTIO for hd devices does not work.


- before you migrate - activate the HAL detection.
(start msconfig-> start-> advanced options-> activate HAL detection.)
shutdown. migrate. start.

Just an idea.

Kind regards
B.