Recent content by gusto

Sorry, yes, that was a question. However, I tried to create LXC several times. Sometimes it takes 50-70 seconds until LXC starts. Today I tried again and LXC was created and started in 10 seconds (like in the old days). Here is the script how I create LXC pct create 114 \...

I don't really mind. I don't create and restore LXC that often. I just wanted to know why it behaves like that in PVE9, when it was OK in PVE8. The HW is exactly the same. I accidentally installed PVE8 in ZFS RAID0. Now in PVE9 I have it installed in ZFS RAID1 It is possible that stripping was...

According to AI, my SSD patriot P200 are old disks and not very suitable for ZFS. They have 39000 hours of operation which is more than 4 years (that's true). I had Proxmox 8 on ZFS RIAD0 and now I have Proxmox 9 on ZFS RAID1 (mirror). Could this be the problem? AI advised me to use this zfs set...

I tried watch -cd -n1 "zpool iostat -vyl 1 1", but I'm not an expert, I can't judge if it's okay. I also tried pveperf 3x pveperf /var/lib/vz CPU BOGOMIPS: 69597.24 REGEX/SECOND: 4606004 HD SIZE: 205.62 GB (rpool/var-lib-vz) FSYNCS/SECOND: 41.41 DNS EXT: 28.69...

Today I updated Proxmox to 9.1.4 and rebooted. I still have problems. LXC (debian 13) takes 70-90 seconds to create. Restoring takes the same amount of time. It's pure LXC (the compressed backup is not even 250MB). zpool status -v pool: datapool state: ONLINE scan: scrub repaired 0B in...

I don't like it at all. If I backup LXC (zstd), the size is 250MB. If I do a restore via the web gui, it takes 70 seconds. Something is definitely wrong there. In Proxmox 8, backup and restore were in the order of seconds. Graphs during LXC manipulation (creation, backup, restoration).

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE MODEL sda 8:0 0 238.5G 0 disk Patriot P200 256GB ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 1G 0 part vfat └─sda3 8:3 0 237G 0...

When I was using proxmox 8, creating LXC debian 12 took very fast (5-10 seconds). Now I'm using Proxmox 9 and creating LXC debian 13 takes more than a minute. See graphs of what happens when creating LXC Is this a bug? pct create 114 \ local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst...

There is criticism of the new installer everywhere. Offline installation was 1000x better. That's why I used the 2.7.2 ISO image for installation and then updated to 2.8.1

I use pfsense as the only router/firewall in the network (there is a gpon modem in bridge mode in front of it). pfSense from ver. 2.8.0 does not use the regular ISO installation, but online installation. After booting the ISO, you need to configure the WAN (IP static/dynamic, PPPoE, VLAN ....)...

AI prepared a working script for me. You only need to set VM ready in 3 seconds #!/bin/bash VM_ID=$(pvesh get /cluster/nextid) VM_NAME="pfSense-2.8.0" STORAGE="local-zfs" ISO_PATH="local:iso/netgate-installer-v1.1.1-RELEASE-amd64.iso" echo "Create VM $VM_ID ($VM_NAME)..." qm create $VM_ID \...

As I wrote at the beginning, I don't like upgrades. After all, I've been using pfSense since 2020 and I've already done one upgrade. It seems to me that I have some ballast in psSense, so I'd rather use a clean install and restore the configuration via xml.

I understand, but I need to prepare the VM for Proxmox VE. The pfSense forum doesn't give me any advice on how to prepare the VM.

I recently installed the latest PVE 9.1 and migrated the VM and LXC to the new PVE. I also migrated the pfSense 2.7.2 VM. I am not a fan of upgrading, but I like to install the latest system. Here is the recommended installation of pfSense on proxmox. I assume this documentation is quite old...

libpve-access-control/stable 9.0.4 all [upgradable from: 9.0.3] libpve-apiclient-perl/stable 3.4.2 all [upgradable from: 3.4.0] libpve-cluster-api-perl/stable 9.0.7 all [upgradable from: 9.0.6] libpve-cluster-perl/stable 9.0.7 all [upgradable from: 9.0.6] libpve-common-perl/stable 9.0.15 all...