Package: qemu
Version: 0.9.1-1
Severity: normal

It seems to be impossible to have a tun/tap device already configured (e.g. in 
/etc/network/interfaces and the if-pre-up.d script from uml-utilities) but not 
yet open (i.e. no file descriptor), and have that device used by qemu.

I tried -nic tap,vlan=0,ifname=tap0,script=/bin/true, but that doesn't work.  
Instead I am now using qemu-start which opens /dev/net/tun, binds to tap0 (or 
whichever I choose) and then passes the file descriptor (using -nic 
tap,vlan=0,fd=<fd-from-opening-tun>) to qemu.

Is there any other way of having tap0 preconfigured and using it in qemu?

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages qemu depends on:
ii  bochsbios          2.3.5-1               BIOS for the Bochs emulator
ii  libasound2         1.0.15-3              ALSA library
ii  libc6              2.7-6                 GNU C Library: Shared libraries
ii  libgnutls13        2.0.4-3               the GNU TLS library - runtime libr
ii  libncurses5        5.6+20080203-1        Shared libraries for terminal hand
ii  libsdl1.2debian    1.2.13-2              Simple DirectMedia Layer
ii  openbios-sparc     1.0~alpha2+20080106-2 SPARC Open Firmware
ii  openhackware       0.4.1-3               OpenFirmware emulator for PowerPC
ii  proll              18-3                  JavaStation PROM 2.x compatible re
ii  vgabios            0.6a-3                VGA BIOS software for the Bochs an
ii  zlib1g             1:1.2.3.3.dfsg-11     compression library - runtime

Versions of packages qemu recommends:
ii  debootstrap                 1.0.8        Bootstrap a basic Debian system
ii  sharutils                   1:4.6.3-1    shar, unshar, uuencode, uudecode
ii  vde2                        2.2.0-pre2-1 Virtual Distributed Ethernet

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to