#qemu

7 posts · Last used 10d

Hot on the heels of the recent 100% failures to install #Haiku in either QEMU VM or lappy SSD [https://infosec.space/@MsDropbear42/117335082820301999 https://infosec.space/@MsDropbear42/117333664504154227] today i am simply "delighted" to report a new round of 100% failures... this time with #GhostBSD. After hours of research last night, including watching a few extremely positive videos of the installation & desktop usage UX, i enthusiastically looked forward keenly to trying it out myself, initially at least in a VM. Downloading the ISO took so many hours that i had to go to bed & hope it would complete ok; returning to pooter this morn showed it did. It then passed the sha256sum check fine. I prepared a #QEMU VM for it, with 4GB RAM & 2 cores, & set it for UEFI bootit booted to the initial menu, where i let it time-out into booting the default multi-user optionit showed several lines of text, then went to a pretty GhostBSD splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screenit showed the splash screeni aborted itmy research had indicated GhostBSD was supposed to be able to boot with either UEFI or BIOS, but as a check, i created a second VM for the ISO, this time with BIOS-boot, & foolishly i blindly accepted all the other default QEMU settingsthis booted with a conspicuously ugly low-resolution screen compared to before, but after the multi-user option initiated, didn't bother with any splash screen, instead a scrolling text wall showing it was loading the ISO into memory... which then summarily failed with an out of memory error & an indignant message it needed min 4GB. that's on me, the default QEMU was only 1GB, d'ohi edited the VM config to give it 6GB, & retriedit got much further this time, but ended in another failure, this time iirc a seg-fault... FFS! i returned to the first VM, increased its RAM also to 6GB, & tried againsplash screensplash screensplash screensplash screenirritated, i began drafting this whinge-posteventually i discovered the VM had emerged from the splash screen, into a wall of text as per pic, ending in another failure... a seg-faulti am really annoyed at this bullshit. Haiku at least has an excuse, being only beta, but wtaf here, Ghost? Is my only bloody option now to escape the invasion of the slopbots in #linux, for me to dig out my abacus or slide-rule? Pretty pissed off atm. #DropbearPooterising #Linux #LinuxWomen #FOSS #FuckGenerativeAI #FuckSlopbots #AntiAI #NoAI
2
2
2
1
Replying to
“what are you trying to do now?” you might be asking. Colima on macOS Ventura and later uses the Apple-supplied 'vz’ engine. #newOldiMac is running Ventura. So maybe docker was interacting poorly with that engine, especially because it was the first macOS version with it… maybe it's buggy? So I'm installing ‘qemu', which is the native colima engine on all pre-Ventura Macs and Linux. building it is taking a bit… #selfhost #footiMac #newOldiMac #mastoAdmin #qemu #colima #cantHelpMyself
2
2
0
0
Replying to
it always takes so much longer than you want…. lol zzzzz #newOldiMac #selfhost #footiMac #newOldiMac #mastoAdmin #qemu #colima #cantHelpMyself
1
1
0
0
You've seen all posts