:: Re: [DNG] Which qemu version is shi…
Top Page
This message is part of the following thread:
Mthe complete thread tree sorted by date
MRalph Ronnquist at <-
MRalph Ronnquist at ->
Delete this message
Reply to this message
Author: Ralph Ronnquist
Date:  
To: dng
Subject: Re: [DNG] Which qemu version is shipped by default with devuan 3 ?
Use: qemu-system-arm -device help
to get a list of available devices; maybe e1000 is good?

Ralph.

On Mon, Aug 14, 2023 at 06:18:35PM +0200, Mario Marietto wrote:
> Now,the points are :
>
> 1) rtl8139 offers poor performance
> 2) virtio-net is bugged (sure I can fix it,but let's say that I don't want
> to do it for the moment)
> 3) something else network interface that I can try and that's supported by
> qemu ?
>
> thanks.
>
> On Mon, Aug 14, 2023 at 6:09 PM Mario Marietto <marietto2008@???>
> wrote:
>
> > There is a bug on the virtio-net driver for FreeBSD. This line :
> >
> >     -device virtio-net,netdev=net0,mac="52:54:00:12:34:55" \

> >
> > is not good,as explained here :
> >
> > https://forums.freebsd.org/threads/kernel-panic-on-armv7-with-qemu.89016/
> >
> > the temp fix is to use this,instead :
> >
> > -device rtl8139,netdev=network0
> >
> > but the real solution is to rebuild the kernel with the patch applied.
> >
> >
> > On Mon, Aug 14, 2023 at 6:01 PM Ralph Ronnquist <rrq@???> wrote:
> >
> >> Turned out building qemu was a walk in the park; hats off for the qemu
> >> developers. But for me v5.1.0 worked just fine.
> >>
> >> Btw, I though the kvm operation was just moved to be an "accel" value
> >> on the machine. I.e., using "-M virt,accel=kvm" instead of
> >> "--enable-kvm" ... (or maybe that's only for amd64?)/
> >>
> >> Ralph.
> >>
> >> On Mon, Aug 14, 2023 at 04:52:34PM +0200, Mario Marietto wrote:
> >> > Chromebook is on armhf,32 bit laptop. Probably we can't compare 32 and
> >> 64
> >> > bit.
> >> >
> >> > On Mon, Aug 14, 2023 at 4:37 PM Ralph Ronnquist <rrq@???> wrote:
> >> >
> >> > > On Mon, Aug 14, 2023 at 04:12:53PM +0200, Mario Marietto wrote:
> >> > > > Can I ask you to compile and run qemu 5.1 instead of 5.2 ? This
> >> will help
> >> > > > me to understand if the problem is on the qemu version used. I
> >> can't use
> >> > > > qemu 5.2,because the developers removed the support for kvm from
> >> 5.2 to
> >> > > > today.
> >> > >
> >> > > I'll look into that but it'll take a little while, i.e. some days.
> >> > >
> >> > > So your host a 64-bit arm machine? That's another difference I
> >> > > suppose; I'm using an amd64.
> >> > >
> >> > > Ralph.
> >> > >
> >> > > > On Mon, Aug 14, 2023 at 3:45 PM Ralph Ronnquist <rrq@???> wrote:
> >> > > >
> >> > > > > I guess we have different qemu versions; you have
> >> > > > > > CPU: ARM Cortex-A15 r0p4 (ECO: 0x00000000)
> >> > > > > > CPU Features:
> >> > > > > > Multiprocessing, Thumb2, Security, Virtualization, Generic
> >> Timer,
> >> > > > > VMSAv7,
> >> > > > > > PXN, LPAE, Coherent Walk
> >> > > > >
> >> > > > > and I have:
> >> > > > > ----
> >> > > > > CPU: ARM Cortex-A15 r2p1 (ECO: 0x00000000)
> >> > > > > CPU Features:
> >> > > > > Multiprocessing, Thumb2, Generic Timer, VMSAv7, PXN, LPAE,
> >> Coherent
> >> > > Walk
> >> > > > >
> >> > > > > % qemu-system-arm --version
> >> > > > > QEMU emulator version 5.2.0 (Debian 1:5.2+dfsg-11+deb11u2)
> >> > > > > Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project
> >> developers
> >> > > > >
> >> > > > > % uname -rmsv
> >> > > > > Linux 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64
> >> > > > > (that's from chimaera-security)
> >> > > > > ----
> >> > > > >
> >> > > > > My startup log otherwise looks almost the same as yours down to
> >> > > > > "Starting devd." and after there they differ a lot; mine moves on
> >> > > > > starting dhclient etc and leading to a login. Yours end with
> >> > > > > complaining about ttyv0 and then eventually a reboot.
> >> > > > >
> >> > > > > Ralph.
> >> > > > >
> >> > > > >
> >> > > > > On Mon, Aug 14, 2023 at 02:44:53PM +0200, Mario Marietto wrote:
> >> > > > > > ok. Using "-drive file=$CD1,media=disk,format=raw \" is a
> >> little bit
> >> > > > > > better,but :
> >> > > > > >
> >> > > > > > 1) I don't reach the freebsd login prompt
> >> > > > > > 2) I should choose the disk to boot in the UEFI BIOS,anyway
> >> > > > > >
> >> > > > > > This is the log :
> >> > > > > >
> >> > > > > > Loading kernel...
> >> > > > > > /boot/kernel/kernel text=0x1b4 text=0x719e9c text=0x19a610
> >> > > data=0xb1f60
> >> > > > > > data=0x0+0x1e8000 0x4+0xa4160+0x4+0x116be3-
> >> > > > > > Loading configured modules...
> >> > > > > > /boot/kernel/umodem.ko text=0x1540 text=0xe90 data=0x230+0x4
> >> > > > > > 0x4+0xe70+0x4+0xa7c
> >> > > > > > loading required module 'ucom'
> >> > > > > > /boot/kernel/ucom.ko text=0x19f8 text=0x2d18 data=0x494+0x838
> >> > > > > > 0x4+0x1480+0x4+0xbcf
> >> > > > > > can't find '/etc/hostid'
> >> > > > > > can't find '/boot/entropy'
> >> > > > > >
> >> > > > > > Hit [Enter] to boot immediately, or any other key for command
> >> prompt.
> >> > > > > > Booting [/boot/kernel/kernel]...
> >> > > > > > Using DTB provided by EFI at 0x5feed000.
> >> > > > > > Kernel entry at 0x56000200...
> >> > > > > > Kernel args: (null)
> >> > > > > > WARNING: Cannot find freebsd,dts-version property, cannot check
> >> DTB
> >> > > > > > compliance
> >> > > > > > ---<<BOOT>>---
> >> > > > > > !!!WARNING!!! CPU(0) is vulnerable to speculative branch
> >> attacks. !!!
> >> > > > > > We cannot enable required bit(s) in ACTRL register
> >> > > > > > because it's locked by secure monitor and/or firmware.
> >> > > > > > Copyright (c) 1992-2021 The FreeBSD Project.
> >> > > > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,
> >> 1993,
> >> > > 1994
> >> > > > > >         The Regents of the University of California. All rights
> >> > > reserved.
> >> > > > > > FreeBSD is a registered trademark of The FreeBSD Foundation.
> >> > > > > > FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC
> >> arm
> >> > > > > > FreeBSD clang version 14.0.5 (
> >> > > https://github.com/llvm/llvm-project.git
> >> > > > > > llvmorg-14.0.5-0-gc12386ae247c)
> >> > > > > > VT: init without driver.
> >> > > > > > CPU: ARM Cortex-A15 r0p4 (ECO: 0x00000000)
> >> > > > > > CPU Features:
> >> > > > > >   Multiprocessing, Thumb2, Security, Virtualization, Generic
> >> Timer,
> >> > > > > VMSAv7,
> >> > > > > >   PXN, LPAE, Coherent Walk
> >> > > > > > Optional instructions:
> >> > > > > >   SDIV/UDIV, UMULL, SMULL, SIMD(ext)
> >> > > > > > LoUU:2 LoC:3 LoUIS:2
> >> > > > > > Cache level 1:
> >> > > > > >  32KB/64B 2-way data cache WB Read-Alloc Write-Alloc
> >> > > > > >  32KB/64B 2-way instruction cache Read-Alloc
> >> > > > > > Cache level 2:
> >> > > > > >  1024KB/64B 16-way unified cache WB Read-Alloc Write-Alloc
> >> > > > > > real memory  = 487772160 (465 MB)
> >> > > > > > avail memory = 460943360 (439 MB)
> >> > > > > > arc4random: WARNING: initial seeding bypassed the cryptographic
> >> > > random
> >> > > > > > device because it was not yet seeded and the knob
> >> > > 'bypass_before_seeding'
> >> > > > > > was enabled.
> >> > > > > > random: entropy device external interface
> >> > > > > > kbd0 at kbdmux0
> >> > > > > > ofwbus0: <Open Firmware Device Tree>
> >> > > > > > simplebus0: <Flattened device tree simple bus> on ofwbus0
> >> > > > > > clk_fixed0: <Fixed clock> on ofwbus0
> >> > > > > > psci0: <ARM Power State Co-ordination Interface Driver> on
> >> ofwbus0
> >> > > > > > gic0: <ARM Generic Interrupt Controller> mem
> >> > > > > > 0x8000000-0x800ffff,0x8010000-0x801ffff on ofwbus0
> >> > > > > > gic0: pn 0x2, arch 0x2, rev 0x0, implementer 0x43b irqs 288
> >> > > > > > gicv2m0: <ARM Generic Interrupt Controller MSI/MSIX> mem
> >> > > > > > 0x8020000-0x8020fff on gic0
> >> > > > > > generic_timer0: <ARMv7 Generic Timer> irq 35,36,37,38 on ofwbus0
> >> > > > > > Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz
> >> quality
> >> > > 1000
> >> > > > > > Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz
> >> quality
> >> > > 1000
> >> > > > > > pcib0: <Generic PCI host controller> mem 0x3f000000-0x3fffffff
> >> on
> >> > > ofwbus0
> >> > > > > > pci0: <PCI bus> on pcib0
> >> > > > > > virtio_pci0: <VirtIO PCI (legacy) Network adapter> port
> >> 0x100-0x11f
> >> > > mem
> >> > > > > > 0x11067000-0x11067fff,0x1105c000-0x1105ffff at device 1.0 on
> >> pci0
> >> > > > > > vtnet0: <VirtIO Networking Adapter> on virtio_pci0
> >> > > > > > vtnet0: Ethernet address: 52:54:00:12:34:55
> >> > > > > > virtio_pci1: <VirtIO PCI (modern) GPU adapter> mem
> >> > > > > > 0x11066000-0x11066fff,0x11058000-0x1105bfff at device 2.0 on
> >> pci0
> >> > > > > > virtio_pci1: cannot alloc resource for COMMON_CFG
> >> > > > > > virtio_pci1: cannot map configs
> >> > > > > > device_attach: virtio_pci1 attach returned 22
> >> > > > > > xhci0: <NEC uPD720200 USB 3.0 controller> mem
> >> 0x11060000-0x11063fff
> >> > > at
> >> > > > > > device 3.0 on pci0
> >> > > > > > xhci0: 32 bytes context size, 32-bit DMA
> >> > > > > > usbus0 on xhci0
> >> > > > > > vgapci0: <VGA-compatible display> port 0x120-0x12f mem
> >> > > > > > 0x10000000-0x10ffffff,0x11040000-0x1104ffff at device 4.0 on
> >> pci0
> >> > > > > > vgapci0: Boot video device
> >> > > > > > virtio_pci1: <VirtIO PCI (legacy) Block adapter> port 0x80-0xff
> >> mem
> >> > > > > > 0x11065000-0x11065fff,0x11054000-0x11057fff at device 5.0 on
> >> pci0
> >> > > > > > vtblk0: <VirtIO Block Adapter> on virtio_pci1
> >> > > > > > vtblk0: 5120MB (10485760 512 byte sectors)
> >> > > > > > virtio_pci2: <VirtIO PCI (legacy) Block adapter> mem
> >> > > > > > 0x11064000-0x11064fff,0x11050000-0x11053fff at device 6.0 on
> >> pci0
> >> > > > > > vtblk1: <VirtIO Block Adapter> on virtio_pci2
> >> > > > > > vtblk1: 51200MB (104857600 512 byte sectors)
> >> > > > > > uart0: <PrimeCell UART (PL011)> mem 0x9000000-0x9000fff irq 34
> >> on
> >> > > ofwbus0
> >> > > > > > uart0: console (115200,n,8,1)
> >> > > > > > cpulist0: <Open Firmware CPU Group> on ofwbus0
> >> > > > > > cpu0: <Open Firmware CPU> on cpulist0
> >> > > > > > Timecounters tick every 1.000 msec
> >> > > > > > usbus0: 5.0Gbps Super Speed USB v3.0
> >> > > > > > Trying to mount root from ufs:/dev/ufs/rootfs [rw]...
> >> > > > > > ugen0.1: <(0x1033) XHCI root HUB> at usbus0
> >> > > > > > uhub0 on usbus0
> >> > > > > > uhub0: <(0x1033) XHCI root HUB, class 9/0, rev 3.00/1.00, addr
> >> 1> on
> >> > > > > usbus0
> >> > > > > > Warning: no time-of-day clock registered, system time will not
> >> be set
> >> > > > > > accurately
> >> > > > > > Dual Console: Serial Primary, Video Secondary
> >> > > > > > /etc/rc: WARNING: hostid: unable to figure out a UUID from DMI
> >> data,
> >> > > > > > generating a new one
> >> > > > > > uhub0: 8 ports with 8 removable, self powered
> >> > > > > > ugen0.2: <QEMU QEMU USB Keyboard> at usbus0
> >> > > > > > ukbd0 on uhub0
> >> > > > > > ukbd0: <QEMU QEMU USB Keyboard, class 0/0, rev 2.00/0.00, addr
> >> 1> on
> >> > > > > usbus0
> >> > > > > > kbd1 at ukbd0
> >> > > > > > ugen0.3: <QEMU QEMU USB Mouse> at usbus0
> >> > > > > > ums0 on uhub0
> >> > > > > > ums0: <QEMU QEMU USB Mouse, class 0/0, rev 2.00/0.00, addr 2> on
> >> > > usbus0
> >> > > > > > ums0: 3 buttons and [XYZ] coordinates ID=0
> >> > > > > > random: unblocking device.
> >> > > > > > Setting hostuuid: 65261609-225a-4311-ac85-ad2f65a7d00d.
> >> > > > > > Setting hostid: 0x6a52658d.
> >> > > > > > Starting file system checks:
> >> > > > > > /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS
> >> > > > > > /dev/ufs/rootfs: clean, 752041 free (649 frags, 93924 blocks,
> >> 0.1%
> >> > > > > > fragmentation)
> >> > > > > > Growing root partition to fill device
> >> > > > > > vtbd0s2 resized
> >> > > > > > vtbd0s2a resized
> >> > > > > > growfs: requested size 4.9GB is equal to the current filesystem
> >> size
> >> > > > > 4.9GB
> >> > > > > > Mounting local filesystems:.
> >> > > > > > Setting hostname: generic.
> >> > > > > > Setting up harvesting:

> >> > > > > >
> >> > > > >
> >> > >
> >> [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,[NET_ETHER],NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED
> >> > > > > > Feeding entropy: .
> >> > > > > > Building /boot/kernel/linker.hints
> >> > > > > > ELF ldconfig path: /lib /usr/lib /usr/lib/compat
> >> > > > > > Soft Float compatibility ldconfig path:
> >> > > > > > lo0: link state changed to UP
> >> > > > > > vtnet0: link state changed to UP
> >> > > > > > Starting Network: lo0 vtnet0.
> >> > > > > > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu
> >> 16384
> >> > > > > >
> >> > >  options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
> >> > > > > >         inet6 ::1 prefixlen 128
> >> > > > > >         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> >> > > > > >         inet 127.0.0.1 netmask 0xff000000
> >> > > > > >         groups: lo
> >> > > > > >         nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
> >> > > > > > vtnet0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> >> metric 0
> >> > > mtu
> >> > > > > 1500
> >> > > > > >         options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
> >> > > > > >         ether 52:54:00:12:34:55
> >> > > > > >         media: Ethernet autoselect (10Gbase-T <full-duplex>)
> >> > > > > >         status: active
> >> > > > > >         nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> >> > > > > > Starting devd.
> >> > > > > > eval: cannot open /dev/ttyv0: No such file or directory
> >> > > > > > eval: cannot open /dev/ttyv0: No such file or directory
> >> > > > > > Starting ums0 moused.
> >> > > > > > eval: cannot open /dev/ttyv*: No such file or directory
> >> > > > > > Starting dhclient.
> >> > > > > > DHCPDISCOVER on vtnet0 to 255.255.255.255 port 67 interval 3

> >> > > > > >
> >> > > > > > *Fatal kernel mode data abort: 'Alignment Fault' on read*
> >> > > > > >
> >> > > > > > trapframe: 0xceb73a78
> >> > > > > > FSR=00000001, FAR=d1e3901a, spsr=20000013
> >> > > > > > r0 =00000000, r1 =00000001, r2 =00000001, r3 =ceb73b64
> >> > > > > > r4 =00000014, r5 =d0910900, r6 =d1e3902e, r7 =0000022c
> >> > > > > > UEFI Interactive Shell v2.2
> >> > > > > > EDK II
> >> > > > > > UEFI v2.70 (EDK II, 0x00010000)
> >> > > > > > Mapping table
> >> > > > > >       FS0: Alias(s):HD0b:;BLK1:

> >> > > > > >
> >> > >  PciRoot(0x0)/Pci(0x5,0x0)/HD(1,MBR,0x00000000,0x800,0x19000)
> >> > > > > >      BLK4: Alias(s):
> >> > > > > >           VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00)
> >> > > > > >      BLK0: Alias(s):
> >> > > > > >           PciRoot(0x0)/Pci(0x5,0x0)
> >> > > > > >      BLK2: Alias(s):

> >> > > > > >
> >> > >  PciRoot(0x0)/Pci(0x5,0x0)/HD(2,MBR,0x00000000,0x19800,0x9E6800)
> >> > > > > >      BLK3: Alias(s):
> >> > > > > >           PciRoot(0x0)/Pci(0x6,0x0)
> >> > > > > > Press ESC in 1 seconds to skip startup.nsh or any other key to
> >> > > continue.

> >> > > > > >
> >> > > > > > On Mon, Aug 14, 2023 at 2:38 PM Mario Marietto <
> >> > > marietto2008@???>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > I have tried these arguments :
> >> > > > > > >
> >> > > > > > > -drive file=$CD1,media=disk,format=raw \
> >> > > > > > > -drive file=$DISK,format=raw \
> >> > > > > > >
> >> > > > > > > but I've got the same error.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Mon, Aug 14, 2023 at 1:39 PM Ralph Ronnquist <rrq@???>
> >> > > wrote:
> >> > > > > > >
> >> > > > > > >> Mmm if you registter that "CD" as a disk instead, it seems
> >> to be
> >> > > > > > >> happier.
> >> > > > > > >>
> >> > > > > > >> I.e., instead of:
> >> > > > > > >> -cdrom $CD \
> >> > > > > > >> you use:
> >> > > > > > >> -drive file=$CD,media=disk,format=raw \
> >> > > > > > >>
> >> > > > > > >> then it boots up to a login prompt for me.
> >> > > > > > >>
> >> > > > > > >> Ralph.
> >> > > > > > >>
> >> > > > > > >>
> >> > > > > > >> On Mon, Aug 14, 2023 at 11:50:26AM +0200, Mario Marietto
> >> wrote:
> >> > > > > > >> > I've found the solution here :
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > https://github.com/utmapp/UTM/issues/2333#issuecomment-786129411
> >> > > > > > >> >
> >> > > > > > >> > The parameters that I have used probably have always been
> >> > > > > correct,but
> >> > > > > > >> for
> >> > > > > > >> > some reason,the qemu disk is not detected at a first shot.
> >> It
> >> > > > > should be
> >> > > > > > >> > chosen from the EFI menu. It seems like a Bug. Once
> >> booted,the
> >> > > boot
> >> > > > > > >> > messages are displayed below :
> >> > > > > > >> >
> >> > > > > > >> > Loading kernel...
> >> > > > > > >> > /boot/kernel/kernel text=0x1b4 text=0x719e9c text=0x19a610
> >> > > > > data=0xb1f60
> >> > > > > > >> > data=0x0+0x1e8000 0x4+0xa4160+0x4+0x116be3-
> >> > > > > > >> > Loading configured modules...
> >> > > > > > >> > /boot/kernel/umodem.ko text=0x1540 text=0xe90
> >> data=0x230+0x4
> >> > > > > > >> > 0x4+0xe70+0x4+0xa7c
> >> > > > > > >> > loading required module 'ucom'
> >> > > > > > >> > /boot/kernel/ucom.ko text=0x19f8 text=0x2d18
> >> data=0x494+0x838
> >> > > > > > >> > 0x4+0x1480+0x4+0xbcf
> >> > > > > > >> > can't find '/etc/hostid'
> >> > > > > > >> > can't find '/boot/entropy'
> >> > > > > > >> >
> >> > > > > > >> > Hit [Enter] to boot immediately, or any other key for
> >> command
> >> > > > > prompt.
> >> > > > > > >> > Booting [/boot/kernel/kernel]...
> >> > > > > > >> > Using DTB provided by EFI at 0x5feed000.
> >> > > > > > >> > Kernel entry at 0x56000200...
> >> > > > > > >> > Kernel args: (null)
> >> > > > > > >> > WARNING: Cannot find freebsd,dts-version property, cannot
> >> check
> >> > > DTB
> >> > > > > > >> > compliance
> >> > > > > > >> > ---<<BOOT>>---
> >> > > > > > >> > !!!WARNING!!! CPU(0) is vulnerable to speculative branch
> >> > > attacks.
> >> > > > > !!!
> >> > > > > > >> > We cannot enable required bit(s) in ACTRL register
> >> > > > > > >> > because it's locked by secure monitor and/or firmware.
> >> > > > > > >> > Copyright (c) 1992-2021 The FreeBSD Project.
> >> > > > > > >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991,
> >> 1992,
> >> > > 1993,
> >> > > > > 1994
> >> > > > > > >> >        The Regents of the University of California. All
> >> rights
> >> > > > > reserved.
> >> > > > > > >> > FreeBSD is a registered trademark of The FreeBSD
> >> Foundation.
> >> > > > > > >> > FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597
> >> GENERIC
> >> > > arm
> >> > > > > > >> > FreeBSD clang version 14.0.5 (
> >> > > > > https://github.com/llvm/llvm-project.git
> >> > > > > > >> > llvmorg-14.0.5-0-gc12386ae247c)
> >> > > > > > >> > VT: init without driver.
> >> > > > > > >> > CPU: ARM Cortex-A15 r0p4 (ECO: 0x00000000)
> >> > > > > > >> > CPU Features:
> >> > > > > > >> >  Multiprocessing, Thumb2, Security, Virtualization, Generic
> >> > > Timer,
> >> > > > > > >> VMSAv7,
> >> > > > > > >> >  PXN, LPAE, Coherent Walk
> >> > > > > > >> > Optional instructions:
> >> > > > > > >> >  SDIV/UDIV, UMULL, SMULL, SIMD(ext)
> >> > > > > > >> > LoUU:2 LoC:3 LoUIS:2
> >> > > > > > >> > Cache level 1:
> >> > > > > > >> > 32KB/64B 2-way data cache WB Read-Alloc Write-Alloc
> >> > > > > > >> > 32KB/64B 2-way instruction cache Read-Alloc
> >> > > > > > >> > Cache level 2:
> >> > > > > > >> > 1024KB/64B 16-way unified cache WB Read-Alloc Write-Alloc
> >> > > > > > >> > real memory  = 487772160 (465 MB)
> >> > > > > > >> > avail memory = 460943360 (439 MB)
> >> > > > > > >> > arc4random: WARNING: initial seeding bypassed the
> >> cryptographic
> >> > > > > random
> >> > > > > > >> > device because it was not yet seeded and the knob
> >> 'bypass_before
> >> > > > > > >> > _seeding' was enabled.
> >> > > > > > >> > random: entropy device external interface
> >> > > > > > >> > kbd0 at kbdmux0
> >> > > > > > >> > ofwbus0: <Open Firmware Device Tree>
> >> > > > > > >> > simplebus0: <Flattened device tree simple bus> on ofwbus0
> >> > > > > > >> > clk_fixed0: <Fixed clock> on ofwbus0
> >> > > > > > >> > psci0: <ARM Power State Co-ordination Interface Driver> on
> >> > > ofwbus0
> >> > > > > > >> > gic0: <ARM Generic Interrupt Controller> mem
> >> > > > > > >> > 0x8000000-0x800ffff,0x8010000-0x801ffff on ofwbus0
> >> > > > > > >> > gic0: pn 0x2, arch 0x2, rev 0x0, implementer 0x43b irqs 288
> >> > > > > > >> > gicv2m0: <ARM Generic Interrupt Controller MSI/MSIX> mem
> >> > > > > > >> > 0x8020000-0x8020fff on gic0
> >> > > > > > >> > generic_timer0: <ARMv7 Generic Timer> irq 35,36,37,38 on
> >> ofwbus0
> >> > > > > > >> > Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz
> >> > > quality
> >> > > > > 1000
> >> > > > > > >> > Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz
> >> > > quality
> >> > > > > 1000
> >> > > > > > >> > pcib0: <Generic PCI host controller> mem
> >> 0x3f000000-0x3fffffff
> >> > > on
> >> > > > > > >> ofwbus0
> >> > > > > > >> > pci0: <PCI bus> on pcib0
> >> > > > > > >> > virtio_pci0: <VirtIO PCI (legacy) Network adapter> port
> >> > > 0x100-0x11f
> >> > > > > mem
> >> > > > > > >> > 0x11067000-0x11067fff,0x1105c000-0x1105ffff at device 1.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtnet0: <VirtIO Networking Adapter> on virtio_pci0
> >> > > > > > >> > vtnet0: Ethernet address: 52:54:00:12:34:55
> >> > > > > > >> > virtio_pci1: <VirtIO PCI (modern) GPU adapter> mem
> >> > > > > > >> > 0x11066000-0x11066fff,0x11058000-0x1105bfff at device 2.0
> >> on
> >> > > pci0
> >> > > > > > >> > virtio_pci1: cannot alloc resource for COMMON_CFG
> >> > > > > > >> > virtio_pci1: cannot map configs
> >> > > > > > >> > device_attach: virtio_pci1 attach returned 22
> >> > > > > > >> > xhci0: <NEC uPD720200 USB 3.0 controller> mem
> >> > > 0x11060000-0x11063fff
> >> > > > > at
> >> > > > > > >> > device 3.0 on pci0
> >> > > > > > >> > xhci0: 32 bytes context size, 32-bit DMA
> >> > > > > > >> > usbus0 on xhci0
> >> > > > > > >> > vgapci0: <VGA-compatible display> port 0x120-0x12f mem
> >> > > > > > >> > 0x10000000-0x10ffffff,0x11040000-0x1104ffff at device 4.0
> >> on
> >> > > pci0
> >> > > > > > >> > vgapci0: Boot video device
> >> > > > > > >> > virtio_pci1: <VirtIO PCI (legacy) Block adapter> port
> >> 0x80-0xff
> >> > > mem
> >> > > > > > >> > 0x11065000-0x11065fff,0x11054000-0x11057fff at device 5.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtblk0: <VirtIO Block Adapter> on virtio_pci1
> >> > > > > > >> > vtblk0: 5120MB (10485760 512 byte sectors)
> >> > > > > > >> > virtio_pci2: <VirtIO PCI (legacy) Block adapter> mem
> >> > > > > > >> > 0x11064000-0x11064fff,0x11050000-0x11053fff at device 6.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtblk1: <VirtIO Block Adapter> on virtio_pci2
> >> > > > > > >> > vtblk1: 51200MB (104857600 512 byte sectors)
> >> > > > > > >> > uart0: <PrimeCell UART (PL011)> mem 0x9000000-0x9000fff
> >> irq 34
> >> > > on
> >> > > > > > >> ofwbus0
> >> > > > > > >> > uart0: console (115200,n,8,1)
> >> > > > > > >> > cpulist0: <Open Firmware CPU Group> on ofwbus0
> >> > > > > > >> > cpu0: <Open Firmware CPU> on cpulist0
> >> > > > > > >> > Timecounters tick every 1.000 msec
> >> > > > > > >> > usbus0: 5.0Gbps Super Speed USB v3.0
> >> > > > > > >> > Trying to mount root from ufs:/dev/ufs/rootfs [rw]...
> >> > > > > > >> > ugen0.1: <(0x1033) XHCI root HUB> at usbus0
> >> > > > > > >> > uhub0 on usbus0
> >> > > > > > >> > uhub0: <(0x1033) XHCI root HUB, class 9/0, rev 3.00/1.00,
> >> addr
> >> > > 1> on
> >> > > > > > >> usbus0
> >> > > > > > >> > Warning: no time-of-day clock registered, system time will
> >> not
> >> > > be
> >> > > > > set
> >> > > > > > >> > accurately
> >> > > > > > >> > Dual Console: Serial Primary, Video Secondary
> >> > > > > > >> > /etc/rc: WARNING: hostid: unable to figure out a UUID from
> >> DMI
> >> > > data,
> >> > > > > > >> > generating a new one
> >> > > > > > >> > uhub0: 8 ports with 8 removable, self powered
> >> > > > > > >> > ugen0.2: <QEMU QEMU USB Keyboard> at usbus0
> >> > > > > > >> > Loading kernel...
> >> > > > > > >> > /boot/kernel/kernel text=0x1b4 text=0x719e9c text=0x19a610
> >> > > > > data=0xb1f60
> >> > > > > > >> > data=0x0+0x1e8000 0x4+0xa4160+0x4+0x116be3-
> >> > > > > > >> > Loading configured modules...
> >> > > > > > >> > /boot/kernel/umodem.ko text=0x1540 text=0xe90
> >> data=0x230+0x4
> >> > > > > > >> > 0x4+0xe70+0x4+0xa7c
> >> > > > > > >> > loading required module 'ucom'
> >> > > > > > >> > /boot/kernel/ucom.ko text=0x19f8 text=0x2d18
> >> data=0x494+0x838
> >> > > > > > >> > 0x4+0x1480+0x4+0xbcf
> >> > > > > > >> > can't find '/etc/hostid'
> >> > > > > > >> > can't find '/boot/entropy'

> >> > > > > > >> >
> >> > > > > > >> > Hit [Enter] to boot immediately, or any other key for
> >> command
> >> > > > > prompt.
> >> > > > > > >> > Booting [/boot/kernel/kernel]...
> >> > > > > > >> > Using DTB provided by EFI at 0x5feed000.
> >> > > > > > >> > Kernel entry at 0x56000200...
> >> > > > > > >> > Kernel args: (null)
> >> > > > > > >> > WARNING: Cannot find freebsd,dts-version property, cannot
> >> check
> >> > > DTB
> >> > > > > > >> > compliance
> >> > > > > > >> > ---<<BOOT>>---
> >> > > > > > >> > !!!WARNING!!! CPU(0) is vulnerable to speculative branch
> >> > > attacks.
> >> > > > > !!!
> >> > > > > > >> > We cannot enable required bit(s) in ACTRL register
> >> > > > > > >> > because it's locked by secure monitor and/or firmware.
> >> > > > > > >> > Copyright (c) 1992-2021 The FreeBSD Project.
> >> > > > > > >> > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991,
> >> 1992,
> >> > > 1993,
> >> > > > > 1994
> >> > > > > > >> >        The Regents of the University of California. All
> >> rights
> >> > > > > reserved.
> >> > > > > > >> > FreeBSD is a registered trademark of The FreeBSD
> >> Foundation.
> >> > > > > > >> > FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597
> >> GENERIC
> >> > > arm
> >> > > > > > >> > FreeBSD clang version 14.0.5 (
> >> > > > > https://github.com/llvm/llvm-project.git
> >> > > > > > >> > llvmorg-14.0.5-0-gc12386ae247c)
> >> > > > > > >> > VT: init without driver.
> >> > > > > > >> > CPU: ARM Cortex-A15 r0p4 (ECO: 0x00000000)
> >> > > > > > >> > CPU Features:
> >> > > > > > >> >  Multiprocessing, Thumb2, Security, Virtualization, Generic
> >> > > Timer,
> >> > > > > > >> VMSAv7,
> >> > > > > > >> >  PXN, LPAE, Coherent Walk
> >> > > > > > >> > Optional instructions:
> >> > > > > > >> >  SDIV/UDIV, UMULL, SMULL, SIMD(ext)
> >> > > > > > >> > LoUU:2 LoC:3 LoUIS:2
> >> > > > > > >> > Cache level 1:
> >> > > > > > >> > 32KB/64B 2-way data cache WB Read-Alloc Write-Alloc
> >> > > > > > >> > 32KB/64B 2-way instruction cache Read-Alloc
> >> > > > > > >> > Cache level 2:
> >> > > > > > >> > 1024KB/64B 16-way unified cache WB Read-Alloc Write-Alloc
> >> > > > > > >> > real memory  = 511139840 (487 MB)
> >> > > > > > >> > avail memory = 483815424 (461 MB)
> >> > > > > > >> > arc4random: WARNING: initial seeding bypassed the
> >> cryptographic
> >> > > > > random
> >> > > > > > >> > device because it was not yet seeded and the knob
> >> 'bypass_before
> >> > > > > > >> _seeding'
> >> > > > > > >> > was enabled.
> >> > > > > > >> > random: entropy device external interface
> >> > > > > > >> > kbd0 at kbdmux0
> >> > > > > > >> > ofwbus0: <Open Firmware Device Tree>
> >> > > > > > >> > simplebus0: <Flattened device tree simple bus> on ofwbus0
> >> > > > > > >> > clk_fixed0: <Fixed clock> on ofwbus0
> >> > > > > > >> > psci0: <ARM Power State Co-ordination Interface Driver> on
> >> > > ofwbus0
> >> > > > > > >> > gic0: <ARM Generic Interrupt Controller> mem
> >> > > > > > >> > 0x8000000-0x800ffff,0x8010000-0x801ffff on ofwbus0
> >> > > > > > >> > gic0: pn 0x2, arch 0x2, rev 0x0, implementer 0x43b irqs 288
> >> > > > > > >> > gicv2m0: <ARM Generic Interrupt Controller MSI/MSIX> mem
> >> > > > > > >> > 0x8020000-0x8020fff on gic0
> >> > > > > > >> > generic_timer0: <ARMv7 Generic Timer> irq 35,36,37,38 on
> >> ofwbus0
> >> > > > > > >> > Timecounter "ARM MPCore Timecounter" frequency 24000000 Hz
> >> > > quality
> >> > > > > 1000
> >> > > > > > >> > Event timer "ARM MPCore Eventtimer" frequency 24000000 Hz
> >> > > quality
> >> > > > > 1000
> >> > > > > > >> > pcib0: <Generic PCI host controller> mem
> >> 0x3f000000-0x3fffffff
> >> > > on
> >> > > > > > >> ofwbus0
> >> > > > > > >> > pci0: <PCI bus> on pcib0
> >> > > > > > >> > virtio_pci0: <VirtIO PCI (legacy) Network adapter> port
> >> > > 0x100-0x11f
> >> > > > > mem
> >> > > > > > >> > 0x11067000-0x11067fff,0x1105c000-0x1105ffff at device 1.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtnet0: <VirtIO Networking Adapter> on virtio_pci0
> >> > > > > > >> > vtnet0: Ethernet address: 52:54:00:12:34:55
> >> > > > > > >> > virtio_pci1: <VirtIO PCI (modern) GPU adapter> mem
> >> > > > > > >> > 0x11066000-0x11066fff,0x11058000-0x1105bfff at device 2.0
> >> on
> >> > > pci0
> >> > > > > > >> > virtio_pci1: cannot alloc resource for COMMON_CFG
> >> > > > > > >> > virtio_pci1: cannot map configs
> >> > > > > > >> > device_attach: virtio_pci1 attach returned 22
> >> > > > > > >> > xhci0: <NEC uPD720200 USB 3.0 controller> mem
> >> > > 0x11060000-0x11063fff
> >> > > > > at
> >> > > > > > >> > device 3.0 on pci0
> >> > > > > > >> > xhci0: 32 bytes context size, 32-bit DMA
> >> > > > > > >> > usbus0 on xhci0
> >> > > > > > >> > vgapci0: <VGA-compatible display> port 0x120-0x12f mem
> >> > > > > > >> > 0x10000000-0x10ffffff,0x11040000-0x1104ffff at device 4.0
> >> on
> >> > > pci0
> >> > > > > > >> > vgapci0: Boot video device
> >> > > > > > >> > virtio_pci1: <VirtIO PCI (legacy) Block adapter> port
> >> 0x80-0xff
> >> > > mem
> >> > > > > > >> > 0x11065000-0x11065fff,0x11054000-0x11057fff at device 5.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtblk0: <VirtIO Block Adapter> on virtio_pci1
> >> > > > > > >> > vtblk0: 5120MB (10485760 512 byte sectors)
> >> > > > > > >> > virtio_pci2: <VirtIO PCI (legacy) Block adapter> mem
> >> > > > > > >> > 0x11064000-0x11064fff,0x11050000-0x11053fff at device 6.0
> >> on
> >> > > pci0
> >> > > > > > >> > vtblk1: <VirtIO Block Adapter> on virtio_pci2
> >> > > > > > >> > vtblk1: 51200MB (104857600 512 byte sectors)
> >> > > > > > >> > uart0: <PrimeCell UART (PL011)> mem 0x9000000-0x9000fff
> >> irq 34
> >> > > on
> >> > > > > > >> ofwbus0
> >> > > > > > >> > uart0: console (115200,n,8,1)
> >> > > > > > >> > cpulist0: <Open Firmware CPU Group> on ofwbus0
> >> > > > > > >> > cpu0: <Open Firmware CPU> on cpulist0
> >> > > > > > >> > Timecounters tick every 1.000 msec
> >> > > > > > >> > usbus0: 5.0Gbps Super Speed USB v3.0
> >> > > > > > >> > Trying to mount root from ufs:/dev/ufs/rootfs [rw]...
> >> > > > > > >> > ugen0.1: <(0x1033) XHCI root HUB> at usbus0
> >> > > > > > >> > uhub0 on usbus0
> >> > > > > > >> > uhub0: <(0x1033) XHCI root HUB, class 9/0, rev 3.00/1.00,
> >> addr
> >> > > 1> on
> >> > > > > > >> usbus0
> >> > > > > > >> > Warning: no time-of-day clock registered, system time will
> >> not
> >> > > be
> >> > > > > set
> >> > > > > > >> > accurately
> >> > > > > > >> > Dual Console: Serial Primary, Video Secondary
> >> > > > > > >> > /etc/rc: WARNING: hostid: unable to figure out a UUID from
> >> DMI
> >> > > data,
> >> > > > > > >> > generating a new one
> >> > > > > > >> > uhub0: 8 ports with 8 removable, self powered
> >> > > > > > >> > ugen0.2: <QEMU QEMU USB Keyboard> at usbus0
> >> > > > > > >> > ukbd0 on uhub0
> >> > > > > > >> > ukbd0: <QEMU QEMU USB Keyboard, class 0/0, rev 2.00/0.00,
> >> addr
> >> > > 1> on
> >> > > > > > >> usbus0
> >> > > > > > >> > kbd1 at ukbd0
> >> > > > > > >> > ugen0.3: <QEMU QEMU USB Mouse> at usbus0
> >> > > > > > >> > ums0 on uhub0
> >> > > > > > >> > ums0: <QEMU QEMU USB Mouse, class 0/0, rev 2.00/0.00, addr
> >> 2> on
> >> > > > > usbus0
> >> > > > > > >> > ums0: 3 buttons and [XYZ] coordinates ID=0
> >> > > > > > >> > random: unblocking device.
> >> > > > > > >> > Setting hostuuid: 4e4c4eb8-b589-4658-b536-efa3c318ce22.
> >> > > > > > >> > Setting hostid: 0x7df9c464.
> >> > > > > > >> > Starting file system checks:
> >> > > > > > >> > /dev/ufs/rootfs: FILE SYSTEM CLEAN; SKIPPING CHECKS
> >> > > > > > >> > /dev/ufs/rootfs: clean, 752041 free (649 frags, 93924
> >> blocks,
> >> > > 0.1%
> >> > > > > > >> > fragmentation)
> >> > > > > > >> > Growing root partition to fill device
> >> > > > > > >> > vtbd0: hard error cmd=write fsbn 0
> >> > > > > > >> > gpart: Input/output error
> >> > > > > > >> > vtbd0: hard error cmd=write 104448-104463
> >> > > > > > >> > gpart: Input/output error
> >> > > > > > >> > growfs: requested size 4.9GB is equal to the current
> >> filesystem
> >> > > size
> >> > > > > > >> 4.9GB
> >> > > > > > >> > vtbd0: hard error cmd=write 144960-144967
> >> > > > > > >> > g_vfs_done():ufs/rootfs[WRITE(offset=20676608,
> >> > > length=4096)]error =
> >> > > > > 6
> >> > > > > > >> > UFS: forcibly unmounting /dev/ufs/rootfs from /
> >> > > > > > >> > pid 89 (mount), jid 0, uid 0: exited on signal 11
> >> > > > > > >> > pid 88 (sh), jid 0, uid 0: exited on signal 11
> >> > > > > > >> > pid 15 (sh), jid 0, uid 0: exited on signal 11

> >> > > > > > >> >
> >> > > > > > >> > the installation stops here,the error is : Guest disabled
> >> > > display.
> >> > > > > > >> >
> >> > > > > > >> > I think that this error should be fixed by asking help on
> >> the
> >> > > > > FreeBSD
> >> > > > > > >> forum
> >> > > > > > >> > because it is related to it.
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > > > > >> > On Mon, Aug 14, 2023 at 1:23 AM Ralph Ronnquist <
> >> rrq@???>
> >> > > wrote:
> >> > > > > > >> >
> >> > > > > > >> > > On Sun, Aug 13, 2023 at 08:22:20PM +0200, Mario Marietto
> >> via
> >> > > Dng
> >> > > > > > >> wrote:
> >> > > > > > >> > > > Hello,
> >> > > > > > >> > > >
> >> > > > > > >> > > > I have copied the following files :
> >> > > > > > >> > > >
> >> > > > > > >> > > > AAVMF32_CODE.fd
> >> > > > > > >> > > > bookworm_mini_armhf.iso
> >> > > > > > >> > > > FreeBSD.img
> >> > > > > > >> > > > AAVMF32_VARS.fd
> >> > > > > > >> > > > FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img
> >> > > > > > >> > > >
> >> > > > > > >> > > >
> >> > > > > > >> > > > inside the directory /home/marietto/Dati/Si and I've
> >> > > configured
> >> > > > > the
> >> > > > > > >> > > > permissions of every file and directory with :
> >> > > > > > >> > > >
> >> > > > > > >> > > > chown marietto:marietto
> >> > > > > > >> > > >
> >> > > > > > >> > > > and
> >> > > > > > >> > > >
> >> > > > > > >> > > > chmod -R 777
> >> > > > > > >> > > >
> >> > > > > > >> > > > and then I've logged out from the ssh server and I
> >> have re
> >> > > > > entered
> >> > > > > > >> with :
> >> > > > > > >> > > >
> >> > > > > > >> > > > ssh -Y marietto@192.168.1.6
> >> > > > > > >> > > >
> >> > > > > > >> > > > and I started the qemu script. Nothing,the error is
> >> still
> >> > > there.
> >> > > > > > >> > >
> >> > > > > > >> > > (And, I assume that you also did "cd
> >> /home/marietto/Dati/Si"
> >> > > when
> >> > > > > you
> >> > > > > > >> > > entered that host so that "/home/marietto/Dati/Si:" was
> >> the
> >> > > > > current
> >> > > > > > >> > > working directory for the command shell wherein you run
> >> the
> >> > > qemu
> >> > > > > > >> > > command)
> >> > > > > > >> > >
> >> > > > > > >> > > That error:
> >> > > > > > >> > > ----
> >> > > > > > >> > > ERROR : qemu-system-arm: device requires 67108864 bytes,
> >> block
> >> > > > > backend
> >> > > > > > >> > > provides 35745792 bytes
> >> > > > > > >> > > ----
> >> > > > > > >> > > most likely concerns the UEFI code or vars, which for me
> >> both
> >> > > are
> >> > > > > > >> > > 67108864 bytes in size. I got mine by installing the
> >> > > qemu-efi-arm
> >> > > > > > >> > > package; maybe you got yours from elsewhere?
> >> > > > > > >> > >
> >> > > > > > >> > > My suggestion is that you replace yours by installing
> >> > > > > qemu-efi-arm.
> >> > > > > > >> > > Possibty you will need to undo whatever that gave you
> >> those
> >> > > files
> >> > > > > > >> > > (i.e., /usr/share/AAVMF/AAVMF32_{CODE,VARS}.fd) first,
> >> and
> >> > > then
> >> > > > > > >> > > install qemu-efi-arm, plus copy them to the Dati/Si
> >> directory
> >> > > for
> >> > > > > > >> > > trying yet again.
> >> > > > > > >> > >
> >> > > > > > >> > > regards,
> >> > > > > > >> > >
> >> > > > > > >> > > Ralph.
> >> > > > > > >> > >
> >> > > > > > >> > > >
> >> > > > > > >> > > >
> >> > > > > > >> > > > On Sun, Aug 13, 2023 at 7:22 PM tempforever <
> >> > > > > dev1@???>
> >> > > > > > >> > > wrote:
> >> > > > > > >> > > >
> >> > > > > > >> > > > > Mario, please re-read this:
> >> > > > > > >> > > > >
> >> > > > > > >> > > > > Ralph Ronnquist wrote:
> >> > > > > > >> > > > > > ----------
> >> > > > > > >> > > > > > UEFICODE=AAVMF32_CODE.fd
> >> > > > > > >> > > > > > UEFIVARS=AAVMF32_VARS.fd
> >> > > > > > >> > > > > > CD=FreeBSD-13.2-RELEASE-arm-armv7-GENERICSD.img
> >> > > > > > >> > > > > > DISK=FreeBSD.img
> >> > > > > > >> > > > > >
> >> > > > > > >> > > > > > qemu-system-arm \
> >> > > > > > >> > > > > > -serial stdio \
> >> > > > > > >> > > > > > -m 512 -M virt -cpu cortex-a15 \
> >> > > > > > >> > > > > > -drive
> >> if=pflash,format=raw,unit=0,file=$UEFICODE \
> >> > > > > > >> > > > > > -drive
> >> if=pflash,format=raw,unit=1,file=$UEFIVARS \
> >> > > > > > >> > > > > > -cdrom $CD \
> >> > > > > > >> > > > > > -drive file=$DISK,format=raw \
> >> > > > > > >> > > > > > -device
> >> > > virtio-net,netdev=net0,mac="52:54:00:12:34:75" \
> >> > > > > > >> > > > > > -netdev type=user,id=net0 \
> >> > > > > > >> > > > > > -device virtio-gpu-pci \
> >> > > > > > >> > > > > > -device vmware-svga,id=video0,vgamem_mb=16
> >> > > > > > >> > > > > > ----------
> >> > > > > > >> > > > > >
> >> > > > > > >> > > > > > 1) For some reason qemu objected to using the
> >> system
> >> > > UEFI
> >> > > > > > >> emulation
> >> > > > > > >> > > > > > files but was happy when I copied them (to `pwd`).
> >> I
> >> > > also
> >> > > > > > >> reordered
> >> > > > > > >> > > > > > the pflash parameters (for clarity).
> >> > > > > > >> > > > > >
> >> > > > > > >> > > > > >
> >> > > > > > >> > > > > the "run" directory, mentioned in a later post, is
> >> the
> >> > > current
> >> > > > > > >> working
> >> > > > > > >> > > > > directory, one which the user has read/write access
> >> to.
> >> > > not
> >> > > > > > >> "/run"
> >> > > > > > >> > > > >
> >> > > > > > >> > > > > not sure it that will fix all the problems, but at
> >> least
> >> > > it
> >> > > > > > >> should fix
> >> > > > > > >> > > > > the UEFI part.
> >> > > > > > >> > > > >
> >> > > > > > >> > > > >
> >> > > > > > >> > > > > _______________________________________________
> >> > > > > > >> > > > > Dng mailing list
> >> > > > > > >> > > > > Dng@???
> >> > > > > > >> > > > >
> >> > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >> > > > > > >> > > > >
> >> > > > > > >> > > >
> >> > > > > > >> > > >
> >> > > > > > >> > > > --
> >> > > > > > >> > > > Mario.
> >> > > > > > >> > >
> >> > > > > > >> > > > _______________________________________________
> >> > > > > > >> > > > Dng mailing list
> >> > > > > > >> > > > Dng@???
> >> > > > > > >> > > >
> >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >> > > > > > >> > >
> >> > > > > > >> > > _______________________________________________
> >> > > > > > >> > > Dng mailing list
> >> > > > > > >> > > Dng@???
> >> > > > > > >> > >
> >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >> > > > > > >> > >
> >> > > > > > >> >
> >> > > > > > >> >
> >> > > > > > >> > --
> >> > > > > > >> > Mario.
> >> > > > > > >> _______________________________________________
> >> > > > > > >> Dng mailing list
> >> > > > > > >> Dng@???
> >> > > > > > >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >> > > > > > >>
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > --
> >> > > > > > > Mario.
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > --
> >> > > > > > Mario.
> >> > > > > _______________________________________________
> >> > > > > Dng mailing list
> >> > > > > Dng@???
> >> > > > > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >> > > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > Mario.
> >> > >
> >> >
> >> >
> >> > --
> >> > Mario.
> >> _______________________________________________
> >> Dng mailing list
> >> Dng@???
> >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> >>
> >
> >
> > --
> > Mario.
> >
>
>
> --
> Mario.
This message was posted to the following mailing lists:
dng
Mailing List Info | Nearby Messages		<-Re: [DNG] Which qemu version is shipped by default with devuan 3 ?Re: [DNG] I understand why a lot of people don't help or report issues.->

Donate to Dyne.org

dyne.org open discussions
administrated by dyne.org hackers		Lurker (version 2.3)