Hi, I have a long time win 2003 server, before it had ide but recently switched to virtio disks and spice console.
now at boot, after login, asks for "drivers", and has "yellow question marks" in device manager.

I already faced a balooning driver issue, but reading the forums, I got "balloon: 0" hint and that was solved.
now
- it always asks drivers for "red hat virtio scsi controller"
- device manager shows a "yellow question mark" for a "controller pci simple communications"
- device manager shows a "yellow question mark" for a "controller video (simple vga)"
as you see it has three virtio disks (working) but can't remember which version was the iso. (can't remember also how to check current drivers version...
)
Any help or experience? Thanks, Marco
[edit] would guest tool referenced here help for device manager issues? http://www.spice-space.org/download.html[/edit]
here the vm conf
and pve version
now at boot, after login, asks for "drivers", and has "yellow question marks" in device manager.

I already faced a balooning driver issue, but reading the forums, I got "balloon: 0" hint and that was solved.
now
- it always asks drivers for "red hat virtio scsi controller"
- device manager shows a "yellow question mark" for a "controller pci simple communications"
- device manager shows a "yellow question mark" for a "controller video (simple vga)"
as you see it has three virtio disks (working) but can't remember which version was the iso. (can't remember also how to check current drivers version...

Any help or experience? Thanks, Marco
[edit] would guest tool referenced here help for device manager issues? http://www.spice-space.org/download.html[/edit]
here the vm conf
Code:
# cat /etc/pve/nodes/pve1/qemu-server/206.conf
acpi: 1
balloon: 0
boot: dc
bootdisk: virtio0
cores: 1
cpuunits: 1000
freeze: 0
ide2: none,media=cdrom
kvm: 1
memory: 2048
name: ADserver
net0: e1000=XXXXXXXX,bridge=vmbr0
onboot: 1
ostype: w2k3
sockets: 2
vga: qxl
virtio0: vm_disks_ts879:vm-206-disk-4,size=15364M
virtio1: vm_disks_ts879:vm-206-disk-5,size=5128M
virtio2: vm_disks_ts879:vm-206-disk-3,size=32G
and pve version
Code:
# pveversion -verbose
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
Last edited: