Search results

I'm wondering what is a realistic limit for using a NAS sever against a Proxmox cluster (or two). I currently have a 16TB NAS (8 drives) server running freeNAS. I have two Proxmox clusters, each with about 50 VMs spread across 13 nodes. The NAS storage has an iSCSI initiator for each...

Thanks! So it looks like Proxmox-ve is GPL-2?

Hi all, I've got two clusters each with over 15 nodes, but I regret to say I've never looked closely at the EULA. Now I'm getting questions about it from others. Where do I find a copy without trying to install a new node? Is there a copy either on the web or in a directory on one of my nodes?

I had this issue on one of my nodes after the upgrade to 4.4. I tried using system restore CD, but no matter how many times I reinstalled grub, I got the same issue. I ended up reinstalling the node and using the online documentation to bring it back online in the cluster.

Now a few months later, and after looking at the link above, I'm ready to try to get this working. However, I need to understand some things from that thread. This is going to get long, so please bear with me. First, it looks like I need to turn off the vlan-aware option on interfaces for...

Thank you! I can't believe I overlooked that file. That took care of the problem.

I found the database in /var/lib/pve-cluster where that config file is generated. Using the sqlite3 cli command, I can see it with: select data from tree where name='corosync.conf'; However, I'm afraid to just modify the database, and I'm not sure how that database gets propagated around the...

I have a node in my cluster that somehow ended up with the wrong spelling in /etc/corosync/corosync.conf. I have tried changing the file itself, but clearly it gets regenerated at some point. The node entry looks like this: nodelist { node { name: bagh nodeid: 2 quorum_votes: 1...

Thanks. I'm working on this in the background with other tasks. That's a page I've been looking at, but not been able to get the time to move ahead. I also moved my interface from openvswitch back to linux bridge. It looks like openvswitch is still working on patches to get QinQ to work.

Greetings all. I have two VM guests that communicate with each other using various VLANs, which requires a bit of trunking configuration with the intervening network equipment. Using QinQ, what I would like to do is configure the system so that ALL outgoing guest packets get tagged with an...

Of course. It's one of the files I need to add to my notes to make sure it gets changed. I missed it before because I wasn't using iSCSI until now.

No, a cloned host image.

I'm guessing it's because the newer nodes were made from a disk image of one of the other nodes. That would explain how they had duplicate names...I'll have to add it to my list of things to modify when a new node is added to the cluster.

cat /etc/iscsi/initiatorname.iscsi I guess more properly called the InitiatorName. I should have paid more close attention to the FreeNAS logs...it was telling me the problem all along.

Sorry, been on PTO for the past 3 weeks. I'm not using lxc on iscsi lvm, these are all kvm. So far what I found is that the three new nodes all had the same iSCSI initiator ID. I've changed them so they are all unique (the initiator IDs were already unique for the other nodes) and that seems...

I have a cluster that was originally set up with 5 nodes. Each node has a management interface, as well as a private network for corosync to communicate over. Over time I added three more nodes to the cluster and all seems to be working. I have now configured iSCSI on the datacenter as...

Thanks! That worked as expected. After editing the config file for the trunks, the interface gets added in native-untagged vlan mode. I was trying to avoid naming the vlan's specifically and instead letting it trunk any vlan to the guest, but the default vlan mode doesn't support that. At...

Ok, I've read over the different guides for OVS bridges with vlans, but I can't seem to get my problem solved without resorting to the CLI, which I don't want to do after my system goes live. I have a VM guest that is essentially a router, and normally expects the hardware it is running on to...

Good deal. I currently only have one node where this is needed, so I can get by with the older kernel until the new one is released.

I just filed bug #983: https://bugzilla.proxmox.com/show_bug.cgi?id=983