Ben Coxford

> That would be really awesome! > > Helping users to understand what is happening on the cluster is valueable. > > One thing to keep in mind: What component...

Yeah I have no issue with this if you'd like to pick it up. So currently, the following events are reported on the virtual machine CR. ```bash 56m Normal SuccessfulDataVolumeCreate...

> I understand, but wouldn't this potentially lead to an excessive number of events in the namespace? In your example, the `Started` event indicates a successful VM start, implying that...

Yeah that is ideal. I'd agree `Resumed`, `Paused` would be useful as well. Should the owning object be `VirtualMachine`? The vm status should report these conditions.

> Now, for objects: I do not think that we should bubble everything up to the VM object ie. @bc185174 last snippet could overwhelm a user imo. Thus some kind...

I think it's fine as they are different objects. Imo it's a bit overkill on VMI, there are a lot of events when ultimately the VM object is what a...

/remove-lifecycle rotten @Acedus is this still being worked on? Always happy to help contribute.

/reopen Re-opening. I managed to get the device plugins working but noticed the libvirt scheme is missing fields for `hostdev`. https://github.com/kubevirt/kubevirt/blob/main/pkg/virt-launcher/virtwrap/api/schema.go#L628 only allows for `address` field to be set and...

> Would you mind opening a new issue with information to reproduce that? Feel free to /cc me so I can take a look. Sure thing. > That's by design....

It'll be `prepend_sudo: false`. Found that without `-a true` no metrics are produced. https://github.com/MindFlavor/prometheus_wireguard_exporter/issues/86