Skip to content

petri: use com3 for kmsg logs #1176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

tjones60
Copy link
Contributor

Using COM3 instead of diag_client allows us to get OpenHCL logs if it crashes early in boot

@tjones60 tjones60 requested a review from a team as a code owner April 10, 2025 22:57
let firmware_load_path = r#"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Virtualization"#;
xshell::cmd!(sh, "reg add {firmware_load_path} /v AllowFirmwareLoadFromFile /t REG_DWORD /d 1 /f").run()?;

// Enable COM3 and COM4 for Hyper-V VMs so we can get the OpenHCL KMSG logs over serial
xshell::cmd!(sh, "Enable-VelocityFeature -Feature 21938063").run()?;
Copy link
Member

Choose a reason for hiding this comment

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

No. This is an internal thing.

I thought we added a reg key or another mechanism to enable COM3, without velocity.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed to use the registry key

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looks like that reg key did not make it to ge_release, which is what we use for our 1es test runners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants