Bluescreen on W2k8 VM

Discussion in 'Proxmox VE 1.x: Installation and configuration' started by andreas70, Mar 16, 2011.

  1. andreas70

    andreas70 New Member

    Joined:
    Jan 27, 2010
    Messages:
    10
    Likes Received:
    0
    Hallo,
    i get a bluescreen on a KVM VM with Windows 2008 64bit OS (SBS) about once a day. It says: "A clock interrupt was not received on a secondary processor within the allocated time interval". Is there any known issue? For me it looks like this error comes from the virtual cpu the OS sees?

    My configuration:
    Code:
     
    pve-manager: 1.7-11 (pve-manager/1.7/5470)
    running kernel: 2.6.35-1-pve
    proxmox-ve-2.6.35: 1.7-9
    pve-kernel-2.6.35-1-pve: 2.6.35-9
    pve-kernel-2.6.24-8-pve: 2.6.24-16
    qemu-server: 1.1-28
    pve-firmware: 1.0-10
    libpve-storage-perl: 1.0-16
    vncterm: 0.9-2
    vzctl: 3.0.24-1pve4
    vzdump: 1.2-10
    vzprocps: 2.0.11-1dso2
    vzquota: 3.0.11-1
    pve-qemu-kvm: 0.13.0-3
    ksm-control-daemon: 1.0-4
    
    VM Configuration:
    Code:
     
    name: myvm
    ide2: local:iso/virtio-win-1.1.16.iso,media=cdrom
    ostype: w2k8
    memory: 6144
    sockets: 1
    onboot: 1
    cores: 4
    boot: c
    freeze: 0
    cpuunits: 2000
    acpi: 1
    kvm: 1
    bootdisk: virtio0
    virtio1: local:107/vm-107-disk-2.qcow2
    vlan0: virtio=8E:79:DB:8F:ED:EA
    virtio0: local:107/vm-107-disk-1.raw
    args: -rtc-td-hack
    
     
     
  2. e100

    e100 Active Member
    Proxmox VE Subscriber

    Joined:
    Nov 6, 2010
    Messages:
    1,227
    Likes Received:
    23
    I just had this same error happen to me, Windows 2008 R2 x64 Standard.

    At the same moment in time I had a disk in my RAID array report a "Reading Error"
    Maybe it was the delayed IO from the disk that caused my BSOD....
     
  3. Nhoague

    Nhoague Member

    Joined:
    Sep 29, 2012
    Messages:
    68
    Likes Received:
    0
    Bump. I have now seen this problem 5 times in as many days. Sometimes it could be the main AD server, sometimes a term server. We are running ISCSI with a Nimble over very fast hardware and bonding. Any ideas?

    See screenshot. Help please! Screen Shot 2013-08-30 at 9.24.57 AM.png
     
  4. torontob

    torontob Member

    Joined:
    Oct 18, 2010
    Messages:
    37
    Likes Received:
    0
    Oh boy! I see the same problem and it just keeps coming back after restart. Anyone found a solution to this?
     
  5. Nhoague

    Nhoague Member

    Joined:
    Sep 29, 2012
    Messages:
    68
    Likes Received:
    0
    I changed my Windows servers from the default processor to Haswell and so far no problem! I have also upgraded to the newest proxmox 3.2 i believe. I have been running well for the past few weeks!
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice