Bug 1035121

Summary: Explicitly document adding virsh based VMs to Beaker
Product: [Retired] Beaker Reporter: Nick Coghlan <ncoghlan>
Component: DocAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 0.14CC: jdanek, qwan, tflink, tools-bugs
Target Milestone: future_maintKeywords: Documentation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1004622 Environment:
Last Closed: 2020-10-21 14:12:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1004622    
Bug Blocks:    

Description Nick Coghlan 2013-11-27 06:37:43 UTC 
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
Comment 2 Dan Callaghan 2014-12-12 02:08:23 UTC 
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.
Comment 3 Amit Saha 2015-04-08 05:34:31 UTC 
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
Comment 4 Amit Saha 2015-04-08 05:37:48 UTC 
(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