On 09/20/2011 09:23 PM, Ian Campbell wrote:
> On Tue, 2011-09-20 at 10:41 +0100, Andreas Olsowski wrote:
>> A pv guest will not reboot after migration, the guest itself does
>> everything right, including the shutdown, but xl does not recreate the
>> guest, it just shuts it down.
>
> After the migrate but before the shutdown is there an xl process
> associated with the guest?
Yes, xl migrate-receive is running, but check this out:
root@xenturio1:/var/log/xen# cat xl-thiswillfail.log
Waiting for domain thiswillfail (domid 7) to die [pid 7475]
root@xenturio1:/usr/src/linux-2.6-xen# xl -vvv migrate thiswillfail
xenturio2
migration target: Ready to receive domain.
Saving to migration stream new xl format (info 0x0/0x0/380)
Loading new save file incoming migration stream (new xl fmt info
0x0/0x0/380)
Savefile contains xl domain config
xc: detail: Had 0 unexplained entries in p2m table
xc: Saving memory: iter 0 (last sent 0 skipped 0): 133120/133120 100%
xc: detail: delta 9519ms, dom0 94%, target 1%, sent 449Mb/s, dirtied
1Mb/s 533 pages
xc: Saving memory: iter 1 (last sent 130565 skipped 507): 133120/133120
100%
xc: detail: delta 39ms, dom0 92%, target 2%, sent 447Mb/s, dirtied
28Mb/s 34 pages
xc: Saving memory: iter 2 (last sent 533 skipped 0): 133120/133120 100%
xc: detail: Start last iteration
libxl: debug: libxl_dom.c:384:libxl__domain_suspend_common_callback
issuing PV suspend request via XenBus control node
libxl: debug: libxl_dom.c:389:libxl__domain_suspend_common_callback wait
for the guest to acknowledge suspend request
libxl: debug: libxl_dom.c:434:libxl__domain_suspend_common_callback
guest acknowledged suspend request
libxl: debug: libxl_dom.c:438:libxl__domain_suspend_common_callback wait
for the guest to suspend
libxl: debug: libxl_dom.c:450:libxl__domain_suspend_common_callback
guest has suspended
xc: detail: SUSPEND shinfo 0007fafc
xc: detail: delta 205ms, dom0 3%, target 0%, sent 5Mb/s, dirtied 25Mb/s
160 pages
xc: Saving memory: iter 3 (last sent 34 skipped 0): 133120/133120 100%
xc: detail: delta 3ms, dom0 0%, target 0%, sent 1747Mb/s, dirtied
1747Mb/s 160 pages
xc: detail: Total pages sent= 131292 (0.99x)
xc: detail: (of which 0 were fixups)
xc: detail: All memory is saved
xc: detail: Save exit rc=0
migration target: Transfer complete, requesting permission to start domain.
migration sender: Target has acknowledged transfer.
migration sender: Giving target permission to start.
migration target: Got permission, starting domain.
migration target: Domain started successsfully.
migration sender: Target reports successful startup.
Migration successful.
root@xenturio1:/var/log/xen# cat xl-thiswillfail.log
Waiting for domain thiswillfail (domid 7) to die [pid 7475]
Domain 7 is dead
Done. Exiting now
root@xenturio2:/var/log/xen# cat xl-thiswillfail--incoming.log
Waiting for domain thiswillfail--incoming (domid 10) to die [pid 5162]
root@xenturio2:/var/log/xen# ps auxww |grep -v grep |grep "migrate-rec"
root 5162 0.0 0.0 36128 1592 ? Ssl 09:30 0:00 xl
migrate-receive
root@xenturio2:/var/log/xen# xl console thiswillfail
PM: early restore of devices complete after 0.071 msecs
PM: restore of devices complete after 14.727 msecs
Setting capacity to 10485760
Setting capacity to 2097152
root@thiswillfail:~# init 6
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal
Using makefile-style concurrent boot in runlevel 6.
Asking all remaining processes to terminate...done.
All processes ended within 1 seconds....done.
Stopping enhanced syslogd: rsyslogd.
Saving the system clock.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access
method.
Deconfiguring network interfaces...Internet Systems Consortium DHCP
Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:16:3e:7e:38:fb
Sending on LPF/eth0/00:16:3e:7e:38:fb
Sending on Socket/fallback
DHCPRELEASE on eth0 to 10.19.46.16 port 67
done.
Cleaning up ifupdown....
Deactivating swap...done.
Will now restart.
md: stopping all md devices.
Restarting system.
root@xenturio2:/var/log/xen# xl list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 4661 8 r-----
77471.3
root@xenturio2:/var/log/xen# ps auxww |grep -v grep |grep xl
root@xenturio2:/var/log/xen# cat xl-thiswillfail--incoming.log
Waiting for domain thiswillfail--incoming (domid 10) to die [pid 5162]
Domain 10 is dead
Action for shutdown reason code 1 is restart
Domain 10 needs to be cleaned up: destroying the domain
Done. Rebooting now
xc: error: 0-length read: Internal error
xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
xc: error: read: p2m_size (0 = Success): Internal error
######
# domU config
root@xenturio2:/var/log/xen# cat /mnt/vmctrl/xenconfig/thiswillfail.sxp
# generated using xen-tool
kernel = "/boot/vmlinuz-3.0-xenU"
ramdisk = "/boot/initrd.img-3.0-xenU"
name = "thiswillfail"
memory = "512"
vcpus = "2"
vif = [ 'bridge=vlanbr27','mac=fe:ff:00:1b:00:06,bridge=mgmtbr27' ]
disk = [
'phy:/dev/xen-data/thiswillfail-root,xvda1,w','phy:/dev/xen-data/thiswillfail-swap,xvda2,w'
]
root = "/dev/xvda1"
extra = "xencons=hvc0 console=hvc0"
This again goes for 2.3.39-xenU and 3.0.4-xenU.
I guess the core of the problem is somewhere around this:
>xc: error: 0-length read: Internal error
>xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error
>xc: error: read: p2m_size (0 = Success): Internal error
with best regards
andreas
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home