Proxmox in QEMU VM Constantly reboots

[kraythax]

I installed Proxmox in a QEMU VM running on Debian Linux to learn it before I commit to using it on my home office hardware. I got it installed and then installed KDE so that I could use the web console from local install. The problem I am having is for unknown reasons the install is constantly rebooting. I dont know why this happens because it never happens when i am interacting with it, learning. But if I leave it running and I am in another window, it will reboot routinely. This makes me doubt if I could use it in my home office. Has anyone seen this or have any ideas why it might be happening. I have other Debian Linux VMs in QEMU that work just fine. Thanks in advance.

 

[Kingneutron]

Check ' journalctl ' for any messages about OOM-killer or anything right before "Command line:" boot indication

 

[kraythax]

I didn't see that in the log but now I have purged journalctl and I will let it run in the background and capture the log when it reboots

 

[kraythax]

It seems like trying to go to sleep is causing a reboot?

May 09 00:26:47 proxmox systemd-journald[429]: System Journal (/var/log/journal/35d9c84fbfa04f9a832425d5c0d3a90d) is 73.8M, max 1.6G, 1.6G free.
May 09 00:26:47 proxmox systemd-journald[429]: Received client request to rotate journal, rotating.
May 09 00:26:47 proxmox systemd-journald[429]: Vacuuming done, freed 0B of archived journals from /var/log/journal/35d9c84fbfa04f9a832425d5c0d3a90d.
May 09 00:26:47 proxmox sudo[4325]: pam_unix(sudo:session): session closed for user root
May 09 00:27:21 proxmox sudo[4439]:    admin : TTY=pts/1 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/journalctl
May 09 00:27:21 proxmox sudo[4439]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1000)
May 09 00:27:21 proxmox sudo[4439]: pam_unix(sudo:session): session closed for user root
May 09 00:28:12 proxmox PackageKit[2000]: daemon quit
May 09 00:28:12 proxmox systemd[1]: packagekit.service: Deactivated successfully.
May 09 00:28:12 proxmox systemd[1]: packagekit.service: Consumed 1.043s CPU time.
May 09 00:33:05 proxmox systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
May 09 00:33:05 proxmox systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
May 09 00:33:05 proxmox systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
May 09 00:33:05 proxmox systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
May 09 00:47:12 proxmox kwin_wayland_wrapper[7820]: libEGL warning: egl: failed to create dri2 screen
May 09 00:47:13 proxmox kwin_wayland_wrapper[7820]: kf.kirigami: Failed to find a Kirigami platform plugin
May 09 00:47:13 proxmox kwin_wayland_wrapper[7820]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
May 09 00:47:13 proxmox kwin_wayland_wrapper[7820]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
May 09 00:55:15 proxmox systemd[1]: Starting apt-daily-upgrade.service - Daily apt upgrade and clean activities...
May 09 00:55:45 proxmox apt-helper[9260]: E: Sub-process nm-online returned an error code (1)
May 09 00:55:46 proxmox systemd[1]: apt-daily-upgrade.service: Deactivated successfully.
May 09 00:55:46 proxmox systemd[1]: Finished apt-daily-upgrade.service - Daily apt upgrade and clean activities.
May 09 00:57:12 proxmox systemd-logind[686]: The system will suspend now!
May 09 00:57:12 proxmox NetworkManager[720]: <info>  [1715237832.8475] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 09 00:57:12 proxmox NetworkManager[720]: <info>  [1715237832.8476] manager: NetworkManager state is now ASLEEP
May 09 00:57:12 proxmox ModemManager[737]: <info>  [sleep-monitor-systemd] system is about to suspend
May 09 00:57:12 proxmox systemd[1]: Reached target sleep.target - Sleep.
May 09 00:57:12 proxmox systemd[1]: Starting systemd-suspend.service - System Suspend...
May 09 00:57:12 proxmox systemd-sleep[9628]: Entering sleep state 'suspend'...
May 09 00:57:12 proxmox kernel: PM: suspend entry (s2idle)
-- Boot d70162a6c02e4b278ea388eb1fd9a595 --
May 09 00:57:32 proxmox kernel: Linux version 6.8.4-2-pve (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PRE>
May 09 00:57:32 proxmox kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.4-2-pve root=/dev/mapper/pve-root ro quiet
May 09 00:57:32 proxmox kernel: KERNEL supported cpus:
May 09 00:57:32 proxmox kernel:   Intel GenuineIntel
May 09 00:57:32 proxmox kernel:   AMD AuthenticAMD
May 09 00:57:32 proxmox kernel:   Hygon HygonGenuine
May 09 00:57:32 proxmox kernel:   Centaur CentaurHauls
May 09 00:57:32 proxmox kernel:   zhaoxin   Shanghai 
May 09 00:57:32 proxmox kernel: BIOS-provided physical RAM map:
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007ffdafff] usable
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x000000007ffdb000-0x000000007fffffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
May 09 00:57:32 proxmox kernel: BIOS-e820: [mem 0x0000000100000000-0x000000084fffffff] usable
May 09 00:57:32 proxmox kernel: NX (Execute Disable) protection: active
May 09 00:57:32 proxmox kernel: APIC: Static calls initialized
May 09 00:57:32 proxmox kernel: SMBIOS 2.8 present.
May 09 00:57:32 proxmox kernel: DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014

 

[Kingneutron]

> I installed Proxmox in a QEMU VM running on Debian Linux
> and then installed KDE so that I could use the web console from local install

This is likely a KDE issue. I'm not familiar with it but you should probably go into power saving settings and turn off sleep mode, then look around for anything similar like screensaver

Also I'm not sure why you would have Proxmox + KDE in a VM, if the host is Debian you should already have a desktop and browser there and just run Proxmox in headless mode like normal--?

 

[kraythax]

when I do the actual install on bare metal I want to be able to admin the instance without needing another computer. Hence the install of KDE.