@@ -37,15 +37,11 @@ jobs:
3737 strategy :
3838 fail-fast : true
3939 matrix :
40- hypervisor : [hyperv, 'hyperv-ws2025', mshv, mshv3, kvm] # hyperv is windows, mshv and kvm are linux
40+ hypervisor : [kvm] # hyperv is windows, mshv and kvm are linux
4141 cpu : [amd, intel]
4242 config : [debug, release]
4343
44- runs-on : ${{ fromJson(
45- format('["self-hosted", "{0}", "X64", "1ES.Pool=hld-{1}-{2}"]',
46- (matrix.hypervisor == 'hyperv' || matrix.hypervisor == 'hyperv-ws2025') && 'Windows' || 'Linux',
47- matrix.hypervisor == 'hyperv' && 'win2022' || matrix.hypervisor == 'hyperv-ws2025' && 'win2025' || matrix.hypervisor == 'mshv3' && 'azlinux3-mshv' || matrix.hypervisor,
48- matrix.cpu)) }}
44+ runs-on : ["self-hosted", "X64", "Linux", "kvmtest"]
4945 steps :
5046 - uses : actions/checkout@v4
5147
9692 # Add audit rules for KVM device monitoring
9793 echo "Adding comprehensive audit rules for KVM monitoring..."
9894
99- ls -al /dev/kvm || echo "❌ /dev/kvm does not exist or is not accessible"
10095 # Monitor file operations on /dev/kvm (if it exists)
10196 sudo auditctl -w /dev/kvm -p rwxa -k hypervisor_kvm || echo "Failed to add /dev/kvm watch rule (device may not exist yet)"
102- ls -al /dev/kvm || echo "❌ /dev/kvm still not accessible after adding watch rule"
103- sudo ausearch -k hypervisor_kvm
10497
10598 # Monitor device creation/deletion in /dev/
10699 sudo auditctl -w /dev/ -p wa -k device_changes || echo "Failed to add /dev/ watch rule"
@@ -543,6 +536,3 @@ jobs:
543536 echo "✅ No device permission/ownership changes detected during job execution"
544537 fi
545538
546- echo "hi"
547- sudo ausearch -k hypervisor_kvm -ts recent
548-
0 commit comments