[CentOS-devel] Vagrant images for Hyper-V

[Laurentiu Pancescu]

On 02/05/17 21:00, Patrick Lang wrote:
> Once the VM boots, it still doesn’t get an IP. Ifconfig -a shows the right MAC address, but grepping dmesg for eth0 finds “udev: renamed network interface eth0 to eth1”. This is some time after hv_netvsc is loaded and has detected the right MAC.

Perhaps we should seal the Vagrant boxes. [1]  I started a build, I'll 
send you the links off-list.

[1] 
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/virtual_machine_management_guide/chap-templates#sect-Sealing_Virtual_Machines_in_Preparation_for_Deployment_as_Templates

> Can you point me to the scripts used to build the boxes? I'd like to get an idea of what’s there so I can provide PRs or feedback as the Hyper-V provider improves.

We're using Image Factory to build the boxes.  It performs a single 
netinst using KVM, and the resulting disk image is converted from the 
qemu format to different formats like VMDK, VHD, etc. (this only affects 
the image format, the files remain untouched as they were when the 
installation ended - the box should be able to boot correctly). 
Metadata is then generated for each virtualization type, and everything 
packed together in Vagrant boxes for each provider we support.  For 
Hyper-V, probably HyperVOVFDescriptor.py is the most interesting part:

https://github.com/redhat-imaging/imagefactory/tree/master/imagefactory_plugins/ovfcommon

Best regards,
Laurențiu