Menu
▾
▴
Re: [Astlinux-devel] Vultr Astlinux Build process
|
From: Lonnie A. <li...@lo...> - 2021-12-22 16:29:13
|
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: 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 > On Dec 21, 2021, at 11:39 PM, Michael Knill <mic...@ip... <mailto:mic...@ip...>> wrote: > > Nope certainly does not work using 1.3.10. No suitable disk found! > Works ok in 1.4.4 however. > > Regards > Michael Knill > > On 21/12/21, 10:55 am, "Michael Knill" <mic...@ip... <mailto:mic...@ip...>> wrote: > > Hmm sorry if I have caused you unnecessary hassle. I will test it out again and report back. > > Regards > Michael Knill > > On 21/12/21, 2:43 am, "Lonnie Abelbeck" <li...@lo... <mailto:li...@lo...>> wrote: > > Hi Michael, > > I created a few new test instances on Vultr using AstLinux 1.4.4 [1] > > Quick answer, this all worked as expected per the docs, I even created a couple Sydney AU location instances. > > Though a couple minor changes since the "Vultr KVM" docs [2] were created: > > 1) "Cloud Compute" is no longer the default, "High Frequency" (for $6 vs. $5/month) is now the default. > > 2) Sometimes when viewing the console with "Cloud Compute" I saw "ISO medium not found" or some such, but closing the console and viewing the console again the "AstLinux Installer" is shown and works as expected. Possibly waiting an additional 30 seconds is needed. > > 3) When using the new "High Frequency" instance, viewing the console always showed the "AstLinux Installer" without any hiccups. > > Otherwise, Vultr seemed to work very nicely. > > Lonnie > > [1] https://s3.amazonaws.com/mirror.astlinux-project/downloads/iso/astlinux-1.4.4-genx86_64-vm.iso <https://s3.amazonaws.com/mirror.astlinux-project/downloads/iso/astlinux-1.4.4-genx86_64-vm.iso> > > [2] https://doc.astlinux-project.org/userdoc:hosted_guest_vm_vultr <https://doc.astlinux-project.org/userdoc:hosted_guest_vm_vultr> > > > > >> On Dec 19, 2021, at 11:06 PM, Michael Knill <mic...@ip... <mailto:mic...@ip...>> wrote: >> >> Hi Devs >> >> Unfortunately the build page is now incorrect as they have changed things in Vultr. Using this process it cant find a disk. >> You need to allocate an OS rather than Custom ISO and then add the ISO afterwards and reboot. >> Would you like us to edit it? >> >> Regards >> >> Michael Knill >> Managing Director > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... <mailto:Ast...@li...> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel <https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... <mailto:Ast...@li...> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel <https://lists.sourceforge.net/lists/listinfo/astlinux-devel> > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... <mailto:Ast...@li...> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
