Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Qube failed to start #8603

Closed
grnklod opened this issue Oct 13, 2023 · 6 comments
Closed

Qube failed to start #8603

grnklod opened this issue Oct 13, 2023 · 6 comments
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: self-closed Voluntarily closed by the person who opened it before another resolution occurred. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@grnklod
Copy link

grnklod commented Oct 13, 2023 •
edited
Loading

Qubes OS release

R4.2

Brief summary

I've started a new Whonix disposable qube by launching Tor Browser but it failed to start.
Seems like it hung for some reason but there is no related info in logs.
Maybe it has happened because of this:
#7956
Disposable qube is from whonix-ws-17-dvm disposable template based on whonix-workstation-17 template with latest updates and Tor Browser 13 using kernel 6.5.6-2.qubes.fc37.x86_64 with default initial memory 400 MB and 2 VCPUs.
Dom0 has latest updates but is using kernel 6.4.13-1.qubes.fc37.x86_64.

I think this is the second time it happened but I'm not sure and I couldn't reproduce it.

guest-disp6708.log
journalctl-disp6708.log
@grnklod grnklod added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels Oct 13, 2023
@marmarek
Copy link
Member

What if you increase initial memory? Do you see it using CPU (for example via domains widget) when it's hanging?

@grnklod
Copy link
Author

grnklod commented Oct 13, 2023

I've tried to reproduce it for around 20 times but it didn't happen anymore. Maybe it happened because of some factors like if I started it when system was on high load or it needed to free some memory for it but couldn't.
I'll try to reproduce it some more.

@andrewdavidwong andrewdavidwong added C: core needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.2 This issue affects Qubes OS 4.2. labels Oct 13, 2023
@grnklod
Copy link
Author

grnklod commented Oct 15, 2023

It happened again with Whonix disposable. I've checked the qube RAM/CPU usage and it stayed at 400 MB 99% CPU the entry time until shutdown.
The system wasn't on high CPU or disk load but I had multiple qubes running so entry RAM was used and memory balancing should've been used.
This time it hung earlier but still no relevant info (for me at least):
guest-disp5413.log
journalctl-disp5413.log
I'll increase initial memory to 800 MB and see if it'll happen again.

@grnklod
Copy link
Author

grnklod commented Oct 20, 2023

This issue happened again but this time it happened for newly created AppVM based on debian-11 template at first start. It had default 400 MB initial memory as well.
After changing Whonix disposables initial memory to 800 MB this issue didn't happen with them anymore.
It seems that there is an issue that happens only at first VM start after creation if there is not enough initial memory.

@grnklod
Copy link
Author

grnklod commented Oct 23, 2023

It seems that there is an issue that happens only at first VM start after creation if there is not enough initial memory.

The same happened to appvm based on debian-12 that wasn't started the first time after creation. It had 400 MB initial memory.

@grnklod
Copy link
Author

grnklod commented Jan 13, 2024

I've returned the qubes initial memory to 400 MB quite some time ago and didn't have this issue anymore.
I guess this can be closed as fixed / can't reproduce.

@grnklod grnklod closed this as completed Jan 13, 2024
@andrewdavidwong andrewdavidwong added R: self-closed Voluntarily closed by the person who opened it before another resolution occurred. and removed needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. labels Jan 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-4.2 This issue affects Qubes OS 4.2. C: core P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. R: self-closed Voluntarily closed by the person who opened it before another resolution occurred. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@marmarek @andrewdavidwong @grnklod