xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: erin.balid@inoutbox.com
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Sat, 21 Jan 2012 15:04:02 -0800	[thread overview]
Message-ID: <1327187042.28621.140661026352253@webmail.messagingengine.com> (raw)
In-Reply-To: <CAPLaKK6izAoCF=TtYK=OxEvNOFvKLOrpg+iMSBfyQb0UaS3c3Q@mail.gmail.com>

Hi Roger,

On Sat, Jan 21, 2012, at 11:57 PM, Roger Pau Monné wrote:
> 2012/1/21  <erin.balid@inoutbox.com>:
> >  vif=[mac=00:16:3e:12:34:01, bridge=br0  , vifname=vifBR']
> 
> The xl toolstack present in version 4.1.2 doesn't support vifname[0]
> (newer versions do), so I think if you remove that it should be ok.
> 
> [0] http://lists.xen.org/archives/html/xen-users/2011-12/msg00225.html

That looked hopeful.

I changed

 - vif=[mac=00:16:3e:12:34:01, bridge=br0  , vifname=vifBR']
 + vif=[mac=00:16:3e:12:34:01, bridge=br0']

and launched again.  I still ended up with no attached VIF interface.

brctl show
 bridge name     bridge id               STP enabled     interfaces
 br0             8000.0052351d5337       yes             eth0

xl list-vm template
 UUID                                  ID    name
 7d46ca9a-9d86-476e-948d-3eddf5d070e4  4    test

xl network-list template
 Idx BE Mac Addr.         handle state evt-ch   tx-/rx-ring-ref BE-path
 0   0  00:16:3e:12:34:01      0     4     15   768/769        
 /local/domain/0/backend/vif/4/0

And, I still can't ping just like my orginal post.

:-(

Regards,

Erin

  reply	other threads:[~2012-01-21 23:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 20:06 After switching from "xm" to "xl" toolstack, can't get Guest networking to work erin.balid
2012-01-21 22:57 ` Roger Pau Monné
2012-01-21 23:04   ` erin.balid [this message]
2012-01-22  0:54     ` erin.balid
2012-01-22 11:08     ` Roger Pau Monné
2012-01-22 17:11       ` erin.balid
2012-01-22 17:28         ` Roger Pau Monné
2012-01-22 17:54           ` erin.balid
2012-01-24 23:13             ` Jim Fehlig
2012-01-25  2:01               ` erin.balid
2012-01-25 15:55                 ` Jim Fehlig
2012-01-25 16:27                   ` erin.balid
2012-01-25 16:47                     ` Jim Fehlig
2012-01-22 15:49 ` djmagee
2012-01-23 11:27 ` Ian Campbell
2012-01-23 15:28   ` erin.balid
2012-01-24 14:26     ` Ian Campbell
2012-01-24 15:56       ` erin.balid
2012-01-24 16:41         ` Ian Campbell
2012-01-24 17:10           ` erin.balid
2012-01-24 18:05             ` erin.balid
2012-01-24 18:19               ` erin.balid
2012-01-24 21:20                 ` Ian Campbell
2012-01-24 21:20               ` Ian Campbell
2012-01-24 21:44                 ` erin.balid
2012-01-25  3:59                   ` erin.balid
2012-01-25  9:35                   ` Ian Campbell
2012-01-25 16:19                 ` Jim Fehlig
2012-01-25 16:32                   ` Ian Campbell
     [not found] <mailman.1527.1327510060.1471.xen-devel@lists.xensource.com>
2012-01-25 17:06 ` John McDermott CIV
2012-01-25 17:16   ` Ian Campbell
2012-01-25 17:22     ` John McDermott CIV
2012-01-25 17:33     ` Jim Fehlig
2012-01-25 17:39       ` John McDermott CIV
2012-01-25 18:02         ` Jim Fehlig
2012-01-25 19:20           ` John McDermott CIV
2012-01-25 21:16             ` Jim Fehlig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1327187042.28621.140661026352253@webmail.messagingengine.com \
    --to=erin.balid@inoutbox.com \
    --cc=roger.pau@entel.upc.edu \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).