Steve Coleman:
I have been having problems with starting a Win10 VM for a while now.
Previously Qubes would always timeout and shut it down even though the VM
was up and running fine. My impression is that once the VM was forcibly
terminated/killed due to a timeout, usually the next time it would start up
normally. I could spend as much as an hour just trying to get it startup
properly, and now it doesn't even get that far.
Disabling swap or setting it to a fixed size seemed to help me here,
although my issue was the Win10 VM crashing on startup.
Now after enough forced terminations it is unable to even begin starting
and no logs are being created at all. The only symptom is the popup message
"block device dom0:loop1 not available". I don't see anything significant
from journalctl or dmesg. Running in debug mode does absolutely nothing.
Restoring from backup just gives the same loop error message when
attempting to start the restored VM.
Have you enabled debug mode, booted, then checked the vm's log in
/var/log/qubes? You might also need to set qvm-feature gui-emulated to 1
on the VM to see a display with debug checked, but see if it's already
set first with qvm-features .
Q: What is this loop1 supposed to point at, and is there a way to recreate
it?
I booted my Win10 VM and don't have a loop1. Is it possible you set up
your VM somehow to automatically map an ISO?
--
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ce82839d-f215-3ab0-2195-d665ffd42b67%40danwin1210.me.
