Search results

It's not really solved, if anyone knows how i can remove the [SOLVED] status from this thread i will

Yeah.. Still with trixie now running /tmp as a ramdisk, this issue would be easily solved if there was an option to use /tmp instead of /var/tmp for ISO uploads..

update.. /var/tmp is still not a ramdisk it seems: # mount | grep tmp udev on /dev type devtmpfs (rw,nosuid,relatime,size=131949456k,nr_inodes=32987364,mode=755,inode64) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=26399632k,mode=755,inode64) tmpfs on /dev/shm type tmpfs...

Unsure what you mean by that.. If you have time, can you check if /tmp is now a ramdisk in PVE9? as per my reply above

Without knowing if relevant, i recently upgraded to PVE 9 (debian trixie) and now remember skimming the changelog and noticed a mention that in Trixie, /tmp is now a RAM disk, just like in Fedora etc, so if anyone here is inclined to check, is /tmp actually a ramdisk in PVE9, and so this is no...

Let's consider that a solution.

Hi all, sorry for no reply, i been away from this for years. I have no clue about this, i had been expecting the dev team to figure this out, but afaik no solutions yet, other than creating custom directories etc.. I would prefer a real solution. Everytime i upload a big 3GB+ ISO to my poor old...

Thank you for this. I'm too busy now, but just wanted to let you know about a thread on servethehome where i have modified my old clumsy script for the x710. Nothing much different there.. But i plan to update the thread with the problems i've learned if you want to use proxmox resource mapping...

Hello, i have the same question, i have 2 block devices containing a ZFS pool that i want to export over iscsi and exclude from zfs.import-scan.service. systemctl disable zfs-import@poolname2ignore.service does nothing, infact just typing anything random for poolname just gives: # systemctl...

Thank you for this guide. Small bug, the intel lines are missing 'blacklist' at beginning of line, results in errors when rebuilding initramfs.

from the source forum thread i linked to: "I obtained the lspci -D -d 8086:154c command by trying various combo's from the output of lspci -vvm -nn -s 0000:01:02.0" #lspci -vvm -nn -s 0000:01:02.0 Device: 01:02.0 Class: Ethernet controller [0200] Vendor: Intel Corporation [8086] Device...

you can reset by writing 0. I've adapted my solarflare proxmox script for my QNAP intel X710 cards: nano /etc/systemd/system/sriov-vfs.service [Unit] Description=Enable SR-IOV and detach guest VFs from host Requires=network.target After=network.target Before=pve-firewall.service [Service]...

Hello, i use encrypted zvol's for my desktop vm's by manually creating them, and then linking them to the VM's using the qm set command, for example: qm set 102 -scsi0 /dev/zvol/zpool_800G/debian-root,discard=on,ssd=1,cache=directsync,iothread=1 but is there an equivalent command for...

i have no idea, but you could start with numactl -H

Sorry, only noticed your reply now. In the VM make sure that "all Functions" is unchecked, and PCI-Express is checked, and the host is q35 machinetype. (just from memory) On my solarflare cards, the NIC processor acts as a hardware L2 switch, and i can communicate between the vf's fine...

Thank you @Neobin , i'll mark this as solved, since this issue is getting attention from developers, and it's likely it will be improved in the future.

Hello, My PVE rpool is on a small 128GB M.2 2242 SSD, and i use a enterprise U.2 SSD for everything not related to rpool. I have disabled local and local-zfs in Datacenter storage. Then i have created the corresponding storage on the datacenter SSD. However, when i upload a .ISO file, it first...

ok, seems i have manually installed sfc-dkms_4.15.14.1001-1_all.deb previously, which is solarflare driver from their homepage. apt remove --purge sfc-dkms seems to have resolved the issue i think.. EDIT: issue solved, it was manually install solarflare kernel module dkms, i had forgot about...

Yes, the cryptsetup complaints are normal. here's my complete term.log

Hello, just tried to update to 8, following the guide. after full upgrade on 7 i first ran ran apt --purge autoremove pve7to8 --full pveversion output was pve-manager/7.4-16/0f39f621 (running kernel: 6.2.16-11-bpo11-pve) and pve7to8 --full resulted in all green. at the end of the upgrade...