Search results

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! :)...

Oh, and I love your username. Do you use that everywhere or is it a happy result of a username generator? Sent from my HTC Glacier using Tapatalk 2

I'm sorry I can't help you but thank you so much for sharing your experience! I was starting to seriously question myself with all the trouble I've been having. Sent from my HTC Glacier using Tapatalk 2

Well now that's confusing. The Proxmox Wiki clearly states: So your comment about manually formatting the partiton is curious. Are the steps actually: Create LUN on your SAN Add iSCSI through Prox web interface: iSCSI_LVM All Nodes, Enabled[y], Use LUNs Directly[n] Drop to cmd and do...

Thansk for being gentle ejc. I know I'm missing the point, which is why I'm asking for help. I now understand that I'd need an NFS to store CTs, and that I will only be able to add VMs to LVM, which is why I clicked "Create VM" instead of "Create CT" I think my question is: how do I make the...

Very old thread but same issue. Current thread is here: http://forum.proxmox.com/threads/19863-Adding-iSCSI-storage-to-HA-cluster

Be sure you are specifying the node by the name as defined in /etc/cluster/cluster.conf, not its DNS name or IP address. The correct command for the original post is: fence_node KSCLOUD-K1 -vv The second poster needs to use the value identified in the above file located on this line...

Thanks for the explaination. When attempting to create a VM and adding the storage, it comes back with TASK ERROR: create failed - no such volume group 'vmdisks', which is why I don't think I added the storage correctly. The image in the linked guide above suggests that the selection of the...

ssh works fine on iDRAC 7: fence_drac5 --ip="10.1.6.7" --username="prox-a-drac" --password="***********************" --ssh --verbose --debug-file="/tmp/foo" --command-prompt="admin1->" --action="off" BIOS ver. 2.1.3 Firmware: 1.56.55 (Build 05)