Search results

Will the HA feature on the roadmap involve a restart of the machines when switching from one server to another or is it just continuing seemlessly?

Hi, I guess this is a bit outside proxmox, but I noticed yesterday my log was flooded with rejecting I/O. It started a few days ago with this in the dmesg: Feb 9 21:26:36 jango kernel: usb 2-1: USB disconnect, address 2 Feb 9 21:26:37 jango kernel: scsi 1:0:0:0: rejecting I/O to dead device...

You could check your DRIVES write cache by using: hdparm -I /dev/sda In the output of this command you should find something like: Enabled Supported * SMART feature set ... ... Write cache Your HW RAID may have disabled this cache to only use it's own cache (data...

Did you find a solution? We are also running 2.6.24 and need iptables in the containers, so I don't want to go for the recommended 2.6.18 unless this is working correctly. Bo

I only see a start entry for the backup in the syslog when running a planned backup from the webinterface. Running it manually it exists like this: vzdump --node 1 --snapshot --storage backup_test --mailto <email> 101 mount.nfs: 192.168.0.120:/home/bo/proxmoxtest failed, reason given by...

I tried mounting a NFS share using the webinterface - only problem now is that it fails silently. If I run vzdump manually I get an error message regarding the NFS share, but it does not send and email. Minor detail ;-). Now I'll just have to add NFS share to the Windows server. Didn't know...

See this post regarding big disks: http://www.proxmox.com/forum/showthread.php?t=2839

We recently had a (planned) electrical cut. We are using a cifs share for backing up the VMs but the proxmox server was online before our Windows server. Therefore the cifs share was not mounted during boot. The result was that the backup was written to the proxmox system disc. Is there a way...

I'm curious about Adaptecs MaxIQ concept of using cheap SATA disks in RAID10 and adding a single SSD disk for cache. Has anyone tried this with Proxmox? They have some nice figures at their home page, but I'd much rather see a real-world benchmark. Thanks in advance, Bo

I'm thinking about buying a P55-based system for myself and I might as well Proxmox it. Did you solve this or find the cause for the trouble?

Have you tried the latest kernel + kmod-kvm from the test repository? http://www.proxmox.com/forum/showthread.php?t=2591

I finished testing compiling over the weekend on the following: 4 Ubuntu 8.04 server i386 2GB RAM, IDE, raw-file, rtl8139, 1 socket, 4 cores My setup is: Intel SR2600URBRB platform 2x Xeon 5520 Adaptec raid controller The VMs have been running without a problem for nearly 5 days of stress...

34 hours of compiling without a hiccup. I've added two more machines to the test and will let them run over the weekend.

The more testing the new kernel and kmod-kvm the better ;-). See http://www.proxmox.com/forum/showthread.php?t=2591 for the upgrade procedure.

Are you running the latest 2.6.24-18 kernel from pvetest repository?

First test results: VMs: 2x Ubuntu 8.04 server i386 2GB RAM, IDE, raw-file, rtl8139, 1 socket, 4 cores So far so good, 10 hours of intensive compiling on both machines without any trouble. Continuing the tests for the rest of the week. I'll raise the load by adding two extra machines when we...

I loaded the new kernel and it seems ok so far. I'll try put some stress on it tomorrow. I noticed the following when starting OpenVZ machines: Nov 17 18:16:03 jango kernel: ioctl32(mount:5639): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bfee8798) on / Nov 17 18:16:03 jango kernel...

Is there a safe way to downgrade again if it does not work correctly? The server is used for production now, but we are only dependent on openVZ machines.

Apparently it does not narrow down to Nehalem based machines: http://sourceforge.net/tracker/?func=detail&atid=893831&aid=2351676&group_id=180599 Someone writes about kernel 2.6.31-rc6 solving the problem. Are the 2.6.31 KVM patches backported to Proxmox 1.4? If someone is not running...

Just to mention it if anybody else encounters the same problem I think I found the thread on the KVM bugtracker: http://sourceforge.net/tracker/?func=detail&atid=893831&aid=2351676&group_id=180599 Judging from some of the replies the error seems to be multicore related - possibly solved in...