From: David K. <da...@ke...> - 2025-07-07 16:26:35
|
Lonnie, I do have a different machine h/w specified... I selected Q35 because it is considered a more modern environment. That may have something to do with it, I will test (with a sandbox this time!!!!) and let you know. >From Google's AI... *In QEMU, the Q35 machine type is generally preferred over i440fx for modern use cases, especially when dealing with PCIe devices and advanced features like GPU passthrough. While i440fx is an older, more compatible option for some legacy systems, Q35 offers better support for newer hardware and virtualization technologies. * Regards, David On Mon, Jul 7, 2025 at 9:51 AM Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > I spent some time testing with Proxmox, and it works as I remembered. > > I ran the AstLinux ISO installer under Legacy BIOS, performed a setup > under Legacy BIOS, and then switched to UEFI BIOS. All worked as > expected. Switched between Legacy and UEFI a couple times for good > measure, no issues. > > I'm using Proxmox Virtual Environment 8.1.11 > > Note: I always get a warning when booing via UEFI: > -- > WARN: no efidisk configured! Using temporary efivars disk. > TASK WARNINGS: 1 > -- > > Hardware: > > > Possibly you have a different "Machine" specified? That can affect > booting. > > Just for giggles, I also tested an AstLinux VM under "UTM" [1] on a M2 Mac > Mini, I can toggle between UEFI enabled and not enabled without issues. > > Lonnie > > [1] https://doc.astlinux-project.org/userdoc:guest_vm_utm > > > > > On Jul 6, 2025, at 8:09 PM, Lonnie Abelbeck <li...@lo...> > wrote: > > > > David, sorry to hear that. I know I have switched back and forth > between Legacy and UEFI BIOS in the past in Proxmox. > > > > The ISO installer must be done via Legacy and switch later to UEFI if > desired, which I have done. > > > > Very surprised to hear your results. > > > > Lonnie > > > > > >> On Jul 6, 2025, at 7:44 PM, David Kerr <da...@ke...> wrote: > >> > >> Lonnie, > >> I have been traveling for a couple of weeks so just got around to > trying this. I did a shutdown -h in astlinux, changed proxmox settings for > the VM to use UEFI, restarted the VM and bad things happened. First, > opening the console just displayed a message that Guest has not initialized > the display (yet) and it just stuck like that. Worse, I could not ssh > in... and it never responded to pings. So I shutdown the VM again from > proxmox, changed the bios back to the SeaBIOS, and rebooted. And it > failed... console reported that it could not find a bootable disk, it tried > to boot from the network. > >> > >> Fortunately I have proxmox doing a daily backup/snapshot of the VM and > I was able to restore that and get going again. > >> > >> I have a feeling that a fresh install with UEFI right from the start > may be required? > >> > >> David. > >> > >> > >> > >> On Fri, Jun 20, 2025 at 7:15 AM Lonnie Abelbeck < > li...@lo...> wrote: > >>> Is it safe to switch an existing installed VM to UEFI and just reboot? > >> > >> "poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then > Start the VM. > >> > >> I have an AstLinux VM with UEFI enabled mostly for testing. I almost > always use SSH when interacting. > >> > >> Also, I seem to recall Proxmox issues a warning about temporary efi > vars or some such ... you can ignore that. > >> > >> Lonnie > >> > >> > >> > >>> On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote: > >>> > >>> Thanks Lonnie, > >>> Looks like I was wrong on the color, I do get that. But I would like > to have a higher resolution. So, if I use UEFI bios then I should get > that? I've always installed Astlinux with the default SeaBIOS (on > Proxmox). Is it safe to switch an existing installed VM to UEFI and just > reboot? > >>> > >>> David > >>> > >>> <image.png> > >>> > >>> On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck < > li...@lo...> wrote: > >>> Hi David, > >>> > >>> The VNC console has been color whenever I use it. Not sure how that > could be B/W. > >>> > >>> Note that if you use UEFI the screen will be higher resolution, for > example [1]. > >>> > >>> Though it has always seemed to be a fixed window size, just a lower > resolution with Legacy BIOS. > >>> > >>> Lonnie > >>> > >>> [1] > >>> > >>> > >>> > >>> > >>>> On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote: > >>>> > >>>> Running Astlinux in a VM and using VNC (Proxmox) console, the text > display is a very confined 80x24 and black-and-white. Every other > text-based VM that I fire up, I can resize the VNC window and the number of > rows/columns expands, and text colors are shown. > >>>> > >>>> Is it possible to have Astlinux do the same? > >>>> > >>>> Thanks > >>>> David > >>>> _______________________________________________ > >>>> Astlinux-devel mailing list > >>>> Ast...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > >>> > >>> _______________________________________________ > >>> Astlinux-devel mailing list > >>> Ast...@li... > >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > >>> _______________________________________________ > >>> Astlinux-devel mailing list > >>> Ast...@li... > >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > >> > >> > >> > >> _______________________________________________ > >> Astlinux-devel mailing list > >> Ast...@li... > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > >> _______________________________________________ > >> Astlinux-devel mailing list > >> Ast...@li... > >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > > > > > _______________________________________________ > > Astlinux-devel mailing list > > Ast...@li... > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel > |