master@bradleyland.com
2005-Sep-15 16:23 UTC
[Xen-users] Is there a working FC4/multiple NIC recipe?
I''ve been usings Rik''s experimental 1454 RPMs and they work fine with the exception of multiple NICs in domU and some spurious ''xm list'' errors. Is there a known working combination that supports FC4 dom0/domU and multiple NICs in the domU? Right now, domU crashes when more than one NIC is specified -- apparently a known bug. I''m trying to build a domU firewall and that will require at least two physical NICs in the domU. I also plan on building a snort monitoring box in their somewhere as well. Thanks, Dave _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nivedita Singhvi
2005-Sep-15 18:07 UTC
Re: [Xen-users] Is there a working FC4/multiple NIC recipe?
master@bradleyland.com wrote:> I''ve been usings Rik''s experimental 1454 RPMs and they work fine with the > exception of multiple NICs in domU and some spurious ''xm list'' errors. > > Is there a known working combination that supports FC4 dom0/domU and > multiple NICs in the domU? Right now, domU crashes when more than one NIC > is specified -- apparently a known bug. > > I''m trying to build a domU firewall and that will require at least two > physical NICs in the domU. I also plan on building a snort monitoring box > in their somewhere as well.Did you really mean physical nics in domU? That isn''t yet supported at the moment for pci devices. The multiple virtual nics problem should be fixed fairly soon... thanks, Nivedita _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcus Brown
2005-Sep-16 00:16 UTC
Re: [Xen-users] Is there a working FC4/multiple NIC recipe?
Hi, Perhaps I''ve missed something. I believe multiple physical NICs and multiple bridges both work correctly (using 2.0.7 from source, anyway) eg. My Firewall config contains (overkill) pci = [''00,0b,0'', ''00,0a,0'' ] nics=11 vif = [ ''mac=aa:00:00:00:22:01, bridge=br10'', \ ''mac=aa:00:00:25:40:01, bridge=xen-br0'', \ ''mac=aa:00:00:25:40:09, bridge=br1'', \ ''mac=aa:00:00:25:40:17, bridge=br2'', \ ''mac=aa:00:00:25:40:25, bridge=br3'', \ ''mac=aa:00:00:25:40:33, bridge=br4'', \ ''mac=aa:00:00:25:40:49, bridge=br5'', \ ''mac=aa:00:00:25:40:45, bridge=br6'', \ ''mac=aa:00:00:25:40:73, bridge=br7'', \ ''mac=aa:00:00:25:40:81, bridge=br8'', \ ''mac=aa:00:00:25:40:97, bridge=br9'' ] So that''s 2 REAL nics and 11 virtual for the Firewall. Marcus. Nivedita Singhvi wrote:> master@bradleyland.com wrote: > >> I''ve been usings Rik''s experimental 1454 RPMs and they work fine with the >> exception of multiple NICs in domU and some spurious ''xm list'' errors. >> >> Is there a known working combination that supports FC4 dom0/domU and >> multiple NICs in the domU? Right now, domU crashes when more than one NIC >> is specified -- apparently a known bug. >> >> I''m trying to build a domU firewall and that will require at least two >> physical NICs in the domU. I also plan on building a snort monitoring box >> in their somewhere as well. > > > Did you really mean physical nics in domU? That isn''t > yet supported at the moment for pci devices. The multiple > virtual nics problem should be fixed fairly soon... > > thanks, > Nivedita_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
master@bradleyland.com
2005-Sep-16 00:52 UTC
Re: [Xen-users] Is there a working FC4/multiple NIC recipe?
Are you running 2.0.7 on FC4 with the latest updates? I haven''t tried anything other than the to-be 3.0 releases. Maybe I should run the stable version and wait for 3.0 to be released. I have "real" work I''d like to get done :). BTW, the thread below refers to the unstable release.> Hi, > Perhaps I''ve missed something. I believe multiple physical NICs and > multiple bridges both work correctly (using 2.0.7 from source, anyway) > > eg. My Firewall config contains (overkill) > pci = [''00,0b,0'', ''00,0a,0'' ] > nics=11 > vif = [ ''mac=aa:00:00:00:22:01, bridge=br10'', \ > ''mac=aa:00:00:25:40:01, bridge=xen-br0'', \ > ''mac=aa:00:00:25:40:09, bridge=br1'', \ > ''mac=aa:00:00:25:40:17, bridge=br2'', \ > ''mac=aa:00:00:25:40:25, bridge=br3'', \ > ''mac=aa:00:00:25:40:33, bridge=br4'', \ > ''mac=aa:00:00:25:40:49, bridge=br5'', \ > ''mac=aa:00:00:25:40:45, bridge=br6'', \ > ''mac=aa:00:00:25:40:73, bridge=br7'', \ > ''mac=aa:00:00:25:40:81, bridge=br8'', \ > ''mac=aa:00:00:25:40:97, bridge=br9'' ] > > So that''s 2 REAL nics and 11 virtual for the Firewall. > > Marcus. > > Nivedita Singhvi wrote: >> master@bradleyland.com wrote: >> >>> I''ve been usings Rik''s experimental 1454 RPMs and they work fine with >>> the >>> exception of multiple NICs in domU and some spurious ''xm list'' errors. >>> >>> Is there a known working combination that supports FC4 dom0/domU and >>> multiple NICs in the domU? Right now, domU crashes when more than one >>> NIC >>> is specified -- apparently a known bug. >>> >>> I''m trying to build a domU firewall and that will require at least two >>> physical NICs in the domU. I also plan on building a snort monitoring >>> box >>> in their somewhere as well. >> >> >> Did you really mean physical nics in domU? That isn''t >> yet supported at the moment for pci devices. The multiple >> virtual nics problem should be fixed fairly soon... >> >> thanks, >> Nivedita >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcus Brown
2005-Sep-16 03:28 UTC
Re: [Xen-users] Is there a working FC4/multiple NIC recipe?
master@bradleyland.com wrote:> Are you running 2.0.7 on FC4 with the latest updates?Debian> I haven''t tried > anything other than the to-be 3.0 releases. Maybe I should run the stable > version and wait for 3.0 to be released. I have "real" work I''d like to > get done :).Yes, I''ve got similar issues :)> > BTW, the thread below refers to the unstable release.OK I''m too far OT then :)> > >>Hi, >>Perhaps I''ve missed something. I believe multiple physical NICs and >>multiple bridges both work correctly (using 2.0.7 from source, anyway) >> >>eg. My Firewall config contains (overkill) >>pci = [''00,0b,0'', ''00,0a,0'' ] >>nics=11 >>vif = [ ''mac=aa:00:00:00:22:01, bridge=br10'', \ >> ''mac=aa:00:00:25:40:01, bridge=xen-br0'', \ >> ''mac=aa:00:00:25:40:09, bridge=br1'', \ >> ''mac=aa:00:00:25:40:17, bridge=br2'', \ >> ''mac=aa:00:00:25:40:25, bridge=br3'', \ >> ''mac=aa:00:00:25:40:33, bridge=br4'', \ >> ''mac=aa:00:00:25:40:49, bridge=br5'', \ >> ''mac=aa:00:00:25:40:45, bridge=br6'', \ >> ''mac=aa:00:00:25:40:73, bridge=br7'', \ >> ''mac=aa:00:00:25:40:81, bridge=br8'', \ >> ''mac=aa:00:00:25:40:97, bridge=br9'' ] >> >>So that''s 2 REAL nics and 11 virtual for the Firewall. >> >>Marcus. >> >>Nivedita Singhvi wrote: >> >>>master@bradleyland.com wrote: >>> >>> >>>>I''ve been usings Rik''s experimental 1454 RPMs and they work fine with >>>>the >>>>exception of multiple NICs in domU and some spurious ''xm list'' errors. >>>> >>>>Is there a known working combination that supports FC4 dom0/domU and >>>>multiple NICs in the domU? Right now, domU crashes when more than one >>>>NIC >>>>is specified -- apparently a known bug. >>>> >>>>I''m trying to build a domU firewall and that will require at least two >>>>physical NICs in the domU. I also plan on building a snort monitoring >>>>box >>>>in their somewhere as well. >>> >>> >>>Did you really mean physical nics in domU? That isn''t >>>yet supported at the moment for pci devices. The multiple >>>virtual nics problem should be fixed fairly soon... >>> >>>thanks, >>>Nivedita >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ve installed gcc32, removed the "tune=pentium4", and do a make CC=gcc32 HOSTCC=gcc32 world (or dist) and get the following error. What am I doing wrong?>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>xen/lowlevel/xc/xc.c: At top level: xen/lowlevel/xc/xc.c:1151: syntax error before ''*'' token xen/lowlevel/xc/xc.c: In function `PyXc_dealloc'': xen/lowlevel/xc/xc.c:1153: `xc'' undeclared (first use in this function) xen/lowlevel/xc/xc.c:1153: syntax error before '')'' token xen/lowlevel/xc/xc.c:1155: `self'' undeclared (first use in this function) xen/lowlevel/xc/xc.c: At top level: xen/lowlevel/xc/xc.c:1158: syntax error before "PyXcType" xen/lowlevel/xc/xc.c:1158: warning: type defaults to `int'' in declaration of `PyXcType'' xen/lowlevel/xc/xc.c:1159: warning: implicit declaration of function `PyObject_HEAD_INIT'' xen/lowlevel/xc/xc.c:1159: `PyType_Type'' undeclared here (not in a function) xen/lowlevel/xc/xc.c:1160: initializer element is not constant xen/lowlevel/xc/xc.c:1160: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1160: syntax error before numeric constant xen/lowlevel/xc/xc.c:1161: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1161: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1162: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1162: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1163: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1163: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1164: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1164: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1165: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1165: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1166: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1166: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1167: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1167: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1168: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1168: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1169: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1169: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1170: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1170: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1171: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1171: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1172: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1172: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1174: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1174: warning: (near initialization for `PyXcType'') xen/lowlevel/xc/xc.c:1174: warning: data definition has no type or storage class xen/lowlevel/xc/xc.c:1176: syntax error before "PyXc_methods" xen/lowlevel/xc/xc.c:1176: warning: type defaults to `int'' in declaration of `PyXc_methods'' xen/lowlevel/xc/xc.c:1177: warning: braces around scalar initializer xen/lowlevel/xc/xc.c:1177: warning: (near initialization for `PyXc_methods[0]'') xen/lowlevel/xc/xc.c:1177: warning: initialization makes integer from pointer without a cast xen/lowlevel/xc/xc.c:1177: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1177: warning: (near initialization for `PyXc_methods[0]'') xen/lowlevel/xc/xc.c:1177: `METH_VARARGS'' undeclared here (not in a function) xen/lowlevel/xc/xc.c:1177: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1177: warning: (near initialization for `PyXc_methods[0]'') xen/lowlevel/xc/xc.c:1177: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1177: warning: (near initialization for `PyXc_methods[0]'') xen/lowlevel/xc/xc.c:1178: warning: braces around scalar initializer xen/lowlevel/xc/xc.c:1178: warning: (near initialization for `PyXc_methods[1]'') xen/lowlevel/xc/xc.c:1178: warning: initialization makes integer from pointer without a cast xen/lowlevel/xc/xc.c:1178: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1178: warning: (near initialization for `PyXc_methods[1]'') xen/lowlevel/xc/xc.c:1178: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1178: warning: (near initialization for `PyXc_methods[1]'') xen/lowlevel/xc/xc.c:1178: warning: excess elements in scalar initializer xen/lowlevel/xc/xc.c:1178: warning: (near initialization for `PyXc_methods[1]'') xen/lowlevel/xc/xc.c:1179: warning: data definition has no type or storage class xen/lowlevel/xc/xc.c:1181: syntax error before "initxc" xen/lowlevel/xc/xc.c:1182: warning: return type defaults to `int'' xen/lowlevel/xc/xc.c: In function `initxc'': xen/lowlevel/xc/xc.c:1183: `PyObject'' undeclared (first use in this function) xen/lowlevel/xc/xc.c:1183: `m'' undeclared (first use in this function) xen/lowlevel/xc/xc.c:1183: `d'' undeclared (first use in this function) xen/lowlevel/xc/xc.c:1183: warning: left-hand operand of comma expression has no effect xen/lowlevel/xc/xc.c:1185: warning: implicit declaration of function `Py_InitModule'' xen/lowlevel/xc/xc.c:1187: warning: implicit declaration of function `PyModule_GetDict'' xen/lowlevel/xc/xc.c:1188: warning: implicit declaration of function `PyErr_NewException'' xen/lowlevel/xc/xc.c:1188: warning: assignment makes pointer from integer without a cast xen/lowlevel/xc/xc.c:1189: warning: implicit declaration of function `PyDict_SetItemString'' xen/lowlevel/xc/xc.c:1191: warning: assignment makes pointer from integer without a cast error: command ''gcc32'' failed with exit status 1 make[2]: *** [install] Error 1 make[2]: Leaving directory `/root/downloads/xen-2.0/tools/python'' make[1]: *** [install] Error 2 make[1]: Leaving directory `/root/downloads/xen-2.0/tools'' make: *** [tools] Error 2 [root@teegeeack xen-2.0]# _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nivedita Singhvi
2005-Sep-16 15:58 UTC
Re: [Xen-users] Is there a working FC4/multiple NIC recipe?
Marcus Brown wrote:> Hi, > Perhaps I''ve missed something. I believe multiple physical NICs and > multiple bridges both work correctly (using 2.0.7 from source, anyway)Yes, I was referring strictly to unstable. thanks, Nivedita> eg. My Firewall config contains (overkill) > pci = [''00,0b,0'', ''00,0a,0'' ] > nics=11 > vif = [ ''mac=aa:00:00:00:22:01, bridge=br10'', \ > ''mac=aa:00:00:25:40:01, bridge=xen-br0'', \ > ''mac=aa:00:00:25:40:09, bridge=br1'', \ > ''mac=aa:00:00:25:40:17, bridge=br2'', \ > ''mac=aa:00:00:25:40:25, bridge=br3'', \ > ''mac=aa:00:00:25:40:33, bridge=br4'', \ > ''mac=aa:00:00:25:40:49, bridge=br5'', \ > ''mac=aa:00:00:25:40:45, bridge=br6'', \ > ''mac=aa:00:00:25:40:73, bridge=br7'', \ > ''mac=aa:00:00:25:40:81, bridge=br8'', \ > ''mac=aa:00:00:25:40:97, bridge=br9'' ] > > So that''s 2 REAL nics and 11 virtual for the Firewall. > > Marcus. > > Nivedita Singhvi wrote: > >>master@bradleyland.com wrote: >> >> >>>I''ve been usings Rik''s experimental 1454 RPMs and they work fine with the >>>exception of multiple NICs in domU and some spurious ''xm list'' errors. >>> >>>Is there a known working combination that supports FC4 dom0/domU and >>>multiple NICs in the domU? Right now, domU crashes when more than one NIC >>>is specified -- apparently a known bug. >>> >>>I''m trying to build a domU firewall and that will require at least two >>>physical NICs in the domU. I also plan on building a snort monitoring box >>>in their somewhere as well. >> >> >>Did you really mean physical nics in domU? That isn''t >>yet supported at the moment for pci devices. The multiple >>virtual nics problem should be fixed fairly soon... >> >>thanks, >>Nivedita > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users