search for: veth7

Displaying 13 results from an estimated 13 matches for "veth7".

Did you mean: veth
2006 Jul 07
4
VM boots BUT keep throwing: "INIT: Id "X" respawning too fast: disabled for 5 minutes"
...uration found for veth2 unused veth3 No configuration found for veth3 unused veth4 No configuration found for veth4 unused veth5 No configuration found for veth5 unused veth6 No configuration found for veth6 unused veth7 No configuration found for veth7 unused vif0.0 No configuration found for vif0.0 unused vif0.1 No configuration found for vif0.1 unused vif0.2 No configuration found for vif0.2 unused vif0.3 No configurat...
2007 Jul 02
4
eth0 does not exist when booting to xen kernel
Hi everyone. I am pretty new to xen, but am having an issue that I can''t seem to crack. I am running the 2-6-16 kernel on Debian Etch. If I boot into the Etch kernel, everything works as it should. When I boot into the Xen kernel, eth0 no longer exists. >From what I understand, the network-bridge script will down my eth0, create a new virtual eth0 and bridge it into xenbr0
2006 Jan 10
0
Lots of IFs in /proc/net/dev
...0 0 0 0 0 0 0 0 0 veth6: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 vif0.7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 veth7: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth0: 9841949 9077 0 0 0 0 0 0 318824 3929 0 0 0 0 0 0 eth1: 0 0 0 0 0 0 0 0...
2006 Sep 05
0
Problem with network-bridge script and veth0
...nloopbacks=<N>); if the driver is compiled statically into the kernel, then you may set the parameter using loopback.nloopbacks=<N> on the domain 0 kernel command line. I have checked the script and it fails because I don''t have any veth0 interface. I have interfaces veth1 to veth7, but I don''t have any veth0, so if I run the same command with parameter vifnum=1 (for example) it works, because it uses veth1 instead of veth0 and add it to the new bridge (although it seems that this is not really necessary, because if I remove veth? from the bridge, networking still wo...
2006 Jun 20
9
no eth0 on guest
Hi, I''ve setup a box with xen. For the root machine, it''s ok, it see the network card: alian@yoda:~> /sbin/lspci ... 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 Gigabit Ethernet Controller (rev 19) alian@yoda:~> lsmod .... sk98lin 208748 1 alian@yoda:~> /sbin/ifconfig eth0 Lien encap:Ethernet HWaddr 00:15:F2:39:D4:DF
2006 Feb 20
3
vif0.0/veth0 or eth0
When does vif0.0 get created? Is there some shell magic? I''m trying to figure out how to do a similar peth1/veth1 split for eth1. -- Nicholas Lee http://stateless.geek.nz gpg 8072 4F86 EDCD 4FC1 18EF 5BDD 07B0 9597 6D58 D70C _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2006 Jan 20
3
domU Device eth0 does not seem to be present
...qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 15: veth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 16: vif0.7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 17: veth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 18: peth0: <BROADCAST,MULTICAST,NOARP,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 19: sit0: <NOARP> mtu 1480 qdisc noop link/sit...
2006 Aug 30
0
ping out of domU OK ping in to domU not OK
...Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth7 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX b...
2007 Apr 28
13
Need help setting up guest''s networking
...ncap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth7 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:...
2017 Nov 01
2
Centos and xen network bridge issue
...Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth7 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX b...
2006 Jan 28
3
Shorewall/Xen setup (correct from-address this time)
...qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 17: veth6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 18: vif0.7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 19: veth7: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 20: xenbr0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 21: vif1.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue link...
2006 Jul 07
7
[PATCH] xenconsole fix
xenconsole fix. reference of tty->count in xencons_close() is racy. It must be protected by tty_sem semaphore like con_close() in drivers/char/vt.c -- yamahata _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2008 Jun 06
32
Dedicate Nic''s to DomU''s
Hey all I''m new to Linux and Virtualizing. I''m trying to dedicate my nic''s to each virtual server. For instance, virt server A would use nic1 and virt server B would use nic2 and so on. I''ve been reading some stuff for this list and to tell you the truth I''m a bit overwhelmed. We are going to run SLES10.1 and Xen. I would appreciate any assistance.