Feature pages are design documents that developers have created while collaborating on oVirt.

Most of them areoutdated, but provide historical design context.

They arenotuser documentation and should not be treated as such.

Documentation is available here.

Guest Agent SLES

oVirt Guest Agent on SLE[S] (SUSE Linux Enterprise [Server])

Summary

Owner

  • Name: Vinzenz ‘evilissimo’ Feenstra (Vfeenstr)

Current status

  • Last updated: ,

Done

Detailed Description

Porting the ovirt-guest-agent to SLE (SuSE Linux Enterprise) 11 SP3

Required changes

  • RC script for the ovirt-guest-agent daemon [DONE]
  • sudoers based elevation [DONE]
  • spec file according to SLE standards [DONE]
  • Path adjustments for the SLE environment [DONE]
  • Update package list to report for SUSE naming conventions [DONE]
  • Create wrapper scripts for elevated tasks [DONE]

Repository

Benefit to oVirt

Documentation / External references

The guest agent reports the following things

  • Current active user
  • Memory usage (including swap usage)
  • Network Interfaces
  • IP Addresses
  • FQDN of the guest OS
  • Disks Usage
  • Configured RPMs to report (see /etc/ovirt-guest-agent.conf for the packages)
  • Hostname

The guest agent also provides the following actions

  • Desktop Locking for GNOME
  • Shutdown/Reboot from within the Guest OS

Installation

# zypper addrepo http://download.opensuse.org/repositories/home:/evilissimo/SLE_11_SP3/home:evilissimo.repo # zypper refresh # zypper install ovirt-guest-agent-common # service ovirt-guest-agent start 

Testing

Verification

  • Follow the installation instructions above to install the guest agent
  • After about 15-30 seconds the Web Admin Portal entry for the VM should show:
    • the IPv4 Addresses of the VM in the grid
    • the FQDN of the VM in the grid
    • kernel package and the ovirt-guest-agent-common package in the application list
    • The FQDN in the general tab
    • Logged-in User: in the Sessions tab should be filled if a user is logged in.
    • All IPs (IPv4 and IPv6) in the Network Interfaces tab in the Guest Agent Data section for each interface.
  • Verification via on the VDSM side: `vdsClient -s 0 getVmStats \`
    • Reported fields are non-empty:
      • guestFQDN
      • netIfaces
      • disksUsage
      • memoryStats
      • guestName
      • appsList
      • guestOs
      • username
      • guestIPs (if there are IPv4 addresses)

Note: The VM UUID can be found on the Admin Portal in the General tab for the VM Note: The FQDN value is only only shown if the FQDN is not empty, not localhost and not localhost.localdomain