Search results

Does it work if you change the OS disk to IDE? If so, after the upgrade you could add another disk as virtio-scsi, install the drivers and change your OS disk back to virtio-scsi.

In that case you could share the disk using NFS and mount this on both nodes from the Proxmox GUI. This way the storage can be marked as shared because it's available on both machines.

If it were true, yes it would be very bad. Given that your disk only has about 400gb of writes that is impossible. Seems like there's a bug in the firmware which counte the media_wearout_indicator the wrong way around...

Hi Devs, Using memory hotplug according to the proxmox wiki I succesfully increased and decreased the memory size of a Debian/Ubuntu guest. However when booting a virtual machine with memory hot-plug enabled and more than 21GB memory the guest OS can kernel panic with the following error...

I'll look into adding a nvme disk as well @spirit. The servers all have pm981 disks installed as they were repurposed vmware servers with them as ex-boot disks. I'm not quite sure I'd like to use those because of the low write endurance. Would you recon the amount of writes will be low enough to...

I tried finding some recommendations on using fleecing on Ceph storage but couldn't find an answer yet. We're running a fresh PVE cluster and PBS server on versions 8.2 and 3.2. This cluster is using Ceph as blockstorage with nvme disks on a 2x10G link using LACP. The same link is being used...

Thank you for the update! I mitigated the issue by switching to secure, I'll update the package once we get a maintenance window from the client.

Hi Widely, It won't show up as "used storage" in the other location as this data is not used on that location. You will see however that the total storage of the other location is lower than before. In this case you'll see the total size of "local" in- and decreasing in size this past year due...

I have a few clusters still on pve7 with a pbs on version 3. So far no issues, you just can't use the newer features like namespaces.

I can see your patch in the mailing list, would it help if I created a feature request in git?

I'm sorry to hear that, I've been running this setup with okay results. root@pbs1:~# dd if=/dev/zero of=testfile.bin bs=4G count=1 0+1 records in 0+1 records out 2147479552 bytes (2.1 GB, 2.0 GiB) copied, 6.73434 s, 319 MB/s This is done using an Intel s3610 1,92,tb sata ssd in a 2.5" enclosure...

Hi Jarvar, It is possible to assign a vlan in Opnsense or create an interface with vlan managed in proxmox. The problem with this however is that you can only have a vlan set-up in one of these two ways at the time. This is a limitation of the inner workings of linux bridges. The solution for...

1. Get the ID of your disk: michael@next-michael:~$ ls /dev/disk/by-id/ dm-name-cryptdata nvme-eui.002538bb21047659-part2 dm-name-cryptswap nvme-eui.002538bb21047659-part3...

As a matter of fact I do, had to do this solution once more a while back. These are the steps: 1. Backup the VG data: vgcfgbackup pve -f lvbackup 2. Edit the ID to match what it's expecting: vim lvbackup 3. restore the backup you made: vgcfgrestore pve -f lvbackup --force You're not done...

I had the same results as you for my testsetup. The way I fixed this is by assigning the disk to the vm instead of usb, this way the IO doesn't run though usb-passtrough. It's not not possible to assign it using the gui but by editing conf file or qm command. In my case it was this line: scsi1...

Yes that works perfectly! Stupid mistake from my side. All servers now use their loopback address.

Thank you for this update! It's almost working as intended but assigns the wrong ip-address. Setting controllers.cfg loopback to lo isis: pve4-test isis-domain 1 isis-ifaces eno8,eno7 isis-net 10.0000.0000.0007.00 loopback: lo node pve4-test And having...

This one works as intended! Was able to have 2 isis sessions and have them failover: pve4-test# show isis interface Area 1: Interface CircId State Type Level eno7 0x0 Up lan L1L2 eno8 0x7 Up lan L1L2 We ran into a small...

The route-map part is back, the other changes broke isis. Interfaces are not added in frr config anymore. Same goes for isis settings. controller.cfg: root@pve1-test:~# cat /etc/pve/sdn/controllers.cfg evpn: evpn asn 65000 peers 10.99.99.1 isis: pve1-test isis-ifaces...

I downloaded the file but it doesn't seem to be the new one, are you sure this is the correct link? root@pve1-test:~# sha1sum libpve-network-perl_0.8.1_all.deb 0c8d46ce6d88400324718d28e260050b928fcc4c libpve-network-perl_0.8.1_all.deb root@pve1-test:~# sha1sum...