Guest Win10x64 LTSB, ACPI device, broken Nework

VecH

Active Member
Sep 12, 2015
43
0
26
Config from hosts
Code:
root@pve:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

allow-hotplug enp6s0
iface enp6s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address  10.2.33.6
        netmask  255.255.255.0
        gateway  10.2.33.3
        bridge-ports enp6s0
        bridge-stp off
        bridge-fd 0
Code:
root@pve:~# ifconfig
enp6s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether e0:d5:5e:81:40:4b  txqueuelen 1000  (Ethernet)
        RX packets 33960397  bytes 40149964407 (37.3 GiB)
        RX errors 0  dropped 4447  overruns 0  frame 0
        TX packets 14380493  bytes 1560190867 (1.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 520969  bytes 196594972 (187.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 520969  bytes 196594972 (187.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tap100i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether aa:e6:ad:bc:4c:61  txqueuelen 1000  (Ethernet)
        RX packets 16216  bytes 1732086 (1.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1299182  bytes 132576929 (126.4 MiB)
        TX errors 0  dropped 3641 overruns 0  carrier 0  collisions 0

tap101i0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST>  mtu 1500
        ether b2:42:a8:6e:cc:b2  txqueuelen 1000  (Ethernet)
        RX packets 260785  bytes 23912312 (22.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4277394  bytes 940073021 (896.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vmbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.2.33.6  netmask 255.255.255.0  broadcast 10.2.33.255
        inet6 fe80::e2d5:5eff:fe81:404b  prefixlen 64  scopeid 0x20<link>
        ether e0:d5:5e:81:40:4b  txqueuelen 1000  (Ethernet)
        RX packets 14257852  bytes 37974847437 (35.3 GiB)
        RX errors 0  dropped 10226  overruns 0  frame 0
        TX packets 13967645  bytes 1526085353 (1.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Guest OS Windows 10 LTSB x64

not received IP from DHCP in LAN
Code:
root@pve:~# cat /etc/pve/qemu-server/101.conf
agent: 1
balloon: 2048
bootdisk: sata0
cores: 4
memory: 4096
name: Win2012r2
net0: e1000=66:A8:0E:5A:BD:8E,bridge=vmbr0
numa: 0
onboot: 1
ostype: win8
sata0: local:101/vm-101-disk-1.raw,size=50G
sata2: local:iso/virtio-win-0.1.141.iso,media=cdrom,size=309208K
scsihw: virtio-scsi-pci
smbios1: uuid=8f5b7462-cabb-4690-b0d7-74bbcb19ef7c
sockets: 1

Guest OS Windows 10 LTSB x64 find device by ID
Code:
ACPI/VEN_ACPI&DEV_0010
Drivers for this device not found on CD virtio-win-0.1.141.iso
 
i would rather use virtio for the network and scsi for the disks instead of e1000 and sata
 
  • Like
Reactions: VecH
did you install the qemu serial device driver, the qemufwcfg driver and the guest agent?
 
Code:
root@pve:~# cat /etc/pve/qemu-server/102.conf
agent: 1
balloon: 1024
bootdisk: virtio0
cores: 4
memory: 2048
name: Win10x64
net0: virtio=22:CD:1A:33:7F:75,bridge=vmbr0
numa: 0
ostype: win10
sata0: local:iso/virtio-win-0.1.141.iso,media=cdrom,size=309208K
sata1: local:iso/Win10_LTSB_x64_2016.iso,media=cdrom,size=3455620K
scsihw: virtio-scsi-pci
smbios1: uuid=c0756adf-7b89-4452-a7bd-269dccf276b4
sockets: 1
virtio0: local:102/vm-102-disk-1.qcow2,size=32G
changed to virtio (HDD and Network) and reinstall OS
The problem remained unresolved
 
you could try the newer virito-latest iso (i believe 0.1.149)
 
After rebooting the host system, the network card (virtio) in the guest system has earned

problem with ACPI\ACPI0010\2&DABA3FF&0 device
driver does not work correctly (Code 31)
The updated driver for the device on the drive virtio-win-0.1.149.iso is not present
 

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 yours easily in our online shop.

Buy now!