X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-pf0-f177.google.com (mail-pf0-f177.google.com [209.85.192.177]) by lists.alpinelinux.org (Postfix) with ESMTP id 6B5F55C4D48 for ; Fri, 1 Dec 2017 15:10:25 +0000 (GMT) Received: by mail-pf0-f177.google.com with SMTP id m26so4753459pfj.11 for ; Fri, 01 Dec 2017 07:10:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L2p2FMdLYaGP6DWzpmfvknm2Jr66g0bQSlvTglLK710=; b=GE1flQcOZcdzaeDxeTpkV+mJWn63HSU+F1IuYPf65w5IYgMDC78fHZCokFJhoLdPeH 9XS21qEqYNvPV09UW9W7FdNuoWYZrk1ax3BJEhs7PsMGXFMDR56DFfItuYk2JykjeYKN Hwvg2N6ZSP5ouiXn/YeU7elnkKtbpMJIjuc7UIl/FVgU1i1wW9bJDufMEshBQ4p3GkcA DH6wDHedKIo8NXrn2Aozn1BQjb9C4LOXhIoXEBrRK9exv50kCMgsc1LjGUCvFb4p9LMy zpYEx2CdtbgWi5VJC2lbLiPlPOQwI+6IvAY10lAG8wE6m3LBsld6v2z4YnlmwufG9X3P 5wuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=L2p2FMdLYaGP6DWzpmfvknm2Jr66g0bQSlvTglLK710=; b=jU9Wv/+RFmPwTZtXdnXUFRpDKRbHilp9Nj86pc4L3f6joozEpw4D/WCS5iDTj5N53s L2PB6nckVJk1RWglpqxzyZD3LhcbNX1pc5iI9aGNBl5aBzgj+chpwHMxTUNitJtxS8wE j6yY0I7mlBtXHv9CHRilBWq5wYqwZFb3LNBS7A7CR7K6nkgCzneYuf7xlLzW44fdaOz6 1ru/Bc500PmpP65dniZX1iRe+pGRkkS8IyAkjvcw/BqV1a9l85q4RssfqeUbRTgfKYxv 3B5lXCguH0VsTOtxf3ID3JKWtYtMFUGYICo4xUmy3JF5nIi3Rdv8BN7saZgjIvhRC0HC WGbg== X-Gm-Message-State: AJaThX77861Au+qAZjCqbgclVfYMGCmsQiXWckpn14REi3R6vB93+757 KRvD6IJtopbTpI01wpOXzjBpHOHU7j2X2iks7nE3Wg== X-Google-Smtp-Source: AGs4zMaQOISlZTOxJ5B6nVm1AhEgTSJh0SZVp12TcXuTS7tJtynOrcTlCqFvzKtFvPu1CnPjqNlO1oh9YDdN6N+7qS0= X-Received: by 10.101.73.12 with SMTP id p12mr6230241pgs.37.1512141024654; Fri, 01 Dec 2017 07:10:24 -0800 (PST) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.100.155.98 with HTTP; Fri, 1 Dec 2017 07:10:04 -0800 (PST) In-Reply-To: References: <20171123224046.0d21352b@ncopa-desktop.copa.dup.pw> <5A19D088.6040806@adelielinux.org> <39316FB2-BAB3-4357-82FC-32FB65EF5AB8@mowsey.org> <20171129181404.4df7941b@ncopa-desktop.copa.dup.pw> <5B02BCE4-04A7-4389-A7F3-BD44477A9C6D@jirutka.cz> From: Gennady Feldman Date: Fri, 1 Dec 2017 10:10:04 -0500 Message-ID: Subject: Re: [alpine-devel] Alpine Linux 3.7.0 Release Candidate 1 on VirtualBox To: Jakub Jirutka Cc: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="089e082207a09ffb1f055f48c43b" --089e082207a09ffb1f055f48c43b Content-Type: text/plain; charset="UTF-8" Hi Jakub, Was thinking a bit more about virt + EFI.. Any reason you are against enabling it? It looks like various VM platforms have already added or are adding EFI support to replace "legacy BIOS" as part of the VM environment. Right now that kernel doesn't boot and from the looks of it it's only enabling 2 modules. P.S. Can somebody bump community/virtualbox-guest-additions/APKBUILD 5.1.26 => 5.1.30? Thank you, Gennady On Thu, Nov 30, 2017 at 7:50 PM, Gennady Feldman wrote: > HI Jakub, > > I am going to answer what I know ( I am sure others will have their own > reasons). I have Virtualbox 5.1.30 (there's also 5.2.x out) installed on > Windows 7. > Right now from what I can see it's NOT a requirement, but the option is > there. > > I did download and try to play a bit with the 3.7rc3 both virt and > standard. Virt doesn't even boot. Standard seems to be fine as long as I > don't install the virt kernel and try to boot with it. > > From what I read EFI seems like the replacement for BIOS and should > provide a number of benefits including a better/bigger console (which I > like quite a bit, kinda hate doing console installs > using legacy BIOS inside VirtualBox) and faster boot time among other > things. I might even convert my Alpine VMs to use it once virt kernel > supports it. > > I guess from MBR <=> GPT perspective it could go either way. Things might > get interesting with bigger external volumes, but not for something I am > working/messing with right now. > > setup-disk does some interesting stuff in EFI mode: > - boot has hard-coded 512 (which seems quite high?) > - creates a swap partition (2G for me). I would love to turn that off if I > am running inside VirtualBox or being able to choose. > > I also wanted to ask if it would make sense to have "setup-virtualbox" > script that would install virtualbox packages and tweak some things for VMs > running inside VirtualBox. > > Thank you, > > Gennady > > On Thu, Nov 30, 2017 at 9:52 AM, Jakub Jirutka wrote: > >> Wait, VirtualBox *requires* EFI now? If not, why to enable it in kernel >> for VMs? >> >> Jakub >> >> On 30. Nov 2017, at 15:50, Gennady Feldman wrote: >> >> Hi, >> >> From a quick look looks like: >> CONFIG_EFI=y >> CONFIG_EFI_STUB=y >> >> are missing from the virthardened config. >> >> Thank you, >> >> On Wed, Nov 29, 2017 at 12:14 PM, Natanael Copa >> wrote: >> >>> Hi, >>> >>> Thanks you very much for testing. >>> >>> I think the most critical issues are fixed. I have not bothered fix the >>> eject issue, since I think it mostly affects virtualbox only. >>> >>> I haven't looked at the alpine-virt + efi issue, yet. I suppose there >>> are some kernel modules that are needed? >>> >>> Can you please re-run the tests with the 3.7.0_rc3? >>> >>> Thanks! >>> >>> -nc >>> >>> On Sat, 25 Nov 2017 21:39:02 -0500 >>> Jack Schmidt wrote: >>> >>> > Here are my notes on Alpine 3.7.0 rc1 installations using VirtualBox >>> hosted on x86_64 Darwin. >>> > >>> > >>> > Summary: >>> > >>> > * Standard, Extended, Vanilla, Virtual on BIOS just work (minor issues) >>> > * Standard, Extended, Vanilla on EFI has one major issue (bad fsck) >>> > * Virtual is broken on EFI (no kernel support) >>> > >>> > In each case I tried to do a base install to an IDE disk, as "sys", >>> default options. I also tried booting the ISO as a run-from-ram system. >>> Virtual on EFI requires a serial console, but otherwise all ISOs >>> run-from-ram smoothly. >>> > >>> > The fsck issue needs to be fixed. The 4.9.63 vs 4.9.59 should be >>> fixed. The Virtual EFI probably should be fixed, but is easily >>> worked-around by end users. The minor issues would be nice to increase >>> adoption of bootable alpine, but aren't necessary. I assume docker >>> containers are just fine: I use edge all the time without trouble. >>> > >>> > >>> > Standard, Extended, Vanilla, Virtual legacy BIOS minor issues: >>> > >>> > * Install boot might be too quiet for too long >>> > >>> > The BIOS boot takes 5 to 20 seconds, so the "quiet" option in >>> boot/syslinux/syslinux.cfg might need to be accompanied by a "say" or a >>> "menu autoboot" type thing. Grub EFI boot is mostly better, but sometimes >>> takes a long time between messages. The installed version is a little slow, >>> but has a reasonable amount of messages to let you know it is progressing. >>> > >>> > >>> > Standard, Extended, Vanilla, Virtual both BIOS and EFI minor issues: >>> > >>> > * After setup-alpine is complete, eject cdrom >>> > * Install boot and installed root use different kernels, rescue is hard >>> > * (hardened/virthardened) Guest additions kernel version problem >>> > >>> > Install for BIOS works easily on Standard, Extended, Vanilla, Virtual. >>> Install for EFI works easily on Standard, Extended, Vanilla, but fails for >>> Virtual. >>> > >>> > After the install, setup-alpine asks to reboot, but doesn't "eject -s" >>> (-s required for me) the cd. That means alpine reboots under the readonly >>> cdrom with a tmpfs. This works fine, but is surprising if you are >>> installing software. >>> > >>> > After the eject, system comes up much more noisily / green, so >>> probably reassuring. >>> > >>> > However, it comes up under 4.9.59-0-*hardened or 4.9.65 vanilla, so >>> one can't use the ISO's 4.9.63 kernel to boot a rescue. If it isn't too >>> much trouble, for the final 3.7 release, it'd be good if the kernel matched >>> on the ISO's boot and the ISO's apk. >>> > >>> > Guest additions (mostly not needed by me) are hard to load, since they >>> are in /lib/modules/4.9.65-* but the kernel is actually 4.9.59-*. Once that >>> is fixed, all good. >>> > >>> > >>> > Standard, Extended, Vanilla EFI issue (vfat.fsck) >>> > >>> > * 1.5GB disk required >>> > * vfat.fsck >>> > >>> > Alpine is known for it's very small size. The ISOs are a nice size. I >>> have a VM that runs off a 10MB iso, and the Virtual ISO is good at under >>> 40MB. I was trying out ubuntu variations and had to choose my physical >>> network to handle the each-iso-is-a-gig downloads. Alpine is very easy to >>> try. However, the new EFI install creates a 500MB /boot/efi partition to >>> hold 500KB of boot data. It might be worthwhile to check the total size of >>> the disk, and not use so much on it for smaller (1 or 2 gig) drives. >>> > >>> > More importantly /boot/efi fails its fsck due to a syntax error: >>> > >>> > fsck.vfat: unrecognized option: C >>> > >>> > This is from /etc/init.d/fsck. Since the fsck service fails, most of >>> the rest of the boot is not really attempted. / is mounted read-only. >>> Network is down. >>> > >>> > Remounting / rw, removing the -C0 from fsck, and rebooting is OK. You >>> still get a scary error, but the system comes up fine. >>> > >>> > See also https://bugs.alpinelinux.org/issues/8090 for raspberry pi >>> breakage and suggested fix (seems reasonable to me: write a simple shell >>> script wrapper for fsck.vfat and fsck.fat that ignores ext2/3/4 arguments). >>> > >>> > I think this must be fixed before a release. >>> > >>> > >>> > Virtual EFI fail >>> > >>> > Virtual's virthardened kernel lacks EFI support (even in module form). >>> Also it is worse on VirtualBox EFI since it also lacks video drivers. The >>> serial console works, but is hard to use (telnet lacks tab-completion, GNU >>> screen requires socat, and only one terminal). Since /sys/firmware/efi is >>> not available, setup-disk does not realize it was an EFI boot and does >>> everything wrong. >>> > >>> > I suspect it would be a good idea to include EFI support for the >>> Virtual ISO / virthardened kernel too. The fix would make Alpine seem more >>> reliable and would cut down on the "why is the screen black?" questions. >>> However, to workaround it is easy to turn off EFI, and legacy BIOS is more >>> standard for virtual machines, I believe. >>> > >>> > >>> > >>> > --- >>> > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org >>> > Help: alpine-devel+help@lists.alpinelinux.org >>> > --- >>> > >>> >>> >>> >>> --- >>> Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org >>> Help: alpine-devel+help@lists.alpinelinux.org >>> --- >>> >>> >> >> > --089e082207a09ffb1f055f48c43b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jakub,

Was thinki= ng a bit more about virt + EFI.. Any reason you are against enabling it? It= looks like various VM platforms have already added or are adding EFI suppo= rt to replace "legacy BIOS" as part of the VM environment.
Right now that kernel doesn't boot and from the looks of it it&#= 39;s only enabling 2 modules.

P.S. Can somebody bump community= /virtualbox-guest-additions/APKBUILD 5.1.26 =3D> 5.1.30?

Th= ank you,

Gennady

On Thu, Nov 30, 2017 at 7:50 PM, Gennady Feldman <gen= a01@gmail.com> wrote:
HI = Jakub,

I am going to answer what I know ( I am sure others wil= l have their own reasons). I have Virtualbox 5.1.30 (there's also 5.2.x= out) installed on Windows 7.
Right now from what I can see it's NO= T a requirement, but the option is there.

I did download and = try to play a bit with the 3.7rc3 both virt and standard. Virt doesn't = even boot. Standard seems to be fine as long as I don't install the vir= t kernel and try to boot with it.

From what I read EFI seems l= ike the replacement for BIOS and should provide a number of benefits includ= ing a better/bigger console (which I like quite a bit, kinda hate doing con= sole installs
using legacy BIOS inside VirtualBox) and faster boot= time among other things. I might even convert my Alpine VMs to use it once= virt kernel supports it.

I guess from MBR <=3D> GPT per= spective it could go either way. Things might get interesting with bigger e= xternal volumes, but not for something I am working/messing with right now.=

setup-disk does some interesting stuff in EFI mode:
= - boot has hard-coded 512 (which seems quite high?)
- creates a sw= ap partition (2G for me). I would love to turn that off if I am running ins= ide VirtualBox or being able to choose.

I also wanted to ask i= f it would make sense to have "setup-virtualbox" script that woul= d install virtualbox packages and tweak some things for VMs
runnin= g inside VirtualBox.

Thank you,

Gennady
=

On Thu, Nov 30, 2017 at 9:52 AM, Jakub Jirutka <jaku= b@jirutka.cz> wrote:
Wait, VirtualBox *requires* EFI now? If not, = why to enable it in kernel for VMs?

Jakub
<= div>

On 30. Nov 2017, at 15:50, Gennady Feldman <gena01@gmail.com> wrote:
Hi,

Fr= om a quick look looks like:
CONFIG_EFI=3Dy
CONFIG_EFI_STUB=3Dy
are missing from the virthardened config.

Thank you,

On Wed, No= v 29, 2017 at 12:14 PM, Natanael Copa <ncopa@alpinelinux.org> wrote:
Hi,

Thanks you very much for testing.

I think the most critical issues are fixed. I have not bothered fix the
eject issue, since I think it mostly affects virtualbox only.

I haven't looked at the alpine-virt + efi issue, yet. I suppose there are some kernel modules that are needed?

Can you please re-run the tests with the 3.7.0_rc3?

Thanks!

-nc

On Sat, 25 Nov 2017 21:39:02 -0500
Jack Schmidt <alp= ine@mowsey.org> wrote:

> Here are my notes on Alpine 3.7.0 rc1 installations using VirtualBox h= osted on x86_64 Darwin.
>
>
> Summary:
>
> * Standard, Extended, Vanilla, Virtual on BIOS just work (minor issues= )
> * Standard, Extended, Vanilla on EFI has one major issue (bad fsck) > * Virtual is broken on EFI (no kernel support)
>
> In each case I tried to do a base install to an IDE disk, as "sys= ", default options. I also tried booting the ISO as a run-from-ram sys= tem. Virtual on EFI requires a serial console, but otherwise all ISOs run-f= rom-ram smoothly.
>
> The fsck issue needs to be fixed. The 4.9.63 vs 4.9.59 should be fixed= . The Virtual EFI probably should be fixed, but is easily worked-around by = end users. The minor issues would be nice to increase adoption of bootable = alpine, but aren't necessary. I assume docker containers are just fine:= I use edge all the time without trouble.
>
>
> Standard, Extended, Vanilla, Virtual legacy BIOS minor issues:
>
> * Install boot might be too quiet for too long
>
> The BIOS boot takes 5 to 20 seconds, so the "quiet" option i= n boot/syslinux/syslinux.cfg might need to be accompanied by a "say&qu= ot; or a "menu autoboot" type thing. Grub EFI boot is mostly bett= er, but sometimes takes a long time between messages. The installed version= is a little slow, but has a reasonable amount of messages to let you know = it is progressing.
>
>
> Standard, Extended, Vanilla, Virtual both BIOS and EFI minor issues: >
> * After setup-alpine is complete, eject cdrom
> * Install boot and installed root use different kernels, rescue is har= d
> * (hardened/virthardened) Guest additions kernel version problem
>
> Install for BIOS works easily on Standard, Extended, Vanilla, Virtual.= Install for EFI works easily on Standard, Extended, Vanilla, but fails for= Virtual.
>
> After the install, setup-alpine asks to reboot, but doesn't "= eject -s" (-s required for me) the cd. That means alpine reboots under= the readonly cdrom with a tmpfs. This works fine, but is surprising if you= are installing software.
>
> After the eject, system comes up much more noisily / green, so probabl= y reassuring.
>
> However, it comes up under 4.9.59-0-*hardened or 4.9.65 vanilla, so on= e can't use the ISO's 4.9.63 kernel to boot a rescue. If it isn'= ;t too much trouble, for the final 3.7 release, it'd be good if the ker= nel matched on the ISO's boot and the ISO's apk.
>
> Guest additions (mostly not needed by me) are hard to load, since they= are in /lib/modules/4.9.65-* but the kernel is actually 4.9.59-*. Once tha= t is fixed, all good.
>
>
> Standard, Extended, Vanilla EFI issue (vfat.fsck)
>
> * 1.5GB disk required
> * vfat.fsck
>
> Alpine is known for it's very small size. The ISOs are a nice size= . I have a VM that runs off a 10MB iso, and the Virtual ISO is good at unde= r 40MB. I was trying out ubuntu variations and had to choose my physical ne= twork to handle the each-iso-is-a-gig downloads. Alpine is very easy to try= . However, the new EFI install creates a 500MB /boot/efi partition to hold = 500KB of boot data. It might be worthwhile to check the total size of the d= isk, and not use so much on it for smaller (1 or 2 gig) drives.
>
> More importantly /boot/efi fails its fsck due to a syntax error:
>
> fsck.vfat: unrecognized option: C
>
> This is from /etc/init.d/fsck. Since the fsck service fails, most of t= he rest of the boot is not really attempted. / is mounted read-only. Networ= k is down.
>
> Remounting / rw, removing the -C0 from fsck, and rebooting is OK. You = still get a scary error, but the system comes up fine.
>
> See also https://bugs.alpinelinux.org/issues/8090<= /a> for raspberry pi breakage and suggested fix (seems reasonable to me: wr= ite a simple shell script wrapper for fsck.vfat and fsck.fat that ignores e= xt2/3/4 arguments).
>
> I think this must be fixed before a release.
>
>
> Virtual EFI fail
>
> Virtual's virthardened kernel lacks EFI support (even in module fo= rm). Also it is worse on VirtualBox EFI since it also lacks video drivers. = The serial console works, but is hard to use (telnet lacks tab-completion, = GNU screen requires socat, and only one terminal). Since /sys/firmware/efi = is not available, setup-disk does not realize it was an EFI boot and does e= verything wrong.
>
> I suspect it would be a good idea to include EFI support for the Virtu= al ISO / virthardened kernel too. The fix would make Alpine seem more relia= ble and would cut down on the "why is the screen black?" question= s. However, to workaround it is easy to turn off EFI, and legacy BIOS is mo= re standard for virtual machines, I believe.
>
>
>
> ---
> Unsubscribe:=C2=A0 alpine-devel+unsubscribe@lists.alpi= nelinux.org
> Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alpine-devel+help@lists.alp= inelinux.org
> ---
>



---
Unsubscribe:=C2=A0 alpine-devel+unsubscribe@lists.alpinelin= ux.org
Help:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0alpine-devel+help@lists.alpinelinux.org
---




--089e082207a09ffb1f055f48c43b-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---