Similar problem for me. I set up the following tap device $ cat /etc/network/interfaces <<<< # Loopback device: auto lo iface lo inet loopback
# device: eth0 auto eth0 iface eth0 inet static address x.x.x.x broadcast x.x.x.x netmask x.x.x.x gateway x.x.x.x # default route to access subnet up route add -net x.x.x.x netmask x.x.x.x gw x.x.x.x eth0 auto tap0 iface tap0 inet manual tunctl_user root uml_proxy_arp x.x.x.x uml_proxy_ether eth0 up ip link set tap0 up post-up sysctl -w net.ipv4.ip_forward=1 post-up sysctl -w net.ipv4.conf.tap0.proxy_arp=1 pre-down sysctl -w net.ipv4.ip_forward=0 down ip link set tap0 down >>>> When i start the virtual domain, the following happens: $ sudo virsh start windows-sbs <<<< Connecting to uri: qemu:///system error: Failed to start domain windows-sbs error: internal error unable to start guest: /etc/qemu-ifup: could not launch network script qemu: Could not initialize device 'tap' >>>> Even when use the "ugly fix" this error persists. I can call /etc/qemu- ifup as a normal user so there should be no problem with acces rights. I also get the same error when i delete /etc/qemu-ifup or comment out its content. What can i do to avoid this error? -- qemu -net nic -net tap does not start due to qemu-ifXXX scripts https://bugs.launchpad.net/bugs/475327 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
