Page MenuHomeFreeBSD

bhyve: namescope virtio_msix to virtio.msix
ClosedPublic

Authored by njain15_protonmail.com on Jul 22 2026, 1:01 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Aug 18, 11:43 AM
Unknown Object (File)
Mon, Aug 17, 11:02 PM
Unknown Object (File)
Mon, Aug 17, 12:41 PM
Unknown Object (File)
Sun, Aug 16, 8:11 PM
Unknown Object (File)
Sun, Aug 16, 8:01 PM
Unknown Object (File)
Sat, Aug 15, 12:55 AM
Unknown Object (File)
Thu, Aug 13, 10:48 PM
Unknown Object (File)
Wed, Aug 12, 2:01 PM

Details

Summary

The bhyve_config(5) variable virtio_msix is namescoped to virtio.msix. Configurations that have the old variable will automatically be mapped to the new one, with a warning message printed out.

Relnotes: yes

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

markj added a subscriber: markj.
markj added inline comments.
usr.sbin/bhyve/riscv/bhyverun_machdep.c
188

Extra newline here.

This revision is now accepted and ready to land.Thu, Jul 23, 4:42 PM
jhb added inline comments.
usr.sbin/bhyve/bhyverun.c
250 ↗(On Diff #182435)

I think you can actually get rid of msg as a separate argument and instead just use new. I would also split this into two commits: one to add bhyve_cfg_warn() and to use it in place of the existing checks, and a second to just do virtio.msix.

Updated per reviewer comments. D58636 is the parent revision, adding the deprecation warning function.

I am not sure how to get Phabricator to only show the diff relative to the parent revision.

This revision now requires review to proceed.Tue, Aug 4, 3:06 AM

Should we put something in UPDATING?

@ziaee Yes I think this should be noted in UPDATING.

@ziaee Yes I think this should be noted in UPDATING.

RELNOTES would be more appropriate. UPDATING is for users tracking main.

This revision is now accepted and ready to land.Tue, Aug 4, 8:45 PM
ziaee added a reviewer: manpages.

@ziaee Yes I think this should be noted in UPDATING.

RELNOTES would be more appropriate. UPDATING is for users tracking main.

LGTM with Relnotes: yes.

njain15_protonmail.com marked an inline comment as done.

@ziaee Yes I think this should be noted in UPDATING.

RELNOTES would be more appropriate. UPDATING is for users tracking main.

LGTM with Relnotes: yes.

I edited the summary with a message and this tag. Is this the right way?

@ziaee Yes I think this should be noted in UPDATING.

RELNOTES would be more appropriate. UPDATING is for users tracking main.

LGTM with Relnotes: yes.

I edited the summary with a message and this tag. Is this the right way?

That's fine, yeah. For more elaborate messages you can edit the RELNOTES file but here that's not necessary IMO. I'll land these two changes first.

This patch doesn't apply to main, does it need to be rebased?

njain15_protonmail.com edited the summary of this revision. (Show Details)

Ok, I've updated the diff to be relative to the parent one (that one applies cleanly to main).

This revision now requires review to proceed.Mon, Aug 10, 8:55 PM
This revision was not accepted when it landed; it landed in state Needs Review.Tue, Aug 11, 2:24 PM
This revision was automatically updated to reflect the committed changes.

Hmm, doesn't fbsdrun_virtio_msix() need to be updated too?

Hmm, doesn't fbsdrun_virtio_msix() need to be updated too?

Oh no, I forgot to include it in the review. Adding a review now.