1 files changed, 0 insertions, 45 deletions
diff --git a/results/classifier/118/network/774 b/results/classifier/118/network/774
deleted file mode 100644
index cb5a74ad..00000000
--- a/results/classifier/118/network/774
+++ /dev/null
@@ -1,45 +0,0 @@
-network: 0.976
-device: 0.971
-peripherals: 0.968
-graphic: 0.958
-ppc: 0.937
-boot: 0.932
-vnc: 0.807
-semantic: 0.757
-performance: 0.741
-architecture: 0.714
-socket: 0.705
-mistranslation: 0.675
-PID: 0.578
-register: 0.559
-i386: 0.480
-x86: 0.477
-files: 0.471
-debug: 0.458
-virtual: 0.405
-permissions: 0.355
-assembly: 0.328
-user-level: 0.323
-risc-v: 0.307
-kernel: 0.294
-VMM: 0.292
-arm: 0.290
-hypervisor: 0.232
-TCG: 0.154
-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:
-