Thanks for the detailed bug report, although I don't think this really qualifies as a bug.
This is a QEMU FAQ: | I'm using a kernel >=2.6.18 and am having problems with tun/tap and QEMU | http://www.kidsquid.com/cgi-bin/moin.cgi/FrequentlyAskedQuestions#head-2511814cb92c14dbe1480089c04f83c281117a86 (Btw, I'm using a slightly adapted version of that script myself -- obviously you want to change it to run kvm and not qemu). I haven't got a plan for what to do about this yet. It seems that giving the qemu/kvm binary cap_net_admin re-opens the hole that the kernel patch fixed to begin with. On the other hand, requiring kvm users to have sudo access is just as bad. Perhaps on '/etc/init.d/kvm start', automatically create one or more interfaces for each user in the kvm group? #!/bin/sh for user in `grep ^kvm: /etc/group | cut -d : -f 4 | tr , ' '`; do tunctl -u ${user} -t tap-${user}0 #tunctl -u ${user} -t tap-${user}1 #tunctl -u ${user} -t tap-${user}2 done This is the kind of task that virt-manager [1] may be more suited to handle at some level. [1] http://virt-manager.et.redhat.com/index.html Thanks for the perror() suggestion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
