Recent content by curlingcanteen

This makes a lot of sense to me. And to avoid a collision between two VMID's, make them UUID's. It's not sexy, but solves the problem. vzctl enter 66b026a3-8d75-46e0-9564-279878059e79 root@66b026a3-8d75-46e0-9564-279878059e79#> _:)

I have a silly question for you Joncak: did you already add the new 'hardware' to the VM through the GUI? What's the result of: ip link show

This is written very confusingly. The word only implies one method (in this case, internal). I think the word you're looking for is either? I think I understand the first two cases. The third strikes me as odd since when creating a venet there exists no method to define a netmask. How does the...

Okay thanks. So what is the OpenVZ standard way to add eth0 and allow traffic to use it as the primary gateway device?

after reboot my routing scheme breaks: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.0.110 172.16.0.109 255.255.255.255 UGH 0 0 0 venet0 10.24.106.0 0.0.0.0 255.255.254.0 U 0 0...

The documentation here: https://openvz.org/Common_Networking_HOWTOs#Venet states: Why would the host be able to ping the venet? I thought the idea of a venet was to provide connectivity between CTs but not between external networks? Second (related) question: Is there any way a venet IP could...

I don't know what I was thinking. Thanks again for straightening me out, spirit!

That's what I thought, but this didn't work. Thanks for the link!

I installed CentOS 6 Standard (also tried with minimal) via a template and cannot seem to enable eth0. Bridge mode to vmbr0 was selected during container creation, and this is the device info: ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback...

As you were, I'm not clear on how you implemented acidrop's solution. Would you please explain how you got from post #5 to #6?

It pains me to respond to these old threads, but I really dislike unanswered posts. Had the same error, my fix was to edit the NFS share in Proxmox and remove the "Enabled" checkmark. Then from my NAS Administration page, change permissions from "Everyone except root" to "Everyone". Then...

This worked! I think I might have had to reboot all nodes after adding the iSCSI device. It was, but that was my first bit of ignornace. It was quickly explained to me that I'd need NFS for OpenVS containers. Right, but this is a HA setup so I'll leave testing that experiment to others! :)...