... | ... | @@ -19,48 +19,53 @@ Install muvirt to the target and configure the network as required. |
|
|
You can run these steps from the CLI, assuming a brand new muvirt system:
|
|
|
|
|
|
```
|
|
|
/usr/libexec/muvirt/muvirt-system-setup /dev/nvme0n1
|
|
|
muvirt-system-setup /dev/nvme0n1
|
|
|
|
|
|
appstore-list
|
|
|
appstore-deploy --password=hunter2 groovy ubuntu-groovy-cloudimage
|
|
|
appstore-deploy --password=hunter2 hirsute ubuntu-hirsute
|
|
|
/etc/init.d/muvirt start groovy
|
|
|
|
|
|
# Wait until groovy shows status 'on'
|
|
|
muvirt-status
|
|
|
```
|
|
|
|
|
|
## Setting up a disk and default settings
|
|
|
To do a 'turnkey' install you can either do 'samedisk' (add extra partitions to the same drive muVirt is on) or 'fulldisk' (dedicate a full drive to VM storage, muvirt needs to be booted from another storage device).
|
|
|
|
|
|
I suggest using 'fulldisk' mode at the moment as there is no sysupgrade support (on LS1088 platforms) yet - so it is a good idea to keep the muvirt system and VM storage on different devices.
|
|
|
|
|
|
\* Currently, samedisk install is only verified to work against the partition layout in the muvirt ext4 image.
|
|
|
|
|
|
|
|
|
## Setting up a disk
|
|
|
`muvirt-system-setup` will:
|
|
|
1. Partition the storage device as required
|
|
|
2. Setup an LVM2 instance along with a 'scratch' (temporary file) partition and swapfile
|
|
|
|
|
|
On the target, do:
|
|
|
```
|
|
|
# Full disk install
|
|
|
MODE=fulldisk /usr/libexec/muvirt/muvirt-system-setup /dev/nvme0n1
|
|
|
You can use either the same disk device muvirt has been booted from, or another device.
|
|
|
|
|
|
# Samedisk install
|
|
|
/usr/libexec/muvirt/muvirt-system-setup /dev/nvme0n1
|
|
|
```
|
|
|
|
|
|
## Workaround unresponsive nginx
|
|
|
At the time of writing, nginx may fail to respond to requests on boot - I suspect this is a race condition.
|
|
|
If you don't want to set up an LVM device yet, it is possible to use the provisioning features with the 'provision in place' flag against a qcow2 file, see [Virtual-Machine-Provisioning#provisioning in place](https://gitlab.com/traversetech/muvirt/-/wikis/Virtual-Machine-Provisioning#provisioning-in-place-example)
|
|
|
|
|
|
You can work around this by adding a restart command to `/etc/rc.local`:
|
|
|
```
|
|
|
root@muvirt:~# cat /etc/rc.local
|
|
|
# Put your custom commands here that should be executed once
|
|
|
# the system init finished. By default this file does nothing.
|
|
|
root@muvirt:~# muvirt-system-setup
|
|
|
These block devices may be formatted for virtual machine storage
|
|
|
sda Cruzer Blade (14.3GiB)
|
|
|
|
|
|
nvme0n1 128GB NVMe SSD CD8E0792149E52103847 (119.2GiB)
|
|
|
|
|
|
What block device should be formatted? [nvme0n1]
|
|
|
How big should the working area / cache partition be? [10240MB]
|
|
|
How big should the swap partition be? [10240MB]
|
|
|
Formatting device nvme0n1 with a 10240 MB work area and 10240 MB swap area
|
|
|
Proceed? (y or n)y
|
|
|
[ 32.920567] Adding 10485736k swap on /dev/nvme0n1p4. Priority:-2 extents:1 across:10485736k SS
|
|
|
[ 32.931947] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts:
|
|
|
Setup done
|
|
|
```
|
|
|
|
|
|
/etc/init.d/nginx restart
|
|
|
exit 0
|
|
|
You can also specify the answers through command line options:
|
|
|
```
|
|
|
root@muvirt:~# muvirt-system-setup --help
|
|
|
muvirt-system-setup - setup muvirt on this system
|
|
|
including partitioning of storage device
|
|
|
Usage:
|
|
|
muvirt-system-setup [options] [device = same disk as / by default]
|
|
|
Options:
|
|
|
--worksize= Set size of "work" partition, in megabytes (default 10240MB)
|
|
|
--swapsize= Set size of swap partition in megabytes (default 10240MB)
|
|
|
--no-prompt Don't prompt before formatting
|
|
|
```
|
|
|
|
|
|
## Login to LuCI
|
... | ... | |