I have a question regarding the 7.3 > 7.4 upgrade.
I'm running on kernel 6.1.
Should I opt-in 6.2 prior to the 7.4 upgrade, or can I upgrade 7.4 first and do the kernel later or remain in 6.1?
I don't mind having the kernel 6.2. I just want to upgrade the proper way.
I creating this thread regarding ZFS Pool space utilization because I would like to make sense of how it is working.
I have a ZFS Pool with 5 NVME drive of 1T.
The pool is in raidz1 configuration.
I did not enabled compression to get the maximum preformances.
I enabled thin provisioning in...
You need to update your grub.
List your avaiulable kernel with
proxmox-boot-tool kernel list
proxmox-boot-tool kernel pin <kernel-version>
Also for futher info
Reboot then remove the the kernel again
I don't know the api that much but, if you check the api viewer
You have to specify the node name. I don't think you could use a wildcard.
They might be a way to get the VM list for each node with the API. But it is just a guess
Then from the list...
You were right !! There was a mistake in the bash script.
In the cookieid variable. I forgot to replace the user field by $apiu. It was set to api@pve.
And off course it worked for me because that's the user I used...
I fixed it.
It's working fine for me.
You can look in your syslog. You should see the api logging attemps. In my case my user is 'api@pve'
Dec 14 13:00:13 qxmx pvedaemon: <root@pam> successful auth for user 'api@pve'
Dec 14 13:00:13 qxmx pvedaemon: <api@pve> starting task...
Yeah, I have this already...
the vendor-reset module as well. It does not help.
To be fair I have no try without video=efifb:off" or "video=simplefb:off
I kept adding stuff in my grub conf file but did not clean up. I'll try that
Thank you for that !
I applied the bios settings and had no issues after installing 5.19.
It has not solved the "BAR 0: can't reserve [mem..." issue though.
I still need to rely on the hookscript to reset the pci bus before starting the VM.
If you look at the script below,
$url_base = "https://$pve$port/api2/json"
$url_end = "/nodes/$node/qemu/$vmid/status/start"
$node is used in the api call, that's why it's just the name of your hypervisor.
$pve is used in the url and you need the hypervisor fqdn or ip.
Yup you don't need an ISO to update minor version.
In the GUI, select your node then on the right panel you should see in the menu collum, summary, shell.. updates
Click on updates then again in the new panel that show up on the right you should see at the top "Upgrades"
Is the button available...
This script is using the API system available with proxmox 6.7 if I remember correctly (Available in version 7 that's for sure).
What you need to feed is the host info and API credentials.
No changes.... :/
I'm not even sure it does something because as you can see below. I still have the same delay between the drive coming on and the zfs import. (around 4/5s)
Oct 21 14:28:15 pxmx kernel: scsi 1:0:0:0: Direct-Access ATA ST2000DM006-2DM1 CC26 PQ: 0 ANSI: 5
Dear Proxmox Community,
I have a slight issue with one of my zfs pool.
The SAN ZFS pool fail to import at boot. But once the node finished its boot sequence. The SAN pool is 100% working fine.
This is what I get
UNIT LOAD ACTIVE SUB DESCRIPTION