Re: [Astlinux-devel] Vultr Astlinux Build process

[Michael K. <li...@mk...>]

I made a new note relecting this at the top of the Vultr Wiki page.

https://doc.astlinux.org/userdoc:hosted_guest_vm_vultr

> Am 22.12.2021 um 20:42 schrieb Michael Knill <mic...@ip...>:
> 
> Great thanks Lonnie. That explains it.
>  
> Regards
> Michael Knill
>  
> From: Lonnie Abelbeck <li...@lo...>
> Reply to: AstLinux Developers Mailing List <ast...@li...>
> Date: Thursday, 23 December 2021 at 3:29 am
> To: AstLinux Developers Mailing List <ast...@li...>
> Subject: Re: [Astlinux-devel] Vultr Astlinux Build process
>  
> Hi Michael,
>  
> Ahhh, OK I now understand ...
>  
> Long story short, deploying a fresh new Vultr instance now requires a Linux kernel 4.x or later Custom ISO, the virtio_blk driver is no longer recognized with a Linux 3.16.x kernel using Vultr's latest VM.
>  
> So, testing with AstLinux 1.3.10 the ISO installer appears but when trying to install a "No suitable disk found." message is displayed.  This is because the /dev/vda virtio_blk mount is not available.
>  
> Bottom line, a Linux 3.16.x kernel is no longer compatible with a fresh new Vultr instance.  Which corresponds to AstLinux 1.3.10 and earlier. In other words if a person created a fresh new Vultr instance using AstLinux 1.4.4 and then did a "upgrade-run-image upgrade ..." to an AstLinux 1.3.10 image, that image will not boot.
>  
> Next you might ask, if a old Vultr instance that was created with a Linux 3.16.x kernel will it still work ... I tried and the answer is yes:
>  
> <Screen Shot 2021-12-22 at 9.59.39 AM.png>
>  
> So my personal older test Vultr instance VM will still work with an AstLinux 1.3.4 or later run image.
>  
> Not sure if this is bug on Vultr's part, but it is highly recommended to use AstLinux 1.4.4 with a fresh new Vultr instance anyway.
>  
> Lonnie

Michael

http://www.mksolutions.info