I'll be blogging about the Chef stuff later. This includes replacing the Boxstarter based install with a Chef cookbook and also using a native Hyper-V builder. I've been playing with some new significant changes to my Packer build process. Obviously hyper-v has no menu item to mount the guest additions CD, but the. Sudo sh /media/VBOXADDITIONS_4.1.10_76795/n uninstall
Luckily the nice folks on freenode IRC #centos pointed me in the right direction: my virtualbox VM had the guest additions installed still! This article explains how to remove the vbox guest additions, but basically just run the installer again with the uninstall argument: I did find that the rescue option would boot, but unfortunately rebuilding initramfs with: dracut -force didn't seem to have any effect. A lot of articles on this issue recommend rebuilding the initramfs by rebooting and choosing the "rescue" option on the GRUB boot menu. A look at journalctl indicated that this was because none of the disks were found. On a normal boot the VM would hang at the graphical boot screen for a few minutes, then fail and dump to the dracut recovery shell. Once those issues were resolved, I had a new vhdx that I was able to attach to a new Hyper-V VM. I ultimately ended up needing to comment out these: The original article is a little vague on which lines might need to be commented out in the "desc.txt" file that is created. This worked as described in the original article.Ģ. Ultimately I ended up finding this article which proposed an alternate command: ConvertTo-MvmcVirtualHardDisk. Convert-VHD would not recognize by vmdk file. Here's the list of issues that I faced that were not covered in that article:ġ. For the most part I followed this guide which has links to all of the required tools. There's plenty of guides out there on how to make this migration, but they all seem to be missing at least a few important points. Because of that, it's no longer possible to run a ring-2 hypervisor like VirtualBox. My understanding for this is that Hyper-V is a ring-1 hypervisor which runs your primary OS as an (albeit special) VM. This is automatically done by the installer, but contains one minor inconvenient caveat: once Hyper-V is enabled, VirtualBox no longer functions. The installation process is pretty straightforward but requires Hyper-V be enabled on the machine. Recently I decided I wanted to install Docker Desktop for Windows in order to do some local testing.
0 kommentar(er)
