qemu.tests: new case to check guest clock with syscall

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: add timedrift_check_clock_offset cfg

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: add check clock offset when vm crash/bsod

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: add cfg for check clock offset when guest bsod/crash

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: new case to check clock offset after hotplug vcpus

check guest clock drift less that $acceptable_offset after online/offline
hotpluged vcpus;

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: cfg for checking clock offset after hotplug vcpu

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: check kvm-clock using newer msr set

Signed-off-by: Xu Tian <xutian@redhat.com>
qemu.tests: cfg for kvm-clock newer msrs support check test

Signed-off-by: Xu Tian <xutian@redhat.com>
virttest: add interface to save lvm object to env file

register lvm object to env file when use lvm storage, and restore it at
postprocess to clean up new volumes when "force_remove_image = yes";
virttest: LVM storage base module

Signed-off-by: Xu Tian <xutian@redhat.com>
virttest: add emulated lvm support

Signed-off-by: Xu Tian <xutian@redhat.com>
virttest: add lvm storage support for qemu tests

Signed-off-by: Xu Tian <xutian@redhat.com>
shared.cfg: add params for supporting lvm partiton

Signed-off-by: Xu Tian <xutian@redhat.com>
virttest.qemu_vm: Log information about the parent PID and the monitor name.

When starting the qemu process, there is not much information about
the running parent PID (the autotest shell script that starts qemu) or
the monitor name that we are trying to connect (for example, hmp1).

So with this commit we're logging this information when qemu is started,
in order to provide information for debugging. Example:

When running  ./run -t qemu --tests=uptime --qemu_sandbox=on

From debug.log:

11:43:17 INFO | Created qemu process with parent PID 15592
11:43:17 INFO | Connecting to monitor 'hmp1'
11:44:17 WARNI| Could not find (qemu) prompt after connecting to monitor. Output so far: ''
11:44:18 ERROR| Could not connect to monitor 'hmp1'
11:44:18 DEBUG| Destroying VM virt-tests-vm1 (PID 15594)

Parent PID is 15592, now we are trying to find what is wrong...

ps -ef | grep 15592
rmoura   15592 15591  0 11:43 pts/3    00:00:00 /bin/bash -c source /tmp/autotestbMRLRL.sh
rmoura   15594 15592  0 11:43 pts/3    00:00:00 [qemu-system-x86] <defunct>

In this situation, it's clear that qemu-system-x86_64 goes bad.

Signed-off-by: Ruda Moura <rmoura@redhat.com>
Merge pull request #1049 from ruda/qemu-vm-monitor-logs

virttest.qemu_vm: Log information about the parent PID and the monitor n...
Merge pull request #908 from xutian/lvm_support

Add lvm support for qemu tests
Merge pull request #974 from xutian/add_timedrift_case

qemu.tests: new case to check guest clock offset
libvirt_vm: Add method to create install cmd with sec_label

Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
Add test for svirt in virt-install.

Signed-off-by: yangdongsheng <yangds.fnst@cn.fujitsu.com>
guest-os: Add filter for svirt_install in guest-os.

Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>