Proxmox node and VM disappear from home network after daily DSL forced disconnection

Diem

New Member
Oct 7, 2022
2
0
1
Hi everyone,

First a big thx to the community I found lots of helpful posts here, you are awesome but I cannot find this particular problem in the forum and therefore I’m posting. Sorry I’m an absolute beginner and just started with virtualisation and Linux, so please expect no deeper knowledge and assume I’m an Idiot

I’m running an Ubuntu Server VM in an Proxmox 7.2 install on a workstation with following hardware:
AMD Ryzen ThreadRipper 3970X
ASUS ROG STRIX TRX40-XE GAMING
GeForce GTX 1650 KalmX

The Node and the VM disappear from my network overnight, not always but 9 out of 10 times. I cannot access the Proxmox web interface or the VM over the network and when I look into the router both are not listed as active/connected devices anymore. Both have dedicated IPs in my Network with no conflict and have their ports open to be accessible from the Internet. Both works absolutely fine until the night hits.

I have an DSL Connection at home, that dis- and reconnects daily at around 3 o’clock in the morning, it takes only a few seconds and I reckon It has something to do with it but I cannot be sure because I’m an Idiot.

I cannot even look into the node or VM to find out what’s wrong because the GPU doesn’t give any output anymore once Proxmox is fully booted and Threadripper has no onboard graphic. Maybe because I passed the GPU through to the VM? But I doubt I would understand much, without the graphics interface, anyway. But I cannot even reboot the node, so the only thing left at the moment is to forcibly shut down the pc and restart it and that cannot be the right thing to do.

Please you smart guys of the Internet, has anyone overcome similar issues or has an idea what I can do?

Kind regards

Dennis
 
Can you connect via SSH after the reboot and look at the journal of the previous boot? (journalctl -b)
Are there any errors visible, or mentions of `network` or `link down`?
 
I just post the whole report.

root@pve1:~# journalctl -b
-- Journal begins at Fri 2022-06-17 19:22:42 CEST, ends at Fri 2022-10-07 13:36:47 CEST. --
Oct 07 13:34:54 pve1 kernel: Linux version 5.13.19-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU >
Oct 07 13:34:54 pve1 kernel: Command line: BOOT_IMAGE=(lvm/pve-root)/boot/pve/vmlinuz ro ramdisk_size=16777216 root=/dev/mapp>
Oct 07 13:34:54 pve1 kernel: KERNEL supported cpus:
Oct 07 13:34:54 pve1 kernel: Intel GenuineIntel
Oct 07 13:34:54 pve1 kernel: AMD AuthenticAMD
Oct 07 13:34:54 pve1 kernel: Hygon HygonGenuine
Oct 07 13:34:54 pve1 kernel: Centaur CentaurHauls
Oct 07 13:34:54 pve1 kernel: zhaoxin Shanghai
Oct 07 13:34:54 pve1 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Oct 07 13:34:54 pve1 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Oct 07 13:34:54 pve1 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Oct 07 13:34:54 pve1 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Oct 07 13:34:54 pve1 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Oct 07 13:34:54 pve1 kernel: BIOS-provided physical RAM map:
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x0000000004000000-0x000000000400efff] ACPI NVS
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x000000000400f000-0x0000000009df1fff] usable
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x0000000009df2000-0x0000000009ffffff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x000000000a000000-0x00000000a2eedfff] usable
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a2eee000-0x00000000a2eeefff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a2eef000-0x00000000a89a3fff] usable
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a89a4000-0x00000000a9f2afff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a9f2b000-0x00000000a9f50fff] ACPI data
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a9f51000-0x00000000a9f51fff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000a9f52000-0x00000000aa09efff] ACPI data
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000aa09f000-0x00000000aa22bfff] ACPI NVS
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000aa22c000-0x00000000ab14efff] reserved
Oct 07 13:34:54 pve1 kernel: BIOS-e820: [mem 0x00000000ab14f000-0x00000000ab1fefff] type 20
lines 1-31
 

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!