Recent content by hybrid512

@aaron thx for your kind help, works perfect.

Hi @aaron , Worked ike a charm, thank you soooo much ! One last question : in ProxMox UI, I have a warning about crashed mgr modules, it is related to the error I had but now everything is fine, how can I clear this log ? Best regards

Hi, I upgraded to Quincy and everything went fine except that I have this issue with the devicehealth module : 2022-08-14T14:06:33.206+0200 7f16e2549700 0 [devicehealth INFO root] creating main.db for devicehealth 2022-08-14T14:06:33.206+0200 7f16e2549700 -1 log_channel(cluster) log [ERR] ...

Wow, 512MB just for EFI ? Isn't it a bit big ? But ok, good to know. Thanks for the maxvz option ! Maybe something more explicit would be welcome such as a simple checkbox "Create default LVM storage for VMs/CTs" or something to enable/disable this feature would be a nice addition. Thanks...

That's a good point. This is a question I wanted to ask too ... Is it possible to disable that LVM group for VMs completely at install time ? It is useless to me since I'm using Ceph and other shared storage solutions so I'd like to remove this completely and reclaim that space for some other...

Damn ... you're right ! I was using a 8GB drive (this was the default value from Virtualobx and I thought this was enough for a base install). Using a 12GB hard drive fixed the issue. Thanks for your help.

Hi, I just wanted to quickly setup a small lab to testbed some ProxMox setup within Virtualbox but the installation keeps failing whatever the settings I try. I don't want to do something serious with this setup, this is just for test and demo purpose. Here is my setup : * Linux Ubuntu 19.10...

nope but this bug happen either after a living VM clone with more than 100GB of data to clone for some of them or after a failed OSD (not allways though)

I don't have logs, the clone itselfs is working without any issue, the VM is cloned properly and you can start it but if you want to restart it, you can't and you get a sysfs write error. I find many reports on the ceph ML when searching these errors on Google ... seems not so uncommon...

Then maybe this is a bug in qemu live mirror with krbd backend (it works well with librados).

The clone. I think the prb mainly occures because we clone a "living" image with moving blocks and not a snapshot or a "cold" image. One solution would be to create an automatic temporary snapshot before the clone, do the clone based on the snapshot then remove the temporary snapshot right...

Hi, I think I found a corner case. We have VMs running on Ceph in KRBD mode. I have a user who cloned such VM but in a living state, neither from a stopped VM nor a snapshot. I don't know why but it works except that when you want to remove the VM, when trying to remove the image, I get a sysfs...

+1 ... any idea on how to fix or mitigate this issue ? It also happens in case of OSD loss even though I/Os pressure is much less intense with Luminous.

Hi, I had many KVMs running in Ceph with very good performances but I decided to give a try to LXC on Ceph in order to benefit for near bare metal performances and lighter overhead on ressources but I was soon disappointed on the disk i/o side. While in KVM (virtio-scsi + writeback cache mode)...

Thanks but I know this roadmap and this is more about upcoming release than real roadmap of longer term objectives ... and by now, there is nothing about multiple datacenter management in this document.