Busk at 20:05, 5 May 2023

2023-05-05T20:05:22Z

imported>Jeremy-busk at 00:16, 1 March 2019

2019-03-01T00:16:38Z

New page

Main Menu
* [[ Virtualbox CLI ]]
* [[ Virtualbox Install ]]
* [[ Virtualbox for Users ]]
* [[ Virtualbox - Remote Management ]]

# Manual
* https://www.virtualbox.org/manual/ch13.html

# Tips & Tricks
* https://wiki.archlinux.org/index.php/VirtualBox/Tips_and_tricks

# Images
* https://virtualboxes.org/images/centos/
* https://docs.openstack.org/image-guide/obtain-images.html

sudo apt-get remove qemu-kvm libvirt-bin

sudo apt install linux-headers-$(uname -r) build-essential dkms

# Live Migration (Teleportation)

Teleporting between hosts of differing CPUs is not always successful.

To support teleporation, the VM guest hard drive must be located on some type of shared storage, "NFS, Windows share or iSCSI", which both computers have concurrent access to. The process of doing the teleporation is done by command line only.

A VM is created on the target computer with the exact same settings as the VM running on the source host including the same hard drives, but with the following modification to cause it to wait for the running state of the source VM to be sent to it.
```
VBoxManage modifyvm VMName --teleporter on --teleporterport 12345 --teleporterpassword PassWord
```

The target VM is started and it listens on the network for a connection from the source VM to transfer the VM state
```
VBoxManage --startvm VMName
```

The source VM is commanded to teleport itself to the waiting target VM.
```
VBoxManage controlvm VMName teleport --host TargetComputer --port 12345 --password PassWord
```

# No console vir cli

So far, no answers. After more research it looks like VirtualBox does not provide this functionality. Best that it seems I can do is to use a remote desktop. For my CentOS, the most convenient app is rdesktop. You need to have the extension pack installed. Then enable remote desktop protocol for the client. Once the VM is running you can then use rdesktop to access the client console. If rdesktop is started immediately after the VM, you do get access to the boot sequence. Thus:

$ vboxmanage modifyvm "archive" --vrde on
$ vboxmanage startvm "archive" --type headless ; rdesktop localhost

# Affecting Bugs

* https://www.virtualbox.org/ticket/18463
* https://bugs.launchpad.net/cloud-images/+bug/1573095

```
sudo sed -i 's/ console=ttyS0//g' /etc/default/grub.d/50-cloudimg-settings.cfg
sudo update-grub
# However, you need ttyS0 in grub in order to interact with vm guest using
```

# Resources
* https://gist.github.com/smoser/6066204

← Older revision		Revision as of 20:05, 5 May 2023
Line 1:		Line 1:
		+	# Install windows
		+	```
		+	winget install Oracle.Virtualbox
		+	sudo multipass set local.driver=virtualbox
		+	```
		+
	Main Menu		Main Menu
	* [[ Virtualbox CLI ]]		* [[ Virtualbox CLI ]]

Virtualbox - Revision history

Busk at 20:05, 5 May 2023

imported>Jeremy-busk at 00:16, 1 March 2019