This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 29 Jul 2011 11:27:50 -0700
Delivery-date: Fri, 29 Jul 2011 11:27:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1773-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Comment #15 from konrad.wilk@xxxxxxxxxx  2011-07-29 11:27 -------

> This should now fire up; well, work correctly in networking too.
> "Do you see vifX.0 interface when you start
> the guest?"
> where should I see it?, in a console using xm create -c??

ifconfig -a

The vifX.0 should be created then moment you launch the guest. The virtbr
should be there all along.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>