hyperlight-dev / hyperlight-dev/hyperlight
max_guest_log_level is not plumbed through snapshot load
- Lenguaje dominante
- Rust
- Estrellas
- 4.7k
- Forks
- 208
- Merge medio
- 1 d 7 h
- PR fusionados (30 d)
- 47
Descripción
### 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?
Guía de contribución
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- rust
- Área
- operating-systems
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 38/100