Are you sure you have successfully installed the driver from master? It sounds like you might still be using the v262 package driver.
This do update the driver (I miss the "
Select: Have Disk..." opertaion before).blue screen of death" happened, by checking the driver version info in Device Manager (I have changed the version info in the source code, and the version info matched ).I'm not seeing a BSOD myself, but I'm only installing the vioscsi driver from master, the rest is v248 (I only did brief testing aside v262).
The host qemu log show that
libvirt hit the fd limit due to lots of connections to ceph OSD, this must be cause of the BSOD. I will handle it and and test the driver again.I think we're just waiting on a new driver package release from Redhat
I'm confused -- Proxmox VE does not ship libvirt. Can you elaborate on your setup? Can you provide the output of
pveversion -v?
Sorry... not for the installer problem but for the real problem this thread is all about:
#!/bin/bash
for vmid in $(qm list | awk '{print $1}' | grep -v VMID)
do
if qm guest cmd $vmid ping > /dev/null 2>&1 ; then
if qm guest cmd $vmid get-osinfo | grep mswindows > /dev/null ; then
PROBE_VER="$(qm guest exec \
$vmid --timeout 0 -- powershell \
"Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object -Property DisplayName -contains Virtio-win-guest-tools | Select-Object DisplayVersion | fl" | \
grep out-data | sed 's/["\\r\\n]//g' | sed 's/ out-data : DisplayVesio : //g')"
if ! echo VM $vmid - VirtIO Tools version: "${PROBE_VER}" ; then
echo Could not get VirtIO Tools Version for VM $vmid.
fi
else
echo VM $vmid - NOT running Windows.
fi
else
echo VM $vmid - OFFLINE or no QEMU Agent.
fi
donechmod +x <filename> and then execute it with sh ./filename.Per @Taomyn's post above, there are some known issues with the installer.