[
https://issues.apache.org/jira/browse/VCL-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15819184#comment-15819184
]
ASF subversion and git services commented on VCL-1008:
------------------------------------------------------
Commit 1778352 from [email protected] in branch 'vcl/trunk'
[ https://svn.apache.org/r1778352 ]
VCL-1008
Added code and uncommented existing code to libvirt.pm::capture to save a .xml
file in the image library and repository locations when an image is captured.
Added libvirt.pm::get_master_xml_info which reads the .xml file and convert it
to a hash reference.
Updated libvirt.pm::generate_domain_xml to attempt to retrieve the disk and
network interface types from the master XML file for an image revision.
Updated libvirt.pm::get_master_image_file_path to prevent it from ever
returning the path to the .xml file saved for an image.
> Extend libvirt/KVM modules to use device settings from captured VM
> ------------------------------------------------------------------
>
> Key: VCL-1008
> URL: https://issues.apache.org/jira/browse/VCL-1008
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Fix For: 2.5
>
>
> The {{libvirt.pm}} and {{KVM.pm}} provisioning modules are hard-coded to
> configure VMs with an IDE disk and the default rtl8139 network interface. If
> an image is captured from a VM which is configured with better devices such
> as virtio, VMs created from the image should also be configured with the same
> device types.
> The capture sequence will need to be extended to save the captured VM's
> hardware in a text file. There is already code to do so.
> The load sequence will be extended to read the text file for the image
> revision if it exists and use the values it contains.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
