Search results

First of all thanks for your suggestions. Most of them is what I do if possible. Just for the records. After testing over and over again the solution is a simple hardware failure. The sda drive sometimes produces bad host memory on heavy write (yes, only write) load. That's the reason for all...

The server just crashed again but this time I found the following inside syslog after reboot:

This is just an information, I don't think my information is helpful enough to locate the problem. But since the KVM live backup is a quite nice feature and this is a call for tests just my notes. I've installed proxmox 2.3 beta yesterday and tried the new backup system. It seems to work fine...

Today I'm trying to use virtio-rng inside a VM (debian squeeze). I just could load virtio-rng without a problem, but it doesn't create the required /dev/hwrng device and therefore the rng-tools refused to work. Running a mail server with TLS support inside a guest with enough random entropy...

I've just reinstalled the system today morning. But I will note the tipp with the certs update. And yes, I know there's no master anymore, that why I've added quotes around master in the first post. Are there some other hints about what to do when there's a problem with the cluster...

I just figured out that one of my systems is also affected. It behaves like your no. 3. The mainboard is a supermicro X7DWU. Downgrading the kernel topve-kernel-2.6.32-11-pve, reboot the system -> anything is fine again. I've noticed that the nic hardware is somewhat different but both use the...

Back in the good old days of proxmox 1.x recreating a cluster configuration was really easy. Yesterday I start playing with proxmox 2.1 and start creating a cluster on host A. This works without any problems and I tried to add host B to the cluster. But host B has already some VM running and I...

To use KSM and since I didn't use openvz is run kernel 2.6.35.

I think virtio support is somewhat broken. I also had to go back to e1000 driver to get a stable system. Just search for virtio and windows. Or look here: http://forum.proxmox.com/threads/7318-WinXP-virtio-proxmox-1-9-gt-crash...

Your problem seems very common to me. I have two proxmox systems with several ST32000644NS drives (all with firmware SN11) with supermicro mainboards. Both systems are running md softraid (level 1 raid) with LVM. Randomly I get drive errors while the promox backup task (with LVM snapshots) is...

As fas as I know there should be no difference. Hmm, or wait. Maybe there's a new/changed configuration option with newly created VM? Here's my configuration for an old VM that crashed frequently. name: winxpsp3 vlan1: virtio=52:54:00:xx:xx:xx ostype: wxp memory: 512 onboot: 0 sockets: 1 cores...

I'm glad to hear that I'm not the only one. As you described my solution was to disable virtio and use a realtek 8139 nic too. I don't think that proxmox is the real source behind these problems but proxmox uses the latest available kvm+qemu. And I think there's a regression that causes this...

I'm sorry but I didn't have something really useful but I think your thoughts about "something with version 1.9" seems right to mee. Did you take a look at the thread http://forum.proxmox.com/threads/7330-VirtIO-Win2003-warnings-errors-reboots ? I can't see what kind off network drivers you're...

Do you use the virtio nic drivers too? You didn't mentioned that in your message but I assume you don't. It may be worth to just try to installed the virtio nic drivers and see if you get wired behaviour with these drivers too. Since my trouble is related to the virtio nic drivers.

Is there anyone else besides fortechitsolutions with virtio trouble? It would be nice if someone could at least confirm "no trouble here with winxp sp3 + latest virtio + proxmox 1.9". I don't know what to try next ...

Hmm, this sound similar to my problems here: http://forum.proxmox.com/threads/7318-WinXP-virtio-proxmox-1.9-gt-crash The erratic behaviour is not exactly the same I get here but close enough I think. You say you're now using promox 1.9 but your pveversion show older version than I would expect...

Hello, I think there is a problem that is related to Windows XP (current SP3 with current updates till 2011-10-19) using virtio using the latest drivers from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/ and a currrent proxmox 1.9. Using a virtio nic results in a BSOD or a...

Indeed such a block level cache would be nice. The solutions offered by Adaptec and LSI are not that "hot" as a single SSD and something like linux taking control (more knobs to play with).

Hello Dietmar, your new kernel will work fine, No boot problem, the driver seems to work. I will run a few test VM for some days and will report back. Many thanks for the quick fix.

Just did the update to proxmox 1,9 on a test system but our scsi controller (driver GDTH) driver is missing now; xxx:/lib# dpkg -l | grep kernel ii pve-kernel-2.6.32-4-pve 2.6.32-33 The Proxmox PVE Kernel Image ii pve-kernel-2.6.32-6-pve 2.6.32-43...