Blue screen with 5.1

Discussion in 'Proxmox VE: Installation and configuration' started by cybermcm, Oct 24, 2017.

  1. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    It seems that changing to 2003/XP avoids the bug. My system is up and running for7 hours, it never ran that long with the original 2016/10 setting. Is there any downside if I change the setting to 2003/XP? If not this can be a sufficient workaround for now...
     
    #161 cybermcm, Nov 28, 2017
    Last edited: Nov 28, 2017
  2. aderumier

    aderumier Member

    Joined:
    May 14, 2013
    Messages:
    203
    Likes Received:
    18
    It'll reduce the performance a little bit, but not too much. (virtio devices are still accelerated).

    I'll try to apply patches on qemu tomorrow and build a deb. if you have time to test it, it could be great.
     
  3. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    Sure thing. I'll test anything you can provide...
     
  4. mac.linux.free

    Joined:
    Jan 29, 2017
    Messages:
    96
    Likes Received:
    5
    kernel 4.13.8 ? is it the cure ?

    ...installed and booting
     
    #164 mac.linux.free, Nov 28, 2017
    Last edited: Nov 28, 2017
  5. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    I'm on Linux 4.13.4-1-pve #1 SMP PVE 4.13.4-26 but yes until now no BSOD...
     
  6. mac.linux.free

    Joined:
    Jan 29, 2017
    Messages:
    96
    Likes Received:
    5
    I had a black screen with the 2003/XP setting on 2 machines...but only on zfs on nvme storage
     
  7. 2beers

    2beers New Member

    Joined:
    Jan 16, 2013
    Messages:
    9
    Likes Received:
    0
    No. At least not for me.
     
  8. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    @mac.linux.free: I'm using LVM on a SSD drive...
    @2beers: You can't even boot or you still experience BSOD?
     
  9. mbaldini

    mbaldini Member

    Joined:
    Nov 7, 2015
    Messages:
    166
    Likes Received:
    19
    Windows 2012R2, switched os type to win2003/xp from yesterday, until now no BSOD
     
  10. 2beers

    2beers New Member

    Joined:
    Jan 16, 2013
    Messages:
    9
    Likes Received:
    0
    Installed and rebooted yesterday => BSOD of Windows guest today.
     
  11. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    @2beers: Do you use ZFS or LVM?
     
  12. 2beers

    2beers New Member

    Joined:
    Jan 16, 2013
    Messages:
    9
    Likes Received:
    0
    LVM
     
  13. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    some bad news: switching to 2003/XP seems to interfere with the boot process (at least on my host). Sometimes the VMs get stuck during boot. So I'll revert back to 4.10 and 10/2016 settings...
     
  14. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,449
    Likes Received:
    391
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    2beers, fireon and kro like this.
  15. cybermcm

    cybermcm Member

    Joined:
    Aug 20, 2017
    Messages:
    88
    Likes Received:
    10
    sounds great, starting upgrade process, will report back
     
  16. speedbird

    speedbird Member
    Proxmox Subscriber

    Joined:
    Nov 3, 2017
    Messages:
    45
    Likes Received:
    4
  17. GadgetPig

    GadgetPig Member

    Joined:
    Apr 26, 2016
    Messages:
    138
    Likes Received:
    19
    As far as BSOD, does it affect only Windows 10/2016 (using Win10/2016 VM setting)? I updated a Dell T300 server last night to latest pve-nosubscription with kernel 4.13.8 and rebooted. So far no BSOD on my Win2008SBS VM (Vista/2008 VM setting) on LVM/Latest Stable VirtIO drivers.
     
  18. David Herselman

    David Herselman Active Member
    Proxmox Subscriber

    Joined:
    Jun 8, 2016
    Messages:
    183
    Likes Received:
    38
    We have a small cluster running 3 x HP ProLiant DL380 G7 systems. Systems are almost identical but one has a slightly different CPU. Two have dual Intel Xeon X5650 CPUs and one has dual Intel Xeon E5506 CPUs.

    Everything had been stable for about a year, even after upgrading PVE 4.4 Ceph Jewel to PVE 5.1 Ceph Luminous.

    Last night we changed the 7 guest VMs from VirtIO and default (kvm64) CPU to VirtSCSI (discard=on) and set CPU features to Nehalem. We upgraded netkvm and installed balloon, vioserial and vioscsi drivers v0.1.126; these are confirmed to be stable on 200+ Windows guests in other clusters. Qemu guest agent was also installed, which wasn't previously running on these guests.

    VMs started crashing almost immediately after making these changes. Installing and booting 4.10.17-5-pve restored stability.

    VMs are set with fixed memory, herewith a sample definition (Windows 2012r2 guests):
    Code:
    agent: 1
    boot: cdn
    bootdisk: scsi0
    cores: 2
    cpu: Nehalem
    ide2: none,media=cdrom
    localtime: 1
    memory: 4096
    name: test-vip
    net0: virtio=00:16:3e:5f:00:05,bridge=vmbr0
    numa: 1
    onboot: 1
    ostype: win8
    protection: 1
    scsi0: virtuals:vm-101-disk-1,discard=on,size=80G
    scsihw: virtio-scsi-pci
    smbios1: uuid=3a04b7a5-084a-4c2e-81b3-7675e5327b48
    sockets: 1
    startup: order=2
    vga: cirrus
    Have upgraded one of the 3 nodes to pve-kernel-4.13.8-2-pve_4.13.8-28_amd64.deb, 6+ hours so far and no problems... ;)
     
  19. David Herselman

    David Herselman Active Member
    Proxmox Subscriber

    Joined:
    Jun 8, 2016
    Messages:
    183
    Likes Received:
    38
    Just to be clear, the same architecture (PVE 5.1, Ceph Luminous, VirtIO v0.1.126, VirtSCSI with discard enabled, VioSerial, NetKVM, Balloon and guest agent) was perfectly stable on two separate clusters where we run with different CPU features (Haswell-noTSX and SandyBridge).
     
  20. mac.linux.free

    Joined:
    Jan 29, 2017
    Messages:
    96
    Likes Received:
    5
    I updated the kernel but on bootup (autostart) my windows 10 machines hang (3 of them) doing a reset on each of them everything works and is stable till now.
     
  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