Qemu VM Does Not Start - Kvm: -vnc 0.0.0.0:1: Failed To Find An ...

• Home
• Forums New posts Search forums
• What's new Featured content New posts Latest activity
• Members Current visitors New profile posts Search profile posts

Log in Register What's new

Search

Everywhere Threads This forum This thread Search titles only Note By: Search Advanced search… Everywhere Threads This forum This thread Search titles only By: Search Advanced…

• New posts
• Search forums

Menu Install the app Install How to install the app on iOS

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

qemu VM does not start - kvm: -vnc 0.0.0.0:1: Failed to find an available port: Address already in use

• Thread starter Thread starter Pierre DEDIEU
• Start date Start date Sep 6, 2021

• Home
• Forums
• Proxmox Virtual Environment
• Proxmox VE: Installation and configuration

You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. P

Pierre DEDIEU

New Member

Jul 31, 2021 5 0 1 61 The concerned VM is a restore from a backup (on pve1) which was on another node (pve2) of the cluster. It seems to be a problem on the destination node, as if I try a migration of the initial VM from pve2 to pve1, it also fails to start in the end: Migration of the initial VM from pve2 fails, after transfering the disk, with a similar message 2021-09-06 11:05:11 starting VM 104 on remote node 'pve' 2021-09-06 11:05:16 [pve] kvm: -vnc 0.0.0.0:1: Failed to find an available port: Address already in use 2021-09-06 11:05:17 [pve] start failed: QEMU exited with code 1 2021-09-06 11:05:17 ERROR: online migrate failure - remote command failed with exit code 255 2021-09-06 11:05:17 aborting phase 2 - cleanup resources 2021-09-06 11:05:17 migrate_cancel 2021-09-06 11:05:17 scsi0: removing block-dirty-bitmap 'repl_scsi0' 2021-09-06 11:05:19 ERROR: migration finished with problems (duration 00:00:21) TASK ERROR: migration problems What could I check ? (qm start 108 just returns the same message as the GUI)

oguz

Proxmox Retired Staff

Retired Staff Nov 19, 2018 5,207 848 118 hi,

Pierre DEDIEU said: 2021-09-06 11:05:16 [pve] kvm: -vnc 0.0.0.0:1: Failed to find an available port: Address already in use 2021-09-06 11:05:17 [pve] start failed: QEMU exited with code 1 2021-09-06 11:05:17 ERROR: online migrate failure - remote command failed with exit code 255 Click to expand...

here's your error, it seems you've added vnc parameter to your VM configuration, but there's another VM running VNC on the same port on the target node. if you change your VM config before migrating to use another vnc port, or change the vnc port of the VM in the target node, it should work Toggle signature Best regards, Oguz Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation P

Pierre DEDIEU

New Member

Jul 31, 2021 5 0 1 61 I found a bypass I still do not understand the reason, but I found in https://pve.proxmox.com/wiki/VNC_Client_Access that one could modify the VNC screen number in /etc/pve/local/qemu-server/<KVM ID>.conf I modified args: -vnc 0.0.0.0:1 to args: -vnc 0.0.0.0:2 And was able to start the VM (!) Any explaination would be appreciated

oguz

Proxmox Retired Staff

Retired Staff Nov 19, 2018 5,207 848 118

Pierre DEDIEU said: And was able to start the VM (!) Any explaination would be appreciated Click to expand...

yes, as i mentioned in my previous post, when you defined the vnc arg with :1 as the port, it starts listening on port 5901. you had another VM in the target node where it's being migrated to, which also had the same port defined for the VNC server, this caused a conflict and the newly migrated VM was thus not started. when you changed the config to use :2, it starts the VNC server on port 5902, which fixes the conflict please mark the thread as [SOLVED] so others know what to expect. Toggle signature Best regards, Oguz Do you already have a Commercial Support Subscription? - If not, Buy now and read the documentation K

kengrass

New Member

Mar 14, 2024 18 0 1

oguz said: yes, as i mentioned in my previous post, when you defined the vnc arg with :1 as the port, it starts listening on port 5901. you had another VM in the target node where it's being migrated to, which also had the same port defined for the VNC server, this caused a conflict and the newly migrated VM was thus not started. when you changed the config to use :2, it starts the VNC server on port 5902, which fixes the conflict please mark the thread as [SOLVED] so others know what to expect. Click to expand...

Can proxmox automatic change the port when migrate ? K

kengrass

New Member

Mar 14, 2024 18 0 1 bump problem, is there any way to fix it automatically? K

kengrass

New Member

Mar 14, 2024 18 0 1 bump problem, is there any way to fix it automatically? G

gotadmin

Active Member

Feb 19, 2020 7 2 43 42 We had the same issue the other day. Seems that an option in Virtualizor for VNC was adding the args to all of the configs on vm creation. While this is not an automatic fix you can run this sed command to drop the vnc args line from all of the clusters vm configs to allow migration: Bash: sed -i '/^args:.*-vnc/d' /etc/pve/nodes/*/qemu-server/*.conf If you are using something like Virtualizor to create vms, just disable the VNC option on all of your packages. You could also set that sed command up on a cron to run every 5 min: Bash: (crontab -l 2>/dev/null; echo "*/5 * * * * sed -i '/^args:.*-vnc/d' /etc/pve/nodes/*/qemu-server/*.conf") | crontab - You must log in or register to reply here. Share: Bluesky LinkedIn Reddit Email Share Link

• Home
• Forums
• Proxmox Virtual Environment
• Proxmox VE: Installation and configuration

Top Bottom Back

• We value your privacy

  We use essential cookies to make this site work, and optional cookies to enhance your experience.

  See further information and configure your preferences

  Accept all cookies Reject optional cookies
  • Essential cookies
  These cookies are required to enable core functionality such as security, network management, and accessibility. You may not reject these.
  • Optional cookies
  We deliver enhanced functionality for your browsing experience by setting these cookies. If you reject them, enhanced functionality will be unavailable.
  • Third-party cookies
  Cookies set by third parties may be required to power functionality in conjunction with our captcha service provider for security and anti-spam purposes.
  • Detailed cookie usage
  • Privacy policy
  Save cookie preferences