On 12/06/2015 10:59 AM, Jim Fehlig wrote:
> On 12/06/2015 10:04 AM, Jim Fehlig wrote:
>> On 12/04/2015 12:45 PM, Joao Martins wrote:
>>> Commit d2e5538b1 changes virDomainDef to include ifnames
>>> that autogenerated by libxl, and that are also cleared
>>> on domain cleanup. One place that's
On 12/04/2015 12:45 PM, Joao Martins wrote:
> Commit d2e5538b1 changes virDomainDef to include ifnames
> that autogenerated by libxl, and that are also cleared
> on domain cleanup. One place that's missing is on
> migration, when domain xml is sent to dst libvirtd and
> would contain ifnames from
On 12/06/2015 10:04 AM, Jim Fehlig wrote:
> On 12/04/2015 12:45 PM, Joao Martins wrote:
>> Commit d2e5538b1 changes virDomainDef to include ifnames
>> that autogenerated by libxl, and that are also cleared
>> on domain cleanup. One place that's missing is on
>> migration, when domain xml is sent
On 12/06/2015 06:11 PM, Jim Fehlig wrote:
> On 12/06/2015 10:59 AM, Jim Fehlig wrote:
>> On 12/06/2015 10:04 AM, Jim Fehlig wrote:
>>> On 12/04/2015 12:45 PM, Joao Martins wrote:
Commit d2e5538b1 changes virDomainDef to include ifnames
that autogenerated by libxl, and that are also
So as planned I tagged rc2 in git and pushed signed tarball and rpms
to the usual place:
ftp://libvirt.org/libvirt/
but in my testing I'm hitting a serious issue. After upgrading to the new
set of rpms and restarting the service and virt-manager, while virt-manager
can connect and list
Hi all,
I'm trying to figure out how apps should request virtio-pci for libvirt + qemu
+ arm/aarch64. Let me provide some background.
qemu's arm/aarch64 original virtio support is via virtio-mmio, libvirt XML
. Currently this is what libvirt sets as the
address default for all arm/aarch64 virtio
On Mon, Dec 07, 2015 at 11:06:52AM +0800, Daniel Veillard wrote:
So as planned I tagged rc2 in git and pushed signed tarball and rpms
to the usual place:
ftp://libvirt.org/libvirt/
but in my testing I'm hitting a serious issue. After upgrading to the new
set of rpms and restarting the
