[Xen-bugs] [Bug 1017] New: qemu-ifup "Could not initialize device 'tap'" if network-nat set

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1017

           Summary: qemu-ifup "Could not initialize device 'tap'" if
                    network-nat set
           Product: Xen
           Version: unstable
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HVM
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: rainer.feigl@xxxxxxxxxxxxxx


xen-3.1 on debian etch x86-64
xend-config.sxp
    (network-script 'network-nat netdev=eth0')
    (vif-script vif-nat)
win.cfg
    kernel  = '/usr/lib/xen/boot/hvmloader'
    builder = 'hvm'
    memory  = '512'
    device_model='/usr/lib/xen/bin/qemu-dm'
    disk    = [ 'phy:/dev/iwtdom0vg/win.interwebtiv.at-c,ioemu:hda,w' ]
    name = 'win'
    vif = ['type=ioemu, ip=10.0.0.50, vifname=wif_win']
    boot='c'
    vnc=1
    sdl=0
    on_poweroff = 'destroy'
    on_reboot   = 'restart'
    on_crash    = 'restart'

if i start the domain with
    xm create win.cfg
i got the following error in qemu-dm.xxx.log
    /etc/xen/qemu-ifup: could not launch network script
    Could not initialize device 'tap'

i got it working with this
    in qemu-ifup outcommented the last line
        #brctl addif $2 $1
    then started windows
    ifconfig vif_win down
    ifconfig tap0 10.0.0.177 netmask 255.255.255.255 up
    route add -host 10.0.0.50 dev tap0

the ip 10.0.0.177 for the tap0 is indicated from the ipadress + 127
this is also the gateway for windows
what finally helped me with some modifications was:
    http://lists.xensource.com/archives/html/xen-users/2006-12/msg00429.html
    http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=584

this was just for getting it working
i'll try to fix this directly in qemu-ifup :-)


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs