6.1.9
RHOSO18 <= FR5(18.0.17)
RHEL-9
✔️
6.1.8
RHOSO18 <= FR3(18.0.11) and RHOSP17.1
RHEL-9
✔️
6.1.7
RHOSO18 <= FR3(18.0.11) and RHOSP17.1
RHEL-9
✔️
6.1.6
RHOSO18 <= FR3(18.0.11) and RHOSP17.1
RHEL-9
✔️
6.1.5
RHOSP17.1
RHEL-9
✔️
6.0.0
RHOSP17.1
RHEL-9
✔️
6.X
2024.1 (Caracal) 2023.2 (Bobcat) 2023.1 (Antelope) Yoga
Jammy Jammy Jammy Jammy
✔️ ✔️ ✔️ ✔️
6.1.7+
2025.1 (Epoxy) 2023.2 (Bobcat)
✔️ ✔️
6.1.1+
2023.2 (Bobcat) 2023.1 (Antelope)
✔️ ✔️
6.1.7+
MOSK25.2 MOSK25.1
✔️ ✔️
6.1.2+
MOSK25.1
✔️ ✔️
All versions of T4O-6.x releases support NFSv3, NFSv4 and S3 as backup targets on all the compatible distributions.
All versions of T4O-6.x releases support encryption using Barbican service on all the compatible distributions.
Installing the QEMU guest agent is an optional but recommended service to run inside the VM to ensure backup data consistency with Trilio. QEMU Guest Agent is the standard OpenSource QEMU/KVM hypervisor agent that runs inside a virtual machine (VM) and communicates with the host system (the hypervisor) to provide enhanced management and control of the VM. It is an essential component of any hypervisor platform that OpenStack can use to provide enhanced functionality when required.
To enable this feature, you must set hw_qemu_guest_agent=yes as a metadata parameter on the image you wish to use to create the guest-agent-capable instances from. Reference: https://docs.openstack.org/nova/pike/admin/configuration/hypervisor-kvm.html
If the Virtual Machine is already created from the glance image which doesn't have the hw_qemu_guest_agent=yes property set, guest agent can be enabled using following process:
The process is stopping the VM, manually adding the lines below to the virsh definition using "virsh edit ", and starting it again:
The VM the needs to be running the qemu-guest agent software:
Ubuntu/Debian: sudo apt install -y qemu-guest-agent && sudo systemctl enable qemu-guest-agent && sudo systemctl restart qemu-guest-agent && sudo systemctl status qemu-guest-agent --no-pager
RHEL/CentOS VMs: sudo yum install -y qemu-guest-agent && sudo systemctl enable qemu-guest-agent && sudo systemctl restart qemu-guest-agent && sudo systemctl status qemu-guest-agent --no-pager
Windows VMs: Inside the guest OS, install the guest agent tools from: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win-guest-tools.exe. Finally, make sure the service is running and set to start on boot automatically, in PowerShell, as Administrator: Set-Service QEMU-GA -StartupType Automatic; Restart-Service QEMU-GA; Get-Service QEMU-GA
You can confirm the qemu-guest-agent is running properly after installed, from the compute host, like this:
virsh qemu-agent-command $INSTANCE '{"execute":"guest-ping"}'
The output must be: {"return":{}}
Software Driven Migration is supported in T4O 5.X release. Please refer VM-Migration-T4O-5.X
Last updated
Was this helpful?
Was this helpful?
<channel type='unix'>
<target type='virtio' name='org.qemu.guest_agent.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>