Hi, Having a little trouble with networking in my domUs! I''m not doing anything fancy at all. My vif setting for the domUs is the default setting: vif = [ '''' ] In fact, the only thing I changed in the config file is the drive configuration so the things know where to boot from! For what its worth, dom0 is slackware 10.2. domU 1 is slack 10.1, domu 2 is slack 10.0. First time I set this up, things worked. "Great!", I thought. I happily skipped along to my second machine and replicated everything, ready to play with other domU setups. It came to testing the first domU... no networking. Checked my first box. Verified networking was ok in the domU, and rebooted. Checked again - it had stopped. I fired up another domU - again, so networking. Scratched my head - a lot. Rebooted again. Still nothing. I shut xen down (xend stop), ran "etc/rc.d/rc.inet1 restart" a few times. Then I fired up xend again, and my domU. I could ping again.>From I can tell, the device "peth0" had "gone missing" before.In a working configuration, I get: brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif7.0 In the non-working scenario, peth0 is not present - in "ifconfig" or in "brctl show". What am I doing wrong? Under what set of circumstances would peth0 disappear / not get created? I still can''t get this device to appear on the second test box... Any hints / tips gratefully received! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Try this to start bridges and peth devices manually /etc/xen/scripts/network-bridge vifnum=1 start - Padma -----Original Message---- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Dave Smif Sent: Thursday, June 22, 2006 9:41 AM To: xen-users@lists.xensource.com Subject: [Xen-users] Networking in domU Hi, Having a little trouble with networking in my domUs! I''m not doing anything fancy at all. My vif setting for the domUs is the default setting: vif = [ '''' ] In fact, the only thing I changed in the config file is the drive configuration so the things know where to boot from! For what its worth, dom0 is slackware 10.2. domU 1 is slack 10.1, domu 2 is slack 10.0. First time I set this up, things worked. "Great!", I thought. I happily skipped along to my second machine and replicated everything, ready to play with other domU setups. It came to testing the first domU... no networking. Checked my first box. Verified networking was ok in the domU, and rebooted. Checked again - it had stopped. I fired up another domU - again, so networking. Scratched my head - a lot. Rebooted again. Still nothing. I shut xen down (xend stop), ran "etc/rc.d/rc.inet1 restart" a few times. Then I fired up xend again, and my domU. I could ping again.>From I can tell, the device "peth0" had "gone missing" before.In a working configuration, I get: brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif0.0 peth0 vif7.0 In the non-working scenario, peth0 is not present - in "ifconfig" or in "brctl show". What am I doing wrong? Under what set of circumstances would peth0 disappear / not get created? I still can''t get this device to appear on the second test box... Any hints / tips gratefully received! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> -----Original Message---- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Dave Smif > Sent: Thursday, June 22, 2006 9:41 AM > To: xen-users@lists.xensource.com > Subject: [Xen-users] Networking in domU > > Hi, > > Having a little trouble with networking in my domUs! I''m not doing > anything fancy at all. My vif setting for the domUs is the default > setting: > > vif = [ '''' ] > > In fact, the only thing I changed in the config file is the drive > configuration so the things know where to boot from!Thanks both - I''ll take a look into those options. I did find another post in the archives with details similar to my own problem, and it appears to happen when a machine has more than 1 physical ethernet card. FWIW, if I stop Xen, stop networking, start Xen and then start networking - peth0 is created. If the networking is already running when I start xen, the result is that peth0 may or may not be created. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users