Search results

Based on the observation that none of the Windows-based build and test jobs executed on our proxmox cluster during the last day have caused a bsod any longer, I'm inclined to say that changing the bios settings as above resolved the issue. Thank you very much for pointing this out, spirit...

Checked the bios of one of the nodes, which had an American Megatrends bios. Under Advanced-CPU Performance there were a number of values mentioning Energy Efficient, which I changed to Performance. Could not find any other settings that I could relate to the features you're mentioning. Will...

Not quite sure if that will help: all Win7 VMs on all our 5 host machines exhibit this behavior on a regular basis, but all of the Centos and Ubuntu VMs on the same host machines are rock solid. There seems to be some kind of pattern though for crashes that occur during our build jobs: Win7...

After upgrading qemu to version 1.7.1, I already experienced the first crashing Win7 VM again, with a similar kernel trace as described above. Any other suggestions? Cheers, Marcel

Hi Tom, I'll give it a try. Anything in there you suspect might help resolve the issue? Cheers, Marcel

I can give one additional piece of information. Before moving to proxmox we had a single ubuntu+libvirt host running a number of Win7 x64 VMs, running similar jobs as the ones which crash the proxmox-hosted VMs. On these VMs we never experienced these type of crashes. The latest version of the...

We have a cluster of 5 proxmox nodes hosting a mix of Linux and Windows 7 x64 VMs which we use as our automated software build and test environment. When starting build and test jobs from our Jenkins server, some of the build and test jobs on the Windows 7 VM fail very regularly, because the...

Sorry, didn't mean virtio-scsi specifically, just virtio, so nothing special there. Cheers, Marcel

I did some further experimentation today. Originally I had the CPU type set to 'host' for ultimate speed. After I changed it back to default (kvm64), that seemed to resolve the issue. So apparently, the virtio drivers (version 61.65.104.7400) have a problem with the specific host CPU (Intel(R)...

After upgrading one of the servers in my cluster to Proxmox 3.2, all Windows 7 x64 VMs on this host consistently BSOD upon rebooting with INTERRUPT_EXCEPTION_NOT_HANDLED. This does not happen after a shutdown, nor does a Windows 8.1 x64 VM exhibit this behavior on reboot. The VMs have the...