From d858b507f5c7867cb1690c8f051b20e05cc3fe81 Mon Sep 17 00:00:00 2001 From: John Bowdre Date: Tue, 6 Feb 2024 09:48:17 -0600 Subject: [PATCH] update post with note on checking nested virtualization availability --- .../index.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md b/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md index e46e8bc..388dc0e 100644 --- a/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md +++ b/content/posts/create-vms-chromebook-hashicorp-vagrant/index.md @@ -1,7 +1,7 @@ --- title: "Create Virtual Machines on a Chromebook with HashiCorp Vagrant" # Title of the blog post. date: 2023-02-20 # Date of post creation. -lastmod: 2024-01-17 +lastmod: 2024-02-06 description: "Pairing the powerful Linux Development Environment on modern Chromebooks with HashiCorp Vagrant to create and manage local virtual machines for development and testing" # Description used for search engine. featured: true # Sets if post is a featured post, making appear on the home page side bar. draft: false # Sets whether to render this page. Draft of true will not be rendered. @@ -29,7 +29,16 @@ Also, because I'm a bit of a sadist, I wanted to do this all on my new [Framewor It took a bit of fumbling, but this article describes what it took to get a Vagrant-powered VM up and running in the [Linux Development Environment](https://chromeos.dev/en/linux) on my Chromebook (which is currently running ChromeOS v111 beta). ### Install the prerequisites -There are are a few packages which need to be installed before we can move on to the Vagrant-specific stuff. It's quite possible that these are already on your system.... but if they *aren't* already present you'll have a bad problem[^problem]. +First things first: you should make sure your Chromebook supports nested virtualization. Many newer ones do, but it's not a universal thing. It's easy to check just by looking for the `kvm` device file: + +```shell +ls -l /dev/kvm # [tl! .cmd] +crw-rw---- 10,232 root 6 Feb 08:03 /dev/kvm # [tl! .nocopy] +``` + +As long as you don't get an error like `No such file or directory` then you should be good to go. + +With that out of the way, there are are a few packages which need to be installed before we can move on to the Vagrant-specific stuff. It's quite possible that these are already on your system.... but if they *aren't* already present you'll have a bad problem[^problem]. ```shell sudo apt update && sudo apt install \ # [tl! .cmd]