Hi All,
As discussed before, upstream are working about PCIE instead of PCI in
AArch64.
Thanks for your efforts about this on AArch64 :-)
If it convenient, could you tell me when we plan to finish this task ?
and which qemu version will support this functions in the future?
Big
Great ~ Thanks for your valuable information~
I will try with the xml and any update I will post here.
On 18 August 2016 at 21:51, Andrea Bolognani wrote:
> On Thu, 2016-08-18 at 20:43 +0800, Kevin Zhao wrote:
> > What's the minimum version of Qemu that support virito-1.0?
On 08/19/2016 11:43 AM, Andrea Bolognani wrote:
On Thu, 2016-08-18 at 08:38 +0200, Andrew Jones wrote:
Finally, FWIW, with a guest kernel of 4.6.4-301.fc24.aarch64. The
following qemu command line works for me.
(notice the use of PCIe), and my network interface gets labeled enp0s1.
$QEMU
On Thu, 2016-08-18 at 08:38 +0200, Andrew Jones wrote:
> > > Finally, FWIW, with a guest kernel of 4.6.4-301.fc24.aarch64. The
> > > following qemu command line works for me.
> > > (notice the use of PCIe), and my network interface gets labeled enp0s1.
> > >
> > > $QEMU -machine
On 08/18/2016 08:43 AM, Kevin Zhao wrote:
Hi Laine,
Thanks :-) I also has a little questions below.
On 18 August 2016 at 01:00, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
On 08/18/2016 08:10 AM, Marcel Apfelbaum wrote:
On 08/17/2016 08:00 PM, Laine Stump wrote:
What I'm not sure about is whether we should always auto-add an extra
pcie-*-root to be sure a device can be hotplugged, or if we should admit
that 1
available slot isn't good enough for all
On 08/18/2016 03:41 AM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 01:00:05PM -0400, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
On Thu, 2016-08-18 at 20:43 +0800, Kevin Zhao wrote:
> What's the minimum version of Qemu that support virito-1.0?
> Does Qemu 2.6 works?
2.6 definitely has virtio 1.0 support, however libvirt does
not yet allow you to control whether a device uses 0.9, 1.0
or both. The default for 2.6 should
Hi All,
Thanks for your all kindly response. Really Great and helpful :-)
On 18 August 2016 at 20:30, Kevin Zhao wrote:
> Hi Jones:
>Thanks~It is great that Qemu has been working on that :-)
>
> On 18 August 2016 at 00:13, Andrew Jones wrote:
On 08/17/2016 08:00 PM, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
[...]
Hi,
1) If we want to support both PCIe devices and PCI, then things are messy.
Currently we propose dropping PCI support.
Hi Laine,
Thanks :-) I also has a little questions below.
On 18 August 2016 at 01:00, Laine Stump wrote:
> On 08/17/2016 12:13 PM, Andrew Jones wrote:
>
>> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
>>
>>> Hi all,
>>> Now I'm investigating net device
Hi Jones:
Thanks~It is great that Qemu has been working on that :-)
On 18 August 2016 at 00:13, Andrew Jones wrote:
> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > Hi all,
> > Now I'm investigating net device hot plug and disk hotplug for
> >
On Wed, Aug 17, 2016 at 01:00:05PM -0400, Laine Stump wrote:
> On 08/17/2016 12:13 PM, Andrew Jones wrote:
> > On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > > Hi all,
> > > Now I'm investigating net device hot plug and disk hotplug for
> > > AArch64. For virtio , the
On Wed, Aug 17, 2016 at 06:41:33PM +0200, Andrea Bolognani wrote:
> On Wed, 2016-08-17 at 18:13 +0200, Andrew Jones wrote:
> > On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > >
> > > Hi all,
> > > Now I'm investigating net device hot plug and disk hotplug for
> > > AArch64.
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
AArch64. For virtio , the default address is virtio-mmio. After Libvirt
1.3.5, user can explicitly specify the
On Wed, 2016-08-17 at 18:13 +0200, Andrew Jones wrote:
> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> >
> > Hi all,
> > Now I'm investigating net device hot plug and disk hotplug for
> > AArch64. For virtio , the default address is virtio-mmio. After Libvirt
> > 1.3.5, user
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> Hi all,
> Now I'm investigating net device hot plug and disk hotplug for
> AArch64. For virtio , the default address is virtio-mmio. After Libvirt
> 1.3.5, user can explicitly specify the address-type to pci and so libvirt
> will
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
AArch64. For virtio , the default address is virtio-mmio. After Libvirt
1.3.5, user can explicitly specify the address-type to pci and so libvirt
will pass the virtio-pci parameters to the Qemu.
Both my host and guest
18 matches
Mail list logo