[PVE-User] question regarding colum in disks view / passtrough disk

[Roland @web.de]

thanks for commenting,

 >The problem here is that during the disk enumeration, we do not touch
 >vm configs (also i am not even sure if we could do it that easily
 >because of package dependency chains) and thus have no information
 >which disk is used by vms

what about some simple blacklisting mechanism , i.e. some config file
where i can tell proxmox:

"don't touch/honor this special disk(s) and give it some special
marker/flag in the gui" ?

i think this could be easily implemented and be very effective/valuable

 >passing through a disk to a vm is always a very advanced feature that

yes, but while neither with xenserver nor with vmware local
disks/storage is a typical/wanted feature
(the vendors don't really "support" local storage in sane way,
especially not with passtrough) i think it's one
of the strengths of proxmox and where it's good at and where it shines.

having local storage zfs as an option and make proper use of local
storage via zfs or lvm is one of the main
reasons , why like proxmox so much.

regards
Roland


Am 28.11.19 um 09:49 schrieb Dominik Csapak:
> On 11/27/19 3:00 PM, Roland @web.de wrote:
>> Hello,
>
> Hi,
>
>>
>> in Datacenter->Nodename->Disks  there is a column "Usage" which shows
>> what filesystem is being used for the disk.
>>
>> I have 2 System disks (ssd) which contain the proxmox system and they
>> are being used as ZFS mirror, i.e. i can put virtual machines on
>> rpool/data
>>
>> The other harddisks (ordinary large sata disks) are being used as
>> passtrough devices, i.e. have added them with command like
>>
>> qm set 100 -scsi5 /dev/disk/by-id/ata-HGST_HUH721212ALE600_AAGVE62H
>>
>> as raw disks to virtual machines, i.e. they are used from a single
>> virtual machine.
>>
>>  From the Disk View in Webgui, you cannot differ between thos, i.e. they
>> simply look "the same" from a hosts management perspective.
>>
>> Wouldn't it make sense to make a difference in the Webgui when a disk
>> containing filesystem/data which is (and should) not being accessed on
>> the host/hypervisor level ?
>
> In general i agree with you that this would be nice.
> The problem here is that during the disk enumeration, we do not touch
> vm configs (also i am not even sure if we could do it that easily
> because of package dependency chains) and thus have no information
> which disk is used by vms
>
>>
>> I would feel much better if proxmox knew some "the host OS should not
>> touch this disk at all" flag and if it would have an understanding of
>> "this is a disk i (can) use" and "this is a disk i can't/should not use"
>
> if a disk is not used by a mountpoint/zfs/lvm/storage definition/etc.
> it will not be touched by pve (normally) so this is only a 'cosmetic'
> issue
>
> passing through a disk to a vm is always a very advanced feature that
> can be very dangerous (thus it is not exposed in the web interface)
> so the admin should already know what hes doing...
>
>>
>> regards
>> Roland
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user