nsult...@gmail.com>
<mailto:deadhorseconsulting@__gmail.com
<mailto:deadhorseconsult...@gmail.com>>>
To: "engine-devel" mailto:engine-devel@ovirt.org>
<mailto:engine-devel@ovirt.org
<mailto:engine-devel@ovirt.org
ith
>> it" sounds like a good plan to me :)
>>
>> But ignoring that, what kind of behaviour would you like? maybe the
>> ability to pass custom libvirt flags on VM startup?
>> This can be pretty easily Implemented as an all purpose hook, isn't
>&g
evel" mailto:engine-devel@ovirt.org>>
Sent: Friday, August 2, 2013 7:43:31 PM
Subject: [Engine-devel] direct manipulation of libvirt
A broad question here, perhaps not a possibility but I figured I
would toss it out there anyway.
VDSM is great at what it does,
> This can be pretty easily Implemented as an all purpose hook, isn't it?
> (write once, pass any argument you like)
>
> - Original Message -
> From: "Dead Horse"
> To: "engine-devel"
> Sent: Friday, August 2, 2013 7:43:31 PM
> Subject: [En
t? (write
once, pass any argument you like)
- Original Message -
From: "Dead Horse"
To: "engine-devel"
Sent: Friday, August 2, 2013 7:43:31 PM
Subject: [Engine-devel] direct manipulation of libvirt
A broad question here, perhaps not a possibility but I figured I would toss
A broad question here, perhaps not a possibility but I figured I would toss
it out there anyway.
VDSM is great at what it does, however there are those times when direct
manipulation of libvirt or libvirt VM configuration would be very handy.
The safe defaults and tested VM configurations that VDS
