On Sat, Feb 23, 2008 at 09:38:02PM -0600, Charles Duffy wrote:
I have a few issues with <interface type='ethernet'>:
- The requirement that either
(1) the tap device already exists and has a constant name, or
(2) the tap device can be created by the current user without
privilege escalation
doesn't work for places where the user wants to
- dynamically generate tap devices
- ...but is running kvm without privileges to do so.
(this is particularly likely now that write privileges to
/dev/net/tap are not enough, and the user needs CAP_NET_ADMIN to
create a tap device).
[snip]
So -- does the proposed syntax extension look reasonable?
Being able to specify an qemu-ifdown script is reasonable, since we already
support an qemu-ifup script, but I don't want to just add that without
a clearer understanding of exactly what type of network config you are
trying to achieve. So rather than describing a desired implementation can
you describe the deployment scenario / level of network connectivity you're
trying to provide.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules:
http://search.cpan.org/~danberr/ -=|
|=- Projects:
http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|