X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-pg0-f47.google.com (mail-pg0-f47.google.com [74.125.83.47]) by lists.alpinelinux.org (Postfix) with ESMTP id 50CD25C56AE for ; Fri, 1 Dec 2017 00:51:10 +0000 (GMT) Received: by mail-pg0-f47.google.com with SMTP id j4so3758894pgp.1 for ; Thu, 30 Nov 2017 16:51:10 -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=jgM3uVTUp0h5XmiVDLinJ0WUSXoyfewAZ3/QIzFSjMw=; b=g9rve/W7Hoba4o/vYtmaPPvi2cNJAm8nnqn5CBTusgjP4MTxYbhKGox4On7ML3UosD 8YNABCZnHZarWTbLjx8J3Y2607f8+XrvxoziiF1fvY03m7TtSFf7weFL5I/JzmmwaYgX Xzx6y5o5Exce2FnLaPn0DMR7vU2FkyKvpIuWSGExC80KXyxBV1bWihl2MGAEhwsbwwpN hoWADeQE4M4WyZVx2GfoEEBA4WpXbnK5avPzibmx9LOc53hpzuvi4ov3HC3j2+Slvft9 t9oOjxa7e2lezbEnXb1Op8y4mEVywVBhkvdy9Tq5zHGuQVuIHU6EMW0zOQKG75vyqCAb SYEQ== 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=jgM3uVTUp0h5XmiVDLinJ0WUSXoyfewAZ3/QIzFSjMw=; b=jg6uPQMSvZy9CugLH1pl121RnW9NRNd1iaEyCiu3qlLnKTqq3KIJYRZDoNL/JBuDDu xJxut6M4+Z7eqaLecXWm+5g9ztudRUcsquDw7A8CR0njNfETqoLDBzZF+t/SR3kX+2KD 8AcY/jcTvkT5gnXi/TtZTHdKsfbvNi0GWsBTtQmEML4CdXVjfqTE/k47HoabCTB13L54 xsvNL0u47fIWSjbaTC2vaq2HnY0Bsl2RynG5ip7TUBxu1x2NS+JKlZ4YnBlJkD5ZCYiP m1JAdlG8CrcCV5/SAiAw0pZdY5aNWX/iI60XxyQJhJnyOFWDuz6z4wl39iZsZv7mO6R6 B08A== X-Gm-Message-State: AJaThX7T2xELdalcBxDEJMr35aoXkpQ271mlUGWs/yEIbVR/0eWC7gnp FaWrVuwuwuf4wus/e8jh1vcWf8NXN+7kIIpobfo= X-Google-Smtp-Source: AGs4zMYw5VoJXUE3lX8R3rzuj4wB6BmSR5Km59MOHfc79PKgbePoLoXa+YYLZ4NTNhKvNfHpCYMKgNfJIMdEPRb2eDo= X-Received: by 10.98.150.26 with SMTP id c26mr8475876pfe.224.1512089469594; Thu, 30 Nov 2017 16:51:09 -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; Thu, 30 Nov 2017 16:50:49 -0800 (PST) In-Reply-To: <5B02BCE4-04A7-4389-A7F3-BD44477A9C6D@jirutka.cz> 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: Thu, 30 Nov 2017 19:50:49 -0500 Message-ID: Subject: Re: [alpine-devel] Alpine Linux 3.7.0 Release Candidate 1 on VirtualBox To: Jakub Jirutka Cc: Natanael Copa , Jack Schmidt , alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary="94eb2c0a4902b434cc055f3cc383" --94eb2c0a4902b434cc055f3cc383 Content-Type: text/plain; charset="UTF-8" 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 >> --- >> >> > > --94eb2c0a4902b434cc055f3cc383 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
HI Jakub,

I am going to answer what I know ( I am sure other= s 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&#= 39;t even boot. Standard seems to be fine as long as I don't install th= e virt kernel and try to boot with it.

From what I read EFI se= ems like the replacement for BIOS and should provide a number of benefits i= ncluding a better/bigger console (which I like quite a bit, kinda hate doin= g 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 <=3D> GP= T perspective it could go either way. Things might get interesting with big= ger external volumes, but not for something I am working/messing with right= now.

setup-disk does some interesting stuff in EFI mode:
<= /div>- 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 runnin= g 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
r= unning inside VirtualBox.

Thank you,

Gennady
<= /div>

On Thu, Nov = 30, 2017 at 9:52 AM, Jakub Jirutka <jakub@jirutka.cz> wrote:<= br>
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 <gena01@gmail.com> wrote:
Hi,

From a quick look looks lik= e:
CONFIG_EFI=3Dy
CONFIG_EFI_STUB=3Dy

are missing from t= he virthardened config.

Thank you,

On Wed, Nov 29, 2017 at 12:14 PM, N= atanael 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
---



--94eb2c0a4902b434cc055f3cc383-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---