Search results

The real problem with the post was that I have an old version of Chrome. Fixed now. Problem with servers remains.

I swear this had line breaks when I posted it.

I have a 2-node HA cluster set up as per http://pve.proxmox.com/wiki/Two-Node_High_Availability_Cluster. When I first bring the servers up, clustat will report both nodes and the quorum disk all online. However, if I reboot a node, it can not connect to drbd on the second node. The second node...

I found a working openvz.conf on http://blog.bodhizazen.net/linux/ubuntu-10-04-openvz-templates/ This says it works on 10.04, and I am using it successfully on 9.10. I wouldn't assume that nothing else has broken in 10.10 though.

init.log: starting init logger init: hwclock main process (24) terminated with status 77 init: openvz pre-start process (22) terminated with status 32 mountall: root filesystem isn't mounted init: mountall main process (26) terminated with status 1 General error mounting filesystems. A...

# vzctl start 113 Starting container ... Container is mounted Setting CPU units: 1000 Setting CPUs: 1 Set hostname: **** File resolv.conf was modified Setting quota ugidlimit: 0 Configure veth devices: veth113.0 Adding interface veth113.0 to bridge vmbr0 on CT0 for CT113 Container start in...

1.7 server has been updated to a 2.6.32 kernel: # pveversion -v pve-manager: 1.7-10 (pve-manager/1.7/5323) running kernel: 2.6.32-4-pve proxmox-ve-2.6.32: 1.7-30 pve-kernel-2.6.32-4-pve: 2.6.32-30 pve-kernel-2.6.24-11-pve: 2.6.24-23 pve-kernel-2.6.24-8-pve: 2.6.24-16 qemu-server: 1.1-28...

This is Ubuntu OpenVZ containers. I can double check later, but I'm pretty sure the server was set up with a 1.7 install disc, roughly a month ago. Just about everything on there came from the 1.5 machine, so I can move stuff off and upgrade it to the 2.6.32 kernel if you think that will help.

I'm trying to migrate all of the guests from a Proxmox 1.5 machine so it can be upgraded. Debian guests have had no problems, but there are a couple of Ubuntu guests which have a problem. After migration, nothing is started except for init. Services can manually be started, but still do not...

"shutdown -h now" will halt the server. For reboot, you need -r. Linux also has "halt" and "reboot" commands as a shortcut.

It's not the only host on the network, so no.

I'd like to be able to set the IP from Proxmox, rather than within the guest. So I'm hoping to figure out to use venet for the additional subnets.

I have a class C, which I have divided into multiple subnets based on function. The proxmox server itself is in one of these subnets. I am trying to configure it so I can use venet on OpenVZ machines in other subnets. As near as I can tell, this means adding IP's in the other subnets to the...

I believe I see now. So my best option ifor now is to have one partition for openvz and one for KVM.

I'd like to set up ProxMox servers with shared storage, to make migrating faster, and failover possible. If my understanding is correct, this is possible with KVM, but OpenVZ doesn't support this. So, is it possible to try OpenVZ on DRBD anyway? I know that migrating from the webui won't...

I've come up with the attached script to spawn (and respawn) VNC listeners for OpenVZ containers. The script assumes each one listens on 59XX (for 100-199 of course). Usage notes are included at the top of the script. Usage: Start with: nohup vz_vnclisten <VMID> & Stop with: kill `cat...

Where can I find that?

In proxmox 1.4, vncterm has a '-rfbauth passwd-file' option, with a note saying to use 'storepasswd' to create the password file. However, there doesn't seem to be a 'storepasswd' program, nor does the -storepasswd option seem to exist for vncterm. So, how can I create the passwd file?

That's a shame. I was hoping to be able to migrate the VM's to the newer machine, and then upgrade the older ones. Fortunately, manual migration looks easier than I thought. I stumbled across vzmigrate (and friend, qmigrate).

I have two servers which I'm trying to set up as a cluster. server1 is pve-manager/1.3/4023. server2 is pve-manager/1.4/4403. I have created the master on server1 (which contains all of the VM's), and attached server2 as a node. However, 'pveca -l' run on server1 gives the following for...