[Xen-users] Restoring saved stated results in hanging domain

[Wiebe Cazemier <halfgaar@xxxxxxx>]

Hi,

I'm having a problem with migrating a domU. I'm merely experimenting with Xen
first, so I don't have any shared storage yet. I merely save the state, copy
it to another xen machine and restore it.

My problem is that the restored domU hangs. The log /var/log/xen/xend.log
doesn't give an error:

> [2010-03-24 13:09:46 2236] DEBUG (XendDomainInfo:1008) Storing domain
details:
{'console/ring-ref': '3515', 'image/entry': '3222274048', 'console/port': '2', 
'store/ring-ref': '3516', 'image/loader': 'generic', 'vm': 
'/vm/e405eb96-37e7-305e-bd22-5cad6273f3c9', 
'control/platform-feature-multiprocessor-suspend': '1', 'image/hv-start-low': 
'4118806528', 'image/guest-os': 'linux', 
'image/features/writable-descriptor-tables': '1', 'image/virt-base': 
'3221225472', 'memory/target': '131072', 'image/guest-version': '2.6', 
'image/features/supervisor-mode-kernel': '1', 'image/pae-mode': 'yes', 
'console/limit': '1048576', 'image/paddr-offset': '0', 'image/hypercall-page': 
'3222278144', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 
'image/features/pae-pgdir-above-4gb': '1', 
'image/features/writable-page-tables': '1', 'console/type': 'xenconsoled', 
'image/features/auto-translated-physmap': '1', 'name': 'virtualnode', 'domid': 
'1', 'image/xen-version': 'xen-3.0', 'store/port': '1'}
> [2010-03-24 13:09:46 2236] DEBUG (XendDomainInfo:1851)
XendDomainInfo.completeRestore done
> [2010-03-24 13:09:46 2236] DEBUG (XendDomainInfo:1092)
XendDomainInfo.handleShutdownWatch
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices vif.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:156) Waiting for 0.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:595)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:609) hotplugStatusCallback 1.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices vbd.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:156) Waiting for 2049.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:595)
hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:609) hotplugStatusCallback 1.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:156) Waiting for 2050.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:595)
hotplugStatusCallback /local/domain/0/backend/vbd/1/2050/hotplug-status.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:609) hotplugStatusCallback 1.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices irq.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices
vkbd.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices vfb.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices
console.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:156) Waiting for 0.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices pci.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices
ioports.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices tap.
> [2010-03-24 13:09:46 2236] DEBUG (DevController:151) Waiting for devices
vtpm.

This supposedly means the migration was successful, but I can't reach it
network devices and trying to attach a console with "xm console" also hangs
(which I can escape with ctrl-]).

xm list shows:

Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0   176     1     r-----    865.6
virtualnode                                  1   128     1     -b----      0.0

network device was created:

vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:69 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

All of that output is the same as on the node on which it does work, excep that
the time is not 0.0.

Any idea what's going on?


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users