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, djmagee@mageenet.net
Subject: Re: After switching from "xm" to "xl" toolstack, can't get Guest networking to work.
Date: Sun, 22 Jan 2012 09:11:16 -0800	[thread overview]
Message-ID: <1327252276.343.140661026559797@webmail.messagingengine.com> (raw)
In-Reply-To: <CAPLaKK5YKuAAG+TL=JjWk7EbSrxiRC1hHFWtr5VwLtRo6Z6-SQ@mail.gmail.com>

Hi Roger.

Here is "ifconfig -a" output from the DomU when launched with xm.

xm create test.cfg
xm list
 Name                                        ID   Mem VCPUs      State  
 Time(s)
 Domain-0                                     0  1010     1     r-----  
  913.4
 template                                     1  2048     2     -b----  
   86.0
xm console template
 ...
ifconfig -a
 eth0      Link encap:Ethernet  HWaddr 00:16:3E:12:34:01
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:38658 errors:0 dropped:24935 overruns:0 frame:0
           TX packets:11009 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:2621879 (2.5 Mb)  TX bytes:10432153 (9.9 Mb)
 
 eth0:1    Link encap:Ethernet  HWaddr 00:16:3E:12:34:01
           inet addr:192.168.1.32   Bcast:192.168.1.255 
           Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
 lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:7 errors:0 dropped:0 overruns:0 frame:0
           TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:563 (563.0 b)  TX bytes:563 (563.0 b)


And, "ifconfig -a" output from the DomU when launched with xl.

xl create test.cfg
xl list
 Name                                        ID   Mem VCPUs      State  
 Time(s)
 Domain-0                                     0  1010     1     r-----  
    66.8
 template                                     1  2048     2     -b----  
     6.8

ifconfig -a
 eth0      Link encap:Ethernet  HWaddr 00:16:3E:12:34:01
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 b)  TX bytes:5241 (5.1 Kb)
 
 eth0:1    Link encap:Ethernet  HWaddr 00:16:3E:12:34:01
           inet addr:192.168.1.32   Bcast:192.168.1.255 
           Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 
 lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:52 errors:0 dropped:0 overruns:0 frame:0
           TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:4431 (4.3 Kb)  TX bytes:4431 (4.3 Kb)

> Also paste the output from "xenstore-ls -fp" on the Dom0 when the xl
> DomU is up and running. From what I saw above in /var/log/messages the
> problem seem to be related to hotplug scripts.

Here is the paste of that output. ===> http://pastebin.com/s0e03VnW


On Sun, Jan 22, 2012, at 10:49 AM, djmagee@mageenet.net wrote:
> You're missing the opening single quote on your vif line.

That's just a copy/paste typo in the email.

Regards,

Erin

  reply	other threads:[~2012-01-22 17:11 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
2012-01-22  0:54     ` erin.balid
2012-01-22 11:08     ` Roger Pau Monné
2012-01-22 17:11       ` erin.balid [this message]
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=1327252276.343.140661026559797@webmail.messagingengine.com \
    --to=erin.balid@inoutbox.com \
    --cc=djmagee@mageenet.net \
    --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).