Search results

Hi I am too busy to tests it this week. I’ll back to you as soon as I get the result. Best regards. Fabien

Here are the system logs: 2025-01-14T14:31:51.920161+01:00 test-pve-01 kernel: [ 3214.087254] kvm[18733]: segfault at 41b8 ip 00005d1ea425fb00 sp 00007b07488fef38 error 4 in qemu-system-x86_64[5d1ea3d7c000+6a4000] likely on CPU 1 (core 1, socket 0) 2025-01-14T14:32:04.378628+01:00 test-pve-01...

Thanks. I tested but still have problems. But the error is now different: 2025-01-14 14:31:45 set migration parameters 2025-01-14 14:31:45 start migrate command to unix:/run/qemu-server/102.migrate 2025-01-14 14:31:47 migration active, transferred 107.2 MiB of 1.5 GiB VM-state, 161.4 MiB/s...

Because I am able to reproduce, please let me know if I can help doing some tests.

Hi, First, I wish a happy new year to all the team. I could make another tests that could help to understand/reproduce my problem. My original infrastructure was nested: One bare metal server use Promox 8.3 as hypervisor. Into it, we installed 6 VM with Proxmox 8.3: The first 3 machines are...

Here are two new debugger files. I am not able to know if it could help you or not...

Hello, Any update? I just tested with the lastest available packages and I still occure the problem. Kind regards. Fabien

I launched the migration just after the debugger attachment using a script. I added a 1 second "sleep" between it but the gdb log output seems to be about the same. I joined it too. I didn't tell you but the command claim's some missing files: 42 ../sysdeps/unix/sysv/linux/ppoll.c: No such...

Hi, Here is the new gdb log file. I joined the VM query-block file too, because another VM (but with same caracteristics) was concerned. Thanks.

I understand, it does not product on all migration for me too... About 10%. Here are the file you requested. Kind regards. Fabien

Hi, I didn't specify yesterday, the snapshot was done without memory. I removed this snapshot and the problem still occur. Best regards. Fabien Hello @dtt Have you validated that your not matching with this issue ...

Hi, I didn't specify yesterday, the snapshot was done without memory. I removed this snapshot and the problem still occur. Best regards. Fabien

Nothing changed instead the pve-qemu-kvm package version during my morning tests. This VMs has got old snapshots (from february, still here). I can test without it if needed. Here's my vmdata storage config: rbd: vmdata content rootdir,images krbd 0 monhost 10.xx.xx.xx...

Here's the informations you requested: VM config: # qm config 103 agent: 1 boot: order=scsi0;ide2;net0 cores: 2 cpu: x86-64-v2-AES,flags=+aes ide2: none,media=cdrom memory: 3072 meta: creation-qemu=7.2.0,ctime=1692804811 name: test-migration4 net0: virtio=72:8D:E9:1E:80:8C,bridge=vmbr0 numa: 0...

I did tests with old versions of both kernel and qemu-kvm packages and my problem seems to have been introduces with the 9.0.2 version of the pve-qemu-kvm packages (OK with 9.0.0-6 and KO with 9.0.2-1).

Hi, We're testing the new 8.3 version on our just upgraded test environment and we occur problems during the VM migrations. An hardware machine is installed with Proxmox 8.3 up-to-date. Three VM are installed with 8.3 Proxmox too into a CEPH cluster for the shared storage. Three other VM are...

apparently not

Hello My datastore is on ZFS pool. No tache is curring but all disk of the zfs pool are busy. Any ideas please ?

Hello I have the same problem with a ceph storage. I thought the backup is done via a snapshot. In this case, a write in the VM should not impact the backup and vice versa?

ok all traffic pass with ssh so... it should be ok