On Fri, Oct 24, 2014 at 11:17:48AM +0100, Daniel P. Berrange wrote:
On Fri, Oct 24, 2014 at 12:15:24PM +0200, Martin Kletzander wrote:
On Fri, Oct 24, 2014 at 07:16:44AM +0200, Michal Privoznik wrote:
On 22.10.2014 13:58, Martin Kletzander wrote:
Hi everyone,
I had this idea that since we are
On Mon, Oct 27, 2014 at 01:42:59PM +0100, Martin Kletzander wrote:
On Fri, Oct 24, 2014 at 11:17:48AM +0100, Daniel P. Berrange wrote:
On Fri, Oct 24, 2014 at 12:15:24PM +0200, Martin Kletzander wrote:
On Fri, Oct 24, 2014 at 07:16:44AM +0200, Michal Privoznik wrote:
On 22.10.2014 13:58,
On Fri, Oct 24, 2014 at 07:16:44AM +0200, Michal Privoznik wrote:
On 22.10.2014 13:58, Martin Kletzander wrote:
Hi everyone,
I had this idea that since we are probing QEMU binaries for devices
using 'qom-list-types', we could store that data in the capabilities
and check whether device models
On Fri, Oct 24, 2014 at 12:15:24PM +0200, Martin Kletzander wrote:
On Fri, Oct 24, 2014 at 07:16:44AM +0200, Michal Privoznik wrote:
On 22.10.2014 13:58, Martin Kletzander wrote:
Hi everyone,
I had this idea that since we are probing QEMU binaries for devices
using 'qom-list-types', we
On 22.10.2014 13:58, Martin Kletzander wrote:
Hi everyone,
I had this idea that since we are probing QEMU binaries for devices
using 'qom-list-types', we could store that data in the capabilities
and check whether device models are supported before starting QEMU.
We do that for _some newer_
Hi everyone,
I had this idea that since we are probing QEMU binaries for devices
using 'qom-list-types', we could store that data in the capabilities
and check whether device models are supported before starting QEMU.
We do that for _some newer_ devices, but this would be global. It
would help
