Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When creating a image in Composer, Microsoft Hyper V is not listed as an output option.
Version-Release number of selected component (if applicable): RHEL 8 Beta, snapshot 3
How reproducible: every time
Steps to Reproduce:
Try to create image in Composer -- Microsoft Hyper V is not listed as option.
Additional info:
This request came from a customer.
This was a customer request as Composer in Cockpit lists Azure as an output format, but not Hyper V, and the documentation doesn't reference Hyper V as supported. If Hyper V uses the same format as Azure, can we update Composer in Cockpit to list both of them? Thanks!
Here is the kickstart for vhd's: https://github.com/weldr/lorax/blob/master/share/composer/vhd.ks
This one installs WALinuxAgent and it's dependencies. Is that desirable in a Hyper V environment, or should we need to make a separate kickstart without WALinuxAgent?
Do you have access to a hyper-v environment? I can try to get hold of one up if not and see what's needed there and if the Azure image even boots on a regular, non-azure Hyper-V environment.
Judging from the WALinuxAgent docs, it seems it's very Azure specific, so there is probably no use on it outside Azure.
https://github.com/Azure/WALinuxAgent
@anilsson, @brasimit, and @bcl:
1. .vhd can be used by both Hyper-V and Azure.
2. Just like WALA is a dependence of Azure, Hyper-V needs hyperv-daemons as its dependence.
3. hyperv-daemons groups hypervfcopyd, hypervkvpd, hypervvssd, hyperv-tools, and hyperv-daemons-license together, and they have same NVR.
4. If running .vhd on Hyper-V, it does not need WALA. Just like @anilsson mentioned, WALA is for Azure ONLY.
Xiaofeng
(In reply to Xiaofeng Wang from comment #7)
> @anilsson, @brasimit, and @bcl:
> 1. .vhd can be used by both Hyper-V and Azure.
> 2. Just like WALA is a dependence of Azure, Hyper-V needs hyperv-daemons as
> its dependence.
> 3. hyperv-daemons groups hypervfcopyd, hypervkvpd, hypervvssd,
> hyperv-tools, and hyperv-daemons-license together, and they have same NVR.
> 4. If running .vhd on Hyper-V, it does not need WALA. Just like @anilsson
> mentioned, WALA is for Azure ONLY.
>
> Xiaofeng
Thanks for the additional details!
Sounds like we can make a new template that includes @hyperv-daemons instead. Is .vhd the preferred disk type or would another be more appropriate?
Hyper-V supports .vhd and .vhdx disk types.
Before Hyper-V 2012 or Windows Server 2012, .vhd is the only disk type supported by Hyper-V.
The .vhdx becomes the default disk type since Hyper-V 2012 or Windows Server 2012, but keep .vhd as another choice.
I think .vhdx is the best choice for Hyper-V image.
1. Microsoft has marked .vhd as legacy format and .vhdx is the default format for Windows Server 2012, 2012R2, 2016 and 2019.
2. .vhdx supports some features which are not supported by .vhd, such as more storage capacity, file corruption protection,etc.
There're two things to note here:
1. Azure does not support .vhdx yet.
2. The Hyper-V images does not have WALA enabled because WALA will report some errors if it's not running on Azure.
Xiaofeng
https://github.com/weldr/lorax/pull/671
I was able to test the output with a Hyper-V manager provided by Xiaofeng. The VM boots and the hyper-V guest daemons are running.