Skip to content

Status/2025Q4/bhyve-cpuid.adoc: Add report#602

Closed
hrosenfeld wants to merge 1 commit intofreebsd:mainfrom
hrosenfeld:main
Closed

Status/2025Q4/bhyve-cpuid.adoc: Add report#602
hrosenfeld wants to merge 1 commit intofreebsd:mainfrom
hrosenfeld:main

Conversation

@hrosenfeld
Copy link
Contributor

Given how late in Q4 this project started, there wasn't really any substantial progress in Q4. I'm using this mainly to introduce the CPUID project and describe the existing proof-of-concept that I created in July.

host CPU should be made available to the VM guest, some other CPU information
such as for system topology needs to be modified to match the VM configuration,
and then there is some additional information that needs to be reported that no
real CPU supports, such as the hypervisor identification,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a comma ending the sentence instead of a period.

based on a real CPU or an architectural subset, would avoid this problem
entirely.

- Hypervisor Signature Modification: Some software such as the Nvidia drivers
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

drivers was written twice

- a user-friendly configuration method for the hypervisor signature reported by
bhyve
- a set of predefined CPUID configurations based on common x86 architecture
levels, perhaps also including a sets of CPUID data for a few real CPU models,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a sets should be a set.

@@ -0,0 +1,90 @@
=== Full CPUID Control for bhyve
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. The status report teams asks for each sentence to be on a separate line.
  2. Do you have any objections to adding a Sponsor: The FreeBSD Foundation at the end?

Here is an example: https://raw.githubusercontent.com/freebsd/freebsd-doc/refs/heads/main/website/content/en/status/report-2025-10-2025-12/lkpi-wireless.adoc

freebsd-git pushed a commit that referenced this pull request Feb 16, 2026
Reviewed by:	jrm
Pull Request:	#602
@lsalvadore
Copy link
Member

Merged, thanks!

@Jehops: I have not added the sponsor line as I know nothing about the sponsorship status of this project. As far as status reporting is concerned, feel free to add and commit it if you think it should have it.

@lsalvadore lsalvadore closed this Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments