On Sun, Nov 30, 2014 at 02:40:30PM -0600, Bruce Dubbs wrote: > Lfs User wrote: > >To use -net nic -net tap (bridging) with qemu as a user I had to also: > > > >chgrp kvm /sbin/ip /usr/sbin/brctl /usr/bin/qemu-system-x86_64 > >setcap cap_net_admin=eip /usr/sbin/brctl > >setcap cap_net_admin=eip /usr/bin/qemu-system-x86_64 > >setcap cap_net_admin=eip /sbin/ip > > > >This requires libcap. I don't use pam. > > > >I could not get bridging working with dhcpcd (in the host), it kept > >timing out. I had to use a static ip address as in the example in the > >book. dhcpcd works fine in the VM. > > Is there a requirement to run qemu as a non-root user? The capabilities are > really in root's domain. >
Running it as a user seems like the correct thing to do. We already say | You will need a dedicated group that will contain users (other than |root) allowed to access the KVM device. Add the group by running the |following command as the root user: | |groupadd -g 61 kvm Note that although I did build bridge-utils and the bootscript on the machine where I initially tried qemu [ I've now moved to another machine to get disk space for images! ], in the mistaken belief that I would need it "to connect to the local network" as the book says, I did not need it. From my qemu session without breidge-utils I can ssh to, and mount nfs shares from, my server. What I obviously cannot do is talk to the host system. But for that, scp'ing to the server (or copying to an nfs mount that they can both use) works fine. On the machine where I originally tested, dhclient works fine in the host with the bridge-utils bootcript enabled. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
