#nvmm — Public Fediverse posts

#qemu #nvmm #archlinux on #netbsd

#qemu #nvmm #archlinux on #netbsd

#qemu #nvmm #archlinux on #netbsd

#netbsd #NVMM #Virtualization
auriga# nvmmctl identify
nvmm: Kernel API version 2
nvmm: State size 1008
nvmm: Max machines 128
nvmm: Max VCPUs per machine 256
nvmm: Max RAM per machine 128G
nvmm: Arch Mach conf 0
nvmm: Arch VCPU conf 0x3<CPUID,TPR>
nvmm: Guest FPU states 0x3<x87,SSE>

#netbsd #NVMM #Virtualization
auriga# nvmmctl identify
nvmm: Kernel API version 2
nvmm: State size 1008
nvmm: Max machines 128
nvmm: Max VCPUs per machine 256
nvmm: Max RAM per machine 128G
nvmm: Arch Mach conf 0
nvmm: Arch VCPU conf 0x3<CPUID,TPR>
nvmm: Guest FPU states 0x3<x87,SSE>

#netbsd #NVMM #Virtualization
auriga# nvmmctl identify
nvmm: Kernel API version 2
nvmm: State size 1008
nvmm: Max machines 128
nvmm: Max VCPUs per machine 256
nvmm: Max RAM per machine 128G
nvmm: Arch Mach conf 0
nvmm: Arch VCPU conf 0x3<CPUID,TPR>
nvmm: Guest FPU states 0x3<x87,SSE>

Haiku OS [GSoC 2024] Hardware Virtualization: Final Report
https://www.haiku-os.org/blog/dalme/2024-08-19_gsoc_2024_hardware_virtualization_final_report/
#ycombinator #gsoc #gsoc2024 #qemu #nvmm

Haiku OS [GSoC 2024] Hardware Virtualization: Final Report
https://www.haiku-os.org/blog/dalme/2024-08-19_gsoc_2024_hardware_virtualization_final_report/
#ycombinator #gsoc #gsoc2024 #qemu #nvmm

Haiku OS [GSoC 2024] Hardware Virtualization: Final Report
https://www.haiku-os.org/blog/dalme/2024-08-19_gsoc_2024_hardware_virtualization_final_report/
#ycombinator #gsoc #gsoc2024 #qemu #nvmm

Haiku OS [GSoC 2024] Hardware Virtualization: Final Report
https://www.haiku-os.org/blog/dalme/2024-08-19_gsoc_2024_hardware_virtualization_final_report/
#ycombinator #gsoc #gsoc2024 #qemu #nvmm

@aep @simondassow

Note that your use of the singular is wrong there. It's not the same across all of the BSDs. "*bsd" is not correct in this case.

https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve

https://netbsd.org/docs/guide/en/chap-virt.html

#NetBSD #FreeBSD #bhyve #nvmm

@aep @simondassow

Note that your use of the singular is wrong there. It's not the same across all of the BSDs. "*bsd" is not correct in this case.

https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve

https://netbsd.org/docs/guide/en/chap-virt.html

#NetBSD #FreeBSD #bhyve #nvmm

@aep @simondassow

Note that your use of the singular is wrong there. It's not the same across all of the BSDs. "*bsd" is not correct in this case.

https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve

https://netbsd.org/docs/guide/en/chap-virt.html

#NetBSD #FreeBSD #bhyve #nvmm

@aep @simondassow

Note that your use of the singular is wrong there. It's not the same across all of the BSDs. "*bsd" is not correct in this case.

https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve

https://netbsd.org/docs/guide/en/chap-virt.html

#NetBSD #FreeBSD #bhyve #nvmm

@aep @simondassow

Note that your use of the singular is wrong there. It's not the same across all of the BSDs. "*bsd" is not correct in this case.

https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve

https://netbsd.org/docs/guide/en/chap-virt.html

#NetBSD #FreeBSD #bhyve #nvmm

And here it is. Slackware 15 running under qemu/nvmm on NetBSD. Retro fvwm theme to honor that of Slackware 1.1.2.
Listening to aNONradio by having qemu redirect OSS output to /dev/audio. Performance is good with 2 dedicated cores and 4G of RAM.
#slackware #netbsd #qemu #nvmm #virtualization #hypervisors #sdf #anonradio

And here it is. Slackware 15 running under qemu/nvmm on NetBSD. Retro fvwm theme to honor that of Slackware 1.1.2.
Listening to aNONradio by having qemu redirect OSS output to /dev/audio. Performance is good with 2 dedicated cores and 4G of RAM.
#slackware #netbsd #qemu #nvmm #virtualization #hypervisors #sdf #anonradio

#NetBSD i386 and amd64 testbeds now use #NVMM which reduces the time it takes to run the test suite from more than 20 hours to about 3-4 hours.
http://mail-index.netbsd.org/current-users/2020/08/10/msg039351.html

#NetBSD i386 and amd64 testbeds now use #NVMM which reduces the time it takes to run the test suite from more than 20 hours to about 3-4 hours.
http://mail-index.netbsd.org/current-users/2020/08/10/msg039351.html

DragonFly seems to run OK under QEMU with NVMM acceleration on NetBSD/adm64 9 (RC2) #dragonflybsd #nvmm