October 20, 20232 yr tower-diagnostics-20231020-1154.zip Other Ubuntu VMs on the same unit reboot fine. I can use Force Stop, then Start on this one when it is in Pause. I've checked that the QEMU guest agent is installed and functional: rick@igpu-22:~$ systemctl status qemu-guest-agent â qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/lib/systemd/system/qemu-guest-agent.service; static) Active: active (running) since Fri 2023-10-20 11:56:51 BST; 40s ago Main PID: 510 (qemu-ga) Tasks: 2 (limit: 7001) Memory: 1.1M CPU: 2ms CGroup: /system.slice/qemu-guest-agent.service ââ510 /usr/sbin/qemu-ga Oct 20 11:56:51 igpu-22 systemd[1]: Started QEMU Guest Agent. I saw in other posts that running out of space can be an issue, that doesn't seem to be my problem: rick@igpu-22:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 605088 1544 603544 1% /run /dev/vda5 30268356 19778112 8927364 69% / tmpfs 3025436 0 3025436 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock /dev/vda1 523248 4 523244 1% /boot/efi tmpfs 605084 84 605000 1% /run/user/1000 I'm running out of google-fu, thanks for your help.
November 15, 20232 yr Author It has been a month, bump for visibility as the issue still exists, thanks.
January 3, 20242 yr Author It has been another six weeks, bump for visibility as the issue still exists, thanks.
January 3, 20242 yr Community Expert Looks like the VM which I am guessing is the igpu one is getting a bad address fault. Does the igpu disappear at the same time. char device redirected to /dev/pts/2 (label charserial0) error: kvm run failed Bad address RAX=0000000000000000 RBX=ffffab1cc1800000 RCX=0000000000000000 RDX=ffffab1cc1fff838 RSI=00000000000fff07 RDI=ffff8d33cb4d7828 RBP=ffffab1cc56cbcc0 RSP=ffffab1cc56cbca0 R8 =0000000000000016 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000 R12=00000000000fff07 R13=000000010d1af001 R14=00000000000000f9 R15=0000000000000000 RIP=ffffffffc0dbb7e7 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 ffffffff 00c00000 CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0000 0000000000000000 ffffffff 00c00000 FS =0000 0000000000000000 ffffffff 00c00000 GS =0000 ffff8d3479c80000 ffffffff 00c00000 LDT=0000 0000000000000000 00000000 00000000 TR =0040 fffffe0e7ce7d000 00004087 00008b00 DPL=0 TSS64-busy GDT= fffffe0e7ce7b000 0000007f IDT= fffffe0000000000 00000fff CR0=80050033 CR2=00007f8689aa05b0 CR3=000000010c7f6005 CR4=00370ee0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=d6 72 39 45 85 c0 74 17 31 c0 48 63 d0 4c 01 e2 48 8d 14 d3 <4c> 89 2a 83 c0 01 44 39 c0 75 eb 5b 41 5c 41 5d 41 5e 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 2023-10-20T10:47:03.136967Z qemu-system-x86_64: terminating on signal 15 from pid 10535 (/usr/sbin/libvirtd) 2023-10-20 10:47:03.737+0000: shutting down, reason=destroyed
January 4, 20242 yr Author 16 hours ago, SimonF said: Looks like the VM which I am guessing is the igpu one is getting a bad address fault. Does the igpu disappear at the same time. char device redirected to /dev/pts/2 (label charserial0) error: kvm run failed Bad address RAX=0000000000000000 RBX=ffffab1cc1800000 RCX=0000000000000000 RDX=ffffab1cc1fff838 RSI=00000000000fff07 RDI=ffff8d33cb4d7828 RBP=ffffab1cc56cbcc0 RSP=ffffab1cc56cbca0 R8 =0000000000000016 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000000 R12=00000000000fff07 R13=000000010d1af001 R14=00000000000000f9 R15=0000000000000000 RIP=ffffffffc0dbb7e7 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 0000000000000000 ffffffff 00c00000 CS =0010 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] DS =0000 0000000000000000 ffffffff 00c00000 FS =0000 0000000000000000 ffffffff 00c00000 GS =0000 ffff8d3479c80000 ffffffff 00c00000 LDT=0000 0000000000000000 00000000 00000000 TR =0040 fffffe0e7ce7d000 00004087 00008b00 DPL=0 TSS64-busy GDT= fffffe0e7ce7b000 0000007f IDT= fffffe0000000000 00000fff CR0=80050033 CR2=00007f8689aa05b0 CR3=000000010c7f6005 CR4=00370ee0 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=d6 72 39 45 85 c0 74 17 31 c0 48 63 d0 4c 01 e2 48 8d 14 d3 <4c> 89 2a 83 c0 01 44 39 c0 75 eb 5b 41 5c 41 5d 41 5e 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 2023-10-20T10:47:03.136967Z qemu-system-x86_64: terminating on signal 15 from pid 10535 (/usr/sbin/libvirtd) 2023-10-20 10:47:03.737+0000: shutting down, reason=destroyed I'm not sure what you are asking. This VM used to reboot fine but a few months ago it started going to pause instead of finishing the reboot cycle when instructed from CLI during an SSH session. I'm not actively using the iGPU for display purposes, it is attached to the VM purely for the computational element it brings. Thanks.
January 4, 20242 yr Community Expert Solution 2 hours ago, Swift1 said: I'm not sure what you are asking. This VM used to reboot fine but a few months ago it started going to pause instead of finishing the reboot cycle when instructed from CLI during an SSH session. I'm not actively using the iGPU for display purposes, it is attached to the VM purely for the computational element it brings. Thanks. There are bug reports like this one, https://access.redhat.com/solutions/5624631. Does the issue happens if you remove the igpu?
January 4, 20242 yr Author 26 minutes ago, SimonF said: There are bug reports like this one, https://access.redhat.com/solutions/5624631. Does the issue happens if you remove the igpu? Okay, I removed the igpu, successfully went through a reboot cycle. Result! Added the igpu back to get comparative logs, reboot cycle also worked fine. What?! That was unexpected. Prior to this I had made sure that the VM and unraid were fully updated, it hadn't made any difference, still paused the VM on a reboot. As unsatisfying as 'turned it off and on again' is as a fix, I'll take a win when I get one. Thanks for pointing me in the correct direction.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.