[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xm save question



To follow up... it seems the issue is due to xend not closing the save file (see attached). An ls of /proc/<xend-pid>/fd shows about 20 open files with a single domU. I then did a save, restore and save of the same domU (to files "/root/sxps/save-a" and "/root/sxps/save-b" respectively) and it seems that xend is not closing the file - either after a save or a restore.

This is on xen-unstable bits, built from the source tarball dated 9/25/05.

Pat

p.s. FWIW, I am able to do the save to a named pipe. Once I updated my system w/ the above tarball, I could restore the domain.

--
Patrick O'Rourke
porourke@xxxxxxxxxxx
[root@laurel sxps]# ls -l /proc/3177/fd | sort -n --key=9,9
lrwx------  1 root root 64 Sep 26 13:28 0 -> /dev/null
total 20
lrwx------  1 root root 64 Sep 26 13:28 1 -> /dev/null
l-wx------  1 root root 64 Sep 26 13:28 2 -> /var/log/xend-debug.log
lrwx------  1 root root 64 Sep 26 13:28 3 -> socket:[10264]
lrwx------  1 root root 64 Sep 26 13:28 5 -> socket:[10266]
l-wx------  1 root root 64 Sep 26 13:28 6 -> /var/log/xend.log
lrwx------  1 root root 64 Sep 26 13:28 7 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 8 -> socket:[10268]
lrwx------  1 root root 64 Sep 26 13:28 9 -> /proc/xen/privcmd
lr-x------  1 root root 64 Sep 26 13:28 10 -> /dev/urandom
lrwx------  1 root root 64 Sep 26 13:28 11 -> socket:[10308]
lrwx------  1 root root 64 Sep 26 13:28 12 -> socket:[10314]
lrwx------  1 root root 64 Sep 26 13:28 13 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 14 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 15 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 16 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 17 -> socket:[10323]
lrwx------  1 root root 64 Sep 26 13:28 18 -> /proc/xen/privcmd
lrwx------  1 root root 64 Sep 26 13:28 19 -> socket:[11076]
lrwx------  1 root root 64 Sep 26 13:28 20 -> socket:[17370]

after save (xm save 1 save-a)

l-wx------  1 root root 64 Sep 26 13:30 21 -> /root/sxps/save-a
lrwx------  1 root root 64 Sep 26 13:30 22 -> socket:[19184]
lrwx------  1 root root 64 Sep 26 13:30 25 -> socket:[19189]

after restore (xm restore save-a)

l-wx------  1 root root 64 Sep 26 13:30 21 -> /root/sxps/save-a
lrwx------  1 root root 64 Sep 26 13:30 22 -> socket:[19184]
lrwx------  1 root root 64 Sep 26 13:30 23 -> socket:[19344]
lr-x------  1 root root 64 Sep 26 13:30 24 -> /root/sxps/save-a
lrwx------  1 root root 64 Sep 26 13:30 25 -> socket:[19189]
lrwx------  1 root root 64 Sep 26 13:30 26 -> socket:[19712]

after second save (xm save 2 save-b)

l-wx------  1 root root 64 Sep 26 13:30 21 -> /root/sxps/save-a
lrwx------  1 root root 64 Sep 26 13:30 22 -> socket:[19184]
lrwx------  1 root root 64 Sep 26 13:30 23 -> socket:[19344]
lr-x------  1 root root 64 Sep 26 13:30 24 -> /root/sxps/save-a
lrwx------  1 root root 64 Sep 26 13:30 25 -> socket:[19189]
lrwx------  1 root root 64 Sep 26 13:30 26 -> socket:[19712]
lrwx------  1 root root 64 Sep 26 13:33 27 -> socket:[22116]
l-wx------  1 root root 64 Sep 26 13:33 28 -> /root/sxps/save-b
lrwx------  1 root root 64 Sep 26 13:33 29 -> socket:[22289]
lrwx------  1 root root 64 Sep 26 13:35 30 -> socket:[24055]
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.