Using the latest 3.0 release seems to have fixed the USB problems on my end. Also make sure that you have updated the bios to the latest release. Let me know how it goes.
Hello All,
I looked over all the forum posts but couldn't get a firm answer to what it is that is causing the problem. I am running a 4 node cluster, and all nodes have no problems or errors when visiting the web-interface except for one. I've re-installed twice once with LVM and once with EXT4...
I have multiple servers with the same card and I found that balance-TLB and LACP work fine for me. LACP will need you to setup your switch first (bond ports), then setup proxmox in LACP mode.
As a wish for the wonderful day today, I would love to see some appliances for Hadoop and Mapreduce in either as an openVZ template or KVM image. If anyone has any experience with creating templates, i'd love to help out and learn how to create them from scratch, and work on creating some images.
Check to see that your switch allows or has enabled multi-casting, as that is what the cluster uses to communicate with other nodes. There is a post here that will help you:
http://pve.proxmox.com/wiki/Multicast_notes
As per the docs that Tom pointed out this would be the short of it:
1) Install Proxmox 2.0 on node1 and node2
2) On node one after all updates and upgrade have been done, reboot the node.
3) Let's say Node01 is the master node, you will run this command:
pvecm create zeus
you will then see...
I have faced the same issue last week and I know how utterly frustrating it is. All I did was safely remove a node from a cluster of 4 nodes using pvecm delnode. That worked but the I noticed that all my nodes had lost quorum, and couldn't figure it out for the life of me. Now what I did notice...
You gotta think of VMBR0 like a virtual switch, so if you bridge eth0 with VMBR0 is like plugging eth0's cable into a virtual switch which is represented by VMBR0.
From what I see above you have made 2 bridges, and both of them carry the same IP address. If these both feed into the same main...
Did you install proxmox as a server or did you installing desktop packages as well? Cloud be that your xorg.conf file is missing:
http://crunchbang.org/forums/viewtopic.php?id=15374
http://forum.proxmox.com/threads/5046-Error-kvm-cpu0-unhandled-wrmsr-amp-unhandled-rdmsr
You also might want to check and see how you are attaching your storage and wether its coming from NFS or not. I have been having the same issue here and there with my NFS attached storage. I've had my...
Tom,
I thought about this for a minute and I think that the best approach is For Ex:
1) User creates VM or CT, and on the last tab have an additional comments field that is editable. These comments can be stored locally within the proxmox system so that when you do step 2 --->
2) Once a...
So I have 2 clusters running proxmox and have 4 different mounted NFS nodes for backing up across 3 different places. I run into this issue often when I've deleted and backed up the wrong VM to the wrong NFS node and lost that VM. Having a more semantic method of defining the backed up VM would...
I find that with multiple NFS shares attached to nodes during testing, it becomes confusing with the way that Proxmox handles the naming of the backups. For example, I have a VM named "Foo" that I want to backup. Instead of Showing "Foo" and a timestamp, it shows the VMID. With multiple NFS...
you can transfer the VM from one local disk to another using the "backup and restore" features that proxmox has. When you restore a back'd up image you can select the local disk. http://www.youtube.com/watch?v=ablnh_c17Ow
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.