Search results

Try again using 1 CPU and the e1000 network driver

The rule of thumb is, more RAM the better. You could run guests with 128MB RAM, but you will start to swap to disk fairly quickly if the VM is busy. A proxmox server with 1GB RAM is going to be very limited in the number of guests it can support, especially if your using KVM rather then OpenVZ.

If the VM has an internal IP address and you are accessing the FTP service via the internet, you will need to specify a port range for PASV commands in the ftp configuration and forward the range to the IP of the VM. For proftpd.. http://www.brandonhutchinson.com/passive_proftpd.html For...

http://downloadmirror.intel.com/17906/a08/PROXP.exe Save in C:\, power down the KVM, delete the realtek ethernet card, add the e1000 and power up. Run the PROXP.exe to install the new driver.

I haven't tested for 7.2-RELEASE, only 7.1-RELEASE. /boot/loader.conf should contain a couple of other lines as well which should not be removed, the line I posted above should be added to the end of whatever is there by default when you install.

Agreed, but I believe the real strenght of this project is the intergration of both virtualization technologies into a single product. Dropping OpenVZ support would be a big blow to the project and userbase in general. Is it possible to upgrade KVM to the newest release (KVM-88) under 2.6.24...

Er, not sure what happened there (i'm no freebsd expert) but it shouldn't of caused that problem. Did you leave all the other lines in /boot/loader.conf and just add it as a new line at the end of the file? No spaces/etc? Maybe try removing all the custom clock settings you have implimented...

Tom, What about providing 2 kernel choices during the installation process, one defined as KVM/OpenVZ (2.6.24) and the other as KVM only (2.6.30+)? I would hate to lose the ability and functionality of OpenVZ VMs, but if these limitations were selectable during the installation process it...

Try adding this line into /boot/loader.conf and rebooting, it solves timing issues under pfSense (FreeBSD 7.1)/KVM for me.. hint.apic.0.disabled="1" Let me know if that helps, cheers

My guess would be faulty RAM, bad power/power supplies or heat issues. Running lots of different hardware setups with different KVM/OpenVZ guests with no issues. Try some testing tools like memtest86+ or mprime

I use pfSense as well to protect all our proxmox servers, runs great under KVM and very small footprint. Highly recommended!

Do yourself a favour and pick up an Intel gigabit NIC (PCI or PCI-E), they are supported out of the box and much less hassle then using flaky onboard network controllers. Having a reliable/well supported NIC for virtualization is extremely important, don't cheap out on this important component.

Er my mistake, there was a configuration error with our squid proxy that was caching the file and thus showing the problem. Running 'apt-get update -o Debug::Acquire::http=True' showed the error. Cheers

No problems pinging download.proxmox.com or fetching Packages.gz via wget.. pve01:/backup# ping download.proxmox.com PING download.proxmox.com (92.51.129.73) 56(84) bytes of data. 64 bytes from lvps92-51-129-73.dedicated.hosteurope.de (92.51.129.73): icmp_seq=1 ttl=51 time=116 ms 64 bytes from...

Actually, I only get this on one server and not the others.. What could be causing this error?

Hello Tom Running apt-get update this morning it is erroring out on a Hash sum mismatch.. apt-get update Hit http://security.debian.org lenny/updates Release.gpg Hit http://ftp.ca.debian.org lenny Release.gpg Hit http://download.proxmox.com lenny Release.gpg Ign http://security.debian.org...

I've been using 3ware 9650SE's with great success. No problems at all and with the 3dm2 utility installed after the proxmox installation it performs regular disk checks and sends email notifications in case of array problems. Been using the 4 channel version with 4x1TB disks and also 4x300GB...

Not bad, here's 4 300GB Western Digital VelociRaptors in Raid10, hanging off a 3Ware 9650SE with read/write cache enabled. mepve02:~# pveperf CPU BOGOMIPS: 43182.54 REGEX/SECOND: 1029900 HD SIZE: 49.22 GB (/dev/pve/root) BUFFERED READS: 242.13 MB/sec AVERAGE SEEK TIME...

http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny Might just be easier to start fresh from the CD installer..

No it is not there by default, just 'apt-get install ethtool' Cheers