WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] More Xen troubles (with xend this time)

To: Jérôme Petazzoni <jp@xxxxxxxx>
Subject: Re: [Xen-devel] More Xen troubles (with xend this time)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 30 Nov 2004 14:09:50 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Nov 2004 14:10:54 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 30 Nov 2004 14:45:53 +0100." <41AC7991.80506@xxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
Unfortunately when a domain crashes it seems to confuse xend such that
it isn't even restartable. So then you need to reboot the
machine. Clearly this needs looking into. :-)

 -- Keir

> 
> When trying to reproduce a crash (when I do "xm restore foo.xen", the 
> restored VM crashed instantaneously), I hit the following "bug" (I hope 
> that the problem lies between my keyboard and my chair and that I didn't 
> find another real bug) :
> 
> I did restore the domain, then noticed it was crashed ("-----c" in xm 
> list). I tried to destroy it, but it didn't work. So I stopped xend, 
> restarted it ... And there it goes :
> 
> isnpro:~# xm list
> (111, 'Connection refused')
> Error: Error connecting to xend, is xend running?
> 
> isnpro:~# xend start
> 
> isnpro:~# xm list
> (111, 'Connection refused')
> Error: Error connecting to xend, is xend running?
> 
> isnpro:~# ps aux | grep x
> root       644  0.0  0.0     0    0 ?        S    Nov29   0:02 [xenblkd]
> root     14003  0.0  1.8  4308 1112 ?        S    14:37   0:00 xfrd
> 
> isnpro:~# lsof | grep LISTEN
> portmap     970      daemon    4u  IPv4       2122                TCP 
> *:sunrpc (LISTEN)
> exim4      1113 Debian-exim    0u  IPv4       2291                TCP 
> localhost:smtp (LISTEN)
> inetd      1119        root    4u  IPv4       2304                TCP 
> *:discard (LISTEN)
> inetd      1119        root    6u  IPv4       2306                TCP 
> *:daytime (LISTEN)
> inetd      1119        root    7u  IPv4       2307                TCP 
> *:time (LISTEN)
> sshd       1129        root    3u  IPv4       2329                TCP 
> *:ssh (LISTEN)
> rpc.statd  1135        root    6u  IPv4       2369                TCP 
> *:893 (LISTEN)
> xfrd      14003        root    2u  IPv4     274713                TCP 
> *:8002 (LISTEN)
> 
> isnpro:~# tail /var/log/xend.log
> [2004-11-30 14:17:00 xend] INFO (XendRoot:91) EVENT> xend.domain.exit 
> ['xipetotec', '22', 'crash']
> [2004-11-30 14:17:00 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy 
> ['xipetotec', '22']
> [2004-11-30 14:17:28 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:18:35 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:19:57 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:23:45 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:25:46 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:31:43 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:31:54 xend] INFO (SrvDaemon:607) Xend Daemon started
> [2004-11-30 14:37:40 xend] INFO (SrvDaemon:607) Xend Daemon started
> 
> (many "Xend Daemon started" messages since I tried many times to restart 
> it...)
> 
> So I thought that xfrd (xend?) was running on port 8002 instead of 8000, 
> and I tried to setup a redir (who knows!) :
> 
> isnpro:~# redir --cport 8002 --lport 8000  &
> [1] 14025
> isnpro:~# xm list
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 9, in ?
>     main.main(sys.argv)
>   File 
> "/root/Xen/xen-2.0-testing.bk/dist/install/lib/python/xen/xm/main.py", 
> line 795, in main
>   File 
> "/root/Xen/xen-2.0-testing.bk/dist/install/lib/python/xen/xm/main.py", 
> line 106, in main
>   File 
> "/root/Xen/xen-2.0-testing.bk/dist/install/lib/python/xen/xm/main.py", 
> line 124, in main_call
>   File 
> "/root/Xen/xen-2.0-testing.bk/dist/install/lib/python/xen/xm/main.py", 
> line 343, in main
> AttributeError: 'str' object has no attribute 'sort'
> 
> Okay, it seems it wasn't a very clever idea after all.
> 
> What should I try now ? (I don't want to reboot the thing yet, since the 
> virtual domains are still running and I can't stop them right now).
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel