Search results

  1. H

    i try us api live remote_migrate happen error

    i have done https://www.reddit.com/user/wichets/comments/15f54tb/pve_qm_remotemigrate_for_migrate_vm_to_a_remote/
  2. H

    i try us api live remote_migrate happen error

    2024-10-09 18:42:29 remote: started tunnel worker 'UPID:raid10-pve-us-02:0017CC63:12FEBE4B:67065E15:qmtunnel:27004:root@pam!qianyi:' tunnel: -> sending command "version" to remote tunnel: <- got reply 2024-10-09 18:42:29 local WS tunnel version: 2 2024-10-09 18:42:29 remote WS tunnel version: 2...
  3. H

    Permissions required for remote-migrate feature

    have wish share your plan , now i am try
  4. H

    migrate vm broken pipe

    i have found issue, php time out
  5. H

    migrate vm broken pipe

    ok we check network is ok
  6. H

    migrate vm broken pipe

    we try more times , still error .
  7. H

    migrate vm broken pipe

    ======== log May 17 22:43:29 xy pvedaemon[1607363]: <root@pam!Qq123654> starting task UPID:xy:001920D1:05403EE0:66476D11:qmtunnel:285:root@pam!Qq123654: May 17 22:43:30 xy pvedaemon[1646801]: [931B blob data] May 17 22:43:30 xy pvedaemon[1646801]: Wide character in print at...
  8. H

    migrate vm broken pipe

    we try agains test () 2024-05-17 22:43:29 remote: started tunnel worker 'UPID:xy:001920D1:05403EE0:66476D11:qmtunnel:285:root@pam!Qq123654:' tunnel: -> sending command "version" to remote tunnel: <- got reply 2024-05-17 22:43:29 local WS tunnel version: 2 2024-05-17 22:43:29 remote WS tunnel...
  9. H

    migrate vm broken pipe

    root@xy:~# journalctl --since="2024-05-13 14:03:54" May 13 14:03:54 xy pvedaemon[2985081]: <root@pam!Qq123654> starting task UPID:xy:002DBA84:03015538:6641AD4A:qmtunnel:138:root@pam!Qq123654: May 13 14:03:55 xy pvedaemon[2996868]: [931B blob data] May 13 14:03:55 xy pvedaemon[2996868]: Wide...
  10. H

    migrate vm broken pipe

    we just check task log is ok? mtunnel started received command 'version' received command 'bwlimit' received command 'bwlimit' received command 'disk' Formatting '/var/lib/vz/images/258/vm-258-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata...
  11. H

    migrate vm broken pipe

    yes , i check vm have remove ,but no start and task error
  12. H

    migrate vm broken pipe

    mtunnel started received command 'version' received command 'bwlimit' received command 'bwlimit' received command 'disk' Formatting '/var/lib/vz/images/258/vm-258-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=42949672960...
  13. H

    migrate vm broken pipe

    proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve) pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15) proxmox-kernel-helper: 8.0.9 proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4 proxmox-kernel-6.5: 6.5.11-4 ceph-fuse: 17.2.7-pve1 corosync: 3.1.7-pve3 criu: 3.17.1-2 glusterfs-client: 10.3-5...
  14. H

    migrate vm broken pipe

    2024-05-13 14:03:54 remote: started tunnel worker 'UPID:xy:002DBA84:03015538:6641AD4A:qmtunnel:138:root@pam!Qq123654:' tunnel: -> sending command "version" to remote tunnel: <- got reply 2024-05-13 14:03:54 local WS tunnel version: 2 2024-05-13 14:03:54 remote WS tunnel version: 2 2024-05-13...
  15. H

    [SOLVED] running tc happen error

    RTNETLINK answers: No such file or directory # tc class add dev tap135i0 parent 1:1 classid 1:10 htb rate 10kbps RTNETLINK answers: No such file or directory proxmox-ve: 7.4-1 (running kernel: 5.15.60-2-pve) pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e) pve-kernel-5.15: 7.4-4...
  16. H

    in cluster, how to running qm guest exec command?

    yeah vm have install qemu guest. we running ssh root@node3 qm guest exec 394 C:\WINDOWS\SYSTEM32\CMD.EXE /c "shutdown -r -t 0" unknow r but we change write have ok ssh root@node3 qm guest exec 394 C:\WINDOWS\SYSTEM32\CMD.EXE /c "shutdown /r" is ok
  17. H

    in cluster, how to running qm guest exec command?

    hi , we have a trouble in cluster 3 node . we connectting node1, running vm location node3. so we how to from node1 running qm guest exec node3 vm. now we try this write loging in node web shell running below shell ssh root@node3 qm guest exec 394 C:\WINDOWS\SYSTEM32\CMD.EXE /c "shutdown -r...
  18. H

    proxmox happen error

    sorry, it's cable cut down. - - tks
  19. H

    proxmox happen error

    pass have resolved.