When attempting to startup whonix-ws-16, getting the following errors:
qrexec-daemon startup failed
qrexec-daemon: qrexec-daemon.c:296: Waiting for VM’s qrexec agent
qrexec-daemon.c:135:sigchld_parent_handler: Connection to VM failed
When you ask a question, you have to show what did you try to resolve it yourself, searches you did, etc…
Yeah; so I have attempted to change the VM’s disk size using both the GUI and also via cli using qvm.
Please see the following thread for the commands run:
What’s interesting is when you attempt to re-install the template, it returns an error message:
qvm-template: error: Template ‘whonix-ws-16’ is not managed by qvm-template
This is what is returned from:
qvm-template --enablerepo=qubes-templates-community reinstall whonix-ws-16
You’ve been already told what to do with that error, but you asked a question without trying or researching on it.
I’ve tried the recommended steps; but I am still getting the same error.
when I check the the log file qubesdb.whonix-ws-16.log there is a long repetition of error messages:
“vchan closed”
vchan protocol is used to stream data between VMs
on a xen host without needing any locks. It is largely undocumented.
I think the issue is related to the disk space being too large actually; but when I attempt to shrink it, I get the
following error message:
For your own safety, shrinking of private is disabled (10000000000 < 26843545600). If you really know what you are doing, resize filesystem manually first, then use -f option.
The issue is that the settings GUI does not allow you to manually resize the disk, it only allows you to increase the size of the disk, not decrease it. So if the issue is that the disk space is too large, then both the GUI and cli methods do not allow you to correct the issue.
The cli call tell you what to do.
You need to use lvresize:
sudo lvresize --size -200G /dev/qubes_dom0/vm-TOO_LARGE-private
This will reduce the size of the private volume of the TOO_LARGE qube by 200G
You will see a warning about potential data loss - it is up to you to
guard against that.
In Qubes the risk is somewhat reduced because qubes creates back-up
volumes, and you can revert to them if you need
Your suggestion worked fine and the command returned successfully. I tried various increments of disk size, but none of them allowed for a proper boot. The same error message gets returned. Please see the following logs from /var/log/xen/console/guest-whonix-ws-16-clone-1.log:
[2022-12-06 09:29:53] Qubes: done.
[2022-12-06 09:29:54] [ 4.130556] EXT4-fs (xvda3): VFS: Found ext4 filesystem with invalid superblock checksum. Run e2fsck?
[2022-12-06 09:29:54] mount: /sysroot: cannot mount; probably corrupted filesystem on /dev/xvda3.
[2022-12-06 09:29:54] Waiting for /dev/xvdd device…
[2022-12-06 09:29:54] [ 4.134881] EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem
[2022-12-06 09:29:54] [ 4.137586] EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[2022-12-06 09:29:54] mount: /tmp/modules: WARNING: device write-protected, mounted read-only.
[2022-12-06 09:29:54] mount: /sysroot/lib/modules: mount point does not exist.
[2022-12-06 09:29:54] mount: /sysroot: mount point not mounted or bad option.
[2022-12-06 09:29:54] switch_root: failed to mount moving /sysroot to /: Invalid argument
[2022-12-06 09:29:54] switch_root: failed. Sorry.
[2022-12-06 09:29:54] [ 4.153087] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[2022-12-06 09:29:54] [ 4.153114] CPU: 0 PID: 1 Comm: switch_root Not tainted 5.15.78-1.fc32.qubes.x86_64 #1
[2022-12-06 09:29:54] [ 4.153138] Call Trace:
[2022-12-06 09:29:54] [ 4.153148]
[2022-12-06 09:29:54] [ 4.153158] dump_stack_lvl+0x46/0x5e
[2022-12-06 09:29:54] [ 4.153175] panic+0xfd/0x2d5
[2022-12-06 09:29:54] [ 4.153190] do_exit.cold+0x93/0x9f
[2022-12-06 09:29:54] [ 4.153205] do_group_exit+0x33/0xa0
[2022-12-06 09:29:54] [ 4.153220] __x64_sys_exit_group+0x14/0x20
[2022-12-06 09:29:54] [ 4.153234] do_syscall_64+0x3b/0x90
[2022-12-06 09:29:54] [ 4.153248] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[2022-12-06 09:29:54] [ 4.153265] RIP: 0033:0x786957a82181
[2022-12-06 09:29:54] [ 4.153278] Code: 1d 4d 0f 00 be e7 00 00 00 ba 3c 00 00 00 eb 16 66 0f 1f 84 00 00 00 00 00 89 d0 0f 05 48 3d 00 f0 ff ff 77 1c f4 89 f0 0f 05 <48> 3d 00 f0 ff ff 76 e7 f7 d8 64 41 89 00 eb df 0f 1f 80 00 00 00
[2022-12-06 09:29:54] [ 4.153325] RSP: 002b:00007ffeb64a25c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
[2022-12-06 09:29:54] [ 4.153351] RAX: ffffffffffffffda RBX: 0000786957b79470 RCX: 0000786957a82181
[2022-12-06 09:29:54] [ 4.153373] RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
[2022-12-06 09:29:54] [ 4.153788] RBP: 0000000000000001 R08: ffffffffffffff80 R09: 0000000000000001
[2022-12-06 09:29:54] [ 4.153810] R10: 00007ffeb64a3fa6 R11: 0000000000000246 R12: 0000786957b79470
[2022-12-06 09:29:54] [ 4.153830] R13: 0000000000000002 R14: 0000786957b79948 R15: 0000000000000000
[2022-12-06 09:29:54] [ 4.153852]
[2022-12-06 09:29:54] [ 4.153901] Kernel Offset: disabled
Don’t reinstall. Delete template and install it again.
Ok; removing the template returns an error message:
qvm-template: error: VM installed by package manager: whonix-ws-16
1 Like
sudo dnf remove qubes-template-whonix*