thr3ads.net - Xen users - [Xen-users] Questions: blocked / migration fails / device 768 [Nov 2007]

If this information is useful, please help other people find it:
Share via:

Stefan de Konink

2007-Nov-11 02:56 UTC

[Xen-users] Questions: blocked / migration fails / device 768

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,


How can I see the resources that are blocked when xm list shows a
''b'' in
state?



My migration basically fails... live or non-live:

xm migrate -l skinkie_gentoo 192.168.0.5
> [2007-11-11 03:48:57 3376] DEBUG (balloon:116) Balloon: 2128 KiB free; need
2048; done.
> [2007-11-11 03:48:57 3376] DEBUG (XendCheckpoint:88) [xc_save]:
/usr/lib64/xen/bin/xc_save 4 3 0 0 1
> [2007-11-11 03:48:57 3376] INFO (XendCheckpoint:362) ERROR Internal error:
Couldn''t enable shadow mode
> [2007-11-11 03:48:57 3376] INFO (XendCheckpoint:362) Save exit rc=1
> [2007-11-11 03:48:57 3376] ERROR (XendCheckpoint:140) Save failed on domain
skinkie_gentoo (3).
> Traceback (most recent call last):
>   File
"usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line
109, in save
>     forkHelper(cmd, fd, saveInputHandler, False)
>   File
"usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line
350, in forkHelper
>     raise XendError("%s failed" % string.join(cmd))
> XendError: /usr/lib64/xen/bin/xc_save 4 3 0 0 1 failed
> [2007-11-11 03:48:57 3376] DEBUG (XendDomainInfo:1793)
XendDomainInfo.resumeDomain(3)
> [2007-11-11 03:48:57 3376] DEBUG (XendCheckpoint:143) XendCheckpoint.save:
resumeDomain


xm migrate skinkie_gentoo 192.168.0.5

> [2007-11-11 03:48:11 3376] DEBUG (XendCheckpoint:88) [xc_save]:
/usr/lib64/xen/bin/xc_save 4 3 0 0 0
> [2007-11-11 03:48:11 3376] DEBUG (XendCheckpoint:333) suspend
> [2007-11-11 03:48:11 3376] DEBUG (XendCheckpoint:91) In saveInputHandler
suspend
> [2007-11-11 03:48:11 3376] DEBUG (XendCheckpoint:93) Suspending 3 ...
> [2007-11-11 03:48:11 3376] DEBUG (XendDomainInfo:451)
XendDomainInfo.shutdown(suspend)
> [2007-11-11 03:48:12 3376] DEBUG (XendDomainInfo:991)
XendDomainInfo.handleShutdownWatch
> [2007-11-11 03:48:12 3376] DEBUG (XendDomainInfo:991)
XendDomainInfo.handleShutdownWatch
> [2007-11-11 03:48:12 3376] INFO (XendCheckpoint:98) Domain 3 suspended.
> [2007-11-11 03:48:12 3376] DEBUG (XendCheckpoint:107) Written done
> [2007-11-11 03:48:12 3376] INFO (XendCheckpoint:362) ERROR Internal error:
write: p2m_frame_list
> [2007-11-11 03:48:12 3376] INFO (XendCheckpoint:362) ERROR Internal error:
Failed to map/save the p2m frame list
> [2007-11-11 03:48:12 3376] INFO (XendCheckpoint:362) Save exit rc=1
> [2007-11-11 03:48:12 3376] INFO (XendDomainInfo:1179) Domain has shutdown:
name=migrating-skinkie_gentoo id=3 reason=suspend.
> [2007-11-11 03:48:12 3376] ERROR (XendCheckpoint:140) Save failed on domain
skinkie_gentoo (3).
> Traceback (most recent call last):
>   File
"usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line
109, in save
>     forkHelper(cmd, fd, saveInputHandler, False)
>   File
"usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line
350, in forkHelper
>     raise XendError("%s failed" % string.join(cmd))
> XendError: /usr/lib64/xen/bin/xc_save 4 3 0 0 0 failed
> [2007-11-11 03:48:12 3376] DEBUG (XendDomainInfo:1793)
XendDomainInfo.resumeDomain(3)
> [2007-11-11 03:48:12 3376] DEBUG (XendCheckpoint:143) XendCheckpoint.save:
resumeDomain

Currently running a Gentoo xen kernel. 2.6.20. And xen-tools-3.1.1-r1.
And having an iscsi device as filesystem.



What is the mysterious device 768? When initiating the domainU Xen hangs
for exactly one minute.
> [2007-11-11 03:20:58 3376] DEBUG (XendDomainInfo:991)
XendDomainInfo.handleShutdownWatch
> [2007-11-11 03:20:58 3376] DEBUG (DevController:150) Waiting for devices
vif.
> [2007-11-11 03:20:58 3376] DEBUG (DevController:150) Waiting for devices
usb.
> [2007-11-11 03:20:58 3376] DEBUG (DevController:150) Waiting for devices
vbd.
> [2007-11-11 03:20:58 3376] DEBUG (DevController:155) Waiting for 768.
> [2007-11-11 03:20:58 3376] DEBUG (DevController:577) hotplugStatusCallback
/local/domain/0/backend/vbd/2/768/hotplug-status.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:577) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:577) hotplugStatusCallback
/local/domain/0/backend/vbd/1/768/hotplug-status.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:577) hotplugStatusCallback
/local/domain/0/backend/vbd/2/768/hotplug-status.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:591) hotplugStatusCallback
1.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
irq.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
vkbd.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
vfb.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
console.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:155) Waiting for 0.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
pci.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
ioports.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
tap.
> [2007-11-11 03:21:58 3376] DEBUG (DevController:150) Waiting for devices
vtpm.
> [2007-11-11 03:21:58 3376] INFO (XendDomain:1117) Domain skinkie_gentoo (2)
unpaused.


Thanks for the possible answers :)



Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHNm9kYH1+F2Rqwn0RCsTFAJ9jFlh/7jZvAY9BKqGxnJwV4mr7+wCeM4UK
8abCplVX1xn8lF7Jpx6quyA=KzcP
-----END PGP SIGNATURE-----

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

Stefan de Konink

2007-Nov-11 13:03 UTC

head link

Re: [Xen-users] Questions: blocked / migration fails / device 768 [solved]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Stefan de Konink schreef:> How can I see the resources that are blocked when xm list shows a
''b'' in
> state?

- From IRC I understood that it is nothing bad to have a ''b''.


> My migration basically fails... live or non-live:
> 
> xm migrate -l skinkie_gentoo 192.168.0.5
> 
> xm migrate skinkie_gentoo 192.168.0.5
Fixed both by referencing my iscsi phy-disk to /dev/disk/by-path instead
of sda/sdb etc.



Stefan

ps. As reference 768 refers to ''disk''.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHNv2sYH1+F2Rqwn0RCq2qAJ4qWPldSduiryFU/GOECANk6KTbHwCdHxN6
FLd87bbElBc5PpNShIAbj2k=1Qqd
-----END PGP SIGNATURE-----

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

Xen users - Nov 2007 - Questions: blocked / migration fails / device 768

[Xen-users] Questions: blocked / migration fails / device 768

Re: [Xen-users] Questions: blocked / migration fails / device 768 [solved]