On 02/06/2013 02:13 PM, Laine Stump wrote:
Now that qemu is getting the q35 machine type, libvirt needs to support it.
In an attempt to make sure that libvirt actually does something useful
with qemu's new machine type, I'm revisiting this topic and trying to
get a more thorough understanding.
On Wed, 2013-02-27 at 13:20 -0500, Laine Stump wrote:
On 02/06/2013 02:13 PM, Laine Stump wrote:
Now that qemu is getting the q35 machine type, libvirt needs to support it.
In an attempt to make sure that libvirt actually does something useful
with qemu's new machine type, I'm revisiting
Alex Williamson alex.william...@redhat.com writes:
On Wed, 2013-02-27 at 13:20 -0500, Laine Stump wrote:
On 02/06/2013 02:13 PM, Laine Stump wrote:
Now that qemu is getting the q35 machine type, libvirt needs to support it.
In an attempt to make sure that libvirt actually does something
Cc'ing a few QOMmers...
Laine Stump la...@redhat.com writes:
Now that qemu is getting the q35 machine type, libvirt needs to support it.
As far as I understand, from libvirt's point of view, q35 is just
another x86_64 system, but with a different set of implicit devices,
and possibly some
On Wed, Feb 06, 2013 at 01:15:05PM -0700, Alex Williamson wrote:
On Wed, 2013-02-06 at 14:13 -0500, Laine Stump wrote:
2) Are there other issues aside from implicit controller devices I
need to consider for q35? For example, are there any devices that (as
I recall is the case for some
On Thu, 2013-02-07 at 17:31 +, Daniel P. Berrange wrote:
On Wed, Feb 06, 2013 at 01:15:05PM -0700, Alex Williamson wrote:
On Wed, 2013-02-06 at 14:13 -0500, Laine Stump wrote:
2) Are there other issues aside from implicit controller devices I
need to consider for q35? For example, are
On Wed, 2013-02-06 at 14:13 -0500, Laine Stump wrote:
Now that qemu is getting the q35 machine type, libvirt needs to
support it.
As far as I understand, from libvirt's point of view, q35 is just
another x86_64 system, but with a different set of implicit devices,
and possibly some extra
