[vfio-users] Installing Catalyst prevents VM from booting.

[Paige Thompson]

Also for anybody who wants to have a look at my setup: Windows.xml attached, also attached my kernel config.


Here's the rest of the details that I can think of off-hand:

kernel cmline:

BOOT_IMAGE=/kernel-genkernel-x86_64-4.20.0-rc5-blazeit root=UUID=2a017de1-b67c-4806-9a62-950c90af6762 ro init=/usr/lib/systemd/systemd crypt_root=UUID=1758cd85-e062-48cf-99fa-5776455e103e root_trim=yes console=ttyS1,115200n8 earlyprintk=ttyS1,115200n8 intel_iommu=on vfio-pci.ids=1002:67b1,1002:aac8 isolcpus=10,11,12,13,14,15,16,17,18,19,30,31,32,33,34,35,36,37,38,39 hugepagesz=1G default_hugepagesz=1G pcie_aspm=off kvm-intel.nested=1 kgdboc=ttyS1,115200n8 --

(allows me to set the process to realtime) with chrt -r --pid 99 <pid
➜  supermicro cat /proc/sys/kernel/sched_rt_runtime_us
-1
➜  supermicro

C1E, C3, and C6 are available
➜  supermicro cpupower idle-info
CPUidle driver: intel_idle
CPUidle governor: menu
analyzing CPU 0:

Number of idle states: 5
Available idle states: POLL C1 C1E C3 C6
POLL:
Flags/Description: CPUIDLE CORE POLL IDLE
Latency: 0
Usage: 1180169
Duration: 4354090
C1:
Flags/Description: MWAIT 0x00
Latency: 2
Usage: 8890060
Duration: 1615968600
C1E:
Flags/Description: MWAIT 0x01
Latency: 10
Usage: 7437145
Duration: 855436569
C3:
Flags/Description: MWAIT 0x10
Latency: 40
Usage: 18927771
Duration: 4638306256
C6:
Flags/Description: MWAIT 0x20
Latency: 133
Usage: 37763378
Duration: 14136114100

➜  supermicro


using the deadline IO scheduler

➜  supermicro cat /sys/block/*/queue/scheduler
none
none
none
none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
none
none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
[mq-deadline] kyber bfq none
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
noop [deadline] cfq
➜  supermicro

➜  supermicro uname -a
Linux molly 4.20.0-rc5-blazeit #1 SMP PREEMPT Thu Dec 27 11:51:29 PST 2018 x86_64 Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz GenuineIntel GNU/Linux
➜  supermicro qemu-system-x86_64 --version
QEMU emulator version 3.0.92 (v3.1.0-rc2-3-gebfd6216ec-dirty)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
➜  supermicro virsh version
Compiled against library: libvirt 4.6.0
Using library: libvirt 4.6.0
Using API: QEMU 4.6.0
Running hypervisor: QEMU 3.0.92

➜  supermicro


its gotten quite elaborate it doesn't ever get any less xD
________________________________________
From: vfio-users-bounces at redhat.com <vfio-users-bounces at redhat.com> on behalf of Patrick O'Callaghan <poc at usb.ve>
Sent: Saturday, December 29, 2018 3:49:13 AM
To: vfio-users at redhat.com
Subject: Re: [vfio-users] Installing Catalyst prevents VM from booting.

On Fri, 2018-12-28 at 16:04 -0500, Kyle Marek wrote:
> q35 is the newer one with better support for more CPUs, PCI-E vs PCI,
> integrated SATA vs integrated IDE emulation, IOMMU emulation, and I
> *think* it is needed for hotplugging CPUs/memory.

[I wish people wouldn't top-post, but anyway ...]

I'm interested in switching to Q35 but it isn't entirely trivial.
Simply editing the machine-type line in the XML file doesn't do it:

If I change:

   <type arch='x86_64' machine='pc-i440fx-3.0'>hvm</type>

to:

   <type arch='x86_64' machine='Q35'>hvm</type>

I get:

   Error: unsupported configuration: IDE controllers are unsupported for this QEMU binary or machine type

I created the VM using Virtual Machine Manager under Fedora over a year
ago, so most of the settings were defaults at the time. Is there a
Dummy's Guide to changing this, or would it be easier to just create a
new VM (keeping the existing storage of course)? The man pages are
pretty unhelpful.

For completeness I attach the full XML file.

poc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Windows.xml
Type: text/xml
Size: 11988 bytes
Desc: Windows.xml
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20181229/937cdd16/attachment.xml>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel.config-4.20.0-rc5-blazeit
Type: application/octet-stream
Size: 207002 bytes
Desc: kernel.config-4.20.0-rc5-blazeit
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20181229/937cdd16/attachment.obj>