public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] ovf duplicate AddressOnParent
Date: Thu, 3 Dec 2020 08:36:04 +0100	[thread overview]
Message-ID: <20201203073603.GA455757@mala.proxmox.com> (raw)
In-Reply-To: <a22cf741-c1b6-309f-eecc-2149d4c23d45@jack.fr.eu.org>

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...

If it still doesn't work, then you can also create a VM and add each disk manually by using qm importdisk. For example,
qm importdisk 110 /path/to/your/disk.vmdk local
adds disk.vmdk as unused disk to VM 110 on storage local. You can then double click it in the GUI. This will open a wizard where you can select where you want to attach it to.

On Wed, Dec 02, 2020 at 02:50:51PM +0100, px@jack.fr.eu.org wrote:
> And indeed, in the OVF file:
>       <Item>
>         <rasd:AddressOnParent>0</rasd:AddressOnParent>
>         <rasd:ElementName>Hard disk 1</rasd:ElementName>
>         <rasd:HostResource>ovf:/disk/vmdisk1</rasd:HostResource>
>         <rasd:InstanceID>11</rasd:InstanceID>
>         <rasd:Parent>5</rasd:Parent>
>         <rasd:ResourceType>17</rasd:ResourceType>
>         <vmw:Config ovf:required="false" vmw:key="backing.writeThrough"
> vmw:value="false"/>
>       </Item>
>       <Item>
>         <rasd:AddressOnParent>0</rasd:AddressOnParent>
>         <rasd:ElementName>Hard disk 2</rasd:ElementName>
>         <rasd:HostResource>ovf:/disk/vmdisk2</rasd:HostResource>
>         <rasd:InstanceID>12</rasd:InstanceID>
>         <rasd:Parent>4</rasd:Parent>
>         <rasd:ResourceType>17</rasd:ResourceType>
>         <vmw:Config ovf:required="false" vmw:key="backing.writeThrough"
> vmw:value="false"/>
>       </Item>
> 
> -> both disk has the same AddressOnParent, 0, because they do not share the
> same Parent (respectively 5 and 4)
> 
> So now, what should we do ?
> I wonder if we could simply increment that number for each disk found, in
> the loop: first disk gets scsi0, second gets scsi1 etc
> 




  reply	other threads:[~2020-12-03  7:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 13:50 px
2020-12-03  7:36 ` Dominic Jäger [this message]
2020-12-21 15:32   ` alexandre derumier
2020-12-21 15:45     ` Thomas Lamprecht
2020-12-21 17:04       ` alexandre derumier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201203073603.GA455757@mala.proxmox.com \
    --to=d.jaeger@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal