Possible to remove Chipset Audio Device from VM?

vlaves

Member
Oct 28, 2017
6
0
21
43
Hi proxmox Community,

hope someone can help out here. I'm running a Windows Server Core 2022 machine configured in proxmox as a Win10/2016 machine with q35 Chipset (Version 5.1 is set) and using all virt components for storage, network and so on.
If I look in the device manager of the Windows Server Core install, there is an unknown device with the Hardware ID "PCI\VEN_8086&DEV_293E", which appears to be the Chipset Audio Device. As there is no Audio Device Support in Server core, I would want to disable this device in the proxmox VM config. How would I be able to do that. This VM will then be prepared as Template for all our future Windows Server Core 2022 VMs, so it would really be helpful to get this cleaned before making an a syspreped template out of it, to avoid upcoming questions when released to all users.
Thanks for the support in advance.

PS: Maybe someone knows if there is dummy driver or somthing like that to make the unused device disappear or at least appear in healthy state.
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
1,980
235
83
Please provide the VM config(qm config <VMID>) and the output of qm showcmd <VMID> --pretty.

In addition, please provide the output of pveversion -v.
 

vlaves

Member
Oct 28, 2017
6
0
21
43
Please provide the VM config(qm config <VMID>) and the output of qm showcmd <VMID> --pretty.

In addition, please provide the output of pveversion -v.
Here we go:
qm config 100
Code:
agent: 1
boot: order=virtio0;ide2;ide0;net0
cores: 4
ide0: ISO-Repository:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
ide2: ISO-Repository:iso/OS_EN_Windows_Server_2022.iso,media=cdrom,size=4925162K
machine: pc-q35-5.1
memory: 4096
meta: creation-qemu=6.2.0,ctime=1656532858
name: dc.delinea.lab
net0: virtio=6A:C5:25:7D:8D:74,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=fed36af3-bb77-48ab-ade2-070eee8ba6e1
sockets: 1
virtio0: local-lvm:vm-100-disk-0,cache=writeback,discard=on,size=128G
vmgenid: d282fa56-3050-45d5-948f-0e8d27064eb8

qm showcmd 100 --pretty:
Code:
/usr/bin/kvm \
  -id 100 \
  -name dc.delinea.lab \
  -no-shutdown \
  -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server=on,wait=off' \
  -mon 'chardev=qmp,mode=control' \
  -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect=5' \
  -mon 'chardev=qmp-event,mode=control' \
  -pidfile /var/run/qemu-server/100.pid \
  -daemonize \
  -smbios 'type=1,uuid=fed36af3-bb77-48ab-ade2-070eee8ba6e1' \
  -smp '4,sockets=1,cores=4,maxcpus=4' \
  -nodefaults \
  -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' \
  -vnc 'unix:/var/run/qemu-server/100.vnc,password=on' \
  -no-hpet \
  -cpu 'kvm64,enforce,hv_ipi,hv_relaxed,hv_reset,hv_runtime,hv_spinlocks=0x1fff,hv_stimer,hv_synic,hv_time,hv_vapic,hv_vpindex,+kvm_pv_eoi,+kvm_pv_unhalt,+lahf_lm,+sep' \
  -m 4096 \
  -readconfig /usr/share/qemu-server/pve-q35-4.0.cfg \
  -device 'vmgenid,guid=d282fa56-3050-45d5-948f-0e8d27064eb8' \
  -device 'usb-tablet,id=tablet,bus=ehci.0,port=1' \
  -device 'VGA,id=vga,bus=pcie.0,addr=0x1,edid=off' \
  -chardev 'socket,path=/var/run/qemu-server/100.qga,server=on,wait=off,id=qga0' \
  -device 'virtio-serial,id=qga0,bus=pci.0,addr=0x8' \
  -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' \
  -device 'virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3' \
  -iscsi 'initiator-name=iqn.1993-08.org.debian:01:9d109dbcac3' \
  -drive 'file=/mnt/pve/ISO-Repository/template/iso/virtio-win-0.1.215.iso,if=none,id=drive-ide0,media=cdrom,aio=io_uring' \
  -device 'ide-cd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=102' \
  -drive 'file=/mnt/pve/ISO-Repository/template/iso/OS_EN_Windows_Server_2022.iso,if=none,id=drive-ide2,media=cdrom,aio=io_uring' \
  -device 'ide-cd,bus=ide.1,unit=0,drive=drive-ide2,id=ide2,bootindex=101' \
  -drive 'file=/dev/pve/vm-100-disk-0,if=none,id=drive-virtio0,cache=writeback,discard=on,format=raw,aio=io_uring,detect-zeroes=unmap' \
  -device 'virtio-blk-pci,drive=drive-virtio0,id=virtio0,bus=pci.0,addr=0xa,bootindex=100' \
  -netdev 'type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on' \
  -device 'virtio-net-pci,mac=6A:C5:25:7D:8D:74,netdev=net0,bus=pci.0,addr=0x12,id=net0,bootindex=103' \
  -rtc 'driftfix=slew,base=localtime' \
  -machine 'type=pc-q35-5.1+pve0' \
  -global 'kvm-pit.lost_tick_policy=discard'

pveversion -v:
Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-3-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Thanks for your support

And attached here is the screenshot of the device manager. The Installation is Windows Server 2022 core with the installed Features on Demand, so you can have at least some GUI Tools for basic management. Hope that information helps.
 

Attachments

  • screenshot.jpg
    screenshot.jpg
    460.6 KB · Views: 5
Last edited:

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
1,980
235
83
Thank you for the information.

The audio device is part of the machine type `q35`, so if you don't want to have one automatically defined, you'll have to switch to the default `i440fx`.
 
  • Like
Reactions: nio707

vlaves

Member
Oct 28, 2017
6
0
21
43
Thank you for the information.

The audio device is part of the machine type `q35`, so if you don't want to have one automatically defined, you'll have to switch to the default `i440fx`.
Thanks for the update and quick response :) that was a really quick fix. Is there a disadvantage compared to q35 when using everything else v irtio?
 

mira

Proxmox Staff Member
Staff member
Aug 1, 2018
1,980
235
83
It's only really required when using PCI Passthrough.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!