Having the ram on either 1848MB or 2048MB didn’t change anything, unfortunately.
Sorry to hear. What I do in these situations is to run in dom0 terminal sudo journalctl -f, then trying to start qube, following dom0 terminal. When it finishes, ctrl+c in terminal, and copy paste the part of the journal here in order to be helped. It is very rare not to be able to start win qube under neither circumstances.
1 Like
It’s np. I kind of break every bit of technology around me by nature, so… lol. But anyways, I ran the command, booted up the vm, the issue happened, then it closed – but the output was… a bit long. so I threw it in an unlisted Pastebin just bc I didn’t want to spam this thread – anyways, here you go: [novum@dom0 Desktop]$ journalctl -fJan 01 19:01:01 dom0 run-parts[135901]: (/e - Pastebin.com
I am seriously hoping this works, because I’m contemplating dual-booting with windows if this fails… but I know that compromises my security 10 fold, so I’m hoping we can figure this out. Which I just wanted to shout out a thank you for everybody that’s tried to help so far, as well as anyone who may. Thank you guys.
Also, instinct tells me somebody may ask if I tried to custom install – I did not. I used the average 4.2.0 iso, flashed it to a thumbdrive, then installed it. Nothing custom about it – even though the whole “hostname=?” is the way it is and all those.
My bad everyone – I was a complete idiot and swapped the two gpus in my mind… so I was trying to hide, passthrough the active gpu. My sincere apologies. That said, there still is an issue that I’m in need of help for – I’m making a new thread now, since it’s not related to this fully anymore.