On Fri, Nov 18, 2022 at 07:19:33PM +0100, Mark Kettenis wrote: > > Date: Fri, 18 Nov 2022 09:18:52 -0800 > > From: Mike Larkin <mlar...@nested.page> > > > > On Fri, Nov 18, 2022 at 12:37:48AM +0100, Mike Fischer wrote: > > > On a host running OpenBSD 7.2 stable, amd64, all updates & patches using > > > vmd I have a VM, configured with 1 GB RAM, 40 GB virtual disk, network > > > access direct through host bridge0 (FAQ option #4). The VM has also been > > > installed with OpenBSD 7.2 stable + patches. > > > > > > For the first time in my life I wanted to try upgrading to -current. This > > > is what happened: > > > > > > 20221118T003040 root@vm2:~# sysupgrade -s > > > Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/ > > > SHA256.sig 100% |*************************************| 2144 > > > 00:00 > > > Signature Verified > > > INSTALL.amd64 100% |************************************| 43554 > > > 00:00 > > > base72.tgz 100% |*************************************| 332 MB > > > 00:50 > > > bsd 100% |*************************************| 22479 KB > > > 00:04 > > > bsd.mp 100% |*************************************| 22584 KB > > > 00:04 > > > bsd.rd 100% |*************************************| 4547 KB > > > 00:01 > > > comp72.tgz 100% |*************************************| 75037 KB > > > 00:12 > > > game72.tgz 100% |*************************************| 2745 KB > > > 00:01 > > > man72.tgz 100% |*************************************| 7609 KB > > > 00:02 > > > xbase72.tgz 100% |*************************************| 52858 KB > > > 00:09 > > > xfont72.tgz 100% |*************************************| 22967 KB > > > 00:04 > > > xserv72.tgz 100% |*************************************| 14815 KB > > > 00:03 > > > xshare72.tgz 100% |*************************************| 4573 KB > > > 00:01 > > > Verifying sets. > > > Fetching updated firmware. > > > fw_update: added none; updated none; kept none > > > Upgrading. > > > syncing disks... done > > > vmmci0: powerdown > > > rebooting... > > > Using drive 0, partition 3. > > > Loading...... > > > probing: pc0 com0 mem[638K 1022M a20=on] > > > disk: hd0+ > > > >> OpenBSD/amd64 BOOT 3.55 > > > upgrade detected: switching to /bsd.upgrade > > > | > > > com0: 115200 baud > > > switching console to com0 > > > >> OpenBSD/amd64 BOOT 3.55 > > > boot> > > > booting hd0a:/bsd.upgrade: 3916484+1643520+3882152+0+704512 > > > [109+439944+293419]=0xa624a8 > > > entry point at 0xffffffff81001000 > > > Copyright (c) 1982, 1986, 1989, 1991, 1993 > > > The Regents of the University of California. All rights reserved. > > > Copyright (c) 1995-2022 OpenBSD. All rights reserved. > > > https://www.OpenBSD.org > > > > > > OpenBSD 7.2-current (RAMDISK_CD) #797: Thu Nov 17 08:26:28 MST 2022 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > > > real mem = 1056952320 (1007MB) > > > avail mem = 1020960768 (973MB) > > > random: good seed from bootblocks > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf36e0 (10 entries) > > > bios0: vendor SeaBIOS version "1.14.0p0-OpenBSD-vmm" date 01/01/2011 > > > bios0: OpenBSD VMM > > > acpi at bios0 not configured > > > cpu0 at mainbus0: (uniprocessor) > > > fatal protection fault in supervisor mode > > > trap type 4 code ffffffff rip ffffffff811d7322 cs 8 rflags 10202 cr2 0 > > > cpl e rsp ffffffff81a06d10 > > > gsbase 0xffffffff818f7ff0 kgsbase 0x0 > > > panic: trap type 4, code=ffffffff, pc=ffffffff811d7322 > > > > > > The operating system has halted. > > > Please press any key to reboot. > > > > > > > > > Note: I tried this a few times with identical results. > > > > > > Is the snapshot broken? > > > Or are snapshots not supported on vmd VMs? > > > Or am I doing something wrong? > > > > > > > Not sure if this was a one-off problem with that snapshot or not, but I just > > tested snapshot 800 (18 nov) and it works fine here on similar hardware in > > vmd. > > > > You might try the sysupgrade again. > > A sysupgrade of the guest won't help. A -current guest will not run > on a -release host running vmd(8) on most AMD hardware because > -current uses an MSR that isn't passed through by the -release vmd(8). > > So a sysupgrade of the host (to a snapshot) will fix this. >
ah, missed the part about the host being 7.2-stable. Thanks.
