View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000589 | AlmaLinux-9 | -OTHER | public | 2025-12-03 06:31 | 2025-12-03 06:31 |
| Reporter | harish | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000589: Does AlmaLinux 9.6 officially support Azure Gen2 (UEFI) VMs, vTPM / Trusted Launch and Gen2 VHD preparation? | ||||
| Description | Hi all — quick technical questions and a request for guidance. Does AlmaLinux 9.6 officially support Azure Generation 2 (UEFI) VMs (including booting and normal operation)? Is vTPM exposure / Trusted Launch (vTPM + Secure Boot) supported for AlmaLinux 9.6 on Azure? If so, any known caveats? Is the official AlmaLinux 9.6 Marketplace image Gen1 only, or are Gen2 Marketplace images available? If uploading our own Gen2-compatible VHD, we hit an Azure error about an invalid VHD footer (cookie value / 'conectix'). Can someone confirm the correct VHD preparation/conversion steps for Gen2 Linux images that are accepted by Azure (fixed VHD, page-blob, footer cookie, UEFI, etc.)? Any official docs or known workarounds would be appreciated. Context / what we tried: We converted a qcow2 image to .vhd and uploaded, but Azure rejected it with an invalid VHD footer / cookie message. We want the recommended conversion steps/commands for a Gen2 (UEFI) Linux VHD that will upload and create a Gen2 VM (and be eligible for Trusted Launch). Thanks — any links to AlmaLinux or Microsoft docs, Marketplace guidance, or step-by-step commands would be great. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-12-03 06:31 | harish | New Issue |
