similar to: FYI: virtio-pci will be the default with libvirt 3.0.0, aarch64 & -M virt

Thanks: Laine Stump, Andrea Bolognani, Marcel Apfelbaum. --- src/guestfs-internal.h | 6 +++--- src/launch-libvirt.c | 41 +++++++++++++++++++++++++++++++++++++++++ 2 files changed, 44 insertions(+), 3 deletions(-) diff --git a/src/guestfs-internal.h b/src/guestfs-internal.h index d437b9a..428da7f 100644 --- a/src/guestfs-internal.h +++ b/src/guestfs-internal.h @@ -137,17 +137,17 @@ /*

This patch causes aarch64 to use virtio-pci instead of virtio-mmio. Virtio-pci is considerably faster than virtio-mmio, it's more like how other architectures work, and it supports hotplugging (although it's not likely we'd use the latter feature). I'm not necessarily suggesting that we apply this. Laine (CC'd) has some further patches to libvirt lined up which AIUI would

Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" <abologna@redhat.com> > To: daggs <daggs@gmx.com>, libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > > Greetings, > > > > I'm trying to bring up a alpine rpi

On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > Greetings, > > I'm trying to bring up a alpine rpi aarch64 image within kvm but I'm ended up with a stuck system, here is the xml: [...] > generated using this cmd: > virt-install --cpu cortex-a53 --name alpine_rpi4_dev_machine --cdrom ./alpine-virt-3.11.2-aarch64.iso --disk path=alpine-rpi4.qcow2,size=8 --vcpus 4 --memory

On Thu, 2019-04-18 at 15:29 +0100, Daniel P. Berrangé wrote: > On Thu, Apr 18, 2019 at 04:23:05PM +0200, Andrea Bolognani wrote: > > qemuDomainAssignAddresses() is supposed to make sure that any address > > configured explicitly by the user (or previously by libvirt) is > > preserved, and it's doing that correctly when it's called from inside > >

On Mon, 2020-01-06 at 20:31 +0100, daggs wrote: > > > I'm using ubuntu 16.04 with libvirt 1.3.1, if this is a version issue, I can upgrade to latest version. > > > what I'm I missing? > > > > Your version of libvirt (as well as QEMU and virt-manager, I assume) > > is fairly old, and aarch64 support specifically has seen quite a few > >

Greetings, I'm trying to bring up a alpine rpi aarch64 image within kvm but I'm ended up with a stuck system, here is the xml: <domain type='qemu'> <name>alpine_rpi4_dev_machine</name> <uuid>b1b155fc-cb92-4f22-8904-c934dd24415b</uuid> <memory unit='KiB'>4194304</memory> <currentMemory

As discussed yesterday: https://www.redhat.com/archives/libguestfs/2017-January/msg00040.html qemu and the kernel now support virtio-pci on aarch64. It turns out that no changes are required for the libvirt backend, since with libvirt 3.0.0 the same XML will switch to using virtio-pci over virtio-mmio. I have tested this on Fedora 25 with a self-compiled libvirt 3.0.0 rc2. However for the

Moving to libvirt-users where it belongs. On Thu, 2019-04-18 at 06:47 +0000, Tal Attaly wrote: > Hi, > I have bridge type interface defined with slot 3 - > <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> > but after running virsh domxml-to-native qemu-argv I get slot 2- > -netdev tap,fd=21,id=hostnet0 -device

ACPI spec 5.0 allows the use of PCI vendor IDs. Since we have one for virtio, it seems neater to use that rather than LNRO. For the device ID, use 103F which is a legacy ID that isn't used in virtio PCI spec - seems to make sense since virtio-mmio is a legacy device but we don't know the correct device type. Guests should probably match everything in the range 1000-103F (just like legacy

ACPI spec 5.0 allows the use of PCI vendor IDs. Since we have one for virtio, it seems neater to use that rather than LNRO. For the device ID, use 103F which is a legacy ID that isn't used in virtio PCI spec - seems to make sense since virtio-mmio is a legacy device but we don't know the correct device type. Guests should probably match everything in the range 1000-103F (just like legacy

We are pleased to announce the second public beta release of CentOS Linux 7 for the AArch64 platform. This release contains fixes and code updates provided in the RHELSA source code recently published to git.centos.org as well as rolling previous updates into the installer. We intend to have a 'Gold' release very soon unless a blocker bugs are reported, so please test this release.

On 10/17/2018 08:56 AM, Andrea Bolognani wrote: > On Wed, 2018-10-17 at 10:50 +0800, Han Han wrote: >> In libvirt, I found pcie-expander-bus controller doesn't support pcie-to-pci-bridge and pcie-switch-upstream-port. > [...] >> # virsh -k0 -K0 define /tmp/c.xml > Aside: the -k and -K virsh options are documented as > > -k | --keepalive-interval=NUM >

Andrea, You are a genius!!! :D It's worked :)) Thank yo so much!!! XD 2017-07-07 12:14 GMT+02:00 Andrea Bolognani <abologna@redhat.com>: > On Fri, 2017-07-07 at 09:46 +0200, Jędrek Domański wrote: > > Hi Dominik, > > > > So what is going on on my computer with the script libvirt-guests.sh? > > Why is it hanging on it? How should I address this problem? >

No XML containing guest information is formed.I'm getting error prior to guest XML formation. On Jul 22, 2015 3:00 PM, "Andrea Bolognani" <abologna@redhat.com> wrote: > On Wed, 2015-07-22 at 14:09 +0530, abhishek jain wrote: > > Hi Andrea > > > > Thanks for the reply. > > Below is some more information regarding the same.. > > > > uname

On Fri, 2020-09-25 at 16:21 +0800, Wei Wang wrote: > On Fri, Sep 25, 2020 at 3:56 PM Andrea Bolognani <abologna@redhat.com> wrote: > > On Fri, 2020-09-25 at 10:33 +0800, Wei Wang wrote: > > > In file included from ../src/util/virfile.c:42: > > > /usr/include/libutil.h:43:10: fatal error: sys/_types.h: No such file or directory > > > 43 | #include

Hi Andrea Thanks for the reply. Below is some more information regarding the same.. uname -a Linux t1040rdb 3.12.37-rt51-QorIQ-SDK-V1.8+gf488de6 #2 SMP Mon Jul 20 14:43:02 IST 2015 ppc GNU/Linux libvirtd --version libvirtd (libvirt) 1.2.13 cat /usr/share/libvirt/cpu_map.xml </arch> <arch name='ppc64'> <model name='POWERPC_e5500'> <vendor

Andrea, I have libvirt version 1.3.1. I am looking at libvirt.org/sources and see more recent versions. Do I have the most up-to-date version? Do I need to upgrade? $libvirtd -V libvirtd (libvirt) 1.3.1 2017-07-10 11:24 GMT+02:00 Jędrek Domański <jedrek.domanski@gmail.com>: > Thank you, Andrea. > After following your instructions I re-enabled it back to check to see if > it will

On Wed, Mar 9, 2016 at 2:49 PM, Andrea Bolognani <abologna@redhat.com> wrote: > On Wed, 2016-03-09 at 14:15 +0000, Andrei Perietanu wrote: > > I am building a custom Linux image which includes KVM and will be > installed on multiple machines. By default when > > installing libvirt you get a 'default network' which adds a 'vrbr0'. > > I found several

Dominik, As far as I am concerned the command provided by Andrea disables libvirt-guests service at boot. jedrek@Home:~$ service libvirt-guests status ● libvirt-guests.service - Suspend Active Libvirt Guests Loaded: loaded (/lib/systemd/system/libvirt-guests.service; *disabled*; vendor preset: enabled) Active: inactive (dead) Docs: man:libvirtd(8) http://libvirt.org When