migration fail

please post:
- pveversion -v on both PVE nodes
- VM config
- migration and start log of the migrated VM
- journalctl of both PVE nodes
 
Eduardo Taboada said:
Which version of Proxmox do you have at the destination? It will be a problem with the versión of Proxmox at the destination cluster, because live migration is only supported on latest PVE 8 versions
Click to expand...

thanks for reply

my pve version is

pveversion -v
proxmox-ve: 8.4.0 (running kernel: 6.8.12-17-pve)
pve-manager: 8.4.14 (running version: 8.4.14/b502d23c55afcba1)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8: 6.8.12-17
proxmox-kernel-6.8.12-17-pve-signed: 6.8.12-17
proxmox-kernel-6.8.12-16-pve-signed: 6.8.12-16
ceph-fuse: 17.2.7-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-2
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.7-1
proxmox-backup-file-restore: 3.4.7-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.8
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.1.2
pve-container: 5.3.3
pve-docs: 8.4.1
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.5
smartmontools: 7.3-pve1
spiceterm: 3.3.1
swtpm: 0.8.0+pve1
vncterm: 1.8.1
zfsutils-linux: 2.2.8-pve1

the same with souce and destdination

still got the same error
 
fabian said:
please post:
- pveversion -v on both PVE nodes
- VM config
- migration and start log of the migrated VM
- journalctl of both PVE nodes
Click to expand...
tks for reply

here is my pveversion
same with souce and destdination

proxmox-ve: 8.4.0 (running kernel: 6.8.12-17-pve)
pve-manager: 8.4.14 (running version: 8.4.14/b502d23c55afcba1)
proxmox-kernel-helper: 8.1.4
proxmox-kernel-6.8: 6.8.12-17
proxmox-kernel-6.8.12-17-pve-signed: 6.8.12-17
proxmox-kernel-6.8.12-16-pve-signed: 6.8.12-16
ceph-fuse: 17.2.7-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.2
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.2
libpve-cluster-perl: 8.1.2
libpve-common-perl: 8.3.4
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.7
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-2
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.7-1
proxmox-backup-file-restore: 3.4.7-1
proxmox-backup-restore-image: 0.7.0
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.4
proxmox-mail-forward: 0.3.3
proxmox-mini-journalreader: 1.5
proxmox-offline-mirror-helper: 0.6.8
proxmox-widget-toolkit: 4.3.13
pve-cluster: 8.1.2
pve-container: 5.3.3
pve-docs: 8.4.1
pve-edk2-firmware: 4.2025.02-4~bpo12+1
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.2
pve-firmware: 3.16-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.5
pve-qemu-kvm: 9.2.0-7
pve-xtermjs: 5.5.0-2
qemu-server: 8.4.5
smartmontools: 7.3-pve1
spiceterm: 3.3.1
swtpm: 0.8.0+pve1
vncterm: 1.8.1
zfsutils-linux: 2.2.8-pve1

config and journalctl plz download

https://send.now/h8yhkyu55eun

use offline migration NOT live migration
 
Last edited:
the logs are maybe incomplete or of the wrong nodes? please limit them to the relevant timespan and also indicate when the problem happened..
 
fabian said:
the logs are maybe incomplete or of the wrong nodes? please limit them to the relevant timespan and also indicate when the problem happened..
Click to expand...
pdm

Dec 09 16:20:06 pdm proxmox-datacenter-api[528]: remote migration requested
Dec 09 16:20:06 pdm proxmox-datacenter-api[528]: forwarding remote migration requested
Dec 09 16:20:06 pdm proxmox-datacenter-api[528]: migrating vm 115 of node "proxmox4155"
Dec 09 16:20:43 pdm login[10531]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
Dec 09 16:20:43 pdm systemd-logind[415]: New session 144 of user root.
Dec 09 16:20:43 pdm systemd[1]: Created slice user-0.slice - User Slice of UID 0.
Dec 09 16:20:43 pdm systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Dec 09 16:20:43 pdm systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Dec 09 16:20:43 pdm systemd[1]: Starting user@0.service - User Manager for UID 0...
Dec 09 16:20:43 pdm (systemd)[10539]: pam_unix(systemd-user:session): session opened for user root(uid=0) by root(uid=0)
Dec 09 16:20:43 pdm systemd-logind[415]: New session 145 of user root.
Dec 09 16:20:43 pdm systemd[10539]: Queued start job for default target default.target.
Dec 09 16:20:43 pdm systemd[10539]: Created slice app.slice - User Application Slice.
Dec 09 16:20:43 pdm systemd[10539]: Reached target paths.target - Paths.
Dec 09 16:20:43 pdm systemd[10539]: Reached target timers.target - Timers.
Dec 09 16:20:43 pdm systemd[10539]: Listening on dirmngr.socket - GnuPG network certificate management daemon.
Dec 09 16:20:43 pdm systemd[10539]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Dec 09 16:20:43 pdm systemd[10539]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Dec 09 16:20:43 pdm systemd[10539]: Starting gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
Dec 09 16:20:43 pdm systemd[10539]: Starting gpg-agent.socket - GnuPG cryptographic agent and passphrase cache...
Dec 09 16:20:43 pdm systemd[10539]: Listening on keyboxd.socket - GnuPG public key management service.
Dec 09 16:20:43 pdm systemd[10539]: Starting ssh-agent.socket - OpenSSH Agent socket...
Dec 09 16:20:43 pdm systemd[10539]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Dec 09 16:20:43 pdm systemd[10539]: Listening on ssh-agent.socket - OpenSSH Agent socket.
Dec 09 16:20:43 pdm systemd[10539]: Listening on gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Dec 09 16:20:43 pdm systemd[10539]: Reached target sockets.target - Sockets.
Dec 09 16:20:43 pdm systemd[10539]: Reached target basic.target - Basic System.
Dec 09 16:20:43 pdm systemd[10539]: Reached target default.target - Main User Target.
Dec 09 16:20:43 pdm systemd[1]: Started user@0.service - User Manager for UID 0.
Dec 09 16:20:43 pdm systemd[10539]: Startup finished in 222ms.
Dec 09 16:20:43 pdm systemd[1]: Started session-144.scope - Session 144 of User root.

source

Dec 09 16:20:06 proxmox4155 pvedaemon[2718544]: VM isn't running. Doing offline migration instead.


destination


no log at Dec 09 16:20:06
 
if there are no further traces than this means that the migration didn't even start..
 
Hi,
kk_proxmox said:
Can a guest not migrate from a cluster to a single node?
Click to expand...
yes, it can. Does your token have the correct access rights for the storages on the target? Are the relevant storages on the target all active/enabled?
 
You must log in or register to reply here.
Top Bottom