Search results

Sometimes you need a VLAN interface on a HN itself. Which wasn't possible to setup from web interface in Proxmox 3.4 at least, you have to configure it manually. And no, you don't generally need a switch with 802.1Q VLANs to work with VLANs as "dumb" switches will pass VLAN tags without...

Sorry, didn't knew they've added VLAN management to iproute2. Always used vconfig for this as most of the guides make use of it.

Hello. Since the Proxmox 4.0 release the vlan package are removed and marked as conflict with pve-manager and proxmox-ve packages. As far as I've read on forums the 4.0 uses it's own VLAN "manager". But could you please explain how it's done? Is it kernel library calls directly from Proxmox VE...

Also related to http://forum.proxmox.com/threads/22866-Gateway-inside-VM and https://bugzilla.proxmox.com/show_bug.cgi?id=733 Something network-related was terribly broken since pve-kernel.2.6.32-41-pve.

Unfortunately I do use OpenVZ extensively. I'm not ready to migrate to LXC and besides 2.6.32 worked just fine before those recent updates.

Proxmox 4.0 was officially release only few days ago. And the kernel 3.10 for pve 3.4 aren't supported and considered experimental.

Hello. Bug #733 are related to this issue. Seems like we have a different pve-kernel-2.6.32-41-pve on repositories with different release dates, sizes and hash sums. /etc/network/interfaces: # network interface settings auto lo iface lo inet loopback iface eth0 inet manual iface eth1 inet...

After upgrade to pve-kernel-2.6.32-41-pve I cannot set bridge offloading options anymore: # ethtool -K vmbr0 tx off Could not change any device features

Any comments from ProxMox devs on this? :rolleyes:

You can always set them manually. E.g.: ifconfig ethX up brctl addbr vmbrX brctl addif vmbrX ethX ifconfig vmbrX 192.168.X.231 netmask 255.255.255.0

Yes, I meant KVM. My mistake for messing that because I use both OpenVZ and KVM. But this is about KVM. My configuration is quite complicated. This is why I didn't posted it at first. Decided I could keep it simple and probably someone had faced similar issue. But I've tried to flush firewall...

https://pve.proxmox.com/wiki/Network_Model

Actually you don't need to route, you need to bridge them. I.e. you need to set those failover IPs on the VMs, not on the physical nodes. Remove those aliases from host nodes (to avoid IP conflicts). Then from the proxmox create a bridge device vmbrX, attached to eth0 (or what your physical...

I've faced some strange behaviour I couldn't resolve yet. Probably I'll figure it out soon, but will post it here in case anyone can answer faster than I handle it myself. I'll simplify things a bit to keep it easier to understand. I have node with recent Proxmox running, call it pve-node1. eth0...

Ouch... I hope they could keep OpenVZ if they made it into the new kernel version soon. Seems like this is a main reason to migrate to LXC, because it lacks some features of OpenVZ like vSwap, ploop and live migration. At least it was last time I've checked.

Ok, after adding 3rd node an alias as node-stor1a and adding this to the altname of the clusterconf seems like the 3rd node are finally joined the cluster. But now I'm getting a few similar messages in /var/log/cluster/corosync.log 2-3 per second: May 08 15:38:22 corosync [TOTEM ] Automatically...

No. In Linux traffic shaping (limit) is controlled by 'tc' utility from iproute2 package. Refer to a LARTC for additinal information: http://www.lartc.org/

Not really, except for try other PC/OS.

Where exactly do you want this? Physical node, CT or VM? The short answer is that proxmox doesn't have a builtin options for that in the interface. Just use any traffic shaping script for tc for that.

What? Proxmox have both INPUT and OUTPUT rules under it's firewall settings: No, this goes to iptables FORWARD policy which are set up individually for each VM under their settings. You don't have to. Proxmox will automatically open the ports it needs for its operation. You just have to add...