hyperlight-dev / hyperlight-dev/hyperlight

max_guest_log_level is not plumbed through snapshot load

未关闭
#1,698 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
lifecycle/confirmed
主要语言
Rust
星标
4.7k
派生
208
平均合并
1 天 7 小时
30 天内合并 PR
47

描述

### What happened?

After https://github.com/hyperlight-dev/hyperlight/pull/1465 is merged,

max_guest_log_level is not plumbed through snapshot load.

### Steps to Reproduce

1. Run '...'
2. And then do '...'
3. Check logs for '...'

### Expected Results

log level to be set when working with snapshot loads.

### Actual Results

TODO: What actually happened?

### Versions and Environment

Hyperlight version or commit: TODO

#### OS Version

Run the following to find your OS version:

Linux:
```console
cat /etc/os-release && uname -a
```

Windows (PowerShell):
```powershell
cmd /c ver
```

#### Hypervisor

Run the following to check hypervisor access:

Linux:
```console
ls -la /dev/kvm /dev/mshv 2>&1; getfacl /dev/kvm /dev/mshv 2>&1; id
[ -r /dev/kvm ] && [ -w /dev/kvm ] && echo "KVM: OK" || echo "KVM: FAIL"
[ -r /dev/mshv ] && [ -w /dev/mshv ] && echo "MSHV: OK" || echo "MSHV: FAIL"
```

Windows (Admin PowerShell):
```powershell
Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -match 'Hyper-V|HypervisorPlatform|VirtualMachinePlatform'} | Format-Table
```

### Extra Info

Anything else you'd like to add?

贡献指南

打开贡献指南

调研方向

Start by tracing the snapshot load path and the handling of max_guest_log_level, using the linked pull request for context. Reproduce the snapshot-loading case described in the issue, then verify that the guest log level is set during snapshot loads and add or update coverage if the relevant test location is found.

由索引模型根据 Issue 内容生成。

评估

技术栈
rust
领域
operating-systems
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
冷清
描述清晰度
需要澄清
新手友好度
38/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。