Date: Tue, 3 Dec 2019 17:55:30 -0700 From: Warner Losh <imp@bsdimp.com> To: KIRIYAMA Kazuhiko <kiri@truefc.org> Cc: freebsd-arm@freebsd.org Subject: Re: Can't boot arm64 image by qemu-system-aarch64 Message-ID: <CANCZdfrnEd3Y7r3LzqqUP7f2PjMgbeNpwpgek_FDO_X1c_p5mA@mail.gmail.com> In-Reply-To: <201912032300.xB3N0FGC061069@kx.truefc.org> References: <201912032300.xB3N0FGC061069@kx.truefc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 3, 2019, 4:00 PM KIRIYAMA Kazuhiko <kiri@truefc.org> wrote: > Hi, all > > # I've posted freebsd-virtualization,but any responces. > # Sorry for same posting. > > I've installed successfully by qemu-system-aarch64 below: > > root@vm:/vm/test # truncate -s 16g test.img > root@vm:/vm/test # qemu-system-aarch64 -machine virt -m 4096M -cpu > cortex-a57 -name test -bios QEMU_EFI.fd -nographic -hda test.img -hdc > FreeBSD-13.0-CURRENT-arm64-aarch64-20191127-r355121-memstick.img > > and rebooted successfully and login with root: > > root@test:~ # uname -a > FreeBSD test.tfc 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r355121: Wed Nov 27 > 03:49:21 UTC 2019 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC > arm64 > root@test:~ # df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/vtbd0p2 14G 1.3G 12G 10% / > devfs 1.0K 1.0K 0B 100% /dev > root@test:~ # ifconfig > vtnet0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > options=80028<VLAN_MTU,JUMBO_MTU,LINKSTATE> > ether 52:54:00:12:34:56 > inet 192.168.1.196 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet 10Gbase-T <full-duplex> > status: active > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > 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> > root@test:~ # > > So, I shutdowned and run by qemu-system-aarch64: > > root@vm:/vm/test # qemu-system-aarch64 -machine virt -m 4096M -cpu > cortex-a57 -name test -bios QEMU_EFI.fd -nographic -drive > if=none,format=raw,file=test.img,id=hd0 -device virtio-blk-device,drive=hd0 > -device virtio-net-device,netdev=net0 -netdev tap,id=net0,ifname=tap2 > > But failed to boot: > > BdsDxe: failed to load Boot0001 "UEFI Misc Device" from > VenHw(93E34C7E-B50E-11DF-9223-2443DFD72085,00): Not Found > BdsDxe: failed to load Boot0002 "UEFI Misc Device 2" from > VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000): Not Found > > >>Start PXE over IPv4. > > > where, tap2 is ready to use: > > root@vm:/vm/test # ifconfig tap2 > tap2: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 > description: vmnet-test-0-local > options=80000<LINKSTATE> > ether 58:9c:fc:10:ec:02 > groups: tap qemu-port > media: Ethernet autoselect > status: no carrier > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > root@vm:/vm/test # > > What's wrong ? > Where did the efi firmware come from? Warner > Best regards. > --- > Kiriyama Kazuhiko <kiri@truefc.org> > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrnEd3Y7r3LzqqUP7f2PjMgbeNpwpgek_FDO_X1c_p5mA>