Didn't seem to help -- the output looks the same.
Code:
$ newgrp kvm
$ kvm-bridge -hda winXP3.img -boot c -m 512
“Bringing up interface tap2 with mac address DE:AD:BE:EF:34:21”
warning: could not open /dev/net/tun: no virtual network emulation
Could not initialize device 'tap'
$
$ sudo kvm-bridge -hda winXP3.img -boot c -m 512
[sudo] password for tomy:
“Bringing up interface tap3 with mac address DE:AD:BE:EF:19:46”
+ [ -n tap3 ]
+ /usr/bin/sudo /usr/sbin/tunctl -u tomy -g kvm -t tap3
TUNSETIFF: Device or resource busy
+ /usr/bin/sudo /sbin/ip link set tap3 up
+ sleep 0.5s
+ /usr/bin/sudo /usr/sbin/brctl addif br0 tap3
+ exit 0
TUNSETIFF: Device or resource busy
/etc/kvm-ifdown: could not launch network script
$
sudo kvm-bridge [options] works fine in spite of the "resource busy" and "could not launch" messages.
________________________________________________
Update: By adding kvm-bridge to /etc/sudoers (using visudo) I no longer have to enter my password. My addition to /etc/sudoers is now:
Code:
# Allow members of the kvm group to configure a bridged virtual network interface
%kvm ALL=(ALL) NOPASSWD: /sbin/ifconfig, /usr/sbin/brctl, /usr/sbin/tunctl, /bin/kvm-bridge
Bookmarks