OmniOS crashes at boot on Vultr's KVM unless disable-hv_vmbus=true about illumos-omnios

[antranigv]

P.S. The Hypervisor is KVM, here are the parameters from the BSD Loader.

[citrus-it]

Well this is weird! That hyper-v information looks fairly real.

To make this permanent, you can do:

echo disable-hv_vmbus=true > /boot/conf.d/vmbus

As for why we think this is a Hyper-V system -- from the booted system, please can you install the cpuid utility (pkg install cpuid) and grab the output of the cpuid -d command?

[antranigv]

Here's the output from cpuid

root@omnios0:~# cpuid -d
CPU 0:
CPUID 00000000:00 = 0000000d 756e6547 6c65746e 49656e69 | ....GenuntelineI
CPUID 00000001:00 = 000306c1 00000800 fffa3203 078bfbff | .........2......
CPUID 00000002:00 = 00000001 00000000 0000004d 002c307d | ........M...}0,.
CPUID 00000003:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 00000004:00 = 00000121 01c0003f 0000003f 00000001 | !...?...?.......
CPUID 00000004:01 = 00000122 01c0003f 0000003f 00000001 | "...?...?.......
CPUID 00000004:02 = 00000143 03c0003f 00000fff 00000001 | C...?...........
CPUID 00000004:03 = 00000163 03c0003f 00003fff 00000006 | c...?....?......
CPUID 00000004:04 = 00000000 00000000 00000000 00000000 | ................
CPUID 00000005:00 = 00000000 00000000 00000003 00000000 | ................
CPUID 00000006:00 = 00000004 00000000 00000000 00000000 | ................
CPUID 00000007:00 = 00000000 000007a9 00000000 84000000 | ................
CPUID 00000008:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 00000009:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 0000000a:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 0000000b:00 = 00000000 00000001 00000100 00000000 | ................
CPUID 0000000b:01 = 00000000 00000001 00000201 00000000 | ................
CPUID 0000000c:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 0000000d:00 = 00000007 00000340 00000340 00000000 | ....@...@.......
CPUID 0000000d:01 = 00000001 00000340 00000000 00000000 | ....@...........
CPUID 0000000d:02 = 00000100 00000240 00000000 00000000 | ....@...........
CPUID 40000000:00 = 40000005 7263694d 666f736f 76482074 | ...@Microsoft Hv
CPUID 40000001:00 = 31237648 00000000 00000000 00000000 | Hv#1............
CPUID 40000002:00 = 00003839 000a0000 00000000 00000000 | 98..............
CPUID 40000003:00 = 0000027e 00000030 00000000 00000008 | ~...0...........
CPUID 40000004:00 = 00000028 00001000 00000000 00000000 | (...............
CPUID 40000005:00 = ffffffff 00000040 00000000 00000000 | ....@...........
CPUID 80000000:00 = 80000008 756e6547 6c65746e 49656e69 | ....GenuntelineI
CPUID 80000001:00 = 000306c1 00000000 00000021 28100800 | ........!......(
CPUID 80000002:00 = 65746e49 6f43206c 50206572 65636f72 | Intel Core Proce
CPUID 80000003:00 = 726f7373 61482820 6c657773 6e202c6c | ssor (Haswell, n
CPUID 80000004:00 = 5354206f 49202c58 29535242 00000000 | o TSX, IBRS)....
CPUID 80000005:00 = 01ff01ff 01ff01ff 40020140 40020140 | ........@..@@..@
CPUID 80000006:00 = 00000000 42004200 02008140 00808140 | .....B.B@...@...
CPUID 80000007:00 = 00000000 00000000 00000000 00000000 | ................
CPUID 80000008:00 = 00003028 00000000 00000000 00000000 | (0..............
CPUID 80860000:00 = 00000007 00000340 00000340 00000000 | ....@...@.......
CPUID c0000000:00 = 00000007 00000340 00000340 00000000 | ....@...@.......

[citrus-it]

CPUID 40000000:00 = 40000005 7263694d 666f736f 76482074 | ...@microsoft Hv

Well, it's identifying itself as Hyper-V in the cpuid information, yet the illumos loader output you pasted shows that the smbios information contains QEMU and KVM.

https://community.netdata.cloud/t/vultr-linux-kvm-vps-but-netdata-detect-it-as-microsoft-any-idea/3535/3 includes this gem from Vultr support:

We enable some Hyper-V enlightenments for support for Windows guests, which systemd may be picking up as being Hyber-V itself. Our host machines use KVM/QEMU for managing guests.

[antranigv]

I think this does answer all the questions.

Thank you!