Re: [libvirt-users] aarch64 vm doesn't boots
Greetings Andrea, > Sent: Tuesday, January 07, 2020 at 1:55 PM > From: "Andrea Bolognani" > To: daggs > Cc: libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > 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 > > > improvements in the meantime. On my Fedora 31 laptop, which has > > > > > > qemu-system-aarch64-4.2.0-2.fc31.x86_64 > > > libvirt-5.10.0-2.fc31.x86_64 > > > virt-manager-2.2.1-2.fc31.noarch > > > > > > I can run the above and, after some time, get a login prompt on the > > > serial console. > > > > I see, I'll try to bump the versions, can you share you're vm's xml file? > > This is the exact virt-install command I used: > > $ virt-install \ > --cpu cortex-a53 \ > --name alpine-aarch64 \ > --cdrom ~/Downloads/alpine-virt-3.11.2-aarch64.iso \ > --disk size=8 \ > --vcpus 4 \ > --memory 2048 \ > --os-variant alpinelinux3.8 \ > --arch aarch64 \ > --boot > loader=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,loader.readonly=yes,loader.type=pflash,nvram.template=/usr/share/edk2/aarch64/vars-template-pflash.raw,loader_secure=no > > The '--boot ...' part is only necessary because of an issue in > current libvirt that's already being worked on. > > Here's the full XML: > > > alpine-aarch64 > e4b687d8-b535-436a-bee7-fac688d3d1b4 > >xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0;> > http://alpinelinux.org/alpinelinux/3.8"/> > > > 2097152 > 2097152 > 4 > > hvm >type='pflash'>/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw >template='/usr/share/edk2/aarch64/vars-template-pflash.raw'>/var/lib/libvirt/qemu/nvram/alpine-aarch64_VARS.fd > > > > > > > > cortex-a53 > > > destroy > restart > destroy > > /usr/bin/qemu-system-aarch64 > > > > > function='0x0'/> > > > > > > > > > function='0x0'/> > > > function='0x0'/> > > > > > > function='0x0' multifunction='on'/> > > > > > function='0x1'/> > > > > > function='0x2'/> > > > > > function='0x3'/> > > > > > function='0x4'/> > > > > > function='0x5'/> > > > function='0x0'/> > > > > > > function='0x0'/> > > > > > > > > > > > > > > > thanks. I'll test it out. Dagg. ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] aarch64 vm doesn't boots
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 > > improvements in the meantime. On my Fedora 31 laptop, which has > > > > qemu-system-aarch64-4.2.0-2.fc31.x86_64 > > libvirt-5.10.0-2.fc31.x86_64 > > virt-manager-2.2.1-2.fc31.noarch > > > > I can run the above and, after some time, get a login prompt on the > > serial console. > > I see, I'll try to bump the versions, can you share you're vm's xml file? This is the exact virt-install command I used: $ virt-install \ --cpu cortex-a53 \ --name alpine-aarch64 \ --cdrom ~/Downloads/alpine-virt-3.11.2-aarch64.iso \ --disk size=8 \ --vcpus 4 \ --memory 2048 \ --os-variant alpinelinux3.8 \ --arch aarch64 \ --boot loader=/usr/share/edk2/aarch64/QEMU_EFI-pflash.raw,loader.readonly=yes,loader.type=pflash,nvram.template=/usr/share/edk2/aarch64/vars-template-pflash.raw,loader_secure=no The '--boot ...' part is only necessary because of an issue in current libvirt that's already being worked on. Here's the full XML: alpine-aarch64 e4b687d8-b535-436a-bee7-fac688d3d1b4 http://libosinfo.org/xmlns/libvirt/domain/1.0;> http://alpinelinux.org/alpinelinux/3.8"/> 2097152 2097152 4 hvm /usr/share/edk2/aarch64/QEMU_EFI-pflash.raw /var/lib/libvirt/qemu/nvram/alpine-aarch64_VARS.fd cortex-a53 destroy restart destroy /usr/bin/qemu-system-aarch64 -- Andrea Bolognani / Red Hat / Virtualization ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
Re: [libvirt-users] aarch64 vm doesn't boots
Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" > To: daggs , 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 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 2048 --os-type linux --arch aarch64 > > > > I've tried adding a vnc server and vga device but the screen stays black, > > qxl doesn't work. > > 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 > improvements in the meantime. On my Fedora 31 laptop, which has > > qemu-system-aarch64-4.2.0-2.fc31.x86_64 > libvirt-5.10.0-2.fc31.x86_64 > virt-manager-2.2.1-2.fc31.noarch > > I can run the above and, after some time, get a login prompt on the > serial console. > I see, I'll try to bump the versions, can you share you're vm's xml file? Thanks, Dagg ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
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 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 2048 --os-type linux --arch aarch64 > > I've tried adding a vnc server and vga device but the screen stays black, qxl > doesn't work. > 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 improvements in the meantime. On my Fedora 31 laptop, which has qemu-system-aarch64-4.2.0-2.fc31.x86_64 libvirt-5.10.0-2.fc31.x86_64 virt-manager-2.2.1-2.fc31.noarch I can run the above and, after some time, get a login prompt on the serial console. -- Andrea Bolognani / Red Hat / Virtualization ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
[libvirt-users] aarch64 vm doesn't boots
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: alpine_rpi4_dev_machine b1b155fc-cb92-4f22-8904-c934dd24415b 4194304 4194304 4 hvm cortex-a53 destroy restart restart /usr/bin/qemu-system-aarch64 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 2048 --os-type linux --arch aarch64 I've tried adding a vnc server and vga device but the screen stays black, qxl doesn't work. 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? Thanks, Dagg. ___ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
