hyperlight-dev / hyperlight-dev/hyperlight
max_guest_log_level is not plumbed through snapshot load
- 主要言語
- Rust
- スター
- 4.7k
- フォーク
- 208
- 平均マージ
- 1日 7時間
- マージ済み PR(30日)
- 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