mmm, seem that
AddressOnParent is indeed the disk location on the controller,
but on the provided ovf example, they are 2 differents controllers (parent=4 &&
parent=5)
(I don't known how vmware manage disk, 1controller with multliples disk, or
1controller by disk. Maybe it's related to vm machine version or config.)
But in the proxmox ovf parser, we only handle 1 controller
# extract corresponding Controller node details
my $adress_on_controller = $xpc->findvalue('rasd:AddressOnParent',
$item_node);
my $pve_disk_address = id_to_pve($controller_type) . $adress_on_controller;
that's why we have a conflict here
On 21/12/2020 16:45, Thomas Lamprecht wrote:
On 21/12/2020 16:32, alexandre derumier wrote:
On 03/12/2020 08:36, Dominic Jäger wrote:
Please try changing the AddressOnParent values so that they are unique.
As you mentioned, the disks should then be attached with different numbers
scsi0, scsi1, scsi2...
Hi,
I wonder if the current proxmox ovs parser is not wrong.
Seem than "adressOnParent" is the pci controller.
So, it's working fine for nic, but for disks , if ovf have multiple disks on
same controller, it'll be always the same AddressOnParent.
That would sound likely, but did not actually looked into it.
I'll to check with differents hypervisors ovf export to be sure.
thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
