Recent content by MeneM

Yeah I guess this makes sense indeed. local storage is not a logical destination to "cluster-wide/shared" kvm templates

Ok awesome, and I see the resulting clone is on the same NFS share as the template? I think that is the thing, I can get that to work as well, but I want to go from the NFS share to the lvm-thin or zfs or even local folder of any node. But that looks awesome, thank you very much for the example!

Do you mean the container templates? Those are fine indeed. I mean the KVM type templates. even though we save them on shared NFS storage, only the node that made the templates "sees" them. As in: the config is in /etc/pve/ but not accessible to the rest? Do you perhaps have an example?

To me this seems strange. So each node needs to have these templates installed? And also with unique VMID's? Then what is the point of making templates when they need to be unique on each node?

Proxmox VE is used in a lot of IT-lab's (Because they do not get the funding to set it up like the rest of the environment for instance.) Because of that, beeing able to quickly reinstall virtual machines (Using cobbler and koan), together with the price of Proxmox VE, it will be a lot easier to...

I don't come here often. Which is because your software simply ROCKS! I must thank you so much for making my life so much more simple! (IT-wise)

Found it! I was installing ssmtp together with the upgrade. Aparently I cannot use ssmtp only postfix. or pve-manager will be removed during the upgrade.

Hi All, I'm having some issues after just upgrading: Restarting web server: apache2Syntax error on line 20 of /etc/apache2/sites-enabled/pve.conf: DocumentRoot must be a directory I've tried running "pveversion".. But it's gone these days? There's also no /usr/share/pve-manager folder...

Without much testing: I can confirm it works now.

I can confirm this issue. I have a ubuntu openvz that has a bridged interface. and on every reboot it looses it's /etc/network/interfaces content. It does help if I put the content in /etc/network/interfaces.tail. But it took some searching before we saw this ;-)

This time around I was clear I think, the firewall is inside a KVM, and the openvz VM's need to use IT as the default gateway, not the hardware node's default gateway. But I think I can solve the whole thing by using shorewall on the node itself. It's probably safer too than using a Virtual...

Yeah.. I'm not beeing all too clear am I ;-) Allright, let me try again... The hardware node has got two network interfaces. One is attached to the Internet and the other is not connected in anyway. I want to only attach the hardware host (proxmox itself) to the Internet and 1 KVM machine...

Ah that's good, I can influence routing ;-) Situation sketch: vmbr0 = 172.167.67.2 and has the default gw to the internet at 172.167.67.1 vmbr0 = 10.10.0.1 and all the vm's get this network (10.10.0.2, etc.) When a VM tries to do something on the Internet, it will be routed out through the...

Hi all, After installing Proxmox, all the openvz VM's I create get a venet0 interface. Which is ofcourse normal. These venet's are linked to the vmbr0 setup within Proxmox. I've created a vmbr1 next to it, and would like to be able to link all the venet's to this new vmbr1. (vmbr0 has got an...