QA » openQA Project » openQA Tests

For details about the requested guests see Fate #319284

Created FATE#320778: "Support HyperV driver in libvirt". Otherwise there's no way to connect to hyperv.

Still with ESX and HyperV we don't have a VNC on the hypervisor by default. Microsoft and VMware have their native solutions (RDP, and 'VMware Remote Console', respectively) in this regard. We might use RDP with FreeRDP, unlike VMware Remote Console which is so far supported on Windows and OS X only.

It seems to me that there's no way to test SLES on VMware in openQA.

1. For JeOS deployment or SLES install from DVD I need a VNC connection to the SUT ("the VM itself"). But I don't have it as VMware does not provide a VNC service on the hypervisor.
2. Network installation on VMware is impossible as it does not support direct kernel boot (kernel + initrd get stripped from the XML on virsh create time).
3. VNC/SSH installation from DVD is impossible because kernel arguments like "sshd=1" or "vnc=1" needs to be provided but that's not possible as there's no VNC.

Perhaps it's possible to do DVD installation with 'VMware Remote Console' on Windows but (1) I don't have access to it, and (2) I am not sure we want to have Windows in the mix.

Let me know if there's a SLES-install vector I omitted here.

Can't 1, 2, and 3 all be resolved by using Direct Kernel Boot?

https://libvirt.org/formatdomain.html#elementsOSKernel

I've used this approach on VMware before, as well as other scenarios where all seemed equally impossible (Debian to openSUSE conversions on bare metal with no IPMI or other management channel)

https://en.opensuse.org/SDB:Remote_installation
https://en.opensuse.org/SDB:Linuxrc

I was wrong claiming "there's no VNC on VMware", there is (RemoteDisplay.vnc.* in VMX file) - though the only reference for "VNC on VMware" on the Internet is.. libvirt tests. So at least JeOS and installs from DVD seems to be possible.

Ad "Direct Kernel Boot": libvirt strips

<os>
    ...
    <kernel>/var/lib/libvirt/images/openQA-SUT-1.kernel</kernel>
    <initrd>/var/lib/libvirt/images/openQA-SUT-1.initrd</initrd>
</os>

on define time (verified by dumpxml). Do you know of any other way?

Current status¶

JeOS works on KVM, Xen (both), VMware; net install works on KVM and Xen (VMware does not support direct kernel boot); installation from DVD is pending. Polishing is needed.

HyperV¶

FATE#320424 requests support of following host environments wrt HyperV: Microsoft Windows 2008 SP2+, 2008 R2 SP1+, 2012+, 2012 R2+, and 2016 (once released). However 'hyperv' driver from libvirt supports only Windows Server 2008 R2 (and perhaps - presumably - the 2008 R1, see https://libvirt.org/drvhyperv.html), WS2008R2 is now in extended support only. There's no way to communicate with WS 2012/2016 via libvirt.

There are two other hurdles along the way: (1) no VNC on HyperV, we may need to use RDP instead, and (2) can't find a way how to output serial port from VM (`virsh console' is not implemented in 'hyperv' driver). Plus 'hyperv' needs to be enabled in our libvirt.

Marita, Richard: In light of this, should I pursue the task on HyperV?

1) No VNC on HyperV - there is no VNC on zKVM or z/VM either but we manage to test both there using the VNC of the OS, instead of the VNC from the hypervisor. Have a look at the s390x backend or talk to Matthias for help with that - should not be a blocker in theory

2) While I admit what I am about to propose is a little hackish, it should be a simple case of using something like netcat from the SUT to forward the data from the Serial to the worker. This wouldn't be that dissimilar from how we have gotten the s390x backend working with it's x3270 emulation of a serial console. Matthias might again be the best person to help with that.

3) the platform support - SUSE OpenStack Cloud supports Windows 2012 https://www.suse.com/products/suse-openstack-cloud/technical-information/
OpenStack uses libvirt...so I guess you need to ask our Cloud guys how the hell they manage to get that working, because it clearly seems to be possible if we support it there..

Status update

I integrated JeOS under svirt backend to 'x-released SLE 12 SP1 6.JeOS group' OSD group. Currently is 12SP2 JeOS images tested under KVM, KVM+UEFI, Xen HVM, and Xen PV. E.g.: https://openqa.suse.de/tests/overview?distri=sle&version=12-SP1&build=25.58&groupid=23.

With snapshots support in svirt (https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/1830) much more tests should be executed.

Currently this Qemu (probably) 12-SP2 bug https://bugzilla.suse.com/show_bug.cgi?id=998613 prevents casual testing because high portion of runs triggers that bug.

Plan:

1. some Server-DVD scenarios via svirt,
2. use kvm and xen virtsh host as a openQA worker

Uodate about VMWare Licenses: we do not have any left, need to buy new ones, on Harald's desk