[SOLVED] Qemu kvm : No eth0 inside a Slackware-13.0 guest, although listed in lspci and lsmod

Linux.tar.gz · 02-08-2010, 04:46 AM

Hi !

Just installed a 13.0 32 bit inside a 13.0 64 bit.
I use qemu-kvm-0.12.2
In the guest, lspci shows me the 8139 card, and the module 8139too seems well-loaded.
But typing ifconfig -a gives me nothing.

Any idea why?

Chuck56 · 02-08-2010, 07:23 AM

That's an unusual situation you have going on. Would you provide a bit more information? What is your qemu-kvm startup command and the output from the vm's lspci and lsmod?

ponce · 02-08-2010, 07:37 AM

maybe you got to use a different -net option when launching qemu.
in my enviroment I launch it with option "-net user": this is the full string I use for launching a vm

Code:

qemu -nographic -net nic,model=e1000 -smp 2 -net user -hda /spazio/qemu_images/slackcurrent.raw -m 1024 -redir tcp:5052:10.0.2.108:22 -boot c

in this example I gave the vm 2 cpus and, to use it with console login in nographic mode, I redirected connection to port 5052 to the internal ssh port of the vm to which I gave address 10.0.2.108 (default -net user gives you a gateway on 10.0.0.2, a dns server on 10.0.2.3 and a working dhcp server for that virtual lan), then I connect to the vm with

Code:

ssh -p 5052 user@localhost

(it should work also with the ip address of your host)

Linux.tar.gz · 02-08-2010, 08:22 AM

qemu-system-x86_64 -hda slack.img -m 1024 -vga std -usb -usbdevice tablet -localtime -cdrom /dev/sr0

lspci shows the realtek 8139 card, and lsmod shows that the module 8139too is loaded.
I see also that 8139 is a 8139C+
I will try another module.

Linux.tar.gz · 02-08-2010, 08:57 AM

Ok i figured it out !
I had to rmmod 8139too and loaded 8139cp instead, and now it works !!!

Thank you all !

Chuck56 · 02-08-2010, 09:05 AM

Quote:

Originally Posted by Linux.tar.gz

Ok i figured it out !
I had to rmmod 8139too and loaded 8139cp instead, and now it works !!!

Thank you all !

Glad you figured it out!

I'm still wondering what's different in your setup that required you to manually unload/load modules? Are you running stable or current in the VM?

Linux.tar.gz · 02-08-2010, 11:12 AM

I'm using 13.0 32 bit stable as guest.
Indeed, it's strange that the wrong module is loaded by default.
I installed all except X related stuff (KDE, fltk, x, xap ...) and kernel sources. I didn't installed TeX too.

Chuck56 · 02-08-2010, 11:35 AM

I've not seen that condition either. I'm running bridged ethernet on the hosts with tap interfaces on the guests in both production and dev environments.

My production hosts are running slackware64-13.0 generic kernels with the stock 2.6.29.6 kvm modules and qemu-kvm-0.12.1.2. The guests are all slackware32-13.0 generic kernels.

My dev host is running slackware64-13.0 generic kernel with kvm-kmod-2.6.32.7 and qemu-kvm-0.12.2. It runs stable and current guests both 32 and 64 bit.

disturbed1 · 02-08-2010, 04:53 PM

Quote:

Originally Posted by Linux.tar.gz

Ok i figured it out !
I had to rmmod 8139too and loaded 8139cp instead, and now it works !!!

Thank you all !

It's blacklisted in /etc/modprobe.d/blacklist

Code:

# Alternate 8139 driver.  Some 8139 cards need this specific driver,
# though...
blacklist 8139cp

hemp4fuel · 02-08-2010, 06:36 PM

I had the exact same problem as the original poster, with the same fix, in a Slackware 13 32bit guest on Slackware64 13.