error when cloning VM

mihachatt · Sep 14, 2023

Hi!

I'm just learning, so I created a test server.
I didn’t find any information about the error when cloning and moving, so I created a post

There is a server HP ML150G6 2xE5520
12x2GB RAM
Hardware raid 4x300GB and 1xSSD 250GB
Proxmox was installed on the SSD, during installation the default file system was selected

Code:

dir: local
    path /var/lib/vz
    content iso,vztmpl,backup

lvmthin: local-lvm
    thinpool data
    vgname pve
    content rootdir,images

lvmthin: raid-lvm
    thinpool raid-lvm
    vgname raid-lvm
    content rootdir,images

local and local-lvm were created automatically
raid-lvm I created

Problem
I can create a new VM on local lvm
I can clone a VM from local-lvm to raid-lvm, I can also transfer a VM from local-lvm to raid-lvm, but I cannot clone a VM from raid-lvm to local-lvm, and I also cannot transfer a VM from raid-lvm to local-lvmI freed up the local lvm completely, but cloning or moving still doesn't work
Also, before I tried to clone the VM, the local-lvm disk was almost completely occupied and I received an error during cloning that the total volume of the VM disks was greater than the total volume of the local-lvm partition.
After that I completely cleared the local-lvm
Now, when cloning or moving a VM to local-lvm, the process hangs at about 2.5-3GB
the process stays in this state until I cancel it

Syslog:

Code:

Sep 14 13:00:49 vmserv1 pvedaemon[280373]: <root@pam> end task UPID:vmserv1:0005191E:006B7EED:6502D9D1:qmconfig:100:root@pam: OK
Sep 14 13:01:19 vmserv1 pvedaemon[281194]: <root@pam> starting task UPID:vmserv1:000519BD:006B8AE6:6502D9EF:qmmove:100:root@pam:
Sep 14 13:01:19 vmserv1 pvedaemon[334269]: <root@pam> move disk VM 100: move --disk ide0 --storage local-lvm
Sep 14 13:01:20 vmserv1 pvedaemon[1198]: worker 277623 finished
Sep 14 13:01:20 vmserv1 pvedaemon[1198]: starting 1 worker(s)
Sep 14 13:01:20 vmserv1 pvedaemon[1198]: worker 334280 started
Sep 14 13:01:21 vmserv1 pvedaemon[334278]: got inotify poll request in wrong process - disabling inotify
Sep 14 13:01:22 vmserv1 pvedaemon[334278]: worker exit
Sep 14 13:01:46 vmserv1 pve-firewall[1144]: firewall update time (6.841 seconds)
Sep 14 13:01:56 vmserv1 pve-firewall[1144]: firewall update time (7.143 seconds)
Sep 14 13:02:20 vmserv1 pvedaemon[334521]: starting termproxy UPID:vmserv1:00051AB9:006BA2C2:6502DA2C:vncshell::root@pam:
Sep 14 13:02:20 vmserv1 pvedaemon[334280]: <root@pam> starting task UPID:vmserv1:00051AB9:006BA2C2:6502DA2C:vncshell::root@pam:
Sep 14 13:02:21 vmserv1 pvedaemon[281194]: <root@pam> successful auth for user 'root@pam'
Sep 14 13:02:21 vmserv1 login[334524]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Sep 14 13:02:21 vmserv1 systemd-logind[824]: New session 54 of user root.
Sep 14 13:02:21 vmserv1 systemd[1]: Started session-54.scope - Session 54 of User root.
Sep 14 13:02:21 vmserv1 login[334529]: ROOT LOGIN  on '/dev/pts/0'
Sep 14 13:02:28 vmserv1 systemd[1]: session-54.scope: Deactivated successfully.
Sep 14 13:02:28 vmserv1 systemd-logind[824]: Session 54 logged out. Waiting for processes to exit.
Sep 14 13:02:28 vmserv1 systemd-logind[824]: Removed session 54.
Sep 14 13:02:28 vmserv1 pvedaemon[334280]: <root@pam> end task UPID:vmserv1:00051AB9:006BA2C2:6502DA2C:vncshell::root@pam: OK
Sep 14 13:06:47 vmserv1 pveproxy[329152]: worker exit
Sep 14 13:06:47 vmserv1 pveproxy[1211]: worker 329152 finished
Sep 14 13:06:47 vmserv1 pveproxy[1211]: starting 1 worker(s)
Sep 14 13:06:47 vmserv1 pveproxy[1211]: worker 336094 started
Sep 14 13:07:52 vmserv1 pveproxy[329111]: worker exit
Sep 14 13:07:52 vmserv1 pveproxy[1211]: worker 329111 finished
Sep 14 13:07:52 vmserv1 pveproxy[1211]: starting 1 worker(s)
Sep 14 13:07:52 vmserv1 pveproxy[1211]: worker 336444 started

the errors are the same when cloning and when moving to local-lvm
But I can still create a VM on local-lvm without problems

Code:

root@vmserv1:~# systemctl status pveproxy
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: active (running) since Wed 2023-09-13 17:26:56 MSK; 20h ago
    Process: 1206 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
    Process: 1209 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCESS)
    Process: 111931 ExecReload=/usr/bin/pveproxy restart (code=exited, status=0/SUCCESS)
   Main PID: 1211 (pveproxy)
      Tasks: 4 (limit: 23953)
     Memory: 187.4M
        CPU: 8min 34.435s
     CGroup: /system.slice/pveproxy.service
             ├─  1211 pveproxy
             ├─345065 "pveproxy worker"
             ├─345514 "pveproxy worker"
             └─348296 "pveproxy worker"

Sep 14 13:48:12 vmserv1 pveproxy[1211]: starting 1 worker(s)
Sep 14 13:48:12 vmserv1 pveproxy[1211]: worker 345065 started
Sep 14 13:50:24 vmserv1 pveproxy[340900]: worker exit
Sep 14 13:50:24 vmserv1 pveproxy[1211]: worker 340900 finished
Sep 14 13:50:24 vmserv1 pveproxy[1211]: starting 1 worker(s)
Sep 14 13:50:24 vmserv1 pveproxy[1211]: worker 345514 started
Sep 14 14:03:44 vmserv1 pveproxy[341425]: worker exit
Sep 14 14:03:44 vmserv1 pveproxy[1211]: worker 341425 finished
Sep 14 14:03:44 vmserv1 pveproxy[1211]: starting 1 worker(s)
Sep 14 14:03:44 vmserv1 pveproxy[1211]: worker 348296 started

I reinstalled proxmox, still have the problem, now cloning freezes on 6GB transferred

I also discovered an IO delay of 60%
there is not a single VM running on the server

Edit 15.09.2023 15:58***********
Only that I tried to clone a working VM
it worked!
But the question remains, why doesn’t it clone a stopped VM or from a template?

mihachatt · Sep 15, 2023

I found this information, but this parameter obtain_device_list_from_udev is 0
https://forum.proxmox.com/threads/f...udev-database-even-after-waiting-10000.56814/
udevadm trigger doesn't help

mihachatt · Sep 15, 2023

Another try, if you do not stop the process and wait, the following error appears

Code:

Sep 15 09:30:23 pveserv1 kernel: INFO: task qemu-img:3851 blocked for more than 120 seconds.
Sep 15 09:30:23 pveserv1 kernel:       Tainted: P           O       6.2.16-12-pve #1
Sep 15 09:30:23 pveserv1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 15 09:30:23 pveserv1 kernel: task:qemu-img        state:D stack:0     pid:3851  ppid:1      flags:0x00000006
Sep 15 09:30:23 pveserv1 kernel: Call Trace:
Sep 15 09:30:23 pveserv1 kernel:  <TASK>
Sep 15 09:30:23 pveserv1 kernel:  __schedule+0x402/0x1510
Sep 15 09:30:23 pveserv1 kernel:  schedule+0x63/0x110
Sep 15 09:30:23 pveserv1 kernel:  io_schedule+0x46/0x80
Sep 15 09:30:23 pveserv1 kernel:  bit_wait_io+0x11/0x90
Sep 15 09:30:23 pveserv1 kernel:  __wait_on_bit+0x4d/0x120
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_bit_wait_io+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  out_of_line_wait_on_bit+0x8c/0xb0
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_wake_bit_function+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  __block_write_begin_int+0x203/0x520
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_blkdev_get_block+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_blkdev_get_block+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  block_write_begin+0x57/0x140
Sep 15 09:30:23 pveserv1 kernel:  blkdev_write_begin+0x20/0x40
Sep 15 09:30:23 pveserv1 kernel:  generic_perform_write+0xd0/0x220
Sep 15 09:30:23 pveserv1 kernel:  __generic_file_write_iter+0xe8/0x1a0
Sep 15 09:30:23 pveserv1 kernel:  blkdev_write_iter+0x13f/0x1e0
Sep 15 09:30:23 pveserv1 kernel:  vfs_write+0x251/0x410
Sep 15 09:30:23 pveserv1 kernel:  __x64_sys_pwrite64+0xa6/0xd0
Sep 15 09:30:23 pveserv1 kernel:  do_syscall_64+0x5b/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? __x64_sys_futex+0x95/0x200
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? exit_to_user_mode_prepare+0x39/0x190
Sep 15 09:30:23 pveserv1 kernel:  ? syscall_exit_to_user_mode+0x29/0x50
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? exc_page_fault+0x91/0x1b0
Sep 15 09:30:23 pveserv1 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Sep 15 09:30:23 pveserv1 kernel: RIP: 0033:0x7f0d61715297
Sep 15 09:30:23 pveserv1 kernel: RSP: 002b:00007f0d55ff63a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000012
Sep 15 09:30:23 pveserv1 kernel: RAX: ffffffffffffffda RBX: 00007f0d5d2553b0 RCX: 00007f0d61715297
Sep 15 09:30:23 pveserv1 kernel: RDX: 0000000000200000 RSI: 00007f0d5cf54000 RDI: 0000000000000008
Sep 15 09:30:23 pveserv1 kernel: RBP: 00007f0d5cf54000 R08: 0000000000000000 R09: 000055b08834e240
Sep 15 09:30:23 pveserv1 kernel: R10: 0000000183fffa00 R11: 0000000000000293 R12: 0000000000000000
Sep 15 09:30:23 pveserv1 kernel: R13: 000055b087f5dd68 R14: 000055b08834e218 R15: 00007f0d557fb000
Sep 15 09:30:23 pveserv1 kernel:  </TASK>

Zaman · Sep 17, 2023

mihachatt said:

Another try, if you do not stop the process and wait, the following error appears

Code:

Sep 15 09:30:23 pveserv1 kernel: INFO: task qemu-img:3851 blocked for more than 120 seconds.
Sep 15 09:30:23 pveserv1 kernel:       Tainted: P           O       6.2.16-12-pve #1
Sep 15 09:30:23 pveserv1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Sep 15 09:30:23 pveserv1 kernel: task:qemu-img        state:D stack:0     pid:3851  ppid:1      flags:0x00000006
Sep 15 09:30:23 pveserv1 kernel: Call Trace:
Sep 15 09:30:23 pveserv1 kernel:  <TASK>
Sep 15 09:30:23 pveserv1 kernel:  __schedule+0x402/0x1510
Sep 15 09:30:23 pveserv1 kernel:  schedule+0x63/0x110
Sep 15 09:30:23 pveserv1 kernel:  io_schedule+0x46/0x80
Sep 15 09:30:23 pveserv1 kernel:  bit_wait_io+0x11/0x90
Sep 15 09:30:23 pveserv1 kernel:  __wait_on_bit+0x4d/0x120
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_bit_wait_io+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  out_of_line_wait_on_bit+0x8c/0xb0
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_wake_bit_function+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  __block_write_begin_int+0x203/0x520
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_blkdev_get_block+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  ? __pfx_blkdev_get_block+0x10/0x10
Sep 15 09:30:23 pveserv1 kernel:  block_write_begin+0x57/0x140
Sep 15 09:30:23 pveserv1 kernel:  blkdev_write_begin+0x20/0x40
Sep 15 09:30:23 pveserv1 kernel:  generic_perform_write+0xd0/0x220
Sep 15 09:30:23 pveserv1 kernel:  __generic_file_write_iter+0xe8/0x1a0
Sep 15 09:30:23 pveserv1 kernel:  blkdev_write_iter+0x13f/0x1e0
Sep 15 09:30:23 pveserv1 kernel:  vfs_write+0x251/0x410
Sep 15 09:30:23 pveserv1 kernel:  __x64_sys_pwrite64+0xa6/0xd0
Sep 15 09:30:23 pveserv1 kernel:  do_syscall_64+0x5b/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? __x64_sys_futex+0x95/0x200
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? exit_to_user_mode_prepare+0x39/0x190
Sep 15 09:30:23 pveserv1 kernel:  ? syscall_exit_to_user_mode+0x29/0x50
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? do_syscall_64+0x67/0x90
Sep 15 09:30:23 pveserv1 kernel:  ? exc_page_fault+0x91/0x1b0
Sep 15 09:30:23 pveserv1 kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Sep 15 09:30:23 pveserv1 kernel: RIP: 0033:0x7f0d61715297
Sep 15 09:30:23 pveserv1 kernel: RSP: 002b:00007f0d55ff63a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000012
Sep 15 09:30:23 pveserv1 kernel: RAX: ffffffffffffffda RBX: 00007f0d5d2553b0 RCX: 00007f0d61715297
Sep 15 09:30:23 pveserv1 kernel: RDX: 0000000000200000 RSI: 00007f0d5cf54000 RDI: 0000000000000008
Sep 15 09:30:23 pveserv1 kernel: RBP: 00007f0d5cf54000 R08: 0000000000000000 R09: 000055b08834e240
Sep 15 09:30:23 pveserv1 kernel: R10: 0000000183fffa00 R11: 0000000000000293 R12: 0000000000000000
Sep 15 09:30:23 pveserv1 kernel: R13: 000055b087f5dd68 R14: 000055b08834e218 R15: 00007f0d557fb000
Sep 15 09:30:23 pveserv1 kernel:  </TASK>

any update?

mihachatt · Sep 17, 2023

Zaman said:
any update?

only that: if I do not stop the VM, then cloning is successful, but it takes a lot longer
I forgot to mention, I use proxmox v.8.0.4

mihachatt · Dec 6, 2023

Zaman said:
any update?

It looks like the problem is in the RAID controller.
In HBA mode and when creating a ZFS software raid, there is no such problem.
In my case, for the controller to work in HBA mode, you need to disable controller in the BIOS. And also turn on the SATA ACHI mode.

maybe it's just an old controller

Search

Search

error when cloning VM

mihachatt

New Member

mihachatt

New Member

mihachatt

New Member

Zaman

Well-Known Member

mihachatt

New Member

mihachatt

New Member