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

[Wensheng Wang <wenshengwang@xxxxxxxxx>]

That works, thank you for fixing it.

Today I noticed another case of this when I tried to create a domU:
Device 0 (vif) could not be connected. Hotplug scripts not working

I got it when I don't specify vif in my domU config file or when I
specify but incorrectly had a xen-br0(should be xenbr0) in vif line.
If I correctly specify vif,  that errer goes away.


Wensheng Wang


On 11/8/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
> On Mon, Nov 07, 2005 at 12:34:20AM -0600, Wensheng Wang wrote:
>
> > 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
>
> This was assigned bug #387, and is now fixed, as of changeset
> 7651:7e3faea076ec.
>
> Cheers,
>
> Ewan.
>

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