That couldn’t be it, though, because it was working fine before. Everyone on the internet had mentioned to enable Virtualization in your BIOS. Results turned up pretty quickly, actually. What on earth had happened?! I hadn’t changed anything since then and now! Naturally, I resorted to my GoogleFu for the answer. I opened up VirtualBox, and was greeted with this beautiful message: Two days later, I had a little bit of downtime at work, so I figured I’d mess around with the VM a little bit more. I then added the Ubuntu Server VM, configured it quickly, and was up in no time. Then, I got sidetracked and finally thought, “Nah, that’s too much work. That’ll be easy.” I went into the “Programs and Features” and enabled Hyper-V. Then I thought to myself, “Maybe I’ll just use Hyper-V on my local machine.
I want to keep this separate from everything else, since it’s just a test machine.” Well, no, actually, I don’t want to do that. “Oh! I’ll just use vCenter and create a quick dev box. I then thought to myself, “How do I want to virtualize this?” So I headed on over to, downloaded the latest version of Ubuntu Server, and was about to get started. I was wanting to install a Linux VM so that I could do some testing on a few applications, as well as use it as an excuse to improve on my pathetic Vim skills (you can find my very basic. I ran into an interesting (read: frustrating) problem this week at work.
0 kommentar(er)
