Search results

Doing a bit more research it turns out the 3ware raid card was verifying itself. 8x2TB drives in RAID10 can take a long time. I turned the verification off and the IO delays have gone away. I'm going to test it over the next day and see if it stays low.

No, other than the fact that rebooting the box is a royal pain as it has 4 production email servers running on it. I *can* do it, but will tick of somebody.

That didn't show anything useful. Any way to tell what's killing our I/O besides iotop?

We're having some performance issues with our PVE setup lately, specifically I/O spikes, and I see tons of these entries in the syslog. What is going on with all these child processes starting? May 25 07:21:07 proxwww 28335 Starting new child 28335 May 25 07:21:30 proxwww 28358 Starting...

And by extension be able to install OS X Server on Proxmox on Apple hardware. I've got an xserve with the hardware raid card I would love to install PVE on and run OS X Server in a few VM's. I currently use Parallels server but it's a dog.

I use an XServe G5 as an NFS share and can see it just fine on PVE. I don't use it for PVE however, I use it on my KVM's as a destination backup nightly for our DB files.

We use 1-to-1 nat in our DC without problems. Our firewall supports aliases on the WAN so we just assign the public IP's as aliases and then NAT them to the private IP of the server. Would that work for you?

I see the same thing with CentOS 5.4 32-bit. It's not that big of a deal to me as I'm never using the UI after the initial installation.

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Okay, I'll have to manually remove the the containers. Maybe in the 1.5 upgrade somewhere along the line this could be automated?

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) Sorry, 114 is a container. This is weird, I had 3 KVM's I could not remove before I posted but they remove just fine now. I still can't get rid of the OpenVZ container however. It was a test container and I don't need or want it anymore.

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) pm01:~# pveversion -v pve-manager: 1.5-1 (pve-manager/1.5/4561) running kernel: 2.6.32-1-pve proxmox-ve-2.6.32: 1.5-2 pve-kernel-2.6.32-1-pve: 2.6.32-2 pve-kernel-2.6.24-9-pve: 2.6.24-18 pve-kernel-2.6.24-8-pve: 2.6.24-16...

Do you have a router in front of PVE? Can you run some snmp probes against your VM's?

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) I upgraded to 2.6.32 and after rebooting I cannot remove a KVM: Dec 28 15:21:12 pvedaemon 28189 destroying VM 114 on node 0 (localhost) Dec 28 15:21:12 pvedaemon 28189 VM 114 destroy failed -

I just put one of the Crucial 256GB SSD drives in my macbook pro and the difference is night and day. The weird thing is that the drive is completely silent, there's no vibration at all in my laptop.

It depends, are you going to change it for the sake of changing it, or add info to it like VM network traffic graphs, disk access info and stuff along those lines? I personally use 1440x900 on my macbook pro but have a 24" LCD monitor at work.

I would use RAID 10 for your setup, not 5.

That's what I assume as well, but it's just weird. The nics are set to activate at boot but they're obviously not. Thanks for the confirmation.

This is strange. I have 3 CentOS 5.4 KVM's that were switched from RTL8129 to e1000 nics. Now at boot all 3 of them have inactive ethernet ports and have to be activated manually. I've checked their settings on all 3 of them and the prefs (within CentOS) say that the ethernet port will be...

Actually raid 5 is falling out of favor due to large drive sizes. The time to write parity to the replacement drive is getting too long that having another drive fail in the meantime is becoming greater. I setup a 8x2TB RAID10 array and it's fast, real fast, and since I bit the bullet and...

Just to post that this is now fixed. I deleted the 2 NFS mount points from the /etc/pve/storage.cfg file and did NOT reboot at that time. I drove to the DC about an hour away and by the time I got there the webadmin was fixed, I could log in and both NFS mounts were gone from the storage menu.