Search results

I didn't get a chance to investigate further, but after restarting BOTH nodes it's back to green again. I'll troubleshoot more next time it happens again. Thanks!

As per the title, I'm not sure why the Node is red. Any ideas? Here's some output (if it helps): root@pn:~# pvecm status Version: 6.2.0 Config Version: 2 Cluster Name: clu5ter Cluster Id: 12868 Cluster Member: Yes Cluster Generation: 24908 Membership state: Cluster-Member Nodes: 1 Expected...

It's a pretty big network, so I have no idea who or which machine has that IP. Hopefully I can reclaim it, else my Proxmox cluster will bjork and I heard it's quite difficult to reconfigure the cluster. :( Thanks for the tip about the IP ranges, I'll keep that in mind the next time I do a...

I have DHCP, would removing the 192.168.42.40 from the lease help? I'm also doing bridging and vlan tagging on the proxmox box, I would if that also has anything to do with it. edit/update: It's looking more like it's another box with duplicate ip on the network as I turned off the proxmox box...

It's physical, 1-Node of a 2-Node Proxmox cluster. Here's the ifconfig: eth0 Link encap:Ethernet HWaddr 84:2b:2b:c2:5e:7a inet6 addr: fe80::862b:2bff:fec2:5e7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13926...

I don't think I'm doing any sort of teaming on the Proxmox node, physically the box has only 1 NIC.

Oct 1 17:24:37 freenas kernel: arp: 192.168.42.20 moved from e0:69:95:90:9c:aa to 84:2b:2b:c2:5e:7a on bge0 Oct 1 17:39:47 freenas kernel: arp: 192.168.42.20 moved from 84:2b:2b:c2:5e:7a to e0:69:95:90:9c:aa on bge0 Oct 1 17:40:45 freenas kernel: arp: 192.168.42.20 moved from...

I'm more interested in getting Aero to work.

Mostly KVM, but I do use VZ containers.

There's a 2.x cluster guideline available. http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster

What determines the console window size and is there a way to make it bigger or even full screen?

I think it also depends on the environment; since I have a small, test lab environment, I don't mind using NAS. In this case, I'm using FreeNAS which has the added features of live migration and ZFS. Performance still seems on par with local storage. No complaints here.

Would have to do more testing, but so far creating a VZ container from the template works. Give it a shot.

You'll have to click on 'Remove' first (don't worry, it won't actually delete the disk), and then you can click edit to change it to virtio.

The bad node is still listed.

One of my nodes in the cluster just died and it's affecting the remaining nodes and the cluster. Is there a way to forcefully remove that bad node from whole cluster? or is there a way to recreate the cluster with the remaining good nodes? Here's my current config: proxmox = master node p2 =...

In addition to various OpenVZ containers in Proxmox, I'm running some guest OSes in KVM (Ubuntu and Windows 7). Ubuntu runs efficiently in KVM, although not as effectively as CT, but that's to be expected. Now on to Windows 7, it seems to be resource hungry and taking up about 95% of my...