Re: [pve-devel] Storage::Plugin::deactivate_volume not executed, when VM does shutdown

> > I do not understand why it does not work with your DRBD driver ... > It is no question of right or wrong. It is simply inconsistent. > Yes, it doesn't matter, because you "repair" it when migrating a VM and you > are > right only then it could be a problem. But I simple like it, when it is >

Re: [pve-devel] Why gets "activate_volume" executed on Harddisk edit

I'm not sure, but I think the size is checked (for the size=... hint) - Mail original - De: "Jasmin J." À: "pve-devel" Envoyé: Jeudi 15 Décembre 2016 03:27:33 Objet: [pve-devel] Why gets "activate_volume" executed on Harddisk edit Hi! When

[pve-devel] Why gets "activate_volume" executed on Harddisk edit

Hi! When you add a HardDisk to a not running VM, it gets simply written to the *.conf file. But when you EDIT a HardDisk, someone executes the storage plugin function "activate_volume", even if the VM is deactivated. Is this a bug or a feature? At least the state of the volume is different after

Re: [pve-devel] Storage::Plugin::deactivate_volume not executed, when VM does shutdown

Hi! >> > First, we call deactivate if you migrate a VM to another node. >> OK, I haven't seen this. I will test once my plugin is ready. The plugin is ready now and I could test this today. -> It works like you said. > I simply do not understand why you think the current approach is wrong. It

[pve-devel] Automatic crashkernel generation

Hi everyone, a lot of people asking about arbitrary crashes of the kernel in the forums and maybe there should be something "out-of-the-box" for that. Integrating crashdump into Debian is very easy and should be - at least - discussed in detail. I normally active crashdump on all my servers (not

Re: [pve-devel] qemu memory hotplug limited to 64 dimm

also see this redhat bugzilla, about kernel bug (even with online_movable) https://bugzilla.redhat.com/show_bug.cgi?id=1320534 " Description Milan Zamazal 2016-03-23 08:38:07 EDT Description of problem: File /usr/lib/udev/rules.d/40-redhat.rules contains the following line:

Re: [pve-devel] qemu memory hotplug limited to 64 dimm

>>Apparently I do have to explicitly mention that I'm talking about *unused* >>memory, iow. memory where the /sys/../enabled file is 0. I think this was >>working at some point on modern guest >>kernels? do you mean "online" instead "enabled" ? also here some notes I have set in the wiki

Re: [pve-devel] qemu memory hotplug limited to 64 dimm

> On December 14, 2016 at 3:45 PM Alexandre DERUMIER > wrote: > > > >>3) Drop support for hot*UN*plugging altogether and simply always hot-add > >>one big dimm. ;-) > >>On that note, my guests currently hang when I unplug memory and I bet > >>that happens to all of you and

Re: [pve-devel] What ist plugin "list_images" used for

> No, you need to set that yourself if you want to test that. If there is no command to force it, is there an action to trigger it somehow? If not, why does it exist? ___ pve-devel mailing list pve-devel@pve.proxmox.com

Re: [pve-devel] What ist plugin "list_images" used for

> > # pvesm list > THX, I could now debug most of the function, but "vollist" is always > undefined. > I used the parameters "-content images" and "-vmid 101". There are no more > options to the list command. > Is there another command to force "vollist" beeing defined? No, you need to set that

Re: [pve-devel] qemu memory hotplug limited to 64 dimm

>>3) Drop support for hot*UN*plugging altogether and simply always hot-add >>one big dimm. ;-) >>On that note, my guests currently hang when I unplug memory and I bet >>that happens to all of you and nobody ever noticed because nobody needs >>that feature anyway ;-) yes, it's a linux guest

Re: [pve-devel] qemu memory hotplug limited to 64 dimm

So I see a few options one or more of which we should consider: 1) Make the *static* memory size configurable: It doesn't make sense to me to eg. want to go from 1G to 200G in small steps. Worse is the fact that even when starting with a higher amount knowing that I'm only going to increase it,

Re: [pve-devel] What ist plugin "list_images" used for

# pvesm list THX, I could now debug most of the function, but "vollist" is always undefined. I used the parameters "-content images" and "-vmid 101". There are no more options to the list command. Is there another command to force "vollist" beeing defined?

[pve-devel] [PATCH installer] actually use more than 8 disks if selected

Signed-off-by: Fabian Grünbichler --- proxinstall | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proxinstall b/proxinstall index 10e5ace..18df7bb 100755 --- a/proxinstall +++ b/proxinstall @@ -2560,7 +2560,7 @@ my $get_raid_devlist = sub { my

[pve-devel] [PATCH manager] fix typo in ceph jewel iops parsing

this prevented the write iops performance charts to get any meaningful data Signed-off-by: Dominik Csapak --- www/manager6/ceph/Status.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/manager6/ceph/Status.js b/www/manager6/ceph/Status.js index