-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] - VMware OVA/OVF #289
Comments
We do plan on providing VM images for on-premises use, but I don't have an ETA to offer at this time. Please stay tuned. |
I think this is a duplicates #102 |
Are there any known caveats to exporting a vanilla AL2023 instance to OVA using the VM import/export function? |
We do set some things up by default in AMIs to limit what kernel modules are in the initramfs (via the dracut-config-ec2 package), so that may be a limiting factor in some non-EC2 environments. IIRC the cloud-init config skips the early phase where it may load things from seed.iso so that would need to be changed too. Otherwise, things should mostly work... (albeit a situation which we are not currently testing) |
An VMware esxi image would be highly appreciated. Is there any ETA? |
Ok AWS. |
This is still under evaluation on our side |
And this is still needed on many peoples side to be (at all / a lot better) able to develop software against AL2023. |
Good news everyone! We have just released the first KVM and VMware images of Amazon Linux 2023. The documentation is up at https://docs.aws.amazon.com/linux/al2023/ug/outside-ec2.html The documentation covers supported device types and related things. This version of the images have a few extra development packages installed by default, and we'll make the minor change in an upcoming revision of the images (i.e. AL2023.3) to more closely mirror the package content of the standard AMIs. At that point in time we'll update the docs to show the full package list of the KVM and VMware images (like is present for the AMIs and container image types). In the meantime, we welcome feedback on these images and documentation on how to use them! |
FYI, https://cdn.amazonlinux.com/al2023/os-images/latest/ works now. |
EDIT: My original workaround is not needed. Thank you for providing this image. |
The minimal version for the VMWare images is set to what it is as it's the oldest revision to support UEFI Secure Boot. |
Secure Boot has been an option since hardware version 13 vmware.com. Wouldn't 13 be the oldest revision? Also, Amazon Linux 2023 doesn't currently support UEFI docs.aws. |
Thank you very very much. This is what we need! That makes developing for AL2023 a lot lot easier. But I have a problem. I have deployed AL2023 on VMWare esxi 6.7. And maybe I messed up, my seed.iso somehow. So I tried to login via VMWare console. I can't, too. But for a different reason. I cannot enter something via keyboard. The cursor blinks, but nothing appears on the console. I also cannot switch terminal using function key buttons. Does someone know what is wrong here with the console? Thanks for your help. |
Not very helpful but i can tell you my cloud-init (user-data and meta-data) files are working as expected. Here are relevant lines in my cloud-init chpasswd:
Expire: true #force reset
list: ["rich:PasswdToReset"]
groups: [docker]
users:
- groups: [wheel, sudo, docker]
lock_passwd: false
name: rich
shell: /bin/bash
ssh-authorized-keys: [ssh-rsa ...]
sudo: ALL=(ALL) NOPASSWD:ALL |
@Rosch I had the same issue where my key was not accepted. I use Proxmox though with KVM. I changed the default CD drive from IDE to SATA. After which the |
Thanks @daniejstriata adding a SATA controller and then using it for the CD-ROM got things working for me on ESXi 8.0u2 And then in the process of writing up a bug report I've now seen it working with an IDE controller :/ It would be handy if the OVA had a suitable CD-ROM (and controller) [and maybe ditch the floppy too]. |
That's strange. I've not been able to get the |
The AL2023 OVA should have minimum HW version 13 for that reason. It also comes with empty SB keys provisionned so that if you actually enable UEFI, you will be in Setup Mode and will be able to run UEFI works, it's not "supported" yet mostly because our testing automation doesn't yet qualfies it and because the current images don't have an EFI framebuffer so you don't get a console unless you use serial. This will be fixed in an upcoming release and we might even switch the OVA default to UEFI at that point. As far as Secure Boot, VMware is a bit weird, so if you do what I described above, you will have the keys provisioned, but you will still need to go enable secure boot in the UI (or using the API), the presence of a valid PK doesnt seem to be sufficient for VMware to enable SB (unlike for example qemu). We are looking at providing OVAs pre-provisioned with our keys in the future (no ETA) |
Thanks, we'll look into this |
What you describe above is a modification of the AL2 images, not the AL2023 ... a whole different topic. This issue is about AL2023 images. While we qualified it with vSphere 8.0 (that's what we have) it should work with 7. Hardware version 13 which is what we require for AL2023 is I think ESXi 6.5 and later (from memory). |
Right topic, wrong files. Thanks for the feedback |
I'm thinking we could just take out both IDE and SATA and just attach the CD-ROM to the SCSI bus ... |
On second thoughts .... I would expect ESXi users to use the VMware |
After a bit more experimentations with VMware Workstation (I haven't tried with vSphere yet), it's messy... if I put a CDROM drive in the OVA it really expects the ISO image to be in there too, at least in the Workstation case. If you take that out, it doesn't know what "backend" to use. The drive is there but it defaults to trying to use a physical device. I'm going to take out the floopy, but I am less an less convinced that adding the cdrom by default is the right approach |
Thanks @ozbenh - I'd never heard of the For anybody else following along and wondering how to use it that maybe doesn't have the Firstly I got the base64 values for my meta-data and user-data with I'm pleased to report that the VM fired up and was accessible with my SSH key without any .iso wrangling :) There's no similar config GUI (that I can find) in Workstation, so after importing the OVA I simply added the extra lines to the .vmx file: With Workstation I also hit snags with the bridged networking getting weird IPs because I hadn't restricted it to just using the ethernet adaptor. Thankfully this guide got me straightened out so that I was getting proper LAN IPs to SSH into. |
Thanks everyone for the info on this thread. I tried various variations but i can't make it work, no user can log into my al2023 vm. For the record i used Any help or suggestion is welcome |
Will Amazon provide OVA or OVF images for support outside of AWS?
The text was updated successfully, but these errors were encountered: