Conventions

In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "These ioctls() fundamentally map to the system KVM level, VM level, and vCPU level ."

A block of code is set as follows:

switch (run->exit_reason) {
        case KVM_EXIT_IO:
              DPRINTF("handle_io\n");
                /* Called outside BQL */
              kvm_handle_io(run->io.port, attrs,
                            (uint8_t *)run + run->io.data_offset,
                          run->io.direction,
                      	    run->io.size,
                      	    run->io.count);
              ret = 0;
            break;

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

include/linux/kvm_host.h : 

struct kvm {
      struct mm_struct *mm; /* userspace tied to this vm */
      struct kvm_vcpu *vcpus[KVM_MAX_VCPUS];
      struct kvm_io_bus *buses[KVM_NR_BUSES];
      struct kvm_coalesced_mmio_ring *coalesced_mmio_ring;
}

Any command-line input or output is written as follows:

#git clone git://git.qemu-project.org/qemu.git

New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "If you want to connect to the remote hypervisor, check Connect to remote host and fill the details."

Note

Warnings or important notes appear in a box like this.

Tip

Tips and tricks appear like this.