Re: [Xen-devel] could not reboot domU in latest xen-unstable

[Wensheng Wang <wenshengwang@xxxxxxxxx>]

Hi, Ewan,
Thank for for the help.

I looked at my /var/log/message
The last line when the xend unable to restart domain is:
Nov  7 00:08:07 m8 logger: /etc/xen/scripts/block: xenstore-read
backend/vbd/2/2049/type failed.

I attached part of xend.log file,  the timeline in that log file is:
23:57:47 machine booted
00:05:21 xm create fc4
00:06:07 xm shutdown -R fc4
1minute after, I did a "xm list", it hangs, another minute later, the
prompt came back showing only domain-0


I also find if I interrupt that "xm list" after domU reboot, then do a
"xend restart", the domainU will shown paused. When I unpause it, it
will be in "r" state forever, even though in reality it doesn't exist
anymore.

My base system is fedora core 4.  gcc version is 4.01(20050727).

A side note is I copied /usr/lib/python/xen to
/usr/lib/python2.4/site-packages/ (the default python package location
on my system)  to get rid of "unable to read memory/target" warning( I
think it just warning, it doesn't seems to affecting anything).  
Though I don't think this has anything to do with the problem I have.

I hope I can provide more detail,  but I don't know whereelse to look,
 If you give me some pointer I can get more information.

thanks

Wensheng Wang



On 11/6/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
> On Sun, Nov 06, 2005 at 09:22:18AM +0000, Ewan Mellor wrote:
>
> > On Sun, Nov 06, 2005 at 01:30:20AM -0600, Wensheng Wang wrote:
> >
> > The seconday problem you have is that Xend is behaving badly when this first
> > error occurs, and I shall look into that.
>
> I've assigned this secondary problem #384.  I'll let you investigate the
> primary problem a little further before filing it.
>
> Cheers,
>
> Ewan.
>

Attachment: xend.log
Description: Binary data

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