qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 589827] [NEW] QEMU netdev tap type id name is not used


From: JP Senior
Subject: [Qemu-devel] [Bug 589827] [NEW] QEMU netdev tap type id name is not used on linux host
Date: Fri, 04 Jun 2010 18:40:53 -0000

Public bug reported:

Tested with 0.12.3, 0.12.4, and latest git as of 4 jun 2010.
The new -netdev type seems to ignore manual specifications of tap ifname.

    qemu-system-x86_64 -hda disk.img -netdev tap,id=ids_e0 -device 
e1000,netdev=ids_e0
 **creates tap0 instead of ids_e0.  tap0 passes traffic, ids_e0 doesn't exist
(I tried -netdev type=tap as well for brevity)

QEMU creates a tap0 (or appropriate) interface and does not name this
"ids_e0" as would be expected.  I also tried 'pre' creating the tap
interface.

Previous alterantive was
    qemu-system-x86_64 -hda disk.img -net nic,model=e1000,vlan=99 -net 
tap,ifname=ids_e0,vlan=99 
  **creates ids_e0 as expected, and passes traffic as expected.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
QEMU netdev tap type id name is not used on linux host
https://bugs.launchpad.net/bugs/589827
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

Status in QEMU: New

Bug description:
Tested with 0.12.3, 0.12.4, and latest git as of 4 jun 2010.
The new -netdev type seems to ignore manual specifications of tap ifname.

    qemu-system-x86_64 -hda disk.img -netdev tap,id=ids_e0 -device 
e1000,netdev=ids_e0
 **creates tap0 instead of ids_e0.  tap0 passes traffic, ids_e0 doesn't exist
(I tried -netdev type=tap as well for brevity)

QEMU creates a tap0 (or appropriate) interface and does not name this "ids_e0" 
as would be expected.  I also tried 'pre' creating the tap interface.

Previous alterantive was
    qemu-system-x86_64 -hda disk.img -net nic,model=e1000,vlan=99 -net 
tap,ifname=ids_e0,vlan=99 
  **creates ids_e0 as expected, and passes traffic as expected.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]