computing:virtmanagerhell
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| computing:virtmanagerhell [2022/12/22 16:37] – oemb1905 | computing:virtmanagerhell [2026/04/05 00:45] (current) – oemb1905 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| ------------------------------------------- | ------------------------------------------- | ||
| - | To make a VM from the command line, do the following. Note that this recipe assumes you have already created your virtual switch, br0. It also presumes you have already created your virtual disk, and if you have not, simply run '' | + | To make a VM from the command line, do the following. Note that this recipe assumes you have already created your virtual switch, br0. It also presumes you have already created your virtual disk, and if you have not, simply run '' |
| sudo virt-install --name=new.img \ | sudo virt-install --name=new.img \ | ||
| Line 18: | Line 18: | ||
| --location=/ | --location=/ | ||
| --network bridge:br0 | --network bridge:br0 | ||
| + | |||
| + | Here's a more complex block, that enables trim on vdd, uses a preseed.cfg file to automate install, establishes a custom vnet name, enables the guest agent, and opens a terminal/ | ||
| + | |||
| + | virt-install --name=domain.com.qcow2 \ | ||
| + | --os-variant=debian12 \ | ||
| + | --vcpu=2 \ | ||
| + | --memory 4096 \ | ||
| + | --disk path=/ | ||
| + | --check path_in_use=off \ | ||
| + | --graphics none \ | ||
| + | --location=/ | ||
| + | --network bridge: | ||
| + | --channel unix, | ||
| + | --initrd-inject=/ | ||
| + | --extra-args=" | ||
| To clone an existing image, do the following: | To clone an existing image, do the following: | ||
| Line 47: | Line 62: | ||
| qemu-img convert -p -f raw -O qcow2 guest1.img guest1.qcow2 | qemu-img convert -p -f raw -O qcow2 guest1.img guest1.qcow2 | ||
| - | qemu-img convert -p -f qcow2 -O raw gust1.qcow2 guest1.raw | + | qemu-img convert -p -f qcow2 -O raw guest1.qcow2 guest1.raw |
| | | ||
| If you do end up using this, then you will need to edit the virtual machine' | If you do end up using this, then you will need to edit the virtual machine' | ||
| Line 119: | Line 134: | ||
| qemu-img convert -O qcow2 guest.qcow2 guest-trimmed.qcow2 | qemu-img convert -O qcow2 guest.qcow2 guest-trimmed.qcow2 | ||
| qemu-img convert -O qcow2 -c guest.qcow2 guest-trimmed.qcow2 | qemu-img convert -O qcow2 -c guest.qcow2 guest-trimmed.qcow2 | ||
| + | | ||
| + | To test trimming functionality, | ||
| + | |||
| + | dd if=/ | ||
| + | | ||
| + | To create a backup volume inside a guest you create the volume, attach it, and then shell into the guest and format, mount, and create an fstab entry. First, on the hostOS: | ||
| + | | ||
| + | cd / | ||
| + | qemu-img create -f qcow2 vm1-backup.qcow2 32G | ||
| + | virsh attach-disk guestOS.qcow2 \ | ||
| + | --source / | ||
| + | --target vdb \ | ||
| + | --persistent | ||
| + | | ||
| + | Then, on the guestOS: | ||
| + | | ||
| + | mkdir /mnt/backup | ||
| + | mkfs.ext4 /dev/vdb | ||
| + | mount -t auto /dev/vdb /mnt/backup | ||
| + | nano /etc/fstab | ||
| + | /dev/vdb /mnt/backup ext4 defaults, 0 0 | ||
| The rest from here on out is my attempt at resizing an .img virtual disk using tools exclusively from virsh / virt-manager. These are highly risky moves and totally not needed for day to day operations. It was more of a mission I was on and based on a tutorial I used nearly 15 years ago when expanding a Windows VM I used for teaching software that was only on that VM. At any rate, I have only succeeded twice doing this, and often get confused looking at the l00ps. Proceed with caution! | The rest from here on out is my attempt at resizing an .img virtual disk using tools exclusively from virsh / virt-manager. These are highly risky moves and totally not needed for day to day operations. It was more of a mission I was on and based on a tutorial I used nearly 15 years ago when expanding a Windows VM I used for teaching software that was only on that VM. At any rate, I have only succeeded twice doing this, and often get confused looking at the l00ps. Proceed with caution! | ||
| Line 199: | Line 235: | ||
| kpartx -d debian10.img | kpartx -d debian10.img | ||
| + | | ||
| + | User and group perms: | ||
| + | |||
| + | adduser libvirt-qemu kvm | ||
| + | adduser cockpit-ws kvm | ||
| + | newgrp kvm | ||
| + | |||
| + | Add network interface as custom name for easy tracking: | ||
| + | |||
| + | < | ||
| + | virsh edit domain.com.qcow2 | ||
| + | | ||
| + | < | ||
| + | <mac address=' | ||
| + | <source bridge=' | ||
| + | <target dev=' | ||
| + | <model type=' | ||
| + | <address type=' | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Make sure that Cockpit can access a terminal: | ||
| + | |||
| + | < | ||
| + | virsh edit domain.com.qcow2 | ||
| + | < | ||
| + | <listen type=' | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | If you don't have video enabled, do the following (also needed for Cockpit Terminal rendering): | ||
| + | |||
| + | Option 1 (cirrus): | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Option 2 (qxl) | ||
| + | < | ||
| + | < | ||
| + | < | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Option 3 (use commands) | ||
| + | virt-xml domain.com.qcow2 --add-device --graphics vnc, | ||
| + | virt-xml domain.com.qcow2 --add-device --video qxl | ||
| + | virsh reboot domain.com.qcow2 | ||
| + | |||
| + | Add virtiofs mount point. Here's two, note the staggered bus entry of '' | ||
| + | |||
| + | < | ||
| + | < | ||
| + | <driver type=' | ||
| + | <source dir='/ | ||
| + | <target dir=' | ||
| + | <address type=' | ||
| + | </ | ||
| + | < | ||
| + | <driver type=' | ||
| + | <source dir='/ | ||
| + | <target dir=' | ||
| + | <address type=' | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | Then, inside the VM: | ||
| + | |||
| + | mkdir -p / | ||
| + | mkdir -p / | ||
| + | nano /etc/fstab | ||
| + | support1 | ||
| + | support2 | ||
| + | | ||
| + | If you find '' | ||
| + | |||
| + | sudo systemctl enable serial-getty@ttyS0.service | ||
| + | sudo systemctl start serial-getty@ttyS0.service | ||
| + | |||
| + | Migrating an existing VDD and virsh instance ... just dump or copy paste the .xml with '' | ||
| + | |||
| + | virsh define host.com.xml | ||
| + | virsh start host.com | ||
| + | | ||
| + | You should for sure check the network interface and MAC address, the storage location directory, and obviously run through anything else that might be different on the target migration host. | ||
| - | --- //[[jonathan@haacksnetworking.org|oemb1905]] | + | --- //[[alerts@haacksnetworking.org|oemb1905]] |
computing/virtmanagerhell.1671727066.txt.gz · Last modified: by oemb1905
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: GNU Free Documentation License 1.3
