[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Trouble creating DomU with 2 NICs



Hey folks,

I created a DomU, installed Linux, and then realized I'd only given it
1 NIC so brought it down to edit the cfg file to give it another NIC.

Originally I just had :

vif = ['']

And so I guess the defaults worked for the 1 NIC.   So I changed it to :

vif = 
['mac=00:1e:68:8e:31:b8,bridge=xenbr0','mac=00:1e:68:8e:31:b9,bridge=xenbr1']

Where those MAC addresses are from the bridge in dom0, as seen here :

My Dom0 has :

eth0      Link encap:Ethernet  HWaddr 00:1e:68:8e:31:b8
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:524414 errors:0 dropped:0 overruns:0 frame:0
          TX packets:519320 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:450798894 (450.7 MB)  TX bytes:362453554 (362.4 MB)
          Interrupt:18 Memory:dffe0000-e0000000

eth1      Link encap:Ethernet  HWaddr 00:1e:68:8e:31:b9
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:126552 errors:0 dropped:395 overruns:0 frame:0
          TX packets:188670 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15672743 (15.6 MB)  TX bytes:234429457 (234.4 MB)
          Interrupt:19 Memory:dffa0000-dffc0000

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:65536  Metric:1
          RX packets:91690 errors:0 dropped:0 overruns:0 frame:0
          TX packets:91690 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:444750187 (444.7 MB)  TX bytes:444750187 (444.7 MB)

xenbr0    Link encap:Ethernet  HWaddr 00:1e:68:8e:31:b8
          inet addr:192.168.160.11  Bcast:192.168.160.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:68ff:fe8e:31b8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:425590 errors:0 dropped:0 overruns:0 frame:0
          TX packets:310648 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:321506246 (321.5 MB)  TX bytes:346274373 (346.2 MB)

xenbr1    Link encap:Ethernet  HWaddr 00:1e:68:8e:31:b9
          inet addr:10.246.159.41  Bcast:10.246.159.255  Mask:255.255.255.0
          inet6 addr: fe80::21e:68ff:fe8e:31b9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:117018 errors:0 dropped:40 overruns:0 frame:0
          TX packets:46216 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11644847 (11.6 MB)  TX bytes:224274081 (224.2 MB)

But when I try to bring this up I get :

root@solexa1:/etc/xen# xl create /etc/xen/openfreezer.cfg
Parsing config from /etc/xen/openfreezer.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000017c328
  TOTAL:         0000000000000000->000000017f800000
  ENTRY ADDRESS: 0000000000100608
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000004
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 8
device model: spawn failed (rc=-3)
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge add [504] exited with error status 1
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus:
/etc/xen/scripts/vif-bridge add [527] exited with error status 1
libxl: error: libxl_create.c:1099:domcreate_attach_pci: unable to add
nic devices
libxl: error: libxl_dm.c:1245:libxl__destroy_device_model: Device
Model already exited
root@solexa1:/etc/xen#


-- 
“Don't eat anything you've ever seen advertised on TV”
         - Michael Pollan, author of "In Defense of Food"

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.