Date: Wed, 17 Jul 2024 02:04:31 +0100 From: Polarian <polarian@polarian.dev> To: virtualization@freebsd.org Subject: Re: nmdm issues with bhyve Message-ID: <20240717020431.2c53edfa@PolarianBSD> In-Reply-To: <4b081401-4f57-42b7-9795-c7c3885e3b68@freebsd.org> References: <20240716153851.60c1ea61@PolarianBSD> <16dfe6b3-2ef1-4859-a5b0-a36efe452804@FreeBSD.org> <4b081401-4f57-42b7-9795-c7c3885e3b68@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
> The -w option is needed so that bhyve won't exit on accessing an
> unimplemented MSR (that particular one is harmless).
Apologies, this is within the wiki [1], however I must have missed it
when I was typing out the command.
However, I have tested it right now, even with the -w option the nmdm
device does not show up still.
When testing with stdio:
wrmsr to register 0xc0011029(0x3) on vcpu 0
Followed by:
sh: turning off NDELAY mode
Which I assume is bhyve forking into the background?
Anyways updated configuration is below:
bhyve -c 1 -m 1G -u -H -w \
-s 0,amd_hostbridge \
-s 3,ahci-hd,/home/bitflame/install75.img \
-s 4,virtio-blk,/dev/zvol/zpool-storage/dns \
-s 5,virtio-net,tap0 \
-s 31,lpc -l com1,stdio \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
dns
Bakul I have read your configuration, I haven't had time to test it, I
will test it shortly to see if something there resolves the problem.
Thank you for the help,
--
Polarian
GPG signature: 0770E5312238C760
Jabber/XMPP: polarian@icebound.dev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240717020431.2c53edfa>