Search results

This kernel is available in pve-no-subscription : Indeed, I guess hot fix is also present in latest kernel (5.11.22-10) as well

Already fixed since kernel 5.11.22-9

You 're right. Pinging a gw during the live migration did the trick :) Only lost one ping. I guess the CT was inactive on my first attempt. This is a good alternative to have CT with live migration !

I am able to live migrate the virtualized pve with few lxc inside. but lxc lost connectivity for about 1 min :/ I was expecting lxc containers should be still reachable during the live migration :/

Of course, this virtualized PVE should be a standalone server with only LXC VMs inside. Yes, we should plan to recreate these LXC VMs to KVM. Or just simply remove them when convenient... Thanks :)

Hi, We usually make KVM VMs. But for history reasons we still have some old containers. Openvz containers which were migrated to lxc since PVE4. Now with pve7 some LXCs refuse to start properly (mainly due to old systemd < 232). Also, LXC live migration is impossible. So I'm wondering if...

don't leave me in the dark :p Maybe upgrades should be done with lrm (pve-ha-lrm) & crm (pve-ha-crm) services stopped in order to prevent such reboots ?

Hi, I tried to upgrade a 6 nodes pve7 cluster yesterday. We use Ceph and HA for all VMs. I was able to upgrade 4 nodes without issue. But on the fifth node, I lost the whole cluster. All nodes rebooted ! Syslogs for nodes 22 to 27 : update ok for nodes 22,23,24 and 27 upgrade of node 25...

Hi, My cluster was also affected by this issue. kernel 5.11.22-9 installed. I keep you in touch too. May I say that packages are moving so fast from testing/no-subscription to enterprise repository ? :p

Hi, Yesterday an updated PVE7 node crashed - Dell R440 - Xeon(R) Silver 4210 CPU @ 2.20GHz (2 Sockets) with 256 GB RAM The weird thing is that network was still OK - and corosync said that all 6 nodes are reachable. the GUI showed involved node grayed - its Vms continue to respond to ping...

Thanks seems to be OK on my VirtualBox test environment I just forgot the following : - Migrate all VM to another node - Stop all OSD and then remove them from config - remove existing ceph monitor/manager - shutdown the node. - remove node from cluster - remove host from ceph config => ceph...

Hi, I recently upgraded a 6 nodes Ceph PVE cluster 6.4 to 7 We discovered higher CPU usage, performance issues. I want to recreate all cluster. What I plan to do for each node : - Migrate all VM to another node - Stop all OSD and then remove them from config - shutdown the node. - remove...

Do you think it is possible to boot on the old 5.4.128 kernel for one node ? I just want to check if iowaits are better

For iowaits Before pve7 update After pve7 update

Hi, Thanks for your answer. First, aio=threads seems to fix the issue. No complains this morning ! I was pretty confident on the fact that issue should be related to PVE7. The complains involved all relatively high loaded LAMP servers on the updated cluster. Mysql queries were incredibly slow...

Hi, I settled all VM disks with aio=threads. I'll keep you in touch. I also saw this :(

And basically, it cannot be done without restarting the VM ?

I see now aio=io_uring I guess previously it was threads. Where can I change the aio value ?

We also noticed relatively more cpu usage & more iowaits for pve 7.0/ ceph pacific

Hi, Of course : qm config 20089 agent: 1 bootdisk: scsi0 cores: 4 cpu: host description: Dolibarr ide2: none,media=cdrom memory: 8192 name: dc-doli-merc02 net0: virtio=36:7C:34:B8:B1:9E,bridge=vmbr0,tag=20 numa: 1 onboot: 1 ostype: l26 scsi0...