Search results

f089e52c10192ec211350c417dd58586 /usr/bin/kvm md5sum is same in both cases. My best guess is that the check simply isn't being done on 2.6.35 but is being done on 2.6.32. Since the kvm binary is dependent on the kernel for a lot of what it does, it's not unreasonable to expect a difference...

I can reproduce the issue on multiple systems. How to reproduce: 1) install minimal Debian 5 x64 with default partition layout. 2) install Proxmox with 2.6.35 kernel following http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny 3) create guest vm with proxmox web interface, specify...

dpkg -l pve-qemu-kvm Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description...

We currently are using Proxmox with the 2.6.35 kernel. Upon becoming aware that 2.6.35 is no longer supported, we attempted to downgrade a server from 2.6.35 to 2.6.32. Everything seems fine, except for one thing: large VE ID's don't seem to work anymore. Given a node with a VE numbered 123...

http://bugzilla.openvz.org/show_bug.cgi?id=1769 Would be great if the Proxmox team could update their 2.6.18 kernels soon to fix this :)

Can you provide a reference for this claim? I can't seem to find anything on Google about 2.6.26 and virtio issues....

Why not just replace apache + mod_perl with a *very* lightweight webserver that only spawns CGI processes. That way you'd have <10MB for the web server and the Proxmox Perl web scripts would not consume any memory unless they were actually being used (i.e. somebody logs into PVE). How feasible...