Search results

Yes, the word "templates" is there at the end. I'm asking about your templates and not about the architectures. You've just helped me decide not to buy Proxmox licenses (would've been 5) and move to something else. At least I can thank you for that. Ridiculous.

Tom, crikey - I'm not an idiot. Where in my post do I ask what the difference is between i386 and amd64? In case there was too much cruft, the questions again: 1. Outside of a need to run 32-bit compiled applications, is the only preference for i386 templates because for most standard uses...

Come on, surely people must want to know answers to these questions?

Howdy I have spent about 3 hours scouring this forum, the OpenVZ documentation and related projects trying to find some definitive information on what exactly the difference is between running an i386 vs a x86_64 template in a container. Below is a long winded background to the following...

Howdy Strange issue at Hetzner. I have 3 servers with them. 2 perform at 100M both ways (EQ4 and EQ8) and this third and newest one (SB74) is 100M both ways when booted on the Debian-based Hetzner rescue system and 100M in and 30-35M out when booted into Proxmox 2.3 (installed from ISO)...

Got it to the point where I can suspend by running pm-hibernate (but proxmox shuts the VMs down - which is ok). Will investigate acpi to see if I can get it to suspend on pressing power button.

Hoppel I'm running a HP Microserver which has an AMD processor in it. When I had Debian Wheezy installed on it before I could just hit the power button and it would hibernate - now that I have installed Proxmox from ISO it does not. Will have a read and give it a bash. Thank you :)

Howdy Did you find a solution to this? Also your OMV installation - did you consider installing it on the host instead of in a VM? I'm thinking of doing that if they can co-exist on the host that would be better than consuming the power of a full KVM. Pity it can't work in a container.