Splitting out the documentation of adding virsh systems from bug 1004622 +++ This bug was initially created as a clone of Bug #1004622 +++ I recently installed beaker and there are a few things that would have been nice to have in those docs: - requirements for power configuration on virthosts (ssh keys, polkit changes etc.) - configuration of VMs to use with beaker (set to boot from network, hd and power settings for virsh) A lot of this is discussed in the dev env setup guide [1] but would be useful to have it in the main install documentation. --- Additional comment from Amit Saha on 2013-09-05 14:52:37 EST --- Tim, thanks for reporting these. (In reply to Tim Flink from comment #0) > - requirements for power configuration on virthosts (ssh keys, polkit > changes etc.) Could you describe the polkit changes that you needed to do? I don't remember having to do any when I setup/wrote the docs for Fedora. --- Additional comment from Tim Flink on 2013-09-05 15:46:34 EST --- (In reply to Amit Saha from comment #2) > Could you describe the polkit changes that you needed to do? I don't > remember having to do any when I setup/wrote the docs for Fedora. It's not so much a "have to" as I chose not to use root on the virthost. Add the file /etc/polkit-1/rules.d/10-libvirt.rules which contains: polkit.addRule(function (action, subject) { if (action.id == "org.libvirt.unix.manage" && subject.isInGroup("kvm")) return polkit.Result.YES; }); then add the remote user to the kvm group and you don't need to have passwordless root access to the virthosts
Something else to cover in the doc: the guests should have a serial console (not a virtio-console!) and then set console=ttyS0 in install options.
The "Setting up a Beaker test bed" guide assumes that the server, lab controller and the test VMs are all on the same network. However, if the test VMs are on a different host and using NAT, it is also needed to load the "nf_nat_tftp" module ("modprobe nf_nat_tftp") on the libvirt host to allow the guests to PXE boot successfully from the lab controller's tftp server. [1] https://beaker-project.org/dev/guide/virtual-fedora/#setup-lab-controller
(In reply to Amit Saha from comment #3) > The "Setting up a Beaker test bed" guide assumes that the server, lab > controller and the test VMs are all on the same network. s/network/libvirt host