Search results

  1. Migration failure between two nodes

    The migration problem has been solved. Once I realized that the VM configuration file was for the VM number and that there were five instances of VMs with that number, I decided to delete the lines for the four instances of "Ubuntu2004". I'm guessing I reused the number at some point (but not...
  2. Migration failure between two nodes

    With the "pvecm updatecerts" command run on both nodes, I'm back to the initial problem. I do not have a migration network configured. I've attached a file with the storage.cfg contents for both nodes, and what I hope are the VM config files for both nodes. I don't know where to find the full...
  3. Migration failure between two nodes

    I now have compound errors and can't get back to the one described above. The new error is "Can't connect to destination address using public key." when I try to migrate the VM in question from node A to node B. A week or so ago, I put a different VM (on node B running Home Assistant) on a...
  4. Migration failure between two nodes

    I have tried detaching the ISO, and I've tried removing the CD/DVD drive entirely. I still get the same result. Is there a way (Corosync file?) to add ISO as an enabled storage type? I've done that in the /etc/pve/storage.cfg file on the node in question, but that didn't have any effect.
  5. Migration failure between two nodes

    Supplemental information: On the GUI under Datacenter, Storage Common is listed as having only Disk image and Container. Edit shows it available on both nodes. When I click on content, there are no other options for storage. If I limit the nodes to only node B or node A, there is still only...
  6. Migration failure between two nodes

    Dietmar, Thanks for the quick response. The GUI for "Common" shows content type "Disk image, Container". I don't see a way of enabling "iso" in the GUI. Is there a way to do that in the GUI? Using the Shell, I added "iso" to the storage types for "Common" in /etc/pve/storage.cfg. I then...
  7. Migration failure between two nodes

    I have two nodes, say A and B. I upgraded both from Proxmox 6.4 to 7 a couple of weeks ago. The upgrade on A went well. However, after the upgrade on B, virtualization didn't work. When I tried to open an Ubuntu VM, I got a message that virtualization wasn't working and a suggestion to turn off...
  8. Suddenly no GUI access

    The message I see on the server that I can still get to on the GUI says: "Error 500: closing file '/var/tmp/pve-reserved-ports.tmp.851' failed - -No space left on device". So on one of the servers that I can't get to on the GUI, in the CLI I went to the folder "/var/tmp" and listed all the...
  9. Suddenly no GUI access

    Thanks, but I'm not sure how to search for mound points with the problem. When I change directories and run du -h, I always get the same response as I found above, with nothing showing 100%.
  10. Suddenly no GUI access

    Here is the result from one of the servers. I don't have a way to snip or copy and paste. Filesystem Size Used Avail Use% Mounted on udev 16G 0 16G 0%...
  11. Suddenly no GUI access

    I have three Proxmox servers in a cluster. One has been turned off for a few months. Suddenly, this morning, I don't have browser access to the two which are active. I've restarted both to no effect. One of the servers hosts a virtual Windows machine, which I can access. The other hosts an...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!