you don’t boot from OVMFX64.fd, you specify it with ‘-bios …/OVMFX64.fd’ .
I just tested installing -current under a -current host with my copy of the bios file and it worked without a glitch. Chavdar On Sun, 17 Jul 2022 at 13:56, Mario Marietto <marietto2...@gmail.com> wrote: > One user gave me the missing file,OVMFX64.fd and I tried to see if it > worked. > > These are the parameters that I've used : > > case 1) > > qemu-system-x86_64 -accel nvmm \ > -cpu max -smp cpus=4 -m 8G \ > #-drive > if=pflash,format=raw,readonly=on,file=/usr/pkg/share/qemu/edk2-x86_64-code.fd > \ > #-drive > if=pflash,format=raw,readonly=on,file=/home/marietto/Downloads/vm/OVMF-X64-r15214/OVMF.fd > \ > -drive > if=pflash,format=raw,readonly=on,file=/home/marietto/Downloads/vm/OVMFX64.fd > \ > -drive > id=cdrom,if=none,media=cdrom,file=/home/marietto/Downloads/vm/ubuntu-22.04-desktop-amd64.iso > \ > -object rng-random,filename=/dev/urandom,id=viornd0 \ > -device virtio-rng-pci,rng=viornd0 \ > -netdev user,id=vioif0 -device virtio-net-pci,netdev=vioif0 \ > -audiodev oss,id=oss,out.dev=/dev/audio,in.dev=/dev/audio \ > -device ac97,audiodev=oss \ > -display sdl,gl=on -vga vmware \ > -usb -device usb-mouse,bus=usb-bus.0 > > and qemu + nvmm started (as you can see on the picture,but the iso image > won't boot) : > > you can see what happened here : ---> https://ibb.co/W5W90KH > > I've also tried to do : > > case 2) > > qemu-system-x86_64 -accel nvmm \ > -cpu max -smp cpus=4 -m 8G \ > -drive > if=pflash,format=raw,readonly=on,file=/home/marietto/Downloads/vm/OVMFX64.fd > \ > -drive > id=cdrom,if=none,media=cdrom,file=/home/marietto/Downloads/vm/ubuntu-22.04-desktop-amd64.iso > \ > -object rng-random,filename=/dev/urandom,id=viornd0 \ > -device virtio-rng-pci,rng=viornd0 \ > -netdev user,id=vioif0 -device virtio-net-pci,netdev=vioif0 \ > -audiodev oss,id=oss,out.dev=/dev/audio,in.dev=/dev/audio \ > -device ac97,audiodev=oss \ > -display sdl,gl=on -vga vmware \ > -usb -device usb-mouse,bus=usb-bus.0 > > and the error "NVMM: Mem Assist Failed [gpa=0xfffffff0]" appeared again. I > really don't understand why in the first case it seems that the bug is > fixed. And i suspect that inside the parameters there is a mistake,since > the iso image is not recognized. > > Il giorno dom 17 lug 2022 alle ore 14:12 Greg Troxel <g...@lexort.com> ha > scritto: > >> >> Mario Marietto <marietto2...@gmail.com> writes: >> >> > Actually I'm running OS108 based on this NetBSD version : >> >> I have never heard of OS108.n >> >> > localhost# uname -a >> > >> > NetBSD localhost 9.1_STABLE NetBSD 9.1_STABLE (GENERIC) #1: Sun Nov 8 >> > 03:50:47 IST 2020 >> > r...@unitedbsd.com:/usr/srcNEW/objNEW/sys/arch/amd64/compile/GENERIC >> > amd64 >> >> Maybe ask unitedbsd.com? >> >> > Someone told me : "the OVMFX64 file can be found in the package system >> > under sysutil/ovmf" ; ok,but I don't have the folder sysutil and I don't >> > have any ovmf file in my system. Why ? I suspect that some components >> are >> > missing in my system. Where can I get what I need to make some >> experiments >> > with qemu and nvmm ? thanks. >> >> See >> >> https://pkgsrc.org/ >> https://netbsd.org/docs/pkgsrc/ >> >> > > -- > Mario. > -- ----
