Date: Sun, 1 Jan 2017 09:18:31 -0500 From: Vincent Olivier <vincent@up4.com> To: freebsd-virtualization@freebsd.org Subject: Re: Arch Linux UEFI Bhyve Setup Message-ID: <680F62F7-9FD7-4FB3-A60A-DED3C784BE7F@up4.com> In-Reply-To: <E37D5989-6675-4EF9-937C-54E29766DAC3@up4.com> References: <E37D5989-6675-4EF9-937C-54E29766DAC3@up4.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Happy 2017 all, I guess my resolution for 2017 is more clarity. So what I mean to know with this experiment is simply this: can UEFI be = used with a serial console (i.e.: without a graphic console), if so, is = it preferable over GRUB for Linux distros that support UEFI? Until I am positive about using UEFI over serial console, I will stick = to GRUB but if someone coule elaborate on this, I would appreciate it = greatly! Thanks, Vincent > On Dec 31, 2016, at 9:26 AM, Vincent Olivier <vincent@up4.com> wrote: >=20 > Hi, >=20 > A new thread for this same target setup: = https://twitter.com/MUP4/status/814595352112283649 >=20 > Please note that the tap interface naming doesn=E2=80=99t follow the = nomenclature in the diagram as I am just testing isolated aspect of the = setup for now. >=20 > The =C2=AB Cinq =C2=BB FreeBSD 11 machine already the ALTNET non-UEFI = (grub-bhyve) machine running Arch Linux. I wanted to try UEFI with the = same Arch Linux distro but it doesn=E2=80=99t seem to work. >=20 > Here is the grub-bhyve command sequence that I used for the Arch Linux = installer on the the ALTNET virtual machine: >=20 > zfs create -V4G -o volmode=3Ddev bhyve/altnet >=20 > grub-bhyve -m /bhyve/altnet/setup/device.map -r cd0 -M 512M altnet < = /bhyve/altnet/setup/grub.cfg >=20 > bhyve -A -H -P -s 0:0,hostbridge -s 1:0,lpc -s 2:0,virtio-net,tap0 = -s3:0,virtio-blk,/dev/zvol/bhyve/altnet -s = 4:0,ahci-cd,/bhyve/archlinux-2016.12.01-dual.iso -l com1,stdio -c 1 -m = 512M altnet >=20 > Here is its grub.cfg file: >=20 > linux (cd0)/arch/boot/x86_64/vmlinuz archisobasedir=3Darch = archisolabel=3DARCH_201612 ro > initrd (cd0)/arch/boot/x86_64/archiso.img > boot >=20 > Here is its device.map file: >=20 > (cd0) /bhyve/archlinux-2016.12.01-dual.iso > (hd0) /dev/zvol/bhyve/altnet >=20 > Here is my adaptation of the above for the UNIFI UEFI virtual machine, = just for the Arch Linux installer: >=20 > zfs create -V2G -o volmode=3Ddev bhyve/unifi >=20 > bhyve -c 1 -m 512M -A -H -P \ > -s 0:0,hostbridge \ > -s 1:0,lpc \ > -s 2:0,virtio-net,tap1 \ > -s 3:0,virtio-blk,/dev/zvol/bhyve/unifi \ > -s 4:0,ahci-cd,/bhyve/archlinux-2016.12.01-dual.iso \ > -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \ > -l com1,stdio \ > unifi >=20 > But when I run this, I get this: >=20 > Arch Linux archiso x86_64 UEFI CD > UEFI Shell x86_64 v1 > UEFI Shell x86_64 v2 > EFI Default Loader > Reboot Into Firmware Interface > Boot in 1 sec. > rdmsr to register 0x34 on vcpu 0 > Unhandled ps2 mouse command 0xe1 > Unhandled ps2 mouse command 0x0a > Unhandled ps2 mouse command 0x01 > Unhandled ps2 mouse command 0x41 >=20 > And then it stalls. I waited max 2 minutes and then I did a "bhyvectl = --destroy --vm=3Dunifi=E2=80=9D in another session. I tried different = bhyve flags (-w, etc.) to no avail. >=20 > Is there hope for me? >=20 > Happy new year! >=20 > Vincent
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?680F62F7-9FD7-4FB3-A60A-DED3C784BE7F>