witness panic: "acquiring blockable sleep lock..." from reaper

>Synopsis: witness panic: acquiring blockable sleep lock with spinlock or critical section held (rwlock) vmmaplk >Category: >Environment: System : OpenBSD 7.5 Details : OpenBSD 7.5-current (GENERIC.MP) #5: Wed Jun 5 20:07:42 CEST 2024

Re: Start VM leads to increased CPU usage and crash at the end

Kirill A. Korinsky writes: > On Tue, 21 May 2024 18:38:39 +0100, > Dave Voutila wrote: >> >> Can you reproduce this and get details on which process panics? It's not >> clear what the vm cpu usage has to do with this panic, if anything. > > I'll try. May you sug

Re: Start VM leads to increased CPU usage and crash at the end

Kirill A. Korinsky writes: > Hi, > > I've removed to related quotes > > On Tue, 21 May 2024 18:09:15 +0100, > Dave Voutila wrote: >> >> >> kir...@korins.ky writes: >> >> > >> >My machine had an uptime for about a day with a lot o

Re: Start VM leads to increased CPU usage and crash at the end

kir...@korins.ky writes: >>Synopsis: Start VM leads to increased CPU usage and crash at the end >>Category: vmd >>Environment: > System : OpenBSD 7.5 > Details : OpenBSD 7.5-current (GENERIC.MP) #138: Mon May 20 > 17:02:52 WEST 2024 > >

Re: vmm guest does not get IP after upgrade to 7.5

Florian Obser writes: > On 2024-05-16 09:42 -04, Dave Voutila wrote: >> Johan Huldtgren writes: >> >>> hello, >>> >>> On 2024-05-16 8:14, Dave Voutila wrote: >>>> >>>> Johan Huldtgren writes: >>> $ doas ca

Re: vmm guest does not get IP after upgrade to 7.5

Johan Huldtgren writes: > hello, > > On 2024-05-16 8:14, Dave Voutila wrote: >> >> Johan Huldtgren writes: >> >> > hello, >> > >> > On 2024-05-15 17:31, Dave Voutila wrote: >> >> >> >> Johan Huldtgren writes

Re: vmm guest does not get IP after upgrade to 7.5

Johan Huldtgren writes: > hello, > > On 2024-05-15 17:31, Dave Voutila wrote: >> >> Johan Huldtgren writes: >> >> >> Synopsis: vmm guest does not get IP after upgrade to 7.5 >> >> Category: vmd >> >> Environment: >> >

Re: vmm guest does not get IP after upgrade to 7.5

Johan Huldtgren writes: >> Synopsis:vmm guest does not get IP after upgrade to 7.5 >> Category:vmd >> Environment: > System : OpenBSD 7.5 > Details : OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 > >

Re: vmd/vionet: locked lladdr regression

Klemens Nanni writes: > kern.version=OpenBSD 7.4-current (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST > 2024 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > 'locked addr' in `switch' block yields > vm/foo/vionet0: vionet_rx_copy: invalid injected packet

Re: vmd/vionet/vioblk: network + disk regression

Klemens Nanni writes: > kern.version=OpenBSD 7.4-current (GENERIC.MP) #1667: Wed Feb 7 20:09:35 MST > 2024 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > This boots fine: > > # cat /tmp/vm.conf > vm foo { > disable >

Re: panic: pool_do_get: mcl2k free list modified on autoinstall VM

"Kirill A. Korinsky" writes: > [[PGP Signed Part:Undecided]] >> On 2. Jan 2024, at 16:34, Dave Voutila wrote: >> >> "Kirill A. Korinsky" writes: >> >>> Greetings, >>> >>> When playing with autoinstall in VM I encounte

Re: vmm guest crash in vio

Stefan Fritsch writes: > On Tue, 9 Jan 2024, Dave Voutila wrote: > >> >> Stefan Fritsch writes: >> >> > On 08.01.24 22:24, Alexander Bluhm wrote: >> >> Hi, >> >> When running a guest in vmm and doing ifconfig operations on vio >&g

Re: vmm guest crash in vio

Mark Kettenis writes: >> From: Dave Voutila >> Date: Tue, 09 Jan 2024 09:19:56 -0500 >> >> Stefan Fritsch writes: >> >> > On 08.01.24 22:24, Alexander Bluhm wrote: >> >> Hi, >> >> When running a guest in vmm and doing ifconfig op

Re: vmm guest crash in vio

Stefan Fritsch writes: > On 08.01.24 22:24, Alexander Bluhm wrote: >> Hi, >> When running a guest in vmm and doing ifconfig operations on vio >> interface, I can crash the guest. >> I run these loops in the guest: >> while doas ifconfig vio1 inet 10.188.234.74/24; do :; done >> while doas

Re: vmm guest crash in vio

Alexander Bluhm writes: > Hi, > > When running a guest in vmm and doing ifconfig operations on vio > interface, I can crash the guest. Any chance you've tried this in another hypervisor, like KVM/QEMU? I'd like to isolate if this is a vmd(8) issue in the emulated network device or if it's in

Re: panic: pool_do_get: mcl2k free list modified on autoinstall VM

"Kirill A. Korinsky" writes: > Greetings, > > When playing with autoinstall in VM I encountered a kernel panic. It doesn't > happened each attempt, but often enough to be easy found. Thanks for the report. It looks like you're using 7.4 for the host and guest (based on the dmesg and the fact

Re: Impossible to use 00:50:56:00:20:a5 at VM

"Kirill A. Korinsky" writes: > Greetings, > > Seems that it is impossible to setup some MAC address to an network interfce > of > VM. For example I have a VM with settings: > > vm "mx0" { > memory 1G > > disk "/var/vm/mx0.qcow2" > > interface { > switch

Re: pflogd spamming syslog

Alexandr Nedvedicky writes: > Hello, > > diff below seems to make empty log message go way. I can't speak for correctness, but I can confirm pflogd stops writing empty messages on my machine with the diff. -dv > we have to check if sig_alrm fired here in pflogd: > > > 725 while (1)

Re: VMD:cu:console: copy-paste causes "vmd" CPU spike for 2-3 min. Massive "ipi" syscalls ~3500 rate.

> finding it via search later. > Cheers! > > --- Original Message --- > On Tuesday, June 20th, 2023 at 4:16 AM, Dave Voutila wrote: > > >> I recommend connecting to your guests via ssh. This is a known design >> issue at the moment without a trivial fix as it

Re: Dell OptiPlex 5070 SFF - Resuming suspended system not working as expected

Ricky Cintron writes: > On 2023-08-01 12:32, Dave Voutila wrote: >> Ricky Cintron writes: >> >>>> Synopsis: Resuming my suspended system requires two attempts >>>> Category: system amd64 >>>> Environment: >>> System

Re: Dell OptiPlex 5070 SFF - Resuming suspended system not working as expected

Ricky Cintron writes: >> Synopsis:Resuming my suspended system requires two attempts >> Category:system amd64 >> Environment: > System : OpenBSD 7.3 > Details : OpenBSD 7.3-current (GENERIC.MP) #1320: Fri Jul > 28 11:14:52 MDT 2023 > >

Re: vmd doesn't honor "local prefix"

"Timothy Beaver" writes: > Hi folks, > > Dave Voutila writes: >> Lucas writes: >> >> >>Fix: >> >Dunno. I have the theory that this "broke" (idk if it worked >> >before or not) after "vmd(8): introduce

Re: vmd doesn't honor "local prefix"

Lucas writes: >>Synopsis: vmd doesn't honor "local prefix" >>Category: vmd >>Environment: > System : OpenBSD 7.3 > Details : OpenBSD 7.3-current (GENERIC.MP) #1175: Wed May 3 > 08:19:33 MDT 2023 > >

Re: tpm0 at acpi0 TPM2: unsupported TPM2 start method 2

Zheng Harteg writes: > Dear OpenBSD team, > > Excuse me, I come from China, and my English is very poor. > I sent an email to ask a question. In my dmesg, there is an error message: > "tpm0 at acpi0 TPM2: unsupported TPM2 start method 2". Can you fix it? Unless the tpm is preventing usage of

Re: OpenBSD 7.3 amd64 crashes in OpenBSD hosted VM

Mike Larkin writes: > On Sat, Apr 22, 2023 at 03:57:35AM -0400, Dave Voutila wrote: >> >> Carson Harding writes: >> >> > Loading version 7.3 amd64 from install media or from sysupgrade into >> > an OpenBSD hosted VM (VMM) leads to immediate crash. This

Re: OpenBSD 7.3 amd64 crashes in OpenBSD hosted VM

Carson Harding writes: > Loading version 7.3 amd64 from install media or from sysupgrade into > an OpenBSD hosted VM (VMM) leads to immediate crash. This for amd64; > booting and installing i386 in a VM is ok, on same underlying 7.2 amd64 > host. > > GUEST: > > OpenBSD 7.3 (RAMDISK_CD) #1063:

Re: vmd guest terminates loading GRUB from debian-11.6.0

jon writes: >>Synopsis: vmd guest terminates loading GRUB from debian-11.6.0 >>Category: system amd64 >>Environment: > System : OpenBSD 7.2 > Details : OpenBSD 7.2 (GENERIC.MP) #7: Sat Feb 25 14:07:58 MST 2023 > >

Re: VM crash on 7.2#4

Mischa writes: > Hi, > > Just noticed one of the VMs greeted me with a ddb> prompt. > The host is running 7.2#4 as well as the VM, dmesg of the host below. > > I managed to get the following data from the VM: > > ddb> show panic > *cpu0: kernel diagnostic assertion "m != NULL" failed: file >

Re: VMM vcpu_exit_eptviolation and vionet_enq_rx buffer issues

Arrigo Triulzi writes: > On 6 Dec 2022, at 18:20, Mike Larkin wrote: >> As dv@ pointed out in a previous mail, the eptviolation exit message can >> be ignored (and as he points out, should probably be removed or > [...] >> packets. You could experiment with raising that (it's in >>

Re: vmm guests die during host's supspend/resume

Dave Voutila writes: > Martin Pieuchot writes: > >> I see the following in the dmesg: >> >> vcpu_run_vmx: failed vmresume for unknown reason >> vcpu_run_vmx: error code = 5, VMRESUME: non-launched VMCS > > This is due to intel's vmx design. We need

Re: vmm guests die during host's supspend/resume

at pci0 dev 22 function 0 not configured > em0 at pci0 dev 25 function 0 "Intel I218-V" rev 0x03: msi, address > 54:ee:75:43:b3:62 > azalia1 at pci0 dev 27 function 0 "Intel 9 Series HD Audio" rev 0x03: msi > azalia1: codecs: Realtek ALC292 > audio0 at azalia1 > ppb0 at pci0 dev 28 function 0 "Intel 9 Series PCIE" rev 0xe3: msi > pci1 at ppb0 bus 3 > ppb1 at pci0 dev 28 function 1 "Intel 9 Series PCIE" rev 0xe3: msi > pci2 at ppb1 bus 4 > iwm0 at pci2 dev 0 function 0 "Intel AC 7265" rev 0x59, msi > pcib0 at pci0 dev 31 function 0 "Intel 9 Series LPC" rev 0x03 > ahci0 at pci0 dev 31 function 2 "Intel 9 Series AHCI" rev 0x03: msi, AHCI 1.3 > ahci0: port 3: 6.0Gb/s > scsibus1 at ahci0: 32 targets > sd0 at scsibus1 targ 3 lun 0: > naa.5002538844584d30 > sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin > ichiic0 at pci0 dev 31 function 3 "Intel 9 Series SMBus" rev 0x03: apic 2 int > 18 > iic0 at ichiic0 > pchtemp0 at pci0 dev 31 function 6 "Intel 9 Series Thermal" rev 0x03 > isa0 at pcib0 > isadma0 at isa0 > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > pckbd0 at pckbc0 (kbd slot) > wskbd0 at pckbd0: console keyboard > pms0 at pckbc0 (aux slot) > wsmouse0 at pms0 mux 0 > wsmouse1 at pms0 mux 0 > pms0: Synaptics clickpad, firmware 8.1, 0x1e2b1 0x943300 0x330040 0xf002a3 > 0x12e800 > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > vmm0 at mainbus0: VMX/EPT > uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics > Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 2 > video0 at uvideo0 > vscsi0 at root > scsibus2 at vscsi0: 256 targets > softraid0 at root > scsibus3 at softraid0: 256 targets > sd1 at scsibus3 targ 1 lun 0: > sd1: 244190MB, 512 bytes/sector, 500102858 sectors > root on sd1a (72519550243ad631.a) swap on sd1b dump on sd1b > inteldrm0: 2560x1440, 32bpp > wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation), using wskbd0 > wsdisplay0: screen 1-5 added (std, vt100 emulation) > iwm0: hw rev 0x210, fw ver 17.3216344376.0, address 60:57:18:c1:8b:d5 > video0 detached > uvideo0 detached > uhub0 detached > uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 > addr 1 > uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics > Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 2 > video0 at uvideo0 > video0 detached > uvideo0 detached > uhub0 detached > uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 > addr 1 > vcpu_run_vmx: failed vmresume for unknown reason > vcpu_run_vmx: error code = 5, VMRESUME: non-launched VMCS > uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics > Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 2 > video0 at uvideo0 > video0 detached > uvideo0 detached > uhub0 detached > uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 > addr 1 > uvideo0 at uhub0 port 8 configuration 1 interface 0 "Chicony Electronics > Co.,Ltd. Integrated Camera" rev 2.00/0.29 addr 2 > video0 at uvideo0 -- -Dave Voutila

Re: vmx_fault_page: uvm_fault returns 14, GPA=0xfe001818, rip=0xffffffffc0d6bb96

Mario Marietto writes: > Hello. > > Premising that I'm using this openbsd version : > > marietto# uname -a > > OpenBSD marietto.homenet.telecomitalia.it 7.0 GENERIC.MP#211 amd64 > > > I'm trying to install the NixOS Linux distribution as a virtual machine > guest hosted on OpenBSD VMM

Re: vmm cpuid handling [was: Re: fdc: fdcresult: overrun]

Philip Guenther writes: > On Wed, 17 Nov 2021, Josh Grosse wrote: > ... >> vmm_handle_cpuid: function 0x0a (arch. perf mon) not supported >> vmx_handle_cr: mov to cr0 @ 100149e, data=0x80010031 >> vmx_handle_wrmsr: wrmsr exit, msr=0x8b, discarding data written from >> guest=0x0:0x0 >>

Re: fdc: fdcresult: overrun

Dave Voutila writes: > Josh Grosse writes: > >> On Wed, Nov 17, 2021 at 08:36:35PM -0500, Dave Voutila wrote: >>> My work adding an ipi for clearing VMCS didn't touch anything to do with >>> emulating instructions touch memory regions. >>> >>> A

Re: fdc: fdcresult: overrun

Josh Grosse writes: > On Wed, Nov 17, 2021 at 08:36:35PM -0500, Dave Voutila wrote: >> My work adding an ipi for clearing VMCS didn't touch anything to do with >> emulating instructions touch memory regions. >> >> Another thing that changed around this time,

Re: panic: "wakeup: p_stat is 2" using btrace(8) & vmd(8)

Dave Voutila writes: > Was tinkering on a bt(5) script for trying to debug an issue in vmm(4) > when I managed to start hitting a panic "wakeup: p_stat is 2" being > triggered by kqueue coming from the softnet kernel task. > > I'm running an amd64 kernel built from t

panic: "wakeup: p_stat is 2" using btrace(8) & vmd(8)

Was tinkering on a bt(5) script for trying to debug an issue in vmm(4) when I managed to start hitting a panic "wakeup: p_stat is 2" being triggered by kqueue coming from the softnet kernel task. I'm running an amd64 kernel built from the tree today (latest CVS commit id UynQo1r7kLKA0Q2p) with

Re: vi: segfault on exit

"Todd C. Miller" writes: > On Sun, 24 Oct 2021 20:45:47 -0400, Dave Voutila wrote: > >> We end up freeing some strings and unlinking the temp file. You can >> easily see this without a debugger by checking /tmp before and after the >> reproduction step o

Re: vi: segfault on exit

Klemens Nanni writes: > I fat fingered commands and it crashed. Here is a reproducer > (files do not have to exist): > > $ vi foo > :e > :e bar > :q! > vi(12918) in free(): write after free 0xea559a2d980 >

Re: VMM Hypervisor, issue with BSD

openbsdtai123 writes: > Hello, > > I am pleased to report the bug, that vmm is not working properly. > The VMM code is non complete. > > acpi0 issue that originates with CPU. > > Error at boot: > http://termbin.com/33fq > > Gallery with terminals, showing the issue: >

Re: Sporadical 6.9 completely system hangs while VM is running Ryzen 4750U

Martin writes: > The hang mostly happened when VM guest run browser or any network activity > (repository updates etc). > > The bad thing I can't debug it because the host system hangs completely. > We'd need ddb backtrace output with register state and details of where the panic or fault is

Re: vmm protection fault trap

Josh Rickmar writes: > > This also fixes the crash for me. Tested by installing git and > electron into the ramdisk with abieber@'s iso as well as temporarily > installing these on my real nixos vm. Committed with ok from mlarkin@. Thanks again for reporting. And thanks abieber@ for helping

Re: vmm protection fault trap

Josh Rickmar writes: > On Sun, May 09, 2021 at 01:50:58PM +0000, Dave Voutila wrote: >> >> Mike Larkin writes: >> >> > On Sat, May 08, 2021 at 08:14:35AM -0400, Dave Voutila wrote: >> >> >> >> Josh Rickmar writes: >> >> &g

Re: vmm protection fault trap

Mike Larkin writes: > On Sat, May 08, 2021 at 08:14:35AM -0400, Dave Voutila wrote: >> >> Josh Rickmar writes: >> >> > On Fri, May 07, 2021 at 04:19:18PM -0400, Dave Voutila wrote: >> >> >> >> Josh Rickmar writes: >> >>

Re: vmm protection fault trap

Josh Rickmar writes: > On Fri, May 07, 2021 at 04:19:18PM -0400, Dave Voutila wrote: >> >> Josh Rickmar writes: >> >> >>Synopsis: vmm protection fault trap >> >>Category: vmm >> >>Environment: >> >System : OpenBSD 6.9

Re: vmm protection fault trap

Josh Rickmar writes: >>Synopsis: vmm protection fault trap >>Category: vmm >>Environment: > System : OpenBSD 6.9 > Details : OpenBSD 6.9-current (GENERIC.MP) #6: Thu May 6 10:16:53 > MDT 2021 > >

Re: vmm/vmd fails to boot bsd.rd

Josh Rickmar writes: > On Wed, Mar 10, 2021 at 04:56:03PM -0500, Dave Voutila wrote: >> >> Josh Rickmar writes: >> >> > On Wed, Mar 10, 2021 at 01:11:30PM -0500, Josh Rickmar wrote: >> >> On Tue, Mar 09, 2021 at 09:36:49PM -0800, Mike Larkin wrote:

Re: vmm/vmd fails to boot bsd.rd

8b}; /* gzip magic header */ > + > +static struct bootimage * > +vmboot_fdopen(int fd) > +{ > + struct bootimage *f; > + struct stat sb; > + u_char magic[2]; > + > + if (fstat(fd, ) == -1) > + return (NULL); > + if (S_ISDIR(sb.st_mode)) { > + errno = EISDIR; > + return (NULL); > + } > + > + if ((f = calloc(1, sizeof *f)) == NULL) > + return (NULL); > + > + if (pread(fd, magic, sizeof(magic), 0) != 2) > + return NULL; > + if (magic[0] == gz_magic[0] && magic[1] == gz_magic[1]) { > + f->type = FILE_GZIP; > + f->ops = _ops; > + if ((f->gzf = gzdopen(fd, "r")) != NULL) > + return f; > + } else { > + f->type = FILE_STREAM; > + f->ops = _ops; > + if ((f->f = fdopen(fd, "r")) != NULL) > + return f; > + } > + > + free(f); > + return NULL; > +} > + > +static struct bootimage * > +wrap_stream(FILE *fp) > +{ > + struct bootimage *f; > + > + if ((f = calloc(1, sizeof *f)) == NULL) > + return (NULL); > + f->type = FILE_STREAM; > + f->ops = _ops; > + f->f = fp; > + return (f); > +} > blob - 325d40d1ace0714e86d20fac20f3eaabd406d721 > file + usr.sbin/vmd/vmd.h > --- usr.sbin/vmd/vmd.h > +++ usr.sbin/vmd/vmd.h > @@ -30,6 +30,7 @@ > #include > #include > #include > +#include > > #include "proc.h" > > @@ -475,9 +476,31 @@ int config_getif(struct privsep *, struct imsg *); > int config_getcdrom(struct privsep *, struct imsg *); > > /* vmboot.c */ > -FILE *vmboot_open(int, int *, int, unsigned int, struct vmboot_params *); > -void vmboot_close(FILE *, struct vmboot_params *); > +struct bootimage_ops; > > +struct bootimage { > + int type; > +#define FILE_STREAM 0 > +#define FILE_GZIP1 > + FILE*f; > + gzFile *gzf; > + struct bootimage_ops const *ops; > +}; > + > +struct bootimage_ops { > + size_t (*read)(struct bootimage *, void *, size_t); > + int (*seek)(struct bootimage *, off_t, int); > +}; > + > +size_t stream_read(struct bootimage *f, void *, size_t); > +int stream_seek(struct bootimage *, off_t, int); > +size_t gzip_read(struct bootimage *f, void *, size_t); > +int gzip_seek(struct bootimage *, off_t, int); > + > +struct bootimage *vmboot_open(int, int *, int, unsigned int, > +struct vmboot_params *); > +void vmboot_close(struct bootimage *, struct vmboot_params *); > + > /* parse.y */ > int parse_config(const char *); > int cmdline_symset(char *); -- -Dave Voutila

Re: Panic in kern_event.c using async tcp sockets

On Mon, Dec 30, 2019 at 3:16 PM Dave Voutila wrote: > > >Synopsis: Panic in kern_event.c using Rust async tcp sockets on > >multi-cpu system > >Category: kernel > >Environment: > System : OpenBSD 6.6 > Details : OpenBSD 6.6-current (GENERIC.MP

Panic in kern_event.c using async tcp sockets

>Synopsis: Panic in kern_event.c using Rust async tcp sockets on multi-cpu >system >Category: kernel >Environment: System : OpenBSD 6.6 Details : OpenBSD 6.6-current (GENERIC.MP) #575: Mon Dec 30 04:47:45 MST 2019

Re: vmd freezes with Alpine Linux (current)

Maximilian Pichler writes: > When running vmd with an Apline Linux install image, it randomly > freezes soon after logging in. This is with the current branch as of > today. > > Steps to reproduce (the install image is >

Re: VMD consumes 100% cpu after unpausing guest

Peter Hessler <phess...@openbsd.org> writes: > On 2018 Feb 26 (Mon) at 18:52:34 -0800 (-0800), Pratik Vyas wrote: > :* Dave Voutila <d...@sisu.io> [2018-02-22 23:40:21 -0500]: > : > :> > Synopsis:VMD consumes 100% cpu after unpausing guest > :> > Ca

VMD consumes 100% cpu after unpausing guest

>Synopsis: VMD consumes 100% cpu after unpausing guest >Category: amd64 >Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-current (GENERIC.MP) #10: Wed Feb 21 21:26:27 MST 2018