From dee4dcba78baf712cab403d47d9db319ab7f95d6 Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 19:39:53 +0200 Subject: restructure results --- results/classifier/108/network/774 | 30 ------------------------------ 1 file changed, 30 deletions(-) delete mode 100644 results/classifier/108/network/774 (limited to 'results/classifier/108/network/774') diff --git a/results/classifier/108/network/774 b/results/classifier/108/network/774 deleted file mode 100644 index 931b1e40..00000000 --- a/results/classifier/108/network/774 +++ /dev/null @@ -1,30 +0,0 @@ -network: 0.976 -device: 0.971 -graphic: 0.958 -boot: 0.932 -vnc: 0.807 -other: 0.764 -semantic: 0.757 -performance: 0.741 -socket: 0.705 -PID: 0.578 -files: 0.471 -debug: 0.458 -permissions: 0.355 -KVM: 0.050 - -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: - -- cgit v1.2.3