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 1017] qemu-ifup "Could not initialize device 'tap'" if n

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1017] qemu-ifup "Could not initialize device 'tap'" if network-nat set
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Tue, 10 Jul 2007 12:46:24 -0700
Delivery-date: Tue, 10 Jul 2007 12:47:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1017-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/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Comment #1 from rainer.feigl@xxxxxxxxxxxxxx  2007-07-10 12:46 -------
couldnt fix this in qemu-ifup.
seems that tap0 doesn't exist at the time the script is executed.
the vif also seems to be created after the execution of qemu-ifup
i gave up on this and created a script which i execute manually after starting
the vm.
i named it win_post with the following content:
ifconfig vif_win down
ifconfig tap0 netmask up
route add -host dev tap0

and made it executable
chmod 744 win.interwebtiv.at_post

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>