Search results

Finally I have still the issue: On this CT no error but no mounted disk: root@CT105:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/loop2 7.8G 1.5G 6.0G 20% / none 492K 4.0K 488K 1% /dev tmpfs 32G 0 32G 0% /dev/shm tmpfs 6.3G...

oh my god, I really need some rest, shame on me :p

Well I am doing further tests and it is weird but all commands even with errors don't return errors: drwxrwxrwx 2 root root 4096 Jul 8 18:57 bkppcloud root@CT105:/mnt# # mount -t cifs //192.168.1.252/bkppcloud /mnt/bkppclou user=jc,password=1111 root@CT105:/mnt# # mount -t cifs...

Yes, but no chance so far. I found the above URL: https://bobcares.com/blog/apparmor-denied-operation-mount-info-failed-flags-match-error-13/ So on my case: root@pve:/etc/apparmor.d/lxc# ls lxc-default lxc-default-cgns lxc-default-with-mounting lxc-default-with-nesting...

nobody :-(

Hello all, I am facing an issue with my Container and I don't have any clue about what is wrong. It is very slow to connect through and each command takes time to provide output. I 've seen that with dmesg: [3095082.011000] audit: type=1400 audit(1720002390.721:206): apparmor="DENIED"...

Hello all, For some reasons and tests, I need to run VM built via proxmox 8.2 to 7.0. To do that, I made a backup of the VM from proxmox 8.2 and copied the file vzdump-qemu-106-2024_05_14-19_35_55.vma.zst to my proxmox server 7.0 and : qmrestore 109 vzdump-qemu-106-2024_05_14-19_35_55.vma.zst...

When I follow all tuto, proxmox stucks at boot from the following add: root@pve:~# echo "options vfio-pci ids=10de:1f82,10de:10fa" > /etc/modprobe.d/vfio.conf

root@pve:~# cat /etc/modprobe.d/blacklist.conf blacklist btusb blacklist bluetooth install bluetooth /bin/true root@pve:~# I wait for reboot, backup in progress

root@pve:~# lsmod | grep bt ebtable_filter 12288 0 ebtables 45056 1 ebtable_filter btusb 73728 0 btrtl 32768 1 btusb btbcm 24576 1 btusb btintel 53248 1 btusb btmtk 12288 1 btusb...

I have a sticker on the computer :(

Thanks @gfngfn256. Can not physically remove due to warranty. @gurubert I did that: root@pve:~# cat /etc/modprobe.d/blacklist.conf blacklist bluetooth install bluetooth /bin/true but doesn't work :(

Hello, I am not able to disable bluetooth in BIOS so I am trying with the OS Conf root@pve:/etc/systemd/system# dmesg | grep hci0 [ 4.538303] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi [ 4.538354] Bluetooth: hci0: Boot Address: 0x24800 [ 4.538356] Bluetooth: hci0...

it seems that I will have to réinstall proxmox 7 :(

I remove options vfio-pci ids=10de:1f82,10de:10fa and I get the output lspci -nnk 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU117 [GeForce GTX 1650] [1458:4026] Kernel modules...

I saw that link: https://forum.proxmox.com/threads/amd-gpu-inaccessible-after-vm-poweroff-unable-to-change-power-state-from-d3cold-to-d0-device-inaccessible.130975/

Sure. my VM conf: root@pve:~# cat /etc/pve/qemu-server/101.conf agent: 1 bios: ovmf boot: order=ide0 cores: 2 efidisk0: local:101/vm-101-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K hostpci0: 0000:01:00.0,pcie=1,x-vga=1 ide0: local:101/vm-101-disk-1.qcow2,size=52G machine: pc-q35-7.2...

I did all of that with those conf: GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt initcall_blacklist=sysfb_init" root@pve:~# dmesg | grep -e IOMMU [ 0.106394] DMAR: IOMMU enabled [ 0.247236] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 0 root@pve:~# /etc/modules...

each time I make changes in that file, I have to run the below command and reboot ? root@pve:~# update-initramfs -u -k all perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG...

root@pve:~# cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. # Parameters can be specified after the module name. vfio...