Hi Neobiker! On Sat, 14 Nov 2009, Neobiker wrote:
> you can try this, maybe it helps: > http://www.ctserver.org/fpost18412.html#18412 > > Edit File /etc/businfotab and try ethconfig -a > > r...@efw23rc1:~ # cat /etc/businfotab > # Generated by ethconfig > eth0 XEN-eth0 > eth1 XEN-eth1 On my system, it looks like this: ,---- [ /etc/businfotab ] | # Generated by ethconfig | eth0 00:00.0 | eth1 00:01.0 | eth2 00:02.0 | eth3 00:03.0 `---- I'm pretty sure that the PCI-IDs didn't change, since they are generated by Xen (they look different on the host system). And I also tried "Restore to factory defaults", that didn't help either. Anyway: my Dom0 still was Debian Etch (Xen 3.0.2). I updated to Debian Lenny (Xen 3.2) because I wanted to reinstall the complete Xen setup, including the virtual machines. My new CPU supports Vanderpool, so I thought I should be able to run a DomU without a modified kernel. Just for fun, I started the Endian DomU after the upgrade, and... it worked! I have no idea why (and that really bugs me), but it's working again. Before my update, a fresh setup Debian DomU was working, too. So the Dom0-setup wasn't broken, either. At least not completely... Whatever: thanks for your help! Ciao, Ronald. -- Ronald Schaten :: http://www.schatenseite.de -- Write a wise saying and your name will live forever. (Anonymous) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
