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

Re: [Xen-users] Error "Device 0 (vif) could not be connected"


  • To: wei huang <huanwei@xxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Two KHz <twokhz@xxxxxxxxx>
  • Date: Tue, 8 Nov 2005 22:09:36 +0530
  • Delivery-date: Tue, 08 Nov 2005 16:39:55 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=RD0X1xCcS3k3Yj2KkLTf696hz8H0P561VDitxEdjf66ZssZ55McCqU5ksUNgpJsIqg5viLmUG2JoZ6Nx3QXWkxMURnL7wdOIsDFtmE4pJJ28d6HqHC5te8lSxmIfbaYfh9PRhvIY81IqPoijb+MkmsbC6J3Jqw0SBPRs/dlskTU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Oh, me too the same issue, simple path.......
Now its working fine...
Thanks Wei for that point..

Regards,

On 11/8/05, wei huang <huanwei@xxxxxxxxxxxxxxxxxx> wrote:
Thanks for all your suggestions!

Actually it turns out to be quite a silly mistake. I use sudo to run all
those commands. brctl is located in /usr/local/sbin, which is in my local
PATH but not in root's. I only check the path under my own account.
However the boot scripts encounters a 'command not found'... I redirect
the output and find this.

Now though I still get some problem with domU's file system, at least I
can go through the initial stage.

Thanks!

Regards,
Wei Huang


> wei huang wrote:
>
> > And I find entry like this in /var/log/messages after xm create fails:
> >
> > Nov  7 20:40:56 c5xen kernel: e100: peth0: e100_watchdog: link up, 100Mbps, full-duplex
> > Nov  7 20:40:56 c5xen kernel: ip_tables: (C) 2000-2002 Netfilter core team
> > Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering learning state
> > Nov  7 20:40:57 c5xen kernel: xenbr0: topology change detected,
> > propagating
> > Nov  7 20:40:57 c5xen kernel: xenbr0: port 2(peth0) entering forwarding state
> > Nov  7 20:41:44 c5xen ntpd[3633]: synchronized to LOCAL(0), stratum 10
>
> > Nov  7 20:42:47 c5xen logger: /etc/xen/scripts/vif-bridge: brctl addif xenbr0 vif1.0 failed
>
> Well, that would be the fatal failure.
>
> You seem to have created bridges successfully so assuming you have brctl
> on your system. But try doing the above step (adding the interface to the
> bridge) manually.
>
> Also, put a set -x in your /etc/xen/scripts/network-bridge and
> /etc/xen/scripts/vif-bridge script, and post their output found
> in /var/log/xen-debug.log. Could be an older version of brctl
> which doesn't return status (?).
>
> thanks,
> Nivedita
>
>
>
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Nov  7 20:42:48 c5xen ntpd[3633]: synchronized to 80.28.46.78, stratum 2
> > Nov  7 20:43:52 c5xen ntpd[3633]: kernel time sync enabled 0001
> >
> > This is the only problem I can find. Would you please give more
> > suggestions?
>
>
> thanks,
> Nivedita
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>


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

_______________________________________________
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®.