Search results

raid controller: CAUTION, don't use ZFS filesystem. Maybe would you like more clear ? you r hardwares switchs are totally ununderstandable without yours hardware in hands. Think logical. It's seem you've 3 hosts. 2 which you want to restall/reimplement with proxmox. Another host, with 2 tb...

:/ i've no more idea For import your VM disk storage, except root dir, you can copy / paste the /etc/pve/storage.cfg part intop the new storage.cfg file.

Did you have completly followed the proxmox VE upgrade guide ? Did you have called pve7to8 ?

oh ok. But i cannot help you anymore, no idea for your final config ^^

red box ?

no any hardware upgrade ?

Better (simple) solution: Create a dedicated VM for wifi-connexion. Passthourg your wf adapter on it ( DELETE all reference to this card before in your network/interface, "inet manual" declaration too. AFter, make a small network tuning for your pve host call it's vm for gateway.

Using 2 card in your bond is a good failover option. But, did you know that you wanna do ? Or are you testing ?

DOn't use default/grub. Modify your /ertc/sysctl.conf file ( not directly, use sysctl.conf.d)

what's your last config edit before proxmox stopped booting ?

Proxmox is really flexible on compatibility hardware (like linux os are). Search the controler you want to buy with proxmox keywords, and check if you see any known issues.

Hey, begin from the beginning. Good guide from Proxmox user : https://forum.proxmox.com/threads/pci-gpu-passthrough-on-proxmox-ve-8-installation-and-configuration.130218/ Before retrying your blacklisting options ( try the another solution that you can found on the post of the guy tutorial)...

Hey, begin by good configure your CPU Guest. In advanced CPU options, activate "pdpe1gb", "hv-evmcs", and (probably) "aes" If you have another bluescreens, back here

hey, from my experience, your problem can provide from dedup fonctionnality. WARNING: Don't do my error: Don't désactivate dedup on the deduplicated pool. Create a new dataset, and desactivate on HIM the dedup fonctionnality. Use your GUI VE to migrate properly yours disks on the new...

Hey, Check your SMART attrributes for your disk. On your VE Host, check (gui) system -> System log

Hey, You've configured a "host" processor. Did your have used advanced CPU tags in the configuration? If host used: Tags need to be enabled for better work. Wouldn't tag ? Take an aes kvm cpu One tag is especially for Windows guest ;)

OK. 2 choices for U: - Create a directory storage in your WebUI and select yours mountpoint (/mnt/1tb /tree-tb) -Destroy actual partition, and initialise them with lvm. DO NOT INITIALISE them with zfs, you gonna loose yours data.(perc h710)

Not easy with lxc.... but with qemu, simple :) https://pve.proxmox.com/wiki/Passthrough_Physical_Disk_to_Virtual_Machine_(VM)

Hey, UPDATE: i've try on my computer your context situation. I'm writing this post with my Ubuntu 24.04 lts with rtx3060 passthrough and 32Gb RAM working. It seems the problem is specific to your case. VM importants points: - Type q35 - UEFI Bios - EFI DIsk & TPM disk - processor on "host"...

How did you use your Audio system ? if your VM use a graphic card passthrough, priorize to connect yours audio external device on them, and your problem was resolved. If you're using a usb passthrough device, just delete your pci audio passthrough and retry it.