{ "componentChunkName": "component---src-templates-blog-post-js", "path": "/docs/trouble-shooting-and-advanced-usages/", "result": {"data":{"site":{"siteMetadata":{"title":"Linuxdev Documentation","social":{"disqusShortName":"kennyyeoyounet"}}},"markdownRemark":{"id":"3983e6bf-1b00-5cf5-ae9e-62d291660e87","excerpt":"Trouble shooting and advanced usages Want to change the host only network IP is hardcoded in so you can edit Want to destroy the VM but use the docker lib…","html":"

Trouble shooting and advanced usages

\n

Want to change the host only network IP

\n

192.168.99.123 is hardcoded in Vagrantfile so you can edit

\n
  config.vm.network \"private_network\", ip: \"192.168.99.123\"
\n

Want to destroy the VM but use the docker lib storage in the new VM

\n

vagrant destory will remove all the VM storage attached.

\n

To avoid deletion of the storage attached,

\n
    \n
  1. Shutdown the VM first with vagrant halt
    2. \n
  2. dettach the disk using Virtualbox\n
      \n
    1. Open Oracle VM VirtualBox
      2. \n
    \n
    3. \n
\n

\"image\"\n2. In Tools > Media, identify docker.xx.vdi in the right pane, which is used in the VM\n3. right click and click Release\n\"image\"\n3. destroy the VM running ./destroy.sh in linuxdev dir\n4. bootstrap.sh\n5. run sudo /root/docker.disk.sh /dev/sdb1 to attach the storage

\n

Want to create another VM

\n

Clone this repo in the other directory and use different machine name during bootstrap.sh

\n

You will need to manage DOCKER_xxx variables manually

\n

Creating machine failed

\n

Find %USERPROFILE%\\VirualBox VMs\\<machine_name>\\Logs and try to delete.\nIf it cannot be deleted, see the Task Manager and

\n

\"image\"

\n

End tasks for VirtualBox Headless Frontend and try to remove the Logs directory and try again.

\n

OSX Big Sur

\n

VirtualBox fails to add host-only network when it’s not allowed in the Security & Privacy

\n

\"image\"

\n

Without this, creating VM using Vagrant won’t work.

\n

Version 11.4?

\n

I had some issue with granting the Virtualbox kernel extension, which was keep asking the permission after rebooting. Allowing actually was not working.

\n

The issue was fixed I upgrade OSX to 16.

\n

If you have 11.4, please consider upgrade to 11.6 or the latest.

\n

Use ext4 partition on Windows 10

\n

This would be just an instace how to use ext4 partitions

\n

USB external disks can be mounted directly to the Linux on VM and if you have VirtualBox Extension pack, USB3 is also supported.

\n

The following instruction is mounting external disk to VirtualBox without the extension pack.

\n

Mount entire system disk to Virutalbox

\n

create vmdk file for the physical drive

\n

Windows Disk Management will show the external disks with the number like 0, 1, 2

\n

if you have the only system drive, it will be 0. so the find the number of the disk which you want to mount.

\n

And run following command in Powershell (admin)\nwith modifying the number 2 to the number of your disk

\n
VBoxManage internalcommands createrawvmdk -filename \"$env:USERPROFILE\\VirtualBox VMs\\external-disk-2.vmdk\" -rawdisk \\\\.\\PhysicalDrive2
\n

add the vmdk to your virtualbox.

\n
  config.vm.provider \"virtualbox\" do |vb|\n...\n    disk_filename = (ENV['USERPROFILE'] || \"\") + \"/VirtualBox VMs/ext4t2.vmdk\"\n    vb.customize ['storageattach', :id, '--storagectl', 'SATA Controller', '--port', 3, '--type', 'hdd', '--medium', disk_filename]\n  end
\n

You will need Administrator privileges to starth the VM.

\n

Shutdown all the running VirtualBox VM and kill close Virtualbox and kill all running VBox related tasks. and runt vagrant reload command as Admnistrator.

\n

When the VM is running, you can check the partitions by

\n
ls -la /dev/disk/by-uuid/
\n

or by root (sudo su -)

\n
fdisk -l
\n

mount the partition by mount /dev/disk/by-uuid/4fcc4aba-dd74-4212-b6f0-154c49c69242 /mnt/external-disk-2\nor add that to /etc/fstab

\n

And you can use startup_as_admin.bat in the scripts directory to start the VM as administrator

","fields":{"slug":"/docs/trouble-shooting-and-advanced-usages/","language":""},"frontmatter":{"title":"Trouble shooting and advanced usages","date":"October 15, 2021","description":null}},"previous":{"fields":{"slug":"/docs/configuring-vm/"},"frontmatter":{"title":"Configuring VM"}},"next":{"fields":{"slug":"/README/"},"frontmatter":{"title":""}}},"pageContext":{"id":"3983e6bf-1b00-5cf5-ae9e-62d291660e87","previousPostId":"bdeda9f4-e066-5cbb-8d3e-d5bc814c0e13","nextPostId":"353110f7-3eab-5001-afc4-9591e38db8e5","language":"en","i18n":{"language":"en","languages":["en","ko","ja"],"defaultLanguage":"en","generateDefaultLanguagePage":false,"routed":false,"originalPath":"/docs/trouble-shooting-and-advanced-usages/","path":"/docs/trouble-shooting-and-advanced-usages/"}}}, "staticQueryHashes": ["2355076697","3347749741"]}