There was a talk in the past to allow edit of the disk as its own entity
it but I think that some of the disk params are vm dependent so editing
them for disk only are a problem.
Ayal, do you remember why editing the disk on it's own was not implemented?
On 02/13/2014 07:33 AM, andreas.ewert(a)cbc.de wrote:
Yes, I know! Why is there this restriction? I have the following
scenario: I have a "recover vm" with one bootable disk attached. Now I want to
repair some broken configs from another vm’s boot disk. First I unattach the device from
the broken vm. If I forget to remove the bootable flag, then I have to attach the disk
again to the broken vm. I remove the bootable flag and attach the disk to my „recover vm“.
This is quite a long way round.
This could be a feature request, right?
best regards
Andreas
Am 12.02.2014 um 16:37 schrieb Dafna Ron <dron(a)redhat.com>:
> disks can only be edited when attached to a vm
>
> On 02/12/2014 03:04 PM, andreas.ewert(a)cbc.de wrote:
>> Hi,
>>
>> If I remove a disk image from a Virtual Machine, then I can’t edit the disk
properties in the „Disks“ tab. (e.g. bootable flag)
>> It is only possible to change the flags on attached disks.
>> My test environments are engine versions 3.3.3 and 3.4 beta2
>>
>> Best regards
>> Andreas
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>
> --
> Dafna Ron
--
Dafna Ron