Danilop95 / Proxmox-Enhanced-Configuration-Utility

Is a comprehensive and versatile Bash script designed to simplify and optimize the configuration and management of Proxmox Virtual Environment (VE) systems.
https://danilop95.github.io/Proxmox-Enhanced-Configuration-Utility/
GNU General Public License v3.0
269 stars 14 forks source link

No such file or directory #7

Open profucius opened 1 month ago

profucius commented 1 month ago

I just ran your script and got these results. I see a number of No such file or directory and am concerned that something may have gone wrong during execution. Is this normal, or is there something I need to do to fix before attempting again?

=================================================
|        GPU Passthrough Configuration           |
=================================================
grep: /dev/fd/script_state.txt: No such file or directory
=================================================
|        Available Graphics Devices             |
=================================================
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
=================================================
Please enter the name of the device you are searching for (e.g., GTX 1080):
GTX 1070
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1) (prog-if 00 [VGA controller])
        Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1070]
Enter the ID of the video device (format xx:xx.x):
01:00.0
Getting the ID of your GPU:
10de:1b81
grep: /etc/modprobe.d/blacklist.conf: No such file or directory
blacklist nouveau
blacklist nvidia
grep: /etc/modprobe.d/vfio.conf: No such file or directory
options vfio-pci ids=10de:1b81 disable_vga=1
=================================================
| Applying kernel configuration                 |
=================================================
grep: /dev/fd/script_state.txt: No such file or directory
update-initramfs: Generating /boot/initrd.img-6.8.12-1-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
update-initramfs: Generating /boot/initrd.img-6.8.4-2-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Kernel configuration applied.
/dev/fd/63: line 259: /dev/fd/script_state.txt: No such file or directory
/dev/fd/63: line 332: /dev/fd/script_state.txt: No such file or directory
=================================================
Danilop95 commented 1 month ago

It looks like there are some 'No such file or directory' errors during the execution of the script, which might be causing issues. The problem with /dev/fd/script_state.txt seems to be related to how the script handles file paths, possibly due to being executed from an unexpected location or permissions.

Firstly, please ensure you're running the script as root and from the correct directory. Running it as sudo might cause path issues. Also, check if the following files exist: /etc/modprobe.d/blacklist.conf and /etc/modprobe.d/vfio.conf. If they don’t exist, you can create them with:

sudo touch /etc/modprobe.d/blacklist.conf
sudo touch /etc/modprobe.d/vfio.conf

I'm working on a new version that should address these issues by removing the need for sudo and improving how file paths are managed. Could you let me know from which directory you're running the script? This information will help ensure a more reliable fix in the upcoming version.

profucius commented 1 month ago

Thanks for the reply. The way I'm running the script is as follows:

  1. Open the Proxmox WebUI, click on PVE (under Datacenter) and click Shell tab.
  2. root@pve:~#
  3. Paste the script from the repo readme.md. bash <(curl -s https://raw.githubusercontent.com/Danilop95/Proxmox-Enhanced-Configuration-Utility/main/proxmox-configurator.sh)
  4. Script menu starts. Type and enter 2 to configure GPU.
  5. Log from my first message appears.

I tried doing the two sudo touch commands you mentioned and running the script again, but I got the same results.

After rebooting and running the script again, this time going to option 3 to check the GPU Installation, I get this:

=================================================
| Checking GPU Installation                     |
=================================================
NVIDIA GPU detected.
nvidia-smi found. Checking NVIDIA GPU status...
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
Detected NVIDIA Gaming GPU.

I already tried installing the Nvidia drivers from another guide, and I had assumed they were installed. But I've also read conflicting blogs that say that this is not necessary for Proxmox for a GTX 1070 for example.

Thoughts?

Danilop95 commented 1 month ago

I've identified the issue. Don't worry, I'll be releasing a new version in a few days that will address the problems with gaming GPUs. You shouldn't need drivers on the host machine (the Proxmox server); you'll need them on the VM instead. I'm currently working on fixing this.