[pve-devel] pve: cloning
Michael Rasmussen
mir at datanom.net
Fri May 24 15:17:44 CEST 2013
Are we using the same version of perl?
My test installation is a bare-bones install of 3.0rc2. I will upgrade
later today to see if this changes anything.
Do I need to make a reinstall of 3.0 or will apt-get update && apt-get
upgrade be sufficient?
On 05-24-2013 15:11, Dietmar Maurer wrote:
> I am unable to reproduce it:
>
> # qm config 105
> bootdisk: virtio0
> cores: 1
> ide2: none,media=cdrom
> memory: 512
> name: nextest
> net0: virtio=AE:DE:EF:50:62:58,bridge=vmbr0
> ostype: l26
> sockets: 1
> virtio0: nex1:vm-105-disk-1,size=1G
>
> I can make a full clone without problems.
>
> Please can you post your VM config?
>
>
>> -----Original Message-----
>> From: pve-devel-bounces at pve.proxmox.com [mailto:pve-devel-
>> bounces at pve.proxmox.com] On Behalf Of Alexandre DERUMIER
>> Sent: Freitag, 24. Mai 2013 06:16
>> To: Michael Rasmussen
>> Cc: pve-devel at pve.proxmox.com
>> Subject: Re: [pve-devel] pve: cloning
>>
>> I can reproduce here too with full clone: (only with nexenta plugin
>> in the
>> game)
>>
>> (Works fine in command line, don't work only with gui)
>>
>> create full clone of drive ide0 (nexentatestapi:vm-277-disk-1) TASK
>> ERROR:
>> clone failed: unable to create image: Insecure dependency in exec
>> while
>> running with -T switch at /usr/share/perl/5.14/IPC/Open3.pm line 186.
>>
>> nexenta -> local : fail on alloc_image (qemu-img create)
>>
>> rbd -> nexenta : ok
>>
>>
>> I don't known exactly how tainted mode work, we have already fixed a
>> bug
>> like this here:
>>
>> https://git.proxmox.com/?p=pve-
>> storage.git;a=blobdiff;f=PVE/Storage/Plugin.pm;h=462d9e1e21d40d66b8545
>> aadfd46669a10b986d8;hp=de2818cd62d0aab634258d27c54aba26ec123ed7;hb
>> =7fc619d5d31c2eba2cfab6f1fcf6cb9dca7ddf55;hpb=32437ed2791882342928e
>> 081bcbffeb9c70cdc59
>>
>>
>>
>> ----- Mail original -----
>>
>> De: "Michael Rasmussen" <mir at datanom.net>
>> À: "Michael Rasmussen" <mir at datanom.net>
>> Cc: "Alexandre DERUMIER" <aderumier at odiso.com>, pve-
>> devel at pve.proxmox.com
>> Envoyé: Vendredi 24 Mai 2013 01:33:58
>> Objet: Re: [pve-devel] pve: cloning
>>
>> On Thu, 23 May 2013 09:16:38 +0200
>> Michael Rasmussen <mir at datanom.net> wrote:
>>
>>> Using the clone features from the nexenta-plugin does not work
>>> either:
>>> create full clone of drive virtio0 (nexenta_iscsi:vm-101-disk-1)
>>> TASK
>>> ERROR: clone failed: unable to create image: Insecure dependency in
>>> exec while running with -T switch at
>>> /usr/share/perl/5.14/IPC/Open3.pm
>>> line 186.
>>>
>> I have found out what is causing the above error. Every time you try
>> to make
>> a clone where the target for the clone is a different storage than
>> the storage
>> of the source the error above is thrown.
>>
>> Following use cases have been tried with the same result:
>> source target result
>> nexenta zfs fails
>> nexenta local fails
>> nexenta nexenta success
>> zfs nexenta fails
>> zfs local fails
>> zfs zfs success
>>
>> seems that command 'exec' in IPC/Open3.pm cannot be executed on a
>> tainted command which normally is seen when path is not untainted.
>>
>>
>> --
>> Hilsen/Regards
>> Michael Rasmussen
>>
>> Get my public GnuPG keys:
>> michael <at> rasmussen <dot> cc
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
>> mir <at> datanom <dot> net
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
>> mir <at> miras <dot> org
>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
>> --------------------------------------------------------------
>> Your step will soil many countries.
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
> !DSPAM:519f6703187841968616024!
--
Hilsen/regards
Michael Rasmussen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vcard.vcf
Type: text/x-vcard
Size: 104 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20130524/3b6a9069/attachment.vcf>
More information about the pve-devel
mailing list