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 unit='KiB'>4194304</currentMemory>
<vcpu placement='static'>4</vcpu>
<os>
<type arch='aarch64' machine='virt'>hvm</type>
</os>
<features>
<gic version='2'/>
</features>
<cpu mode='custom' match='exact'>
<model fallback='allow'>cortex-a53</model>
</cpu>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-aarch64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/home/dagg/alpine-rpi4.qcow2'/>
<target dev='vda' bus='virtio'/>
<boot order='2'/>
<address type='virtio-mmio'/>
</disk>
<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/home/dagg/alpine-virt-3.11.2-aarch64.iso'/>
<target dev='sdb' bus='scsi'/>
<readonly/>
<boot order='1'/>
<address type='drive' controller='0' bus='0'
target='0' unit='1'/>
</disk>
<controller type='scsi' index='0'
model='virtio-scsi'>
<address type='virtio-mmio'/>
</controller>
<controller type='pci' index='0'
model='pcie-root'/>
<controller type='pci' index='1'
model='dmi-to-pci-bridge'>
<model name='i82801b11-bridge'/>
<address type='pci' domain='0x0000' bus='0x00'
slot='0x01' function='0x0'/>
</controller>
<controller type='pci' index='2'
model='pci-bridge'>
<model name='pci-bridge'/>
<target chassisNr='2'/>
<address type='pci' domain='0x0000' bus='0x01'
slot='0x01' function='0x0'/>
</controller>
<controller type='virtio-serial' index='0'>
<address type='virtio-mmio'/>
</controller>
<interface type='network'>
<mac address='52:54:00:e0:7a:7b'/>
<source network='default'/>
<model type='virtio'/>
<address type='virtio-mmio'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<console type='pty'>
<target type='virtio' port='1'/>
</console>
</devices>
</domain>
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.
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
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 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