[SOLVED] proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon-pci

Discussion in 'Proxmox VE: Installation and configuration' started by yarick123, Mar 14, 2013.

  1. yarick123

    yarick123 New Member

    Joined:
    Mar 14, 2013
    Messages:
    14
    Likes Received:
    0
    Dear Proxmox team, thank you for very good product - it works rock-stable!

    After upgrading proxmox ve 2.2 to 2.3 my windows server 2003 kvm cannot be startet - it stops with BSOD on booting.

    If I manually start the virtual machine without '-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3', the machine runs without any problem.

    Is it possible to start a kvm host without virtio-balloon-pci over the gui?

    A KVM with windows server 2008 works on the same server without any problem.

    my pveversion -v shows:
    Code:
    [INDENT]pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)[/INDENT]
    [INDENT]running kernel: 2.6.32-18-pve[/INDENT]
    [INDENT]proxmox-ve-2.6.32: 2.3-88[/INDENT]
    [INDENT]pve-kernel-2.6.32-17-pve: 2.6.32-83[/INDENT]
    [INDENT]lvm2: 2.02.95-1pve2[/INDENT]
    [INDENT]clvm: 2.02.95-1pve2[/INDENT]
    [INDENT]corosync-pve: 1.4.4-4[/INDENT]
    [INDENT]openais-pve: 1.1.4-2[/INDENT]
    [INDENT]libqb: 0.10.1-2[/INDENT]
    [INDENT]redhat-cluster-pve: 3.1.93-2[/INDENT]
    [INDENT]resource-agents-pve: 3.9.2-3[/INDENT]
    [INDENT]fence-agents-pve: 3.1.9-1[/INDENT]
    [INDENT]pve-cluster: 1.0-36[/INDENT]
    [INDENT]qemu-server: 2.3-18[/INDENT]
    [INDENT]pve-firmware: 1.0-21[/INDENT]
    [INDENT]libpve-common-perl: 1.0-48[/INDENT]
    [INDENT]libpve-access-control: 1.0-26[/INDENT]
    [INDENT]libpve-storage-perl: 2.3-6[/INDENT]
    [INDENT]vncterm: 1.0-3[/INDENT]
    [INDENT]vzctl: 4.0-1pve2[/INDENT]
    [INDENT]vzprocps: 2.0.11-2[/INDENT]
    [INDENT]vzquota: 3.1-1[/INDENT]
    [INDENT]pve-qemu-kvm: 1.4-8[/INDENT]
    [INDENT]ksm-control-daemon: 1.1-1[/INDENT]
    
    The vm is 32 bit and has the following configuration:
    Code:
    [INDENT]acpi: 1
    args: -cpu host
    boot: c
    bootdisk: virtio0
    cores: 2
    cpu: host
    cpuunits: 1000
    kvm: 1
    memory: 2200
    name: vmotcs
    net0: virtio=00:0C:29:56:DA:FA,bridge=vmbr0
    ostype: wxp
    scsihw: virtio-scsi-pci
    sockets: 1
    tablet: 1
    virtio0: local:101/vm-101-disk-1.qcow2,cache=writethrough,size=30G[/INDENT]
    

    Best regards
    yarick123
     
    #1 yarick123, Mar 14, 2013
    Last edited: Mar 14, 2013
  2. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    12,834
    Likes Received:
    307
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    not via gui but you can disable it by adding the following line into your VMID.conf file

    Code:
    balloon: 0
    do not use virtio-scsi-pci on WinXP, afaik this does not work.

    btw, can you boot in safe-mode?
     
  3. yarick123

    yarick123 New Member

    Joined:
    Mar 14, 2013
    Messages:
    14
    Likes Received:
    0
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    Hi Tom, thank you for the quick answer!

    it works with 'balloon: 0', thank you!

    btw, I could not boot the machine anyhow. I tried hundred of variants. With safe-mode, without, with installed ballooning drivers, with uninstalled ballooning drivers,..

    Best regards
    yarick123
     
  4. spirit

    spirit Well-Known Member
    Proxmox VE Subscriber

    Joined:
    Apr 2, 2010
    Messages:
    3,034
    Likes Received:
    84
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    is it win2003 or win2003R2 ? 32 oe 64bit ?

    Because I don't have problem with win2003R2 64bit + balloon driver
     
  5. yarick123

    yarick123 New Member

    Joined:
    Mar 14, 2013
    Messages:
    14
    Likes Received:
    0
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    Hi spirit, it is win2003 std SP2 32bit
     
  6. greenvomit8

    greenvomit8 Member

    Joined:
    Jul 31, 2012
    Messages:
    34
    Likes Received:
    0
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    Hi Tom,
    What Bus/Device type for a Win 2003/XP VM HDD would you recommend to use?
    Current Proxmox Wiki recommendations appears to be Virtio for Win2003
    http://pve.proxmox.com/wiki/Windows_2003_guest_best_practices
     
    #6 greenvomit8, May 30, 2013
    Last edited: May 30, 2013
  7. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    12,834
    Likes Received:
    307
  8. dea

    dea Member
    Proxmox VE Subscriber

    Joined:
    Feb 6, 2009
    Messages:
    118
    Likes Received:
    0
    Re: proxmox 2.3: win2003 server vm cannot be started - BSOD, caused by virtio-balloon

    Yes, I use several cluster and several Windows server (2003, 2008r1, 2008r2) and is *very important* carefully choose which version of the virt-io drivers uses.
    On 2008r2 (Win7 kernel) I use 0.1-59
    On 2008r1 (Vista kernel) and 2003 I use 0.1-49

    This solution is rock solid on several tens of servers, if you use 0.1-52 on 2003-2008r1 (BSOD or instability).

    Luca
     
  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