|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] two bridges with xen 3.2.0
hi, i keep trying until you guys find what the problem is....i read somewhere that instead of
"vif = [ 'bridge=eth0' , 'bridge=eth1' ]"
i should use something like
"vif0 = [ 'bridge=eth0' , 'bridge=eth1' ]"
the thing is that ifconfig only shows this:
*********
eth0 Link encap:Ethernet HWaddr 00:30:48:7E:9D:8E
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe7e:9d8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:779 errors:0 dropped:0 overruns:0 frame:0
TX packets:501 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:60508 (59.0 KiB) TX bytes:66287 (64.7 KiB)
eth1 Link encap:Ethernet HWaddr 00:30:48:7E:9D:8F
inet addr:192.168.2.200 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe7e:9d8f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:468 (468.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 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)
peth0 Link encap:Ethernet HWaddr 00:30:48:7E:9D:8E
inet6 addr: fe80::230:48ff:fe7e:9d8e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:991 errors:0 dropped:0 overruns:0 frame:0
TX packets:607 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:94602 (92.3 KiB) TX bytes:77779 (75.9 KiB)
Base address:0x2000 Memory:d8020000-d8040000
peth1 Link encap:Ethernet HWaddr 00:30:48:7E:9D:8F
inet6 addr: fe80::230:48ff:fe7e:9d8f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:882 (882.0 b)
Base address:0x2020 Memory:d8060000-d8080000
*********
I've tried all the possible ways to get the vifx.x i used to get in
older releases. have they also changed? we don't get vifxx devices anymore?
anyway... if try to replace vif with vif0, in the virtual machine, it actually runs, but gets stuck here: ******** XENBUS: Device with no driver: device/console/0 BIOS EDD facility v0.16 2004-Jun-25, 0 devices found EDD information not available. md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE.EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 176k freed Adding 4194296k swap on /dev/sda2. Priority:-1 extents:1 across:4194296kdevice-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver *********I guess this is the normal behaviour, because vif0 doesn't exist at all... isn't it? Thanks. En/na Jordi Moles Blanco ha escrit: Hi, the answer is ... the same!! with all the 3.0 and 3.1 releases i've always used the bridge this way,without any ip address at all.anyway... i've also tried to set the ip address before i perform de "xm create", just in case this had also changed, but it doesn't work either. i just used your line and put the correct ip addresses in my case, but it just doesn't work. i'm using debian etch. i've tried in a couple of servers, just to check if there was some particular problem with that machine, but found nothing. I've used etch to run xen 3.1.x releases for quite a while now, i don't see why it's not working now. i'm also using mdadm to build a raid-1 array for xen, to make sure that the virtual machines are always up. I don't think it has something to do whit it... but i prefer to give all the details so that you can say what it's wrong with my sytem. thank you. El dc 20 de 02 del 2008 a les 18:34 +0000, en/na Gareth Bult va escriure:Urm, I've never tried "not" giving it an IP/MAC in the vif= .. what happens if you add them as per my example? ----- Original Message ----- step 3.: "Jordi Moles" <jordi@xxxxxxxxx> To: "Gareth Bult" <gareth@xxxxxxxxxxxxx> Cc: xen-users@xxxxxxxxxxxxxxxxxxx Sent: 20 February 2008 18:11:16 o'clock (GMT) Europe/London Subject: Re: [Xen-users] two bridges with xen 3.2.0 Hi, i tried something new....i read somewhere that the problem now was that i had not installed hotplug on my debian.i did this: ******** # apt-get install hotplug S'està llegint la llista de paquets... Fet S'està construint l'arbre de dependÃncies... Fet Paquets suggerits: ifrename S'ELIMINARAN els segÃents paquets: initramfs-tools udev S'instalÂlaran els segÃents paquets NOUS: hotplug 0 actualitzats, 1 nous a instalÂlar, 2 a eliminar i 0 no actualitzats. Es necessita obtenir 67,3kB d'arxius. DesprÃs de desempaquetar s'alliberaran 971kB d'espai en disc. Voleu continuar [S/n]? Des:1 http://ftp.rediris.es etch/main hotplug 0.0.20040329-26 [67,3kB] 67,3kB descarregats en 1s (48,9kB/s) S'estan preconfigurant els paquets...(S'està llegint la base de dades ... hi ha 31229 fitxers i directoris instalÂlats actualment.)S'està desinstalÂlant initramfs-tools ... S'està desinstalÂlant udev ... ************************************************************** * Please reboot your system as soon as possible! * After removing udev the system may not be fully functional. ************************************************************** S'està seleccionant el paquet hotplug prÃviament no seleccionat.(S'està llegint la base de dades ... hi ha 31093 fitxers i directoris instalÂlats actualment.)S'està desempaquetant hotplug (de .../hotplug_0.0.20040329-26_all.deb) ... S'està configurant hotplug (0.0.20040329-26) ... x01glus01:/etc/udev/rules.d# ********The thing is that it removed 2 different paquets, "initramfs-tools" and "udev", which i don't if xen needs.anyway... after that, i keep getting the same error; ********** Error: Device 0 (vif) could not be connected. Hotplug scripts not working. ********** any idea?En/na Jordi Moles ha escrit: _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |