Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Matthieu Herrb]

On Tue, Jan 02, 2018 at 08:37:04PM +0100, Landry Breuil wrote:
> On Sat, Dec 30, 2017 at 09:23:03PM -0800, Mike Larkin wrote:
> > On Tue, Jan 02, 2018 at 11:30:47AM -0500, Brian Rak wrote:
> > > 
> > > 
> > The only thing I can say is that recently I've been noticing an uptick in 
> > the
> > quantity of KVM related issues on OpenBSD. Whether this is due to some 
> > recent
> > changes in KVM, or maybe due to more people running OpenBSD on KVM (and thus
> > increasing the number of reports), I'm not sure. But kettenis@ did note a 
> > few
> > days ago in a reply to a different KVM related issue that it seems their 
> > local
> > APIC emulation code isn't behaving exactly as we expect. But that code 
> > hasn't
> > changed in OpenBSD since, well, forever, so it's likely a KVM issue there.
> > Whether this is your issue or not I don't know. You might bring this up on
> > the KVM mailing lists and see if someone can shed light on it. If you search
> > the tech@/misc@ archives for proxmox related threads, there was a KVM option
> > reported a week or so back that seemed to fix the issue kettenis@ was 
> > commenting
> > on; perhaps this can help you.
> 
> ftr that option was kvm-intel.preemption_timer=0 on the host kernel
> commandline.

FWIW, I'm running OpenBSD-current in qemu / KVM using libvirt and
virt-manager for some years now. Current -current still works OK for
me. /var/run/ntpd.drift is 0.47 which doesn't look bad.

Here are dmesg from the VM and the xml file for libvirt.

OpenBSD 6.2-current (GENERIC.MP) #28: Fri Dec 29 18:10:50 CET 2017
matth...@obsd64-current.herrb.net:/usr/obj/GENERIC.MP
real mem = 2130698240 (2031MB)
avail mem = 2059264000 (1963MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf1430 (13 entries)
bios0: vendor Bochs version "Bochs" date 01/01/2011
bios0: Bochs Bochs
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP SSDT APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel Xeon E3-12xx v2 (Ivy Bridge), 772.12 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 1000MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel Xeon E3-12xx v2 (Ivy Bridge), 919.08 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu1: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu1: smt 0, core 0, package 1
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel Xeon E3-12xx v2 (Ivy Bridge), 1016.77 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS
cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu2: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu2: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu2: smt 0, core 0, package 2
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel Xeon E3-12xx v2 (Ivy Bridge), 968.46 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,VMX,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,RDTSCP,LONG,LAHF,PERF,FSGSBASE,SMEP,ERMS
cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu3: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu3: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu3: smt 0, core 0, package 3
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpicpu1 at acpi0: C1(@1 halt!)
acpicpu2 at acpi0: C1(@1 halt!)
acpicpu3 at acpi0: C1(@1 halt!)
"ACPI0006" at acpi0 not configured
"ACPI0007" at acpi0 not configured

Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Mike Larkin]

On Tue, Jan 02, 2018 at 08:37:04PM +0100, Landry Breuil wrote:
> On Sat, Dec 30, 2017 at 09:23:03PM -0800, Mike Larkin wrote:
> > On Tue, Jan 02, 2018 at 11:30:47AM -0500, Brian Rak wrote:
> > > 
> > > 
> > The only thing I can say is that recently I've been noticing an uptick in 
> > the
> > quantity of KVM related issues on OpenBSD. Whether this is due to some 
> > recent
> > changes in KVM, or maybe due to more people running OpenBSD on KVM (and thus
> > increasing the number of reports), I'm not sure. But kettenis@ did note a 
> > few
> > days ago in a reply to a different KVM related issue that it seems their 
> > local
> > APIC emulation code isn't behaving exactly as we expect. But that code 
> > hasn't
> > changed in OpenBSD since, well, forever, so it's likely a KVM issue there.
> > Whether this is your issue or not I don't know. You might bring this up on
> > the KVM mailing lists and see if someone can shed light on it. If you search
> > the tech@/misc@ archives for proxmox related threads, there was a KVM option
> > reported a week or so back that seemed to fix the issue kettenis@ was 
> > commenting
> > on; perhaps this can help you.
> 
> ftr that option was kvm-intel.preemption_timer=0 on the host kernel
> commandline.
> 

Thanks Landry, I knew someone would chime in :)

Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Landry Breuil]

On Sat, Dec 30, 2017 at 09:23:03PM -0800, Mike Larkin wrote:
> On Tue, Jan 02, 2018 at 11:30:47AM -0500, Brian Rak wrote:
> > 
> > 
> The only thing I can say is that recently I've been noticing an uptick in the
> quantity of KVM related issues on OpenBSD. Whether this is due to some recent
> changes in KVM, or maybe due to more people running OpenBSD on KVM (and thus
> increasing the number of reports), I'm not sure. But kettenis@ did note a few
> days ago in a reply to a different KVM related issue that it seems their local
> APIC emulation code isn't behaving exactly as we expect. But that code hasn't
> changed in OpenBSD since, well, forever, so it's likely a KVM issue there.
> Whether this is your issue or not I don't know. You might bring this up on
> the KVM mailing lists and see if someone can shed light on it. If you search
> the tech@/misc@ archives for proxmox related threads, there was a KVM option
> reported a week or so back that seemed to fix the issue kettenis@ was 
> commenting
> on; perhaps this can help you.

ftr that option was kvm-intel.preemption_timer=0 on the host kernel
commandline.

Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Mike Larkin]

On Tue, Jan 02, 2018 at 11:30:47AM -0500, Brian Rak wrote:
> 
> 
> On 12/30/2017 5:13 PM, Mike Larkin wrote:
> > On Wed, Dec 27, 2017 at 01:10:13PM -0500, Brian Rak wrote:
> > > I have a server with an Intel Platinum CPU: 
> > > https://ark.intel.com/products/120505/Intel-Xeon-Platinum-8176M-Processor-38_5M-Cache-2_10-GHz
> > > 
> > > It's running Fedora 27 Server, kernel version 4.14.8-300.fc27.x86_64,
> > > qemu-system-x86-core-2.10.1-2.fc27.x86_64
> > > 
> > > I'm starting qemu like this:
> > > 
> > > /usr/bin/qemu-system-x86_64 -machine accel=kvm -name
> > > guest=test,debug-threads=on -S -object 
> > > secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-test/master-key.aes
> > > -machine pc-i440fx-2.10,accel=kvm,usb=off,dump-guest-core=off -cpu
> > > Skylake-Client,hypervisor=on -m 32768 -realtime mlock=off -smp
> > > 16,sockets=2,cores=8,threads=1 -uuid 6427e485-5aee-4fb6-b5e5-a80c1dc0f4af
> > > -no-user-config -nodefaults -chardev 
> > > socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-test/monitor.sock,server,nowait
> > > -mon chardev=charmonitor,id=monitor,mode=control -rtc 
> > > base=utc,driftfix=slew
> > > -global kvm-pit.lost_tick_policy=delay -no-shutdown -boot strict=on 
> > > -device
> > > piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
> > > file=/var/tmp/cd62.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on
> > > -device 
> > > ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
> > > -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=32 -device 
> > > virtio-net-pci,netdev=hostnet0,id=net0,mac=56:00:00:27:d6:3f,bus=pci.0,addr=0x3,rombar=0,bootindex=3
> > > -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc
> > > 127.0.0.1:4788,websocket=40688 -device
> > > cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
> > > virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -object
> > > rng-random,id=objrng0,filename=/dev/random -device
> > > virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -msg timestamp=on
> > Could you try a simpler config? There's a lot in there that's not needed for
> > OpenBSD, and I'm wondering if there is some option you've chosen that's
> > causing problems.
> > 
> > For what it's worth, there have been a number of reports of OpenBSD guests
> > recently failing when run on KVM (mainly clock related issues but other
> > things as well). You are using a very new CPU on a very new host OS, I'm not
> > surprised some things are behaving a bit strangely.
> > 
> > -ml
> The simplest command line I can come up with is:
> 
> /usr/bin/qemu-system-x86_64 -machine accel=kvm -name guest=test -machine
> pc-i440fx-2.10 -cpu Skylake-Client -m 32768 -drive
> file=/var/tmp/cd62.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
> -device cirrus-vga,id=video0,bus=pci.0,addr=0x3 -vnc 127.0.0.1:4788
> 
> I still see the same hang.  Even using more ancient virtual CPUs (-cpu
> pentium3) doesn't seem to help.
> 
> Switching to '-machine pc-q35-2.10' doesn't appear to help either.
> 
> If I disable KVM, the instance appears to boot normally.  However, I'm not
> sure if this points to a KVM issue or if it's just masking a timing issue
> (because it runs so much slower emulated)
> 
> In this case, we went with Fedora 27 to rule out a problem that would be
> fixed by upgrading some part of the host OS.  This isn't an OS we normally
> use, and we've seen issues with older versions of qemu.
> 

The only thing I can say is that recently I've been noticing an uptick in the
quantity of KVM related issues on OpenBSD. Whether this is due to some recent
changes in KVM, or maybe due to more people running OpenBSD on KVM (and thus
increasing the number of reports), I'm not sure. But kettenis@ did note a few
days ago in a reply to a different KVM related issue that it seems their local
APIC emulation code isn't behaving exactly as we expect. But that code hasn't
changed in OpenBSD since, well, forever, so it's likely a KVM issue there.
Whether this is your issue or not I don't know. You might bring this up on
the KVM mailing lists and see if someone can shed light on it. If you search
the tech@/misc@ archives for proxmox related threads, there was a KVM option
reported a week or so back that seemed to fix the issue kettenis@ was commenting
on; perhaps this can help you.

-ml

Re: Thinkpad x230 usb3 xhci(4) issues with usb drives

[Klemens Nanni]

On Tue, Jan 02, 2018 at 06:09:38PM +, mer...@aaathats3as.com wrote:
> On 2017-12-30 16:11, Mike Larkin wrote:
> > On Mon, Jan 01, 2018 at 04:52:45PM +, mer...@aaathats3as.com wrote:
> > > bios0: vendor coreboot version "CBET4000 4.6-196-g0fb6568" date
> > > 05/22/2017
> > 
> > Please retest using stock BIOS and let us know how that works for you.
> tested it with stock BIOS and have to report back that usb3 works now.
> I guess this is a coreboot related problem then?
Yes.

> Can OpenBSD do anything about it
No.

> or should I try to fill a bug report at coreboot?
Yes. Reach out to their mailing list or IRC channel on freenode.

> I have two x230 to play with here. One is still running coreboot.
> Please let me know if I should do more tests with it, otherwise I'll
> probably flash it with stock BIOS as well. Can't easily flash back and
> forth for now, because I have no external programmer ready.
This is most likely an issue with xHCI (read: USB 3.0) only. As
mentioned above, this is an OS independent problem, so all further tests
should be handled by the coreboot community.

See you there :)

Re: Thinkpad x230 usb3 xhci(4) issues with usb drives

[merino]

On 2017-12-30 16:11, Mike Larkin wrote:

On Mon, Jan 01, 2018 at 04:52:45PM +, mer...@aaathats3as.com wrote:
bios0: vendor coreboot version "CBET4000 4.6-196-g0fb6568" date 
05/22/2017


Please retest using stock BIOS and let us know how that works for you.

-ml



Hi ml,

tested it with stock BIOS and have to report back that usb3 works now.
I guess this is a coreboot related problem then? Can OpenBSD do
anything about it or should I try to fill a bug report at coreboot?

I have two x230 to play with here. One is still running coreboot.
Please let me know if I should do more tests with it, otherwise I'll
probably flash it with stock BIOS as well. Can't easily flash back and
forth for now, because I have no external programmer ready.

Thank you.
-merino

Re: ktrace firefox freeze my box

[Martin Pieuchot]

On 02/01/18(Tue) 17:14, Martin Pieuchot wrote:
> on -current amd64, simply doing "$ ktrace -p $pid_of_firefox" is enough
> to freeze my box:

Same problem with chromium.  It seems that a CPU is never giving the
KERNEL_LOCK() back.  It always happen when executing one of the browser
threads and DDB can't get a trace from it.

These are the same symptoms as my backed out solock/kqueue diff.

> 
> OpenBSD 6.2-current (GENERIC.MP) #313: Mon Jan  1 17:51:21 MST 2018
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> real mem = 8238301184 (7856MB)
> avail mem = 7981707264 (7611MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
> bios0: vendor LENOVO version "N14ET26W (1.04 )" date 01/23/2015
> bios0: LENOVO 20BS006BGE
> acpi0 at bios0: rev 2
> acpi0: sleep states S0 S3 S4 S5
> acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT 
> SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
> acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpihpet0 at acpi0: 14318179 Hz
> acpiec0 at acpi0
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2295.07 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
> cpu0: 256KB 64b/line 8-way L2 cache
> acpihpet0: recalibrated TSC frequency 2394462310 Hz
> cpu0: smt 0, core 0, package 0
> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
> cpu1: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
> cpu1: 256KB 64b/line 8-way L2 cache
> cpu1: smt 1, core 0, package 0
> cpu2 at mainbus0: apid 2 (application processor)
> cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
> cpu2: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
> cpu2: 256KB 64b/line 8-way L2 cache
> cpu2: smt 0, core 1, package 0
> cpu3 at mainbus0: apid 3 (application processor)
> cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
> cpu3: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
> cpu3: 256KB 64b/line 8-way L2 cache
> cpu3: smt 1, core 1, package 0
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
> acpimcfg0 at acpi0 addr 0xf800, bus 0-63
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (PEG_)
> acpiprt2 at acpi0: bus 3 (EXP1)
> acpiprt3 at acpi0: bus 4 (EXP2)
> acpiprt4 at acpi0: bus -1 (EXP3)
> acpiprt5 at acpi0: bus -1 (EXP6)
> acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
> C1(1000@1 mwait.1), PSS
> acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
> C1(1000@1 mwait.1), PSS
> acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
> C1(1000@1 mwait.1), PSS
> acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
> C1(1000@1 mwait.1), PSS
> acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
> acpipwrres1 at acpi0: NVP3, resource for PEG_
> acpipwrres2 at acpi0: NVP2, resource for PEG_
> acpitz0 at acpi0: critical temperature is 128 degC
> acpibtn0 at acpi0: LID_
> acpibtn1 at acpi0: SLPB
> "LEN0071" at acpi0 not configured
> "LEN0048" at acpi0 not configured
> acpibat0 at acpi0: BAT0 model "00HW003" serial   887 type LiP oem "SMP"
> acpiac0 at acpi0: AC unit online
> acpithinkpad0 at 

Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Brian Rak]

On 12/30/2017 5:13 PM, Mike Larkin wrote:

On Wed, Dec 27, 2017 at 01:10:13PM -0500, Brian Rak wrote:

I have a server with an Intel Platinum CPU: 
https://ark.intel.com/products/120505/Intel-Xeon-Platinum-8176M-Processor-38_5M-Cache-2_10-GHz

It's running Fedora 27 Server, kernel version 4.14.8-300.fc27.x86_64,
qemu-system-x86-core-2.10.1-2.fc27.x86_64

I'm starting qemu like this:

/usr/bin/qemu-system-x86_64 -machine accel=kvm -name
guest=test,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-test/master-key.aes
-machine pc-i440fx-2.10,accel=kvm,usb=off,dump-guest-core=off -cpu
Skylake-Client,hypervisor=on -m 32768 -realtime mlock=off -smp
16,sockets=2,cores=8,threads=1 -uuid 6427e485-5aee-4fb6-b5e5-a80c1dc0f4af
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-test/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew
-global kvm-pit.lost_tick_policy=delay -no-shutdown -boot strict=on -device
piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
file=/var/tmp/cd62.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on
-device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
-netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=32 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=56:00:00:27:d6:3f,bus=pci.0,addr=0x3,rombar=0,bootindex=3
-device usb-tablet,id=input0,bus=usb.0,port=1 -vnc
127.0.0.1:4788,websocket=40688 -device
cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -object
rng-random,id=objrng0,filename=/dev/random -device
virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -msg timestamp=on

Could you try a simpler config? There's a lot in there that's not needed for
OpenBSD, and I'm wondering if there is some option you've chosen that's
causing problems.

For what it's worth, there have been a number of reports of OpenBSD guests
recently failing when run on KVM (mainly clock related issues but other
things as well). You are using a very new CPU on a very new host OS, I'm not
surprised some things are behaving a bit strangely.

-ml

The simplest command line I can come up with is:

/usr/bin/qemu-system-x86_64 -machine accel=kvm -name guest=test -machine 
pc-i440fx-2.10 -cpu Skylake-Client -m 32768 -drive 
file=/var/tmp/cd62.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on 
-device 
ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1 
-device cirrus-vga,id=video0,bus=pci.0,addr=0x3 -vnc 127.0.0.1:4788


I still see the same hang.  Even using more ancient virtual CPUs (-cpu 
pentium3) doesn't seem to help.


Switching to '-machine pc-q35-2.10' doesn't appear to help either.

If I disable KVM, the instance appears to boot normally.  However, I'm 
not sure if this points to a KVM issue or if it's just masking a timing 
issue (because it runs so much slower emulated)


In this case, we went with Fedora 27 to rule out a problem that would be 
fixed by upgrading some part of the host OS.  This isn't an OS we 
normally use, and we've seen issues with older versions of qemu.






I do not have a functional OpenBSD install here, this happens even when I
try to boot off the ISO.

OpenBSD hangs after printing:

pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility

There is a flashing "_" cursor, but I'm unable to interact with it in any
way.

I tried setting this to use an older CPU type, which changed the -cpu flag
to be "-cpu Nehalem,vme=off,x2apic=off,hypervisor=off", but this did not
seem to have any effect.

If I boot the VM with 'boot -c', then 'disable pciide*', I can actually get
to the 'Welcome to the OpenBSD/amd64 6.2 installation program' prompt, but
then the machine hangs whenever I type 'A'. If I choose another option
('I'), I can get partially through the install before it hangs.  The hangs
at that point seem to be random.

I've attached a screenshot of where it's hanging during the initial boot.

So far we've been able to reproduce this on all of our Intel Scalable
processors, which includes a few other Gold CPUs.  This does work ok on our
older E5 CPUs

ktrace firefox freeze my box

[Martin Pieuchot]

on -current amd64, simply doing "$ ktrace -p $pid_of_firefox" is enough
to freeze my box:

OpenBSD 6.2-current (GENERIC.MP) #313: Mon Jan  1 17:51:21 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8238301184 (7856MB)
avail mem = 7981707264 (7611MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (65 entries)
bios0: vendor LENOVO version "N14ET26W (1.04 )" date 01/23/2015
bios0: LENOVO 20BS006BGE
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT 
SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR
acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpiec0 at acpi0
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2295.07 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
acpihpet0: recalibrated TSC frequency 2394462310 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz, 2294.69 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG_)
acpiprt2 at acpi0: bus 3 (EXP1)
acpiprt3 at acpi0: bus 4 (EXP2)
acpiprt4 at acpi0: bus -1 (EXP3)
acpiprt5 at acpi0: bus -1 (EXP6)
acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), 
C1(1000@1 mwait.1), PSS
acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1
acpipwrres1 at acpi0: NVP3, resource for PEG_
acpipwrres2 at acpi0: NVP2, resource for PEG_
acpitz0 at acpi0: critical temperature is 128 degC
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
"LEN0071" at acpi0 not configured
"LEN0048" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "00HW003" serial   887 type LiP oem "SMP"
acpiac0 at acpi0: AC unit online
acpithinkpad0 at acpi0
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"INT340F" at acpi0 not configured
acpivideo0 at acpi0: VID_
acpivout at acpivideo0 not configured
acpivideo1 at acpi0: VID_
cpu0: Enhanced SpeedStep 2295 MHz: speeds: 2401, 2400, 2300, 2100, 2000, 1900, 
1700, 1600, 1400, 1300, 1200, 1000, 900, 800, 600, 500 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 5G Host" rev 0x09

Re: 6.2 Installation Fails on Soekris net5501

[Kenneth Hendrickson]

On Tue, 1/2/18, Philip Guenther  wrote:
> The problem is that you've
> created a filesystem for /var/tmp/.

Yep.  That fixes it.

Thanks.

Performance degradation with two systems running iwm(4)

[Matthias Schmidt]

Hi guys,

I'm currently facing a network performance degradation with two different
devices both connected via iwm(4) to the local access point.  Both are
running 6.2-current, one with a snapshot from Dec 16 the other with a
snapshot from Dec 26.  dmesg of one device attached.  Both devices are
connected to a standard German FritzBox with 11n in the 2.4GHz band.  I
do not have 5GHz enabled.

When I start a new download, the data transfer rate on both devices
significantly drops after a while.  When the transfer is still fast, my
DSL router says that both devices are connected with 11n and have about
130Mbit/s.  After a while I am down to 1-2MBit/s. When I abort the
transfer and wait some time (around 30s) I can again start with full
speed and the AP shows 130MBit/s.  After a while I am down to 1-2Mbit/s,
again.

I downloaded the 100M file from hostserver.de in a loop and it looks
like this (stripped down curl downloads):

% Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  100M  100  100M0 0  3657k  0  0:00:28  0:00:28 --:--:-- 4266k
100  100M  100  100M0 0  2327k  0  0:00:44  0:00:44 --:--:-- 2356k
100  100M  100  100M0 0  2275k  0  0:00:45  0:00:45 --:--:-- 1961k
100  100M  100  100M0 0  1678k  0  0:01:01  0:01:01 --:--:--  131k
100  100M  100  100M0 0   193k  0  0:08:50  0:08:50 --:--:--  117k
  8  100M8 8516k0 0   144k  0  0:11:49  0:00:59  0:10:50  141k^C

I run the above download loop for the last couple of days and could
reproduce it every time.

Any hint on how I could debug further?

Cheers

Matthias


OpenBSD 6.2-current (GENERIC.MP) #292: Sat Dec 16 13:27:27 MST 2017
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17047859200 (16258MB)
avail mem = 16524275712 (15758MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7b1d5000 (58 entries)
bios0: vendor Intel Corp. version "SYSKLi35.86A.0062.2017.0831.1905" date 
08/31/2017
bios0: Intel corporation NUC6i5SYB
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET LPIT SSDT SSDT SSDT SSDT DBGP 
DBG2 SSDT SSDT UEFI SSDT DMAR
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
SIO1(S3) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) 
RP12(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz, 1696.55 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 23MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz, 1696.04 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz, 1696.04 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz, 1696.04 MHz
cpu3: 

Re: Unable to boot OpenBSD within QEMU on an Intel Platinum 8176M

[Mike Larkin]

On Wed, Dec 27, 2017 at 01:10:13PM -0500, Brian Rak wrote:
> I have a server with an Intel Platinum CPU: 
> https://ark.intel.com/products/120505/Intel-Xeon-Platinum-8176M-Processor-38_5M-Cache-2_10-GHz
> 
> It's running Fedora 27 Server, kernel version 4.14.8-300.fc27.x86_64,
> qemu-system-x86-core-2.10.1-2.fc27.x86_64
> 
> I'm starting qemu like this:
> 
> /usr/bin/qemu-system-x86_64 -machine accel=kvm -name
> guest=test,debug-threads=on -S -object 
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-6-test/master-key.aes
> -machine pc-i440fx-2.10,accel=kvm,usb=off,dump-guest-core=off -cpu
> Skylake-Client,hypervisor=on -m 32768 -realtime mlock=off -smp
> 16,sockets=2,cores=8,threads=1 -uuid 6427e485-5aee-4fb6-b5e5-a80c1dc0f4af
> -no-user-config -nodefaults -chardev 
> socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-6-test/monitor.sock,server,nowait
> -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew
> -global kvm-pit.lost_tick_policy=delay -no-shutdown -boot strict=on -device
> piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive
> file=/var/tmp/cd62.iso,format=raw,if=none,id=drive-ide0-1-0,readonly=on
> -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0,bootindex=1
> -netdev tap,fd=29,id=hostnet0,vhost=on,vhostfd=32 -device 
> virtio-net-pci,netdev=hostnet0,id=net0,mac=56:00:00:27:d6:3f,bus=pci.0,addr=0x3,rombar=0,bootindex=3
> -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc
> 127.0.0.1:4788,websocket=40688 -device
> cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device
> virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -object
> rng-random,id=objrng0,filename=/dev/random -device
> virtio-rng-pci,rng=objrng0,id=rng0,bus=pci.0,addr=0x6 -msg timestamp=on

Could you try a simpler config? There's a lot in there that's not needed for
OpenBSD, and I'm wondering if there is some option you've chosen that's
causing problems.

For what it's worth, there have been a number of reports of OpenBSD guests
recently failing when run on KVM (mainly clock related issues but other
things as well). You are using a very new CPU on a very new host OS, I'm not
surprised some things are behaving a bit strangely.

-ml


> 
> I do not have a functional OpenBSD install here, this happens even when I
> try to boot off the ISO.
> 
> OpenBSD hangs after printing:
> 
> pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
> 0 wired to compatibility, channel 1 wired to compatibility
> 
> There is a flashing "_" cursor, but I'm unable to interact with it in any
> way.
> 
> I tried setting this to use an older CPU type, which changed the -cpu flag
> to be "-cpu Nehalem,vme=off,x2apic=off,hypervisor=off", but this did not
> seem to have any effect.
> 
> If I boot the VM with 'boot -c', then 'disable pciide*', I can actually get
> to the 'Welcome to the OpenBSD/amd64 6.2 installation program' prompt, but
> then the machine hangs whenever I type 'A'. If I choose another option
> ('I'), I can get partially through the install before it hangs.  The hangs
> at that point seem to be random.
> 
> I've attached a screenshot of where it's hanging during the initial boot.
> 
> So far we've been able to reproduce this on all of our Intel Scalable
> processors, which includes a few other Gold CPUs.  This does work ok on our
> older E5 CPUs
>