>> Example volume names:
>>>
>>> local:6000/base-6000-disk-9.raw
>>> local:6000/base-6000-disk-9.raw/7000/vm-7000-disk-9.qcow2
>>> local:6000/base-6000-disk-9.raw/7000/base-7000-disk-10.qcow2
>>That way it is easy to check if a volume is a clone or a template. Do you
>>think
>>this can be i
> i would like to allow a group of ldap users access to pve. But it seems this
> is
> not possible. I have to specifiy the access level for each user.
> Is this correct?
Yes.
I you really need that you can write some import script.
Maybe we can add an LDAP configuration option like 'import
Hello,
i would like to allow a group of ldap users access to pve. But it seems
this is not possible. I have to specifiy the access level for each user.
Is this correct?
Greets,
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.p
Hi,
Am 30.01.2013 14:27, schrieb Dietmar Maurer:
> we need to use the new command.
done
>> Would you like to have a patchset to make pve-qemu-kvm compatible with
>> 1.4?
>
> Yes, but I will start that in 2 weeks (not earlier). I will let you know when
> I need that patches.
OK just send a mail
> I've a question regarding the virtio ballooning patches. qemu 1.4 supports
> the new statistics out of the box but they've changed the command to: guest-
> stats-polling-interval .
we need to use the new command.
>
> Should i patch qemu to support the old stats-polling-interval or patch pve?
n
Hi,
sorry got it working. So this patch is now also working fine with qemu 1.4.
I've a question regarding the virtio ballooning patches. qemu 1.4
supports the new statistics out of the box but they've changed the
command to: guest-stats-polling-interval .
Should i patch qemu to support the old s
Hi,
OK saving / snapshotting works fine now with 1.4. I've not ported it to
threads like the migration code but i adpoted the changes to the while loop.
But restoring does still not work. Anjy ideas where to look here?
Am 30.01.2013 06:02, schrieb Dietmar Maurer:
>> Everything works fine except
> Example volume names:
>
> local:6000/base-6000-disk-9.raw
> local:6000/base-6000-disk-9.raw/7000/vm-7000-disk-9.qcow2
> local:6000/base-6000-disk-9.raw/7000/base-7000-disk-10.qcow2
That way it is easy to check if a volume is a clone or a template. Do you think
this can be implemented for all st
This is an iplementation for file base storage types.
changes compared to patches from Alexandre:
* use correct locking
* private find_free_diskname() with bug fixes
* changed names of new methods
* always refer to base volumes in volume names
Example volume names:
local:6000/base-6000-disk-9.r
Hi,
Am 30.01.2013 06:02, schrieb Dietmar Maurer:
>> Everything works fine except the savevm-async - it compiles fine but the VM
>> hangs. Do you have already an idea what needs to be changes there? So
>> maybe i can start working on that.
>
> Compare with the code in migration.c (migrate_fd_put_re
>>The series start with patches about volume_protect().
>>But this should not be required at all with the new system?
Yes, indeed, we can't start the template, but Isn't it always better to have a
protection on the storage ?
(user try to move file manually with ssh, or something else...)
Only
On Wed, 30 Jan 2013 06:12:56 +
Dietmar Maurer wrote:
>
> What is the advantage of 'chattr +i'? I usually use 'chmod -w' to
> set a file read only.
>
chattr +i also prevents creating hard-links to the file which a
read-only file does not guaranty against. A hard-link would effectively
preven
12 matches
Mail list logo
