On 07/17/2014 03:05 AM, Michal Privoznik wrote:
>> Furthermore, I'm trying to figure out how to advertise whether a given
>> domain will support active commit (and similarly, Peter's patches for
>> relative backing name preservation). Advertising the feature just
>> through 'virsh capabilities' i
On 17.07.2014 11:11, Daniel P. Berrange wrote:
On Thu, Jul 17, 2014 at 11:05:08AM +0200, Michal Privoznik wrote:
# tools/virsh domcapabilities --virttype kvm
error: failed to get emulator capabilities
error: invalid argument: at least one of emulatorbin or architecture
fields must be present
Wo
On Thu, Jul 17, 2014 at 11:05:08AM +0200, Michal Privoznik wrote:
> ># tools/virsh domcapabilities --virttype kvm
> >error: failed to get emulator capabilities
> >error: invalid argument: at least one of emulatorbin or architecture
> >fields must be present
> >
> >Would it be nicer to behave the sa
On 16.07.2014 21:00, Eric Blake wrote:
We have some inconsistencies in the node capabilities (which shows guest
capabilities for some default binaries) and domcapabilities (which shows
guest capabilities for a specified binary). It might be nicer for
client applications if the two XML components
On Wed, Jul 16, 2014 at 01:00:30PM -0600, Eric Blake wrote:
> Furthermore, I'm trying to figure out how to advertise whether a given
> domain will support active commit (and similarly, Peter's patches for
> relative backing name preservation). Advertising the feature just
> through 'virsh capabili
We have some inconsistencies in the node capabilities (which shows guest
capabilities for some default binaries) and domcapabilities (which shows
guest capabilities for a specified binary). It might be nicer for
client applications if the two XML components share a common schema and
output layout,
