NetBSD Problem Report #59721
From www@netbsd.org Fri Oct 24 02:46:45 2025
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits)
client-signature RSA-PSS (2048 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 919FD1A9239
for <gnats-bugs@gnats.NetBSD.org>; Fri, 24 Oct 2025 02:46:45 +0000 (UTC)
Message-Id: <20251024024644.310941A923A@mollari.NetBSD.org>
Date: Fri, 24 Oct 2025 02:46:44 +0000 (UTC)
From: roy@marples.name
Reply-To: roy@marples.name
To: gnats-bugs@NetBSD.org
Subject: qemu VM's blackscreen over VNC wth -machine q35
X-Send-Pr-Version: www-1.0
>Number: 59721
>Notify-List: riastradh@NetBSD.org
>Category: pkg
>Synopsis: qemu VM's blackscreen over VNC wth -machine q35
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: pkg-manager
>State: analyzed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Oct 24 02:50:01 +0000 2025
>Closed-Date:
>Last-Modified: Fri Jan 02 05:20:01 +0000 2026
>Originator: Roy
>Release: 11.99.3
>Organization:
It Doesn't Work Dot Com
>Environment:
NetBSD cube 11.99.3 NetBSD 11.99.3 (GENERIC) #0: Fri Oct 24 00:41:11 BST 2025 roy@cube:/home/roy/src/obj/sys/arch/amd64/compile/GENERIC amd64
>Description:
Starting a QEMU VM with -machine q35 and -accel nvmm results in a black screen over VNC. Network probes (aka no DHCP request) show the VM isn't functioning.
$ doas cpuctl identify 0
cpu0: highest basic info 00000010
cpu0: highest extended info 80000020
cpu0: "AMD Ryzen 9 3900X 12-Core Processor "
cpu0: AMD Family 17h (686-class), 3792.86 MHz
cpu0: family 0x17 model 0x71 stepping 0 (id 0x870f10)
cpu0: features 0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE>
cpu0: features 0x178bfbff<MCA,CMOV,PAT,PSE36,CLFSH,MMX,FXSR,SSE,SSE2,HTT>
cpu0: features1 0x7ef8320b<SSE3,PCLMULQDQ,MONITOR,SSSE3,FMA,CX16,SSE41,SSE42>
cpu0: features1 0x7ef8320b<X2APIC,MOVBE,POPCNT,AES,XSAVE,OSXSAVE,AVX,F16C>
cpu0: features1 0x7ef8320b<RDRAND>
cpu0: features2 0x2fd3fbff<SYSCALL/SYSRET,NOX,MMXX,MMX,FXSR,FFXSR,P1GB,RDTSCP>
cpu0: features2 0x2fd3fbff<LONG>
cpu0: features3 0x75c237ff<LAHF,CMPLEGACY,SVM,EAPIC,ALTMOVCR0,LZCNT,SSE4A>
cpu0: features3 0x75c237ff<MISALIGNSSE,3DNOWPREFETCH,OSVW,IBS,SKINIT,WDT,TCE>
cpu0: features3 0x75c237ff<TopoExt,PCExtC,PCExtNB,DBExt,L2IPERFC,MWAITX>
cpu0: features3 0x75c237ff<AddrMaskExt>
cpu0: features5 0x219c91a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,QM,PQE,RDSEED,ADX,SMAP>
cpu0: features5 0x219c91a9<CLFLUSHOPT,CLWB,SHA>
cpu0: features6 0x400004<UMIP,MAWAU=0,RDPID>
cpu0: xsave features 0x207<x87,SSE,AVX,PKRU>
cpu0: xsave instructions 0xf<XSAVEOPT,XSAVEC,XGETBV,XSAVES>
cpu0: xsave area size: current 832, maximum 896, xgetbv enabled
cpu0: enabled xsave 0x7<x87,SSE,AVX>
cpu0: I-cache: 32KB 64B/line 8-way, D-cache: 32KB 64B/line 8-way
cpu0: L2 cache: 512KB 64B/line 8-way
cpu0: L3 cache: 16MB 64B/line 16-way
cpu0: ITLB: 64 4KB entries fully associative, 64 2MB entries fully associative, 64 1GB entries fully associative
cpu0: DTLB: 64 4KB entries fully associative, 64 2MB entries fully associative, 64 1GB entries fully associative
cpu0: L2 ITLB: 1024 4KB entries 8-way, 1024 2MB entries 8-way
cpu0: L2 DTLB: 2048 4KB entries 8-way, 2048 2MB entries 4-way
cpu0: Initial APIC ID 0
cpu0: Cluster/Package ID 0
cpu0: Core ID 0
cpu0: SMT ID 0
cpu0: MONITOR/MWAIT extensions 0x3<EMX,IBE>
cpu0: monitor-line size 64
cpu0: C0 substates 1
cpu0: C1 substates 1
cpu0: DSPM-eax 0x4<ARAT>
cpu0: DSPM-ecx 0x1<HWF,NTDC=0>
cpu0: SEF highest subleaf 00000000
cpu0: Power Management features: 0x6799<TS,TTP,HTC,HWP,ITSC,CPB,EffFreq,CONNSTBY,RAPL>
cpu0: AMD Extended features 0x10cb657<CLZERO,IRPERF,XSAVEERPTR,RDPRU,MBE>
cpu0: AMD Extended features 0x10cb657<WBNOINVD,B10,IBPB,INT_WBINVD,STIBP>
cpu0: AMD Extended features 0x10cb657<PREFER_IBRS,IBRS_SAMEMODE,SSBD>
cpu0: RAS features 0x1b<OVFL_RECOV,SUCCOR,MCAX>
cpu0: SVM Rev. 1
cpu0: SVM NASID 32768
cpu0: SVM features 0x13bcff<NP,LbrVirt,SVML,NRIPS,TSCRate,VMCBCleanBits>
cpu0: SVM features 0x13bcff<FlushByASID,DecodeAssist,PauseFilter,B11>
cpu0: SVM features 0x13bcff<PFThreshold,AVIC,V_VMSAVE_VMLOAD,VGIF,GMET>
cpu0: SVM features 0x13bcff<SPEC_CTRL>
cpu0: IBS features 0x3ff<IBSFFV,FetchSam,OpSam,RdWrOpCnt,OpCnt,BrnTrgt>
cpu0: IBS features 0x3ff<OpCntExt,RipInvalidChk,OpBrnFuse,IbsFetchCtlExtd>
cpu0: Encrypted Memory features 0x1000f<SME,SEV,PageFlushMsr,SEV-ES,VTE>
cpu0: UCode version: 0x8701030
$
>How-To-Repeat:
Here's the shell output trying to start a netbsd vm on a netbsd host.
+ qemu-system-x86_64 -machine q35 -drive file=netbsd.qcow2,if=none,id=disk1 -device virtio-blk-pci,drive=disk1 -object rng-random,id=rng1,filename=/dev/urandom -device virtio-rng-pci,rng=rng1 -netdev tap,ifname=tap0,id=net0,script=no,downscript=/home/roy/qemu/qctrl-tapdown -device 'virtio-net-pci,netdev=net0,mac=52:54:00:73:78:00' -netdev tap,ifname=tap1,id=net1,script=no,downscript=/home/roy/qemu/qctrl-tapdown -device 'virtio-net-pci,netdev=net1,mac=52:54:00:73:78:01' -pidfile /home/roy/qemu/run/qemu-netbsd.pid -daemonize -m 4G -smp cpus=2 -vnc ':0'
>Fix:
1) Don't use -machine q35
2) Don't use NVMM
3) Use DragonflyBSD as the host with NVMM and it's peachy
The problem with 1) is that timings go out of whack which renders testing DHCP clients and servers useless.
The problem with 2) is that it's dog slow
The problem with 3) is that it's not NetBSD.
>Release-Note:
>Audit-Trail:
From: mlelstv@serpens.de (Michael van Elst)
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Fri, 24 Oct 2025 08:55:45 -0000 (UTC)
roy@marples.name writes:
>Starting a QEMU VM with -machine q35 and -accel nvmm results in a black screen over VNC. Network probes (aka no DHCP request) show the VM isn't functioning.
The VM is starting with serial console and shows:
[ 1.019149] pci0 at mainbus0 bus 0: configuration mode 1
[ 1.019149] pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
[ 1.019149] pchb0 at pci0 dev 0 function 0: Intel 82G33/P35 Host Bridge (rev. 0x00)
[ 1.019149] agp0 at pchb0autoconfiguration error: : can't find internal VGA config space
[ 1.019149] vga0 at pci0 dev 1 function 0: vendor 1234 product 1111 (rev. 0x02)
[ 1.019149] wsdisplay0 at vga0 kbdmux 1
[ 1.019149] wsmux1: connecting to wsdisplay0
[ 1.019149] wskbd0: connecting to wsdisplay0
[ 1.019149] drm at vga0 not configured
with no tty attached to wsdisplay0.
With a VNC console, NVMM spits out lots of Unexpeced MSR accesses
and the machine doesn't come up. The same happens for a regular
graphical console.
In the latter case qemu also segfaults when shutting down in an atexit()
routine,
No such problems when NVMM is not in use.
Here is how I start qemu:
qemu-system-x86_64 \
-accel nvmm \
-machine q35 \
-cpu host \
-display vnc=0.0.0.0:0 \
-serial mon:stdio \
-m 256 \
-smp 1 \
-rtc base=utc,clock=host \
\
-netdev tap,id=n1,ifname=tap0,script=no,downscript=no \
-device virtio-net,netdev=n1 \
\
-device virtio-blk,drive=d0,bootindex=2 \
-drive if=none,format=qcow2,file=disk.qcow2,id=d0 \
\
-device virtio-scsi,id=scsi0 \
-device scsi-cd,bus=scsi0.0,drive=d1 \
-drive if=none,id=d1,media=cdrom,read-only=on,index=1,format=raw,file=bo
ot-com.iso
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Fri, 24 Oct 2025 11:48:40 +0200
On Fri, Oct 24, 2025 at 09:00:01AM +0000, Michael van Elst via gnats wrote:
> With a VNC console, NVMM spits out lots of Unexpeced MSR accesses
> and the machine doesn't come up. The same happens for a regular
> graphical console.
See PR 59715 for the MSRs (I suppose).
Martin
From: Taylor R Campbell <riastradh@NetBSD.org>
To: Roy Marples <roy@marples.name>,
Michael van Elst <mlelstv@serpens.de>,
Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Sun, 26 Oct 2025 16:03:05 +0000
I reproduced this with the following command line using qemu-10.1.1 on
a netbsd-10 kernel:
curl -L -O https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/amd64/installation=
/cdrom/boot.iso
qemu-system-x86_64 -m 512m -cdrom boot.iso -machine q35 -accel nvmm
If I make any of the seven possible nonempty subsets of the following
changes, it works:
- replace `q35' by `pc'
- add `-bios $PREFIX/share/ovmf/OVMFX64.fd' (from sysutils/ovmf)
- remove `-accel nvmm'
The black screen failure is purely graphical. If I do:
curl -L -O https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/amd64/installation=
/cdrom/boot-com.iso
qemu-system-x86_64 -m 512m -cdrom boot-com.iso -machine q35 -accel nvmm -no=
graphic
then it presents a serial console just fine. And if I do:
qemu-system-x86_64 -m 512m -cdrom boot.iso -machine q35 -accel nvmm -serial=
mon:stdio -vga std
then I can blindly hit `3' to drop to the boot prompt and type
`consdev com0' and the bootloader prompt shows up at the serial
console, and the boot proceeds normally.
So something is screwy with BIOS boot graphics under -machine q35 with
NVMM.
From: Taylor R Campbell <riastradh@NetBSD.org>
To: Roy Marples <roy@marples.name>,
Michael van Elst <mlelstv@serpens.de>,
Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Sun, 26 Oct 2025 21:56:17 +0000
Following https://www.seabios.org/Debugging.html I tried building my
own SeaBIOS with extra debugging output, and diffed the output of
qemu-system-x86_64 \
-machine q35 \
-chardev stdio,id=3Dseabios \
-device isa-debugcon,iobase=3D0x402,chardev=3Dseabios
with and without `-accel nvmm'. Here are the main differences
(skipping a profusion of probably-insignificant hypervisor-section
cpuid queries), with - bad (-accel nvmm) and + good (no -accel nvmm):
No Xen hypervisor found.
enabling shadow ram
Running on QEMU (q35)
-physbits: signature=3D"GenuineIntel", pae=3Dyes, lm=3Dyes, phys-bits=3D39,=
valid=3Dyes
-cpuid 0x40000000: eax 40000000, signature '___ NVMM ___'
+physbits: signature=3D"AuthenticAMD", pae=3Dyes, lm=3Dyes, phys-bits=3D40,=
valid=3Dyes
+cpuid 0x40000000: eax 40000001, signature 'TCGTCGTCGTCG'
Found QEMU fw_cfg
QEMU fw_cfg DMA interface supported
+Add to e820 map: fd00000000 300000000 2
+qemu/e820: addr 0x000000fd00000000 len 0x0000000300000000 [reserved]
Add to e820 map: 00000000 08000000 1
qemu/e820: addr 0x0000000000000000 len 0x0000000008000000 [RAM]
qemu/e820: RamSize: 0x08000000
@@ -297,7 +298,7 @@
phys_alloc zone=3D0x06fffe78 size=3D148 align=3D10 ret=3D6fea500 (detail=
=3D0x06fea4d0)
Add romfile: etc/boot-fail-wait (size=3D4)
phys_alloc zone=3D0x06fffe78 size=3D148 align=3D10 ret=3D6fea430 (detail=
=3D0x06fea400)
-Add romfile: etc/e820 (size=3D20)
+Add romfile: etc/e820 (size=3D40)
phys_alloc zone=3D0x06fffe78 size=3D148 align=3D10 ret=3D6fea360 (detail=
=3D0x06fea330)
Add romfile: etc/smbios/smbios-anchor (size=3D31)
phys_alloc zone=3D0x06fffe78 size=3D148 align=3D10 ret=3D6fea290 (detail=
=3D0x06fea260)
@@ -398,6 +399,7 @@
phys_free 6fe9aa0 (detail=3D0x06fe9a70)
PCI: Using 00:01.0 for primary VGA
init smm
+handle_smi cmd=3D0 smbase=3D0x00030000
init mtrr
Found 1 cpu(s) max supported 1 cpu(s)
init PIR table
@@ -787,9 +789,13 @@
a=3D00000008 b=3D0000ffff c=3D00000000 d=3D0000ffff ds=3D0000 es=3Df=
000 ss=3D0000
si=3D00000000 di=3D00004c00 bp=3D00000000 sp=3D00006d52 cs=3Df000 ip=3Dc=
7eb f=3D0000
Attempting to allocate 512 bytes lowmem via pmm call to f000:c89f
+call32_smm 0x06ffee31 6cf8
+handle_smi cmd=3Db5 smbase=3D0x000a0000
pmm call arg1=3D0
pmm00: length=3D20 handle=3Dffffffff flags=3D9
phys_alloc zone=3D0x06fffe88 size=3D512 align=3D10 ret=3De6120 (detail=3D0=
x06fe8cd0)
+handle_smi cmd=3Db5 smbase=3D0x000a0000
+call32_smm done 0x06ffee31 e6120
VGA stack allocated at e6120
Turning on vga text mode console
I also inserted a sleep in enable_vga_console, and confirmed that the
first difference happens immediately after the first INT 10h(ax=3D0003)
call: in the good case, there's a blinking cursor after that; in the
bad case, there's none.
The missing handle_smi and call32_smm lines look suspicious.
From: RVP <rvp@SDF.ORG>
To: Taylor R Campbell <riastradh@NetBSD.org>
Cc: gnats-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Sun, 26 Oct 2025 22:20:12 +0000 (UTC)
On Sun, 26 Oct 2025, Taylor R Campbell wrote:
> The black screen failure is purely graphical. If I do:
> [...]
> So something is screwy with BIOS boot graphics under -machine q35 with
> NVMM.
>
Another workaround is to blindly force VESA mode:
boot> vesa on
OR,
boot> vesa 0xXXX # modenum from `vesa list'
-RVP
From: Taylor R Campbell <riastradh@NetBSD.org>
To: Roy Marples <roy@marples.name>,
Michael van Elst <mlelstv@serpens.de>,
Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Sun, 26 Oct 2025 23:09:13 +0000
I found that nvmm is not actually the culprit here -- it is only
indirectly responsible. qemu's nvmm accelerator doesn't support SMM
(System Management Mode), so
-machine q35 -accel nvmm
implies
-machine q35,smm=off -accel nvmm
and it turns out that `smm=off' is enough to reproduce the issue.
That is, minimal reproducer (no extra arguments needed):
(works) qemu-system-x86_64 -machine q35
(fails) qemu-system-x86_64 -machine q35,smm=off
I tried with qemu-6.2 and seabios-1.15.0 on Ubuntu, and both worked
fine. I also tried with qemu-10.1.1 and seabios-1.15.0 on NetBSD, and
the bug reproduced. So maybe something changed with smm=off between
qemu-6.2 and qemu-10.1.1 that broke SeaBIOS but not OVMF UEFI.
From: Taylor R Campbell <riastradh@NetBSD.org>
To: Roy Marples <roy@marples.name>,
Michael van Elst <mlelstv@serpens.de>,
Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Mon, 27 Oct 2025 00:19:19 +0000
Upstream bug report:
Black screen in Windows XP
https://gitlab.com/qemu-project/qemu/-/issues/2608
> This can be reduced to:
>=20
> ./qemu-system-x86_64 -machine q35,smm=3Doff,accel=3Dkvm -vga std -cdrom w=
inxp.iso
>=20
> The key here is smm=3Doff. Without it, the thing just works.
>=20
> The behavior change has been introduced by (bisection points to)
> commit b07bf7b7 (before this commit, winXP guest shows text-mode
> output fine, after - only graphics mode is shown).
From: Taylor R Campbell <riastradh@NetBSD.org>
To: Roy Marples <roy@marples.name>,
Michael van Elst <mlelstv@serpens.de>,
Martin Husemann <martin@duskware.de>
Cc: gnats-bugs@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: kern/59721: qemu VM's blackscreen over VNC wth -machine q35
Date: Mon, 27 Oct 2025 01:15:09 +0000
This is a multi-part message in MIME format.
--=_17Wymd7lPaKOmlAiVMiz9N/EY5eA0fm1
The attached patch to qemu makes q35 with smm=off -- or with nvmm --
work to display a VGA console again on my machine.
As workarounds pending an upstream fix or pkgsrc patch, you can:
1. use serial console instead of graphical console,
2. use OVMF for UEFI boot rather than SeaBIOS for BIOS boot, by adding
`-bios $LOCALBASE/share/ovmf/OVMFX64.fd' to qemu arguments
--=_17Wymd7lPaKOmlAiVMiz9N/EY5eA0fm1
Content-Type: text/plain; charset="ISO-8859-1"; name="patch-hw_pci-host_q35"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="patch-hw_pci-host_q35.c"
$NetBSD$
Work around black screen in VGA mode with SMM disabled, as required by,
e.g., NVMM:
https://gnats.NetBSD.org/59721
https://gitlab.com/qemu-project/qemu/-/issues/2608
--- hw/pci-host/q35.c.orig 2025-10-08 20:50:34.000000000 +0000
+++ hw/pci-host/q35.c
@@ -373,6 +373,10 @@ static void mch_update_smram(MCHPCIState
memory_region_set_enabled(&mch->high_smram, false);
}
=20
+ if (!mch->has_smm_ranges) {
+ goto out;
+ }
+
if ((pd->config[MCH_HOST_BRIDGE_ESMRAMC] & MCH_HOST_BRIDGE_ESMRAMC_T_E=
N) &&
(pd->config[MCH_HOST_BRIDGE_SMRAM] & SMRAM_G_SMRAME)) {
switch (pd->config[MCH_HOST_BRIDGE_ESMRAMC] &
@@ -406,7 +410,7 @@ static void mch_update_smram(MCHPCIState
mch->below_4g_mem_size - tseg_size);
memory_region_set_alias_offset(&mch->tseg_window,
mch->below_4g_mem_size - tseg_size);
-
+out:
memory_region_transaction_commit();
}
=20
@@ -478,15 +482,15 @@ static void mch_write_config(PCIDevice *
mch_update_pciexbar(mch);
}
=20
- if (!mch->has_smm_ranges) {
- return;
- }
-
if (ranges_overlap(address, len, MCH_HOST_BRIDGE_SMRAM,
MCH_HOST_BRIDGE_SMRAM_SIZE)) {
mch_update_smram(mch);
}
=20
+ if (!mch->has_smm_ranges) {
+ return;
+ }
+
if (ranges_overlap(address, len, MCH_HOST_BRIDGE_EXT_TSEG_MBYTES,
MCH_HOST_BRIDGE_EXT_TSEG_MBYTES_SIZE)) {
mch_update_ext_tseg_mbytes(mch);
@@ -589,10 +593,6 @@ static void mch_realize(PCIDevice *d, Er
PAM_EXPAN_BASE + i * PAM_EXPAN_SIZE, PAM_EXPAN_SIZE);
}
=20
- if (!mch->has_smm_ranges) {
- return;
- }
-
/* if *disabled* show SMRAM to all CPUs */
memory_region_init_alias(&mch->smram_region, OBJECT(mch), "smram-regio=
n",
mch->pci_address_space, MCH_HOST_BRIDGE_SMRAM=
_C_BASE,
@@ -608,6 +608,10 @@ static void mch_realize(PCIDevice *d, Er
&mch->open_high_smram, 1);
memory_region_set_enabled(&mch->open_high_smram, false);
=20
+ if (!mch->has_smm_ranges) {
+ return;
+ }
+
/* smram, as seen by SMM CPUs */
memory_region_init(&mch->smram, OBJECT(mch), "smram", 4 * GiB);
memory_region_set_enabled(&mch->smram, true);
--=_17Wymd7lPaKOmlAiVMiz9N/EY5eA0fm1--
State-Changed-From-To: open->analyzed
State-Changed-By: riastradh@NetBSD.org
State-Changed-When: Mon, 27 Oct 2025 01:52:49 +0000
State-Changed-Why:
bug found, patch posted, forwarded upstream, workarounds listed
Responsible-Changed-From-To: kern-bug-people->pkg-manager
Responsible-Changed-By: bsiegert@NetBSD.org
Responsible-Changed-When: Wed, 29 Oct 2025 08:23:34 +0000
Responsible-Changed-Why:
This is a qemu issue, not a kernel bug.
From: "Taylor R Campbell" <riastradh@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc:
Subject: PR/59721 CVS commit: pkgsrc/emulators/qemu
Date: Fri, 2 Jan 2026 05:16:24 +0000
Module Name: pkgsrc
Committed By: riastradh
Date: Fri Jan 2 05:16:24 UTC 2026
Modified Files:
pkgsrc/emulators/qemu: Makefile distinfo
Added Files:
pkgsrc/emulators/qemu/patches: patch-hw_pci-host_q35.c
Log Message:
emulators/qemu: Allow VGA register access with smm=off.
PR kern/59721: qemu VM's blackscreen over VNC wth -machine q35
https://gnats.NetBSD.org/59721
https://gitlab.com/qemu-project/qemu/-/issues/2608
To generate a diff of this commit:
cvs rdiff -u -r1.391 -r1.392 pkgsrc/emulators/qemu/Makefile
cvs rdiff -u -r1.243 -r1.244 pkgsrc/emulators/qemu/distinfo
cvs rdiff -u -r0 -r1.1 pkgsrc/emulators/qemu/patches/patch-hw_pci-host_q35.c
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.47 2022/09/11 19:34:41 kim Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
Home