Recent content by thesubmitter

I used ZFS in the past for a while and it was a huge pita. I love the theory but in practice it performs poorly for intensive applications and causes a lot of headaches. On the flip side I have an hp server 4 x Raid 10 x NVME with mdadm/lvm/ext4 and had major corruptiion which completely...

Seeing a similar issue now with LVM Raid MD10 and NVME disks....

There is a difference from a security perspective. You are giving each container on that interface access to all the vlans . I agree that your solution works but the limit of interfaces seems arbitrary and trivial to fix (if ur reading this support staff, I’m a paying user - 50 machines)

+1, I need to some times have 12 vlan interfaces on my containers and the way i do it now, i trunk on the Hypervisor and so I can only trunk 10 in total per container

How long does this take, how can I know when everything I currently have in no-sub is in enterprise

I don't see that file on any of my servers...

In the latest versions of proxmox what file can I modify with to set the email address configured here. (or what non-gui action can I take)

Just as a followup the only thing required was to have multiple network interfaces - i put 4 using regular gui method

I'm trying to get infoblox server to work on proxmox kvm. The Infoblox setup calls for somethign like this: <interface type='network'> <rom bar='off' /> <source network='MGMT'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>...

Hi, Currently my host has something like 40 interfaces, all configured to be on the proper vlan with no ip address. My containers bridge these interfaces and have the proper IP address (no vlan configuration inside the lxc container) The problem is that I can't "share" more than 10 interfaces...

For me this error was due to being on the wrong kernel

I'm considering building out a cluster of promox machines between several datacenters. I read that latency is key for corosync. I ran a little test and I got these results from machines that would be in approximately in the same locations as the cluster members. Host is up (0.0039s latency)...