Hi there.
I am Swedish so english is not my native language but I'll do my best =).
I have a Windows10 Vm and it's been running flawlessly for 1y+.
I upgraded my VM storage pool so yesterday I moved all my VMs the this new ZFS pool.
Everything went well but not for this W10 VM!
Out of 30+ containers and VMs this one has problems.
It can be started but it's IP does not show up. I have QMagent installed and it shows nothing. I use this VM to run Asheron's call, a vintage online game and I use Moonlight to connect to it. After migration to the new pool it cannot be reached from any PC on the LAN, nor pinged or trying to get IP from proxmox CLI (tested various methods).
I have a similiar VM that I host for a friend and it's working after migration.
Config file looks fine, VM console does not work (black screen) but it was like that before too.
I have moved both TPM7EFI disks as well on the nonfunctional VM just like the one working.
I have tried to search all kinds of solutions to this problem and after 2y of Proxmox tinkering I cannot find the cause or solution to this.
VM config is the same after migration (I tried and restore a backup of the VM but still not working...)
One thing is strange though. If I start the VM, it is runnign but do not appear to get a valid IP config.
Stranger yet is that my chars in the online game seems to be online but I cannot get the VMs IP from interface or CLI.
Running pve-manager/8.4.11/14a32011146091ed (running kernel: 6.5.13-5-pve)
VM config:
audio0: device=ich9-intel-hda,driver=none
balloon: 0
bios: ovmf
boot: order=ide0;net0;ide2
cores: 2
cpu: host
cpulimit: 4
description: Asheron's Call gaming server
efidisk0: SAS-15k:vm-109-disk-2,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:08:00.0,mdev=nvidia-68
ide0: SAS-15k:vm-109-disk-0,cache=writeback,discard=on,size=110G
machine: pc-q35-8.1
memory: 8192
meta: creation-qemu=7.2.0,ctime=1691052965
name: W10-AC-GNF
net0: virtio=9E:C9:E2:83:7F:C2,bridge=vmbr0,firewall=1
numa: 1
ostype: win11
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=378ea534-8da3-4634-9a32-274bc4df4adf
sockets: 2
tpmstate0: SAS-15k:vm-109-disk-1,size=4M,version=v2.0
usb0: host=046d:c404
vga: none
vmgenid: 013be45a-6cac-42c9-b6f4-c1acd7198afa
I am Swedish so english is not my native language but I'll do my best =).
I have a Windows10 Vm and it's been running flawlessly for 1y+.
I upgraded my VM storage pool so yesterday I moved all my VMs the this new ZFS pool.
Everything went well but not for this W10 VM!
Out of 30+ containers and VMs this one has problems.
It can be started but it's IP does not show up. I have QMagent installed and it shows nothing. I use this VM to run Asheron's call, a vintage online game and I use Moonlight to connect to it. After migration to the new pool it cannot be reached from any PC on the LAN, nor pinged or trying to get IP from proxmox CLI (tested various methods).
I have a similiar VM that I host for a friend and it's working after migration.
Config file looks fine, VM console does not work (black screen) but it was like that before too.
I have moved both TPM7EFI disks as well on the nonfunctional VM just like the one working.
I have tried to search all kinds of solutions to this problem and after 2y of Proxmox tinkering I cannot find the cause or solution to this.
VM config is the same after migration (I tried and restore a backup of the VM but still not working...)
One thing is strange though. If I start the VM, it is runnign but do not appear to get a valid IP config.
Stranger yet is that my chars in the online game seems to be online but I cannot get the VMs IP from interface or CLI.
Running pve-manager/8.4.11/14a32011146091ed (running kernel: 6.5.13-5-pve)
VM config:
audio0: device=ich9-intel-hda,driver=none
balloon: 0
bios: ovmf
boot: order=ide0;net0;ide2
cores: 2
cpu: host
cpulimit: 4
description: Asheron's Call gaming server
efidisk0: SAS-15k:vm-109-disk-2,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:08:00.0,mdev=nvidia-68
ide0: SAS-15k:vm-109-disk-0,cache=writeback,discard=on,size=110G
machine: pc-q35-8.1
memory: 8192
meta: creation-qemu=7.2.0,ctime=1691052965
name: W10-AC-GNF
net0: virtio=9E:C9:E2:83:7F:C2,bridge=vmbr0,firewall=1
numa: 1
ostype: win11
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=378ea534-8da3-4634-9a32-274bc4df4adf
sockets: 2
tpmstate0: SAS-15k:vm-109-disk-1,size=4M,version=v2.0
usb0: host=046d:c404
vga: none
vmgenid: 013be45a-6cac-42c9-b6f4-c1acd7198afa
Last edited: