Manjaro on Hyper-V keeps rebooting while away

Support Virtualization
1

I’ve been running a Manjaro VM on Hyper-V for ~6 months with no apparent issues. About a week ago, I noticed that when I’m away (Windows host locks or VM is idle for a while), the VM shows the usual post-shutdown console window (the disk block scan thing). I can CTRL+ALT+F2 to open another console window, but I can’t seem to get the GUI running; I think the VM is trying to shut down, but stalled, I’m not sure.

How can I investigate and resolve this? I tried wiping my VM and installing a new one from scratch, but the issue persisted.

2

Could it be related to this? (Vbox uses Hyper-V.)
Some fedora users report that vbox 6.1.35 testing version works, in this forum.
Most reports mention Windows, but some say that it affects every kind of guest OS.

3

I don’t understand.

  • You mention VBox; I’m using Hyper-V.
  • The linked post mentions a Windows guest on a Linux host; my situation is a Linux guest on a Windows host.
4

Yeah, sorry, it’s late here, getting sleepy :wink: have altered my post already.

5

Thanks for the reminder. I forgot to mention: I tried 5.15 (original LTS kernel where I saw this issue) and 5.17. Both failed. I’ve now upgraded to 5.18, will report back if that fixes the problem…

6

I think I noticed something similar with manjaro vm in QEMU. It’s not rebooting though, it’s just showing messages from startup (I think, I haven’t really paid any attention to it). Gonna try to reproduce it again.

Maybe it’s trying to hibernate or whatever.

7

Is there a way to verify what it’s doing? I tried launching the IDE (KDE in my case) from another window, but it didn’t work.

8

Can’t reproduce it anymore, btw. Check journal for any clues. Can you ssh into it after this happens?

9

Hyper-V runs on Windows - so this is a Windows or Hyper-V issue.

10

Lots of things that look sus. I don’t know much about Linux, maybe you or someone else can comment on if these are red herrings or real issues.

Here are some intersting-looking subsets:

Jun 21 15:15:29 Manjaro systemd-journald[8482]: File /var/log/journal/0b0f13fe298e40b9a64ea40038dbb49f/system.journal corrupted or uncleanly shut down,>
Jun 21 15:15:29 Manjaro systemd[1]: Starting Journal Service...
Jun 21 15:15:29 Manjaro systemd[1]: Stopped Journal Service.
Jun 21 15:15:29 Manjaro systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.

Jun 21 15:15:28 Manjaro rtkit-daemon[717]: Successfully demoted thread 2068 of process 1123.
Jun 21 15:15:28 Manjaro systemd[1]: systemd-journald.service: Killing process 284 (systemd-journal) with signal SIGABRT.
Jun 21 15:15:28 Manjaro rtkit-daemon[717]: Successfully demoted thread 3711 of process 1132.
Jun 21 15:15:28 Manjaro systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
Jun 21 15:15:28 Manjaro rtkit-daemon[717]: Successfully demoted thread 6170 of process 1119.
Jun 21 15:15:28 Manjaro systemd[1]: systemd-logind.service: Killing process 386 (systemd-logind) with signal SIGABRT.
Jun 21 15:15:28 Manjaro rtkit-daemon[717]: Demoting known real-time threads.
Jun 21 15:15:28 Manjaro systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)!
Jun 21 15:15:28 Manjaro rtkit-daemon[717]: The canary thread is apparently starving. Taking action.

Jun 21 15:16:36 Manjaro systemd[1]: Started Getty on tty2.
Jun 21 15:15:33 Manjaro sddm[433]: Could not start Display server on vt 1
Jun 21 15:15:33 Manjaro sddm[433]: Attempt 3 starting the Display server on vt 1 failed
Jun 21 15:15:33 Manjaro sddm[433]: Display server stopping...
Jun 21 15:15:33 Manjaro sddm[433]: Failed to read display number from pipe
Jun 21 15:15:32 Manjaro sddm[433]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09>
Jun 21 15:15:32 Manjaro sddm[433]: Adding cookie to "/var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09ded7baa3}"
Jun 21 15:15:32 Manjaro sddm[433]: Display server starting...
Jun 21 15:15:31 Manjaro sddm[433]: Attempt 2 starting the Display server on vt 1 failed
Jun 21 15:15:31 Manjaro sddm[433]: Display server stopping...
Jun 21 15:15:31 Manjaro sddm[433]: Failed to read display number from pipe
Jun 21 15:15:31 Manjaro sddm[433]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09>
Jun 21 15:15:31 Manjaro sddm[433]: Adding cookie to "/var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09ded7baa3}"
Jun 21 15:15:31 Manjaro sddm[433]: Display server starting...
Jun 21 15:15:29 Manjaro plasmashell[684]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationItem.qml:219:21: QML >
Jun 21 15:15:29 Manjaro sddm[433]: Attempt 1 starting the Display server on vt 1 failed
Jun 21 15:15:29 Manjaro sddm[433]: Display server stopping...
Jun 21 15:15:29 Manjaro sddm[433]: Failed to read display number from pipe
Jun 21 15:15:29 Manjaro org_kde_powerdevil[688]: org.kde.powerdevil: The profile  "AC" tried to activate "DimDisplay" a non-existent action. This is us>
Jun 21 15:15:29 Manjaro sddm[433]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt1 -auth /var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09>
Jun 21 15:15:29 Manjaro sddm[433]: Adding cookie to "/var/run/sddm/{9596c662-c9e1-45a5-bf10-ab09ded7baa3}"
Jun 21 15:15:29 Manjaro sddm[433]: Display server starting...
Jun 21 15:15:29 Manjaro sddm[433]: Loading theme configuration from ""
Jun 21 15:15:29 Manjaro sddm[433]: Adding new display on vt 1 ...

Lots of authentication failures, although I haven’t failed any authentication prompts (sudo or KDE) that I remember:

Jun 21 15:16:38 Manjaro kcheckpass[8571]: Authentication failure for nb (invoked by uid 1000)
Jun 21 15:16:38 Manjaro kcheckpass[8571]: pam_unix(kde:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0 ruser= rhost=  user=nb
Jun 21 15:16:38 Manjaro unix_chkpwd[8573]: password check failed for user (nb)

I can confirm that this affects my system on kernels 5.15, 5.17, and 5.18.

11

Yeah well, no idea. When you are bored you can start throwing those lines into google search and see if anything pops out. :stuck_out_tongue: