This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 378] New: xm save deadlocks


           Summary: xm save deadlocks
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: ewan@xxxxxxxxxxxxx

>From Gerd Knorr:

"xm save" doesn't work for me, the command just blocks forever.  In the
process list it looks like this:

 6567 ?        Ssl    0:00 python /usr/sbin/xend restart
 7978 ?        SL     0:00  \_ /usr/lib/xen/bin/xc_save 14 17 10 0 0 0

xc_save is blocked, in a write call to stderr:

  master-xen root /vm/ttylinux# strace -p7978
  Process 7978 attached - interrupt to quit
  write(2, "FNI 28 : [10000004,815] pte=2b92"..., 80 <unfinished ...>
  Process 7978 detached

7977 seems to be responsible for the xc_save and does this:

  master-xen root /vm/ttylinux# strace -p7977
  Process 7977 attached - interrupt to quit
  read(20,  <unfinished ...>
  Process 7977 detached

fd 20 is the other end of the *stdout* pipe, whereas xc_save writes
stuff to *stderr*.  Hmm.  Maybe xend causes the deadlock by simply
reading from the wrong file handle?

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 378] New: xm save deadlocks, bugzilla-daemon <=