Hello,
I have a Windows Server 2022 and Win11 VM running on Proxmox. I'm using Virtio drivers for Network, SATA, etc.
The VMs themselves are running fine.
For testing purposes I need to perform remote kernel debugging on those hosts.
The debugger host is a VM on an ESXi server, and the VMs on Proxmox are in the same VLAN/network like the debuggees.
As long as the debugee is also on ESXi or a physical machine on the same VLAN/network everything works perfectly.
When the debuggee is one of the VMs on Proxmox mentioned above I am not able to get the debuggees to connect to the debugger.
The normal procedure to set this up is:
* Disable SecureBoot on the debugee
* As admin: bcdedit /dbgsettings net hostip:<debugger> port:49152 key:1.2.3.4
* As Admin: bcdedit /debug yes
And reboot the machine
On the debugger I configure the same port and key and "Attach to kernel".
Then during bootup the debuggee should break after few seconds and the debugger should show allow for debugging
This does not happen, the debugee starts up normally.
I tcpdumped on the Proxmox host all interfaces for the port 49152 and see 0 network packets. So it seems the Windows VM does not even try to reach out.
I tried switching from Virtio as the network adapter driver to EE1000, I tried fixed IPs and DHCP address leases.
I verified that the VM and the debugger can communicate without any issues (port probe) with each other once they are up and running, and nothing is filtering there. So it's also not a question of VLAN tags, bridge configuration or anything in that direction I presume.
Is there anything from the Proxmox side which could explain why the debugee is not reaching out? My best guess was the original virtio setup but a switch to EE1000 as the NIC should definitely work? Checked here: https://learn.microsoft.com/en-us/w...cs-for-network-kernel-debugging-in-windows-10
The settings I perform in those VMs are the same as in any other VM, so the commands themselves are correct and work.
Proxmox 8.3.4
Any ideas?
I have a Windows Server 2022 and Win11 VM running on Proxmox. I'm using Virtio drivers for Network, SATA, etc.
The VMs themselves are running fine.
For testing purposes I need to perform remote kernel debugging on those hosts.
The debugger host is a VM on an ESXi server, and the VMs on Proxmox are in the same VLAN/network like the debuggees.
As long as the debugee is also on ESXi or a physical machine on the same VLAN/network everything works perfectly.
When the debuggee is one of the VMs on Proxmox mentioned above I am not able to get the debuggees to connect to the debugger.
The normal procedure to set this up is:
* Disable SecureBoot on the debugee
* As admin: bcdedit /dbgsettings net hostip:<debugger> port:49152 key:1.2.3.4
* As Admin: bcdedit /debug yes
And reboot the machine
On the debugger I configure the same port and key and "Attach to kernel".
Then during bootup the debuggee should break after few seconds and the debugger should show allow for debugging
This does not happen, the debugee starts up normally.
I tcpdumped on the Proxmox host all interfaces for the port 49152 and see 0 network packets. So it seems the Windows VM does not even try to reach out.
I tried switching from Virtio as the network adapter driver to EE1000, I tried fixed IPs and DHCP address leases.
I verified that the VM and the debugger can communicate without any issues (port probe) with each other once they are up and running, and nothing is filtering there. So it's also not a question of VLAN tags, bridge configuration or anything in that direction I presume.
Is there anything from the Proxmox side which could explain why the debugee is not reaching out? My best guess was the original virtio setup but a switch to EE1000 as the NIC should definitely work? Checked here: https://learn.microsoft.com/en-us/w...cs-for-network-kernel-debugging-in-windows-10
The settings I perform in those VMs are the same as in any other VM, so the commands themselves are correct and work.
Proxmox 8.3.4
CPU(s) 4 x Intel(R) Celeron(R) J4105 CPU @ 1.50GHz (1 Socket) |
Kernel Version Linux 6.8.12-7-pve (2025-01-17T08:18Z) |
Boot Mode EFI |
Manager Version pve-manager/8.3.4/65224a0f9cd294a3 |