
|
If you were logged in you would be able to see more operations.
|
|
|
|
If you create a OVF file descriptor with the following information about the hard disk controller:
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Description>SCSI Controller</rasd:Description>
<rasd:ElementName>scsi0</rasd:ElementName>
<rasd:InstanceID>3</rasd:InstanceID>
<rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>
In VirtualBox, this information is not applied in the configuration of the Virtual Machine.
For all the hypervisor, it should be created a Hard Disk controller according to the information provided by the OVF, and no assumption about the hard disk controller should be done.
At this moment, it seems that the virtual machines created for each hypervisor uses the default controller and this is not correct. It should use the controller provided in the OVF.
If no information about the controller is provided. then it should be assigned the 'lsilogic' controller by default, because it's the one that guarantees that will work in all the hypervisors.
|
|
Description
|
If you create a OVF file descriptor with the following information about the hard disk controller:
<Item>
<rasd:Address>0</rasd:Address>
<rasd:Description>SCSI Controller</rasd:Description>
<rasd:ElementName>scsi0</rasd:ElementName>
<rasd:InstanceID>3</rasd:InstanceID>
<rasd:ResourceSubType>lsilogic</rasd:ResourceSubType>
<rasd:ResourceType>6</rasd:ResourceType>
</Item>
In VirtualBox, this information is not applied in the configuration of the Virtual Machine.
For all the hypervisor, it should be created a Hard Disk controller according to the information provided by the OVF, and no assumption about the hard disk controller should be done.
At this moment, it seems that the virtual machines created for each hypervisor uses the default controller and this is not correct. It should use the controller provided in the OVF.
If no information about the controller is provided. then it should be assigned the 'lsilogic' controller by default, because it's the one that guarantees that will work in all the hypervisors. |
Show » |
Sort Order:
| There are no comments yet on this issue.
|
|