openSUSE Leap Documentation › Virtualization Guide › Managing Virtual Machines with libvirt › Starting and Stopping libvirtd
ContentsContents
Virtualization Guide
  1. About This Manual
  2. I Introduction
    1. 1 Virtualization Technology
    2. 2 Introduction to Xen Virtualization
    3. 3 Introduction to KVM Virtualization
    4. 4 Introduction to Linux Containers
    5. 5 Virtualization Tools
    6. 6 Installation of Virtualization Components
  3. II Managing Virtual Machines with libvirt
    1. 7 Starting and Stopping libvirtd
    2. 8 Guest Installation
    3. 9 Basic VM Guest Management
    4. 10 Connecting and Authorizing
    5. 11 Managing Storage
    6. 12 Managing Networks
    7. 13 Configuring Virtual Machines
  4. III Hypervisor-Independent Features
    1. 14 Disk Cache Modes
    2. 15 VM Guest Clock Settings
    3. 16 libguestfs
  5. IV Managing Virtual Machines with Xen
    1. 17 Setting Up a Virtual Machine Host
    2. 18 Virtual Networking
    3. 19 Managing a Virtualization Environment
    4. 20 Block Devices in Xen
    5. 21 Virtualization: Configuration Options and Settings
    6. 22 Administrative Tasks
    7. 23 XenStore: Configuration Database Shared between Domains
    8. 24 Xen as a High-Availability Virtualization Host
  6. V Managing Virtual Machines with QEMU
    1. 25 QEMU Overview
    2. 26 Setting Up a KVM VM Host Server
    3. 27 Guest Installation
    4. 28 Running Virtual Machines with qemu-system-ARCH
    5. 29 Virtual Machine Administration Using QEMU Monitor
  7. VI Managing Virtual Machines with LXC
    1. 30 Linux Containers
    2. 31 Migration from LXC to libvirt-lxc
  8. Glossary
  9. A Appendix
  10. B XM, XL Toolstacks and Libvirt framework
  11. C GNU Licenses
Navigation←→
openSUSE Leap Documentation › Virtualization Guide › Managing Virtual Machines with libvirt › Starting and Stopping libvirtd
Top
←→
Applies to openSUSE Leap 42.3

7 Starting and Stopping libvirtd

The communication between the virtualization solutions (KVM, Xen, LXC) and the libvirt API is managed by the daemon libvirtd, which needs to run on the VM Host Server. libvirt client applications such as virt-manager, possibly running on a remote machine, communicate with libvirtd running on the VM Host Server, which services the request using native hypervisor APIs. Use the following commands to start and stop libvirtd or check its status: 

tux > sudo systemctl start libvirtd

tux > sudo systemctl status libvirtd
libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled)
Active: active (running) since Mon 2014-05-12 08:49:40 EDT; 2s ago
[...]

tux > sudo systemctl stop libvirtd

tux > sudo systemctl status libvirtd
[...]
Active: inactive (dead) since Mon 2014-05-12 08:51:11 EDT; 4s ago
[...]

To automatically start libvirtd at boot time, either activate it using the YaST Services Manager module or by entering the following command: 

tux > sudo systemctl enable libvirtd
Important
Important: Conflicting Services: libvirtd and xendomains

In case libvirtd fails to start, check if the service xendomains is loaded: 

tux > systemctl is-active xendomains
active

In case the command returns active, you need to stop xendomains before you will be able to start the libvirtd daemon. In case you want libvirtd to also start after rebooting, you should additionally prevent xendomains from starting automatically by disabling the service: 

tux > sudo systemctl stop xendomains
tux > sudo systemctl disable xendomains
tux > sudo systemctl start libvirtd

xendomains and libvirtd provide the same service and when used in parallel may interfere with one another. As an example, xendomains may attempt to start a domU already started by libvirtd.

→Chapter 8 Guest Installation←Part II Managing Virtual Machines with libvirt
Print this page

© 2018 SUSE