---
# System prepended metadata

title: OpenShift Guest tools validation

---

# OpenShift Guest tools validation 

## Steps for Linux based Systems
* if guest tools is installed it will populate with the `Hostname` 
![image](https://hackmd.io/_uploads/BJWwxgi8A.png)

The command `grep -i virtio /boot/config-$(uname -r)` is used to check if the current Linux kernel configuration includes support for Virtio drivers.

![image](https://hackmd.io/_uploads/ryK1eesIA.png)

**Verify the Status of the QEMU Guest Agent:**
`sudo systemctl status qemu-guest-agent`
![image](https://hackmd.io/_uploads/Sk0yMgoIA.png)


To determine the storage requirements for a QCOW2 image in OpenShift Virtualization, you need to understand the difference between the virtual size and the actual disk size of the image. Here’s a step-by-step guide to help you manage and allocate the correct storage:

## Understanding QCOW2 Image Sizes

1. **Virtual Size**: This is the maximum size that the virtual disk can grow to. For example, if a QCOW2 image has a virtual size of 50 GiB, it means the virtual machine (VM) will see a 50 GiB disk.

2. **Actual Disk Size**: This is the current size of the QCOW2 file on the host system. It represents the actual space used by the data stored in the image. For instance, a QCOW2 image with a virtual size of 50 GiB might only use 10 GiB of actual disk space if only 10 GiB of data has been written to it.

* https://unix.stackexchange.com/questions/677513/how-to-get-qemu-cow2-actual-file-size
* 