Search results

pfSense and OpnSense both operate fine within a KVM VM on Proxmox. I have used them extensively. The issue will be due to your configuration. Remember that traffic shaping/limiting and any IDS/IPS processes you use are very CPU heavy and will effect your throughput dramatically. Also be aware...

Howdy all, migrating another HyperV Cluster to Proxmox VE. I have been using Proxmox VE since 3.0 and love it. Have deployed single instances to 16 node clusters, including ceph, iscsi, you name it... In fact I have deployed Proxmox VE into some of the most prestigious organisations in the...

Thanks for the reply. I actually resolved this simply by adding the no sub repo into sources.list, running an apt update and then pveceph install. However I swear blind that the 3 seperate proxmox ceph installs I done 2 months ago installed Ceph just fine without me manually adding the no sub...

I am having exactly the same problem. Fresh install using the 5.2 iso. pveceph install does not work and attempts to remove proxmox-ve. This is a fresh install, not changed any repo or anything. I do not have a subscription. I installed proxmox 5.2 3 times 2 months ago and installed Ceph...

Thanks for the reply. This does however appear to add a fair amount of additional steps into the backup process. Guess the easiest backup solution will just be to make sure I have a ton of storage available and to rotate as needed with a periodic archival of a full backup set to tape or elsewhere.

Thanks for the reply. So essentially this means the best way to control the storage requirements of Proxmox's built in backup system is to use a destination file system that supports de-duplication and compression? ZFS on freenas for example. Any examples of a good backup storage system would...

Hi there, I am a fan of the out the box Proxmox backup solution. Its simple yet effective! However on larger clusters with many VM's, running daily full backups obviously means huge disk space requirements. I am a long time Proxmox user and have built several large clusters with it, but in...

This issue appears to be present in 5.2.

Are there any updates on this issue. I have just had a Windows VM on a new proxmox 5.2 install suffer exactly the same symptoms. Loss of network connectivity, only restored by a vm reboot or disable/reenable of NIC.

I know that.... The portal address is an address to the storage controller(s) and it will respond with other IP's in the portal group.... But does this mean that iSCSI in proxmox / debian now multipath's without the need for multipath-tools and a bunch of devices in /etc/multipath.conf? I was...

See this, installed multipath-tools and ran multipath -ll straight away:

Sorry but im not sure I follow.... I have only given proxmox a single portal address of my iSCSI target which is a HP P2000 SAN with dual controllers. This proxmox node has two 10Gb connections to 2 seperate storage networks. Each controller in the SAN has a connection to both of those...

When I run vgdisplay I get the following messages: I have two iSCSI LUN's connected to this host, multipath-tools is NOT installed. When I run fdisk -l I see several /dev/sdX devices for the same LUN's as follows: What is going on here? I am having iSCSI problems and was wondering if this...

No-one care to shine any light on this then?

This appears to be due to the adoption of the Ubuntu kernel?

So I created udev rules to set the max_sectors_kb to 512 on all block devices however even though I confirm it sets the values, it seems that as soon as something uses the device, it is reset back to 32767. Help!

I have managed to get this working, udev wasn't starting. However it hasn't resolved my issue with iscsi.

I am also suffering from this issue. However when I manually set max_sectors_kb to 512 on all my block devices, it reverts back to 32767 as soon as I try and make a VM on the disk. I cannot seem to get a udev rule to work?

Well I had a feeling that changing max_sectors_kb to 512 instead of 32767 might help on all sd and dm devices under /sys/block might help, but it done nothing.

See here: https://forum.proxmox.com/threads/udev-rule-for-changing-max_sectors_kb-for-all-sd-devices.28510/