-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Split the cloud-in-a-box file (#656)
This way it's easier to document more different virtual machine scenarios. Signed-off-by: Christian Berendt <[email protected]>
- Loading branch information
Showing
5 changed files
with
45 additions
and
47 deletions.
There are no files selected for viewing
File renamed without changes
File renamed without changes
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
docs/guides/other-guides/cloud-in-a-box/running-on-a-virtual-machine.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Running on a virtual machine | ||
|
||
## KVM | ||
|
||
### Nested virtualization | ||
|
||
You likely want to run virtual machines on top of your Cloud in a Box. | ||
The host machine has to support and enabled nested virtualization. | ||
|
||
To enable nested virtualization the CPU configuration of the VM has to be `host-passthrough` or `host-model` | ||
|
||
* [Enabling nested virtualization in Fedora](https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/) | ||
|
||
The linked guide can be used in other distributions as well. | ||
|
||
### Disk space saving | ||
|
||
When using Cloud in a Box in a VM, you can utilize the qcow2 disk image or similar technology to save space. | ||
In that case, the base installation requires just around 70 GB instead of a full 1 TB. | ||
(*The drive still needs to be made with a capacity of at least 1TB; however, the actual disk space usage is lower.*) | ||
|
||
Also in case you want to experiment a bit more and "hack around" using the manual installation | ||
you can make disk snapshots when turned off after the Ubuntu installs, `bootstrap.sh` and `deploy.sh` to speed up your | ||
progress. | ||
|
||
If you use qemu, you can use following command to do snapshots. | ||
|
||
```bash | ||
sudo virsh snapshot-create-as --domain cib bootstrap "run of bootstrap.sh" --disk-only --diskspec sda,snapshot=external,file=/var/lib/libvirt/images/ub2022_cib_boostrap.qcow2 --atomic | ||
``` | ||
|
||
### QEMU guest agent | ||
|
||
When running inside QEMU, it may be worth it to install the QEMU guest agent. | ||
|
||
```bash | ||
sudo apt -y install qemu-guest-agent | ||
sudo systemctl enable qemu-guest-agent | ||
sudo systemctl start qemu-guest-agent | ||
``` |