Dear Xen wranglers, I have the following problem: Hardware: - HP ProLiant ML150 G3 Software: - Ubuntu Linux "Feisty Fawn" (7.04) AMD64 edition - Xen 3 (Ubuntu packages) I successfully installed Xen 3, and dom0 is running fine (without apparent errors), even on the Tigon3 network chip (see attached dom0-eth0.txt excerpt from dmesg) using the Ubuntu kernel 2.6.19-4-generic-amd64 (as per dmesg). I had some trouble setting up a HVM based VM, but I finally mastered it, and was able to install the following OS: - domU: Ubuntu Linux "Feisty Fawn" (7.04) i386 edition, from the netboot mini.iso, using Linux kernel 2.6.20-15-generic. I failed installing the amd64 mini.iso as Ubuntu barked at me with some errors. The reason to use this 7.04 edition is because using the LiveCD results in a blank screen for some technical reasons (Intel not properly virtualising some VBE commands?) However, the mini.iso booted fine, and I was able to install Ubuntu 7.04. Note that the installation accessed the Internet to download the packages from the Ubuntu GB archive. The installation finished, and I rebooted the VM (after switching the boot order to the "harddrive"). Rebooting goes fine, and I can attach a VNCviewer and watch my VM boot up. :-) However, and this is the downside, the VM brings up only the loopback device. The VM exports the virtual eth0 as RTL8139, but trying to bring up eth0 manually results in the following error: ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ---------- mdrescher@baseline-vm:~$ sudo ifup eth0 Password: eth0: ERROR while getting interface flags: No such device SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ---------- Unfortunately, as I don''t have network and my vncViewer does''nt capture screens, I have to describe the dmesg output of domU: According to the dmesg output, the RTL8139too Fast Ethernet driver v0.9.28 is loaded, which detects an "enhanced" 8139C+ chip (?) so it will use the 8139cp driver for improved performance (well, well...) Later, the driver says "unknown chip version, assuming RTL-8139" Can you help me out getting the following issues resolved? a) Getting networking up (obviously) using the real Tigon3 driver or something emulating b) When booting domU from the mini.iso, networking went just fine, but why? b) When trying to export the disk image as "ioemu:sda" the domU Ubuntu 7.04 mini.iso wasn''t able to find the disk, probably because lacking an appropriate kernel module? Thanks, and any help is much appreciated! Attached TEXT files: - dom0-eth0-txt: Excerpt from dom0 dmesg output related to eth0 - test.hvm: My HVM VM config file I''m using. Cheers, Michel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Michel Drescher wrote:> Dear Xen wranglers, > > I have the following problem: >> ---- 8< ----> > However, and this is the downside, the VM brings up only the loopback > device. The VM exports the virtual eth0 as RTL8139, but trying to bring up > eth0 manually results in the following error: > > ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ---------- > mdrescher@baseline-vm:~$ sudo ifup eth0 > Password: > eth0: ERROR while getting interface flags: No such device > SIOCSIFADDR: No such device > eth0: ERROR while getting interface flags: No such device > SIOCSIFNETMASK: No such device > eth0: ERROR while getting interface flags: No such device > Failed to bring up eth0. > ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP ---------- > > Unfortunately, as I don''t have network and my vncViewer does''nt capture > screens, I have to describe the dmesg output of domU: > > According to the dmesg output, the RTL8139too Fast Ethernet driver v0.9.28 > is loaded, which detects an "enhanced" 8139C+ chip (?) so it will use the > 8139cp driver for improved performance (well, well...) > Later, the driver says "unknown chip version, assuming RTL-8139" > > Can you help me out getting the following issues resolved? > a) Getting networking up (obviously) using the real Tigon3 driver or > something emulating > b) When booting domU from the mini.iso, networking went just fine, but why?You have to specify the mac address in the vif=... line of the domU config file. As you don''t, the mac address is asigned a new random mac on each boot. This is the reason why the network works correctly during the install, but fails after the reboot: the system doesn''t know about this *new* network device. You should be able to know the mac you have been assigned during the install by looking in the file /etc/udev/rules.d/z25_persistent-net.rules I''ve already been hit by this feature ;) HTH Didier> b) When trying to export the disk image as "ioemu:sda" the domU Ubuntu 7.04 > mini.iso wasn''t able to find the disk, probably because lacking an > appropriate kernel module? > > Thanks, and any help is much appreciated! > > Attached TEXT files: > - dom0-eth0-txt: Excerpt from dom0 dmesg output related to eth0 > - test.hvm: My HVM VM config file I''m using. > > > Cheers, > Michel > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Didier Trosset-Moreau Agilent Technologies Geneva, Switzerland _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Didier Trosset wrote:> Michel Drescher wrote: >> Dear Xen wranglers, >> >> I have the following problem: >> >> ---- 8< ---- >> >> However, and this is the downside, the VM brings up only the loopback >> device. The VM exports the virtual eth0 as RTL8139, but trying to >> bring up >> eth0 manually results in the following error: >> >> ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP >> ---------- >> mdrescher@baseline-vm:~$ sudo ifup eth0 >> Password: >> eth0: ERROR while getting interface flags: No such device >> SIOCSIFADDR: No such device >> eth0: ERROR while getting interface flags: No such device >> SIOCSIFNETMASK: No such device >> eth0: ERROR while getting interface flags: No such device >> Failed to bring up eth0. >> ---------- SNIP ---------- SNIP ---------- SNIP ---------- SNIP >> ---------- >> >> Unfortunately, as I don''t have network and my vncViewer does''nt capture >> screens, I have to describe the dmesg output of domU: >> >> According to the dmesg output, the RTL8139too Fast Ethernet driver >> v0.9.28 >> is loaded, which detects an "enhanced" 8139C+ chip (?) so it will use the >> 8139cp driver for improved performance (well, well...) >> Later, the driver says "unknown chip version, assuming RTL-8139" >> >> Can you help me out getting the following issues resolved? >> a) Getting networking up (obviously) using the real Tigon3 driver or >> something emulating >> b) When booting domU from the mini.iso, networking went just fine, but >> why? > > You have to specify the mac address in the vif=... line of the domU > config file. As you don''t, the mac address is asigned a new random mac > on each boot. This is the reason why the network works correctly during > the install, but fails after the reboot: the system doesn''t know about > this *new* network device.Alright, this sounds logical, but ...> You should be able to know the mac you have been assigned during the > install by looking in the file /etc/udev/rules.d/z25_persistent-net.rules... while I have the directory "/etc/udev/rules.d/", I do *not* have the file "25-persistent-net.rules". :-( I tried other rules I found in this directory, but none seem even remotely related to the network... :-/ Do I have to reinstall domU? Hopefully not... Cheers, Michel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2007/5/22, Michel Drescher <Michel.Drescher@uk.fujitsu.com>: [cut] can you post an lspci of your machine? -- Alessandro R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Alessandro R. wrote:> 2007/5/22, Michel Drescher <Michel.Drescher@uk.fujitsu.com>: > > [cut] > > can you post an lspci of your machine?Sure, here it comes (attached). Cheers and thanks, Michel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2007/5/23, Michel Drescher <Michel.Drescher@uk.fujitsu.com>:> > 07:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev02) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ You are lucky :-) try to put in you hvm conf file this ne2000=1 Which version of xen are you running? -- Alessandro R. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Alessandro R. wrote:> 2007/5/23, Michel Drescher <Michel.Drescher@uk.fujitsu.com>: >> >> 07:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X >> Gigabit Ethernet (rev > 02) > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > You are lucky :-) > > try to put in you hvm conf file this > > ne2000=1 > > Which version of xen are you running? >*ARGH* *pulling my hair out* I am running Xen 3.0.3, Ubunty 7.04 Server AMD64 edition prepackaged. It is important to note that this odd behaviour also happened when using an Intel PRO 1000 adapter... However, I wiped the system, installed Ubunty 7.04 i386, and are just about to create the first guest VM... Cheers, Michel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users