Search results

This looks like a network-related issue on your end, not a Proxmox VE problem. You just failed to connect to three completely unaffiliated sites.

Not that big a deal, just drop in a new processor.

I would not expect any troubles running Proxmox VE on that hardware. It's similar to what I'm running Proxmox VE on, except my 3ware is a mere 2-disk mirror rather than a beefy 9550SXU. The 3ware 3dm2 software works fine and your 3ware RAID array should be useable immediately from the Proxmox VE...

You're not looking for hyperthreading, you're looking for "Hyper-V" or "Virtualization Extensions" or something similar. cat /proc/cpuinfo | grep vmx If you don't have vmx listed in your cpuflags you don't have Hyper-V enabled. Same problem the OP is having, his CPU should support Hyper-V, but...

Have you tried updating the BIOS on the problematic machine? Have you tried using e1000 instead of realtek as your NIC inside the KVM?

You should remove ~/.toprc like OP did then :)

Sounds like something for the todo list: Change "vztop" to use ~/.vztoprc instead of ~/.toprc

Your cpuflags lacks "vmx" which means as far as Linux can tell, "Intel Hyper-V" is disabled. Best guess is your BIOS isn't setting it.

You could just pull the cover off and hook up a floppy drive real quick, I do that sometimes. Or put the BIOS updater on a DOS bootable CD that you craft. Nero actually makes an ok DOS boot disk that automatically loads a CDROM driver and mounts your CD's contents as a drive letter.

Why not do a mysqldump (or equivalent for your database) inside the vz container then snapshot backup that container some time after that's finished? That's what I do.

Just update your BIOS and see if it helps, Supermicro and other server/mobo manufacturer first-level tech support is not always competent. Mostly they just want to get rid of you.

Supermicro obviously just googled and copypasted the first thing they found. Your problem is you don't have Intel Hyper-V detected as enabled, their response is to show you a forum post that has nothing to do with your problem...

The first thing everybody is going to say is update to the latest Proxmox VE which provides a later KVM. It's not all that useful to troubleshoot old versions. I have a FreeBSD 6.3 KVM and a Win2k KVM running 24/7 as servers and both have been crash-free.

Yeah, that's pretty normal. It can go a little faster if you can do your backup over a gigabit LAN to an SMB or NFS share.

I believe Proxmox Mail Gateway uses postfix so you could use a command like: mailq | awk ' /^[0-9A-F][0-9A-F]*[^*].*MAILER-DAEMON$/ {print $1}' | sed s/\*//g | xargs -rn1 postsuper -dTo remove, for example, all messages from MAILER-DAEMON. Can also customize the above command to pick out...

I messed around with it for about 20 minutes with KVM-75 with a Win2k server guest and it was all kinds of weird. When I used two CPUs for the KVM, Win2k would take a looooong time to boot and finally even hung the PVE host when trying to restart the guest and required a hard reset of the...

Ah well, as Tom said, it is difficult to use a different version of KVM just because the Proxmox VE kernel goes along with the rest of the packages. I definitely would NOT recommend using an SMP guest in KVM, just stick to using one CPU and enjoy the stability. When I tried two CPUs for my...

Hmm, I can't say my network traffic is really really heavy on my two KVM VMs but they are working nicely. One's FreeBSD 6.3 and one's Win2k Server. Neither are heavily loaded but they are fairly steadily loaded. They are both set to use only one CPU and the host is an 8-way Xeon. So far so good...

If the container does no network traffic for at least a few minutes at a time and then starts up its polling cycle, it may have a delay for the traffic that it tries within the first half-second to each host on the same LAN segment that it has to do arp with. I have definitely seen slow arp with...

I'm using a cheapie 2-port SATA 3ware. Works fine right from the default installation, though I did need to change my I/O scheduler from default cfq to deadline because cfq was causing ridiculous I/O wait times.