diff options
Diffstat (limited to 'results/classifier/gemma3:12b/network/774')
| -rw-r--r-- | results/classifier/gemma3:12b/network/774 | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/network/774 b/results/classifier/gemma3:12b/network/774 new file mode 100644 index 00000000..6461ad60 --- /dev/null +++ b/results/classifier/gemma3:12b/network/774 @@ -0,0 +1,16 @@ + +Win(PE) NIC issue with pc-q35-6.1 +Description of problem: +When booting WinPE (via PXE via WDS) on a `pc-q35-6.1` machine, the NIC will not initialize. + +What I got with `pnputil.exe /enum-devices /class net` is `Device has problem: 56 0x38 (CM_PROB_NEED_CLASS_CONFIG)` See: [CM_PROB_NEED_CLASS_CONFIG](https://docs.microsoft.com/en-us/windows-hardware/drivers/install/cm-prob-need-class-config) + +I'm using virt manager and I've tried both `e1000e` and `virtio` network adapters (virtio with drivers injected into the image of course). Both yield the aforementioned error and `ipconfig` remains empty. This is an obscure problem - I haven't checked if a normal windows install behaves the same way, but it might be unique to winpe. + +However, with `pc-q35-5.2`, the NIC initializes without a problem. +Steps to reproduce: +1. Create `pc-q35-6.1` based vm in virt manager with default settings (network bridged to network bridge) +2. PXE boot Windows Setup +3. Observe hang (observe errors with console `SHIFT+F10`) +Additional information: + |