Yes , but not only.
I'm using oVirt - a KVM management tool and I can currently make a snapshot 
only by pausing the VM or by completely stopping it first.
For now, it's not a big deal - as I'm still exploring openBSD , but who knows.
Also the management interface cannot provide details about CPU and RAM usage , 
nor I cannot gracefully shut the VM down from the interface.
The oVirt manager allows automatic evacuation of the VM, if it requires more 
memory/cpu than the host can currently providing (for a lab overcommitting is 

I'm just looking to enable those fancy things that make our life easier.

Best Regards,
Strahil Nikolov

On April 29, 2019 12:07:32 AM GMT+03:00, Tom Smyth 
<> wrote:
>Hello Strahil,
>what are you trying to achieve with the Qemu Guest Agent ?
>is it  quiescing during backups .>?
>On Sun, 28 Apr 2019 at 20:59, Kristjan Komloši
><> wrote:
>> On Sun, 2019-04-28 at 11:10 +0000, Strahil Nikolov wrote:
>> > Hi All,
>> > I am new to openBSD and I really like the idea. Sadly I do not have
>> > suitable hardware to run on , thus I use KVM and I would be happy
>> > anyone hint me of a working solution for Qemu Guest Agent.
>> > Anything I dig up (via google searches) show up only suggestions ,
>> > but nothing more.In openBSD 6.4  I successfully installed qemu (and
>> > thus the agent), but I can't understand how to get the device
>> > for communication with the host up and running.
>> > As I mainly know linux - I know that we need a kernel module that
>> > be loaded and with combination of udev rules - the devices is
>> > on the necessary location and with the correct rights.According to
>> > many google findings - openBSD doesn't support any more loadable
>> > kernel module support.
>> > I have tried to figure it out by myself, but I cannot find the
>> > necessary module needed, nor how to load it in a proper manner.
>> > Any hint is well appreciated.
>> > Best Regards,Strahil Nikolov
>> Kernel modules don't exist under OpenBSD to ensure security, so don't
>> go there. Communication with host is probably best done through the
>> serial console. Take a look at the boot.conf(8) manpage.

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Reply via email to