Start of daytime week

Bit of a status update.

Typing this at Bachelor Farmer Cafe. Expensive but there’s good wifi and the chairs are comfy. It’s becoming a bit of a habit after a shift at SysadminJerb but somehow the vibe here lets me think, which is nice. I can then go home and sleep and still feel productive about my night at work.

It’s getting cold. Got me a cool leather jacket but I will definitely need more heavy winter gear.

Still working at merBOHjob… which makes for long shifts when there are days when I have to work at both places at once. Staying up 30 hours or more is now a common occurrence and it would seem my psyche has stabilized enough to be able to do this and not feel like I’m losing myself anymore.

Chuckling as I type this cos one of the barists totally looks like she doesn’t want to be here, and she looks like the old GM at 112 that is a… colorful character, to me.

Oh right, I got kicked out of 112 this past Sunday. First time I’ve been kicked out of a restaurant. Just walked out, didn’t fight it. At least now I know for sure they don’t want my business, nor any business I might send their way. Guess I could send people to bFOHjob but I’m pretty sure they also fucken hate me.

Guess I’ll have to send people to Bachelor Farmer.

VERR_CPUM_INVALID_HWVIRT_CONFIG

The error message from Virtualbox reads:

"Cannot enable nested VT-x/AMD-V without nested-paging and unresricted guest execution!

(VERR_CPUM_INVALID_HWVIRT_CONFIG). "

Encountered this error when trying to run any VM under VirtualBox Version 6.0.12 r133076 (Qt5.6.2). I’m assuming all versions of VBox are affected when running under Windows 10.

Looking around the web found this reddit post where this solution is proposed:

PS C:\Windows\system32> bcdedit /set hypervisorlaunchtype off

On my system (Windows Version 10.0.18362.329) it didn’t ask for a reboot but even after rebooting VirtualBox still didn’t work. That’s when I remembered I had enabled the Virtual Machine Platform option in the “Turn Windows Features on or off” section of Programs and Features. Disabling this feature and rebooting allowed Virtualbox VMs to boot without issues.

Here’s how to disable the option through PowerShell with Admin rights:

PS C:\Windows\system32> Disable-WindowsOptionalFeature -online -FeatureName VirtualMachinePlatform

I’m not sure if other Hyper-V options would affect VirtualBox in the same way but it’d seem they do. Posting up here mostly so it doesn’t get lost in social media link morass.