Search results

  1. S

    iSCSI and LVM issues after NAS IP change

    My Proxmox server (version 8.1.3) is hosting several virtual machines, the first of which is TrueNAS Scale. Three of the other machines use iSCSI from TrueNAS as block storage. I imported the three iSCSI block storages into Proxmox and built LVMs on top of each. Everything was running...
  2. S

    [SOLVED] GPU passthrough last step issue, AMD driver doesn't work

    One final note for anyone who has the same problem. I have an ASRock Z790 Taichi motherboard and an AMD 6400 based video card. I am still unable to disable "above 4G decoding". However, I've discovered that that doesn't matter. The key to making the AMD Radeon RX 6400 work in Windows 11 is...
  3. S

    [SOLVED] GPU passthrough last step issue, AMD driver doesn't work

    a9udn9u, I thought you'd be mildly interested in this update, as might others who stumble across this thread. I did disable "above 4G decoding" in my BIOS. (The motherboard is ASRock Z790 Taichi.) After a couple of more frustrating days, I discovered that the disable wasn't holding. After the...
  4. S

    [SOLVED] GPU passthrough last step issue, AMD driver doesn't work

    No, I used my own device IDs and the "lspci nnk" command shows "Kernel driver in use: vfio-pci". I did notice that you had three IDs. I have two, 1002:743f and 1002:ab28, which are close to yours. I also have two devices identified as AMD but are PCI bridges, 1002:1478 and 1002:1479. I've...
  5. S

    [SOLVED] GPU passthrough last step issue, AMD driver doesn't work

    You indicated above that you "just got Windows to work as well". Was the 4g decoding setting in BIOS the key? I've done that, but my Device Manager screen still looks the same as yours towards the top of this thread. Any other suggestions, given your experience with this? I've done...
  6. S

    [SOLVED] GPU passthrough last step issue, AMD driver doesn't work

    a9udn9u, I'm having the same problem. I did disable above 4g decoding in my BIOS. You say that you disabled Re-size Bar. Is that a reference to ROM-Bar checkmark that I see in the that I see in the edit for the passed-through PCI device? I've tried that, but I'm not sure if that's what...
  7. S

    Structuring shared storage

    bbgeek17: I can't get past one final obstacle. Maybe you can help. In Proxmox, I've added an LVM on top of the LUN that's imported from TrueNAS. I'm trying to install a Windows VM in that LVM. I get as far in the Windows installation as the Windows installer finding the LVM as a drive, but...
  8. S

    Structuring shared storage

    bbgeek17: Just a note of thanks. I'm on my way again through this maze.
  9. S

    Structuring shared storage

    bbgeek17: Thanks for the reference to iSCSI multipath, but I'm not sure that I need that. I assume that once I succeed in establishing the iSCSI block in Proxmox, it wil be shared with the other nodes when I cluster them. In the meantime, I've deleted iscsi storage from the node. It doesn't...
  10. S

    Structuring shared storage

    floh8: The first two nodes have been running for a long time with their own storage. My intent is to connect the new node to a cluster with the other two and make available the shared storage to all three nodes. But not until I get the new node set up to my satisfaction. bbgeek17: Here are...
  11. S

    Structuring shared storage

    My goal is to use shared storage for VMs, including Windows and Ubuntu machines. However, I'm new to storage concepts and haven't been able to make it work. I have a new server running Proxmox 7.4-3. (It is stand-alone at the moment but will eventually be joined to a cluster with two small...
  12. S

    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...
  13. S

    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...
  14. S

    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...
  15. S

    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.
  16. S

    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...
  17. S

    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...
  18. S

    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...
  19. S

    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...
  20. S

    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%.

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 yours easily in our online shop.

Buy now!