LPI 304-200 Dumps

qemu-info snapshots vm1.img

qemu-img snapshot -l vm1.img

qemu -hda snapshot -l vm1.img -noboot -list snapshots

qemu-snapshots -l vm1.img

qemu-monitor -snapshots -hda vm1.img

virsh list --volumes --pool vol1 --details

virsh vol-details vol1

virsh --show-pool vol1 --details

virsh vol-list vol1 --details

virsh volumes --source vol1–details

dmesg |grep -i intel|grep -i vt; dmesg |grep -i amd|grep -i v

egrep '(vmx|svm)' /proc/cpuinfo

xl dmesg | grep -i hvm

grep -i "Full Virtualization" /proc/xen

grep -i "Full Virtualization" /etc/xen/*

An extension to the Linux Kernel used to provide container virtualization similar to LXC and OpenVZ.

A library that provides access to several different virtualization technologies in a common manner.

A comprehensive management infrastructure for Linux-based virtualization.

An approach used to eliminate the need for virtualization called Zero-Virt.

A Linux-based hypervisor similar to KVM and Xen.

vif

eth

vnet

vbr

net

Emulation can only provide distinct hardware components but no complete virtual machines.

Emulation requires changes to the guest operating system.

Emulation reimplements a whole computing system in software.

Emulation allows operating systems to be run on foreign architectures.

Emulation is one of the most resource efficient virtualization techniques.

cat /proc/drdb/status

cat /proc/drdb

drbdadm dstate all

drbdadm diskstatus all

drbdadm state --disk all

Each GFS2 filesystem has exactly one journal.

Once a GFS2 filesystem is created, the number of journals cannot be changed.

Every node that simultaneously mounts the filesystem requires its own GFS2 journal.

Journals were heavily used in GFS and are deprecated and optional in GFS2.

The GFS Cluster Journal Daemon, GCJD, handles the journaling in a GFS2 cluster.

ocfs2.setprops

ocfs2tool

crm_edit

tunefs.ocfs2

o2cbtool

It segments the cluster nodes into several logical groups that are always fenced together.

It balances incoming TCP connections to a logical service to several backend nodes.

It makes logical volumes on shared storage available to all cluster nodes.

It allows several nodes to share file system locks in order to access the same files simultaneously.

OCFS2 is an integral part of Pacemaker and relies on Pacemaker services for functionality.

To avoid the need for shared storage, OCFS2 can replicate the content of its filesystems via the network.

When using OCFS2 with additional cluster software, OCFS2 must be integrated into the overall cluster manager to ensure consistent cluster behaviour.

OCFS2 can be used without any additional software as it contains its own cluster manager, O2CB.

In addition to filesystems, OCFS2 can handle other cluster services such as IP addresses and server daemons.

user

dlm

heartbeat

kernel

echo "1" > /proc/sys/net/ipv4/ip_forward

iptables -t nat -Z

ipvsadmin -L -n

ipmasq -A 192.168.10.1 -A 192.168.10.2 -p tcp --dport www -j DEMASQ

netstat -r

-1

0

1

FORCE

INFINITY

Failover clusters are not operational without at least one dedicated load balancer.

All response packages sent from a backend server to a client must pass through the load balancer.

The load balancer is usually deployed on one of the backend servers.

Load balancers may be able to analyze traffic.

All incoming connections to the cluster services are received by the load balancer.

The addresses of backend servers that were overloaded in the past and should be scheduled with a reduced priority.

The hostnames of the servers that, despite the remaining configuration, should always be scheduled by the Serial Operation Round Robin algorithm.

The addresses of backend servers that should not get assigned any new connections.

The default virtual host that is assigned to incoming HTTP requests missing a Host: header before forwarding them to a backend server.

The address of a server to which requests are redirected in case no real server is available.

persistent

weightedrr

source

leastconn

destination