jammy-server-cloudimg-amd64.ova does not create cdrom device on vsphere
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
In Progress
|
Undecided
|
Simon Poirier | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Simon Poirier | ||
Jammy |
Fix Released
|
Undecided
|
Simon Poirier | ||
Kinetic |
Fix Released
|
Undecided
|
Simon Poirier |
Bug Description
[Impact]
* Ubuntu jammy OVA images will not have a CD-ROM drive by default when imported by vmware
[Test Plan]
* having the free vmware-player (or vsphere)
* file: import the ova
* open settings and check for the presence of the CD-ROM drive
[Where problems could occur]
* The change is limited only to the OVA template, so other image generation should not be affected
* This is a revert to a previous bus mapping, prior to adding the serial port. From this bug, getting the bus mapping wrong will have vmware to keep discarding that config.
* virtualbox doesn't appear to use that setting. There is a small risk that another hypervisor not mentioned here loses cdrom in the same way if it relies on the cdrom being only on a SCSI bus.
[Original description]
jammy-server-
VMware vsphere injects properties like user-data or ssh keys to the VM by means of an iso image mounted on the first CDROM device at boot.
jammy-server-
Prior versions of ubuntu server (such as focal-server-
Related branches
- Utkarsh Gupta: Approve
-
Diff: 28 lines (+8/-1)2 files modifieddebian/changelog (+7/-0)
live-build/ubuntu-cpc/hooks.d/base/ovf/ubuntu-ova-v1-vmdk.tmpl (+1/-1)
- Utkarsh Gupta: Approve
-
Diff: 28 lines (+8/-1)2 files modifieddebian/changelog (+7/-0)
live-build/ubuntu-cpc/hooks.d/base/ovf/ubuntu-ova-v1-vmdk.tmpl (+1/-1)
Changed in cloud-images: | |
assignee: | nobody → Simon Poirier (simpoir) |
status: | New → In Progress |
description: | updated |
Changed in livecd-rootfs (Ubuntu Kinetic): | |
status: | New → In Progress |
Changed in livecd-rootfs (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → Simon Poirier (simpoir) |
Changed in livecd-rootfs (Ubuntu Kinetic): | |
assignee: | nobody → Simon Poirier (simpoir) |
tags: |
added: verification-done verification-done-jammy removed: verification-needed verification-needed-jammy |
Thank you for reporting this issue. for comparison:
definition for jammy:
https:/ /git.launchpad. net/livecd- rootfs/ tree/live- build/ubuntu- cpc/hooks. d/base/ ovf/ubuntu- ova-v1- vmdk.tmpl
with the cdrom passthrough item:
<Item ovf:required= "false" >
<rasd: AddressOnParent >0</rasd: AddressOnParent >
<rasd: AutomaticAlloca tion>false< /rasd:Automatic Allocation>
<rasd: ElementName> CD-ROM 1</rasd: ElementName>
<rasd: InstanceID> 9</rasd: InstanceID>
<rasd: Parent> 3</rasd: Parent>
<rasd: ResourceSubType >vmware. cdrom.remotepas sthrough< /rasd:ResourceS ubType>
<rasd: ResourceType> 15</rasd: ResourceType> "false" vmw:key= "backing. exclusive" vmw:value="false"/>
<vmw:Config ovf:required=
</Item>
definition for focal:
https:/ /git.launchpad. net/livecd- rootfs/ tree/live- build/ubuntu- cpc/hooks. d/base/ ovf/ubuntu- ova-v1- vmdk.tmpl? h=ubuntu/ focal
and cdrom passthrough:
<Item ovf:required= "false" >
<rasd: AddressOnParent >0</rasd: AddressOnParent >
<rasd: AutomaticAlloca tion>false< /rasd:Automatic Allocation>
<rasd: ElementName> CD-ROM 1</rasd: ElementName>
<rasd: InstanceID> 8</rasd: InstanceID>
<rasd: Parent> 4</rasd: Parent>
<rasd: ResourceSubType >vmware. cdrom.remotepas sthrough< /rasd:ResourceS ubType>
<rasd: ResourceType> 15</rasd: ResourceType> "false" vmw:key= "backing. exclusive" vmw:value="false"/>
<vmw:Config ovf:required=
</Item>
I think the issue may be the rasd:Parent. It's set to 3 on Jammy, which lines up with the SCSI controller, not the IDE controller. We'll check that assumption and start working on it.