Search results

Same problem here, the only solution seems to be to give up ttySX in grub.

You can upgrade straight to 3.0.

Thanks, I thought so. I didn't have any problems with the 3.2 kernel on Proxmox, using only KVM. Obviously, OpenVZ containers didn't work because it was non-openvz kernel.

Just a quick question - does Proxmox 3.0 still use kernel 2.6? I have updated two Proxmox 2.3 servers to 3.0 today and one of them uses kernel 3.2 (3.2.0-4-amd64 #1 SMP Debian 3.2.41-2+deb7u2), the other one uses 2.6 (2.6.32-20-pve). Both work fine... but which one is the right one?

bump

Is there any way to get the init log via API now?

Nope, it's not. You should now see the connections and IP addresses ordered by transfer rate.

Well, the procedure they use is unacceptable. They should handle it on their own and much faster. If you want to find out IP adddresses, here is the simplest method: run iftop. It will hang (SSH connection) when you get attacked but you will have the IP address(es).

You can't do anything about (D)DoS. Data Center should handle that. Good (expensive) ones do, Kimsufi doesn't.

Yes, now you did. I will contribute the code when/if I do that.

I know where to start if I want to contribute, my question was different.

Hi, I'd like to ask if there are plans to implement ALL functionality of command-line vzctl tool into the PVE API? There are many things that are missing in the web interface and the API (obviously), like vzctl exec, setting noatime, changing userpassword, changing I/O priority or adjusting UBC...

Thanks for the info, noone else mentioned that it's even possible. However, I don't think that multicast/VPN was the problem here. I reconfigured everything for unicast and I still get exactly same error as above. I guess it has something to do with SSH tunnel being set up and not the communication.

Any other suggestions?

No, unfortunately it did not help. I also rebooted the whole first node but with no success.

Hello, I have came across another problem, one of very few we had with Proxmox so far ;) We want to setup a cluster and we do it with the use of VPN. It's not exactly as in the ned's tutorial you link on the wiki because the VPN is exclusively for the communication between nodes and everything...

I think this is a definitely wanted feature. Imagine we create OpenVZ servers for clients from specially prepared appliances with a particular software installed. We want to incorporate various task (eg. MySQL root password change) in client area. Without this API functionality it is impossible.

I would really like to see that feature in 2.0. It's unbelievably hard to manage the addresses now - unnecessary trouble.

modprobe kvm-intel solves the issue Additionally I had to enable vmbr0 interface

Hello, I have just installed Promox 2 on a new dedicated server on top of a clean Debian Squeeze. The proper kernel is running (Linux hn2.dondaniello.com 2.6.32-6-pve #1 SMP Mon Dec 19 10:15:23 CET 2011 x86_64 GNU/Linux), all packages are installed. The problem is that VMs don't work, while...