Package: qemu
Version: 0.6.1+20050407-1
Followup-For: Bug #290569
Hi,
the TUN/TAP network interface doesn't work in the (my) Debian version of
qemu. There is no DHCP server present and configuring the network manually
doesn't help in any guest os.
Using -user-net makes the built-in DHCP server work and I can ping myself
and the DHCP server. But I need the TUN/TAP interface :)
An IRC log about my problem:
<seebyr> hi, host OS is Linux with tun/tap in kernel and qemu-ifup (su
-c "/sbin/ifconfig $1 172.20.0.1") is in /etc, I am asked for a password
and ethereal is able to sniff on tun0, but network isn't really working
in my guest OS. What could it be?
<pbrook> Are you using the debian qemu packages?
<seebyr> tested with Debian's 0.6.1+20050407-1 and 0.6.1-1
<seebyr> pbrook, yes
<pbrook> They have a broken bios.
<seebyr> hm, vgabios 0.5a-1
<seebyr> should I switch to the official vgabios? ;) ...or another
version? or another bios?
<pbrook> It's teh main bios that's the problem, not the vgabios.
<seebyr> ah ok
<seebyr> so I should compile qemu from source ;)
<pbrook> Either use the binary tarball from the qemu website, or build
your own qemu from cvs.
<seebyr> thank you ;)
So compiling the current upstream version solved the problem but I hope
it will be fixed for upcoming Debian packages.
best regards,
Stephan Beyer
PS: I added a reply and did not open a new bug because it *could* be
caused by the same problem.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Versions of packages qemu depends on:
ii bochsbios 2.1.1+20041109-3 BIOS for the Bochs emulator
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libsdl1.2debi 1.2.7+1.2.8cvs20041007-4.1 Simple DirectMedia Layer
ii vgabios 0.5a-1 VGA BIOS software for the Bochs an
ii zlib1g 1:1.2.2-4 compression library - runtime
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
