Storage_setup

Links: https://libvirt.org/storage.html

this one is more so for FYI - on how virt-manager can be used:

https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/chap-Virtualization_Administration_Guide-Storage_Pools-Storage_Pools.html

self-explantory link:

http://ask.xmodulo.com/change-default-location-libvirt-vm-images.html

ADDING THE NVME SSD as a STORAGE POOL:

dharra:~# vgcreate nvmep3_lvm /dev/nvme0n1p3
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/nvme0n1p3" successfully created Volume group "nvmep3_lvm" successfully created

then run virt-manager on local PC.

connect to xen (which has libvirt already installed)

open edit --> connection details

click storage tab

add new storage:

give name nvme3_ssd_lvm + type logical: lvm volume group

target: /dev/nvmep3_lvm (from vgcreate command)

NO SOURCE

UNCHECK BUILD POOL

CHECKING:

on xen

virsh

virsh # pool-list
Name State Autostart------------------------------------------- default active yes nvme3_ssd_lvm active yes virsh # pool-info nvme3_ssd_lvmName: nvme3_ssd_lvmUUID: fff9dd7f-4093-4786-b66e-ee1291332517State: runningPersistent: yesAutostart: yesCapacity: 456.94 GiBAllocation: 0.00 BAvailable: 456.94 GiB

ADDING THE SATA DISK AS TWO STROAGE POOLS -

SWAP:

DID NOT RAID THIS - AS NO POINT IN COPYING SWAP DATA ACROSS 2 DISKS.

something like swap in this...

pvcreate /dev/sda2 /dev/sdb2
vgcreate sataAB_swap /dev/sda2 /dev/sdb2

from here on follow the instructions of adding the vol group into Storage pool.

dharra:~# pvcreate /dev/sda2 /dev/sdb2
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/sda2" successfully created allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/sdb2" successfully created
dharra:~# vgcreate sataAB_swap /dev/sda2 /dev/sdb2

Volume group "sataAB_swap" successfully created

ADDED to XEN using the same method as for nvme3 - described earlier using Virt-Manager on local PC

REST OF 2 NAS DISKS:

ref: 2_4TB_Disks

dharra:~# apk add mdadm
(1/1) Installing mdadm (3.3.4-r1)Executing busybox-1.24.1-r7.triggerOK: 392 MiB in 114 packages
dharra:~# mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sda3 /dev/sdb3
mdadm: Note: this array has metadata at the start and may not be suitable as a boot device. If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90Continue creating array? Ymdadm: Defaulting to version 1.2 metadatamdadm: array /dev/md0 started.
dharra:~# echo 'raid1' >> /etc/modules #load raid module on boot
dharra:~# rc-update add mdadm-raid
* service mdadm-raid added to runlevel default
dharra:~# mdadm --detail --scan >> /etc/mdadm.conf
dharra:~# pvcreate /dev/md0
allocation/use_blkid_wiping=1 configuration setting is set while LVM is not compiled with blkid wiping support. Falling back to native LVM signature detection. Physical volume "/dev/md0" successfully created
dharra:~# vgcreate sataAB_data /dev/md0
Volume group "sataAB_data" successfully created

ADDED to XEN using the same method as for nvme3 - described earlier using Virt-Manager on local PC