There is an Proxmox VE 5.3-11 server running several VM's.
Disk images are stored on Ceph RBD.
I modified "print_drivedevice_full" subroutine in /usr/share/perl5/PVE/QemuServer.pm for RBD tuning as described in https://pve.proxmox.com/pipermail/pve-devel/2018-June/032787.html
Here is my patch:
https://gist.github.com/ilyaevseev/effc9a6a2bdc4f9bf90000a384488bd0
Problem:
- print_drivedevice_full is successfully executed with new functionality when VM is started by CLI "qm start 123" command (and that's fine
- VM can be started from GUI too, but nothing is applied nor printed in this case -- it seems that print_drivedevice_full is not reached at all.
Is it a bug or a feature?
Disk images are stored on Ceph RBD.
I modified "print_drivedevice_full" subroutine in /usr/share/perl5/PVE/QemuServer.pm for RBD tuning as described in https://pve.proxmox.com/pipermail/pve-devel/2018-June/032787.html
Here is my patch:
https://gist.github.com/ilyaevseev/effc9a6a2bdc4f9bf90000a384488bd0
Problem:
- print_drivedevice_full is successfully executed with new functionality when VM is started by CLI "qm start 123" command (and that's fine
- VM can be started from GUI too, but nothing is applied nor printed in this case -- it seems that print_drivedevice_full is not reached at all.
Is it a bug or a feature?