1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Hang on reboot when stopping vz service

Discussion in 'Proxmox VE: Installation and configuration' started by e100, May 2, 2012.

  1. e100

    e100 Active Member
    Proxmox VE Subscriber

    Joined:
    Nov 6, 2010
    Messages:
    1,129
    Likes Received:
    7
    I have two nodes with identical hardware running the latest Proxmox 2.1 fully updated
    These are two brand new nodes, installed proxmox and joined them to existing cluster, they have no KVM or OpenVZ containers running on them.

    When rebooting one of them it hangs when stopping the vz service.
    The specific thing hanging is "modprobe -r vzrst"

    EDIT: This does not seem to fix it, the problem happens randomly and this does not help at all:
    When it hangs if I issue the command "/etc/init.d/open-iscsi stop" or if I do that before I try to reboot it does not hang.
    I am not using any iscsi devices.


    EDIT: It only seems to hang to 2-3 minutes when it hangs. It also seems to only hang every other reboot.

    The other machine, with identical hardware installed from the same media is not having this problem.

    Any idea what is wrong?
     
    #1 e100, May 2, 2012
    Last edited: May 2, 2012
  2. PigLover

    PigLover New Member

    Joined:
    Apr 8, 2013
    Messages:
    14
    Likes Received:
    0
    Apologies for digging up an old thread but I notice this was never answered/resolved. I now find I am having the same problem.

    My config:
    - Proxmox VE 3.0 with all updates from the stable repository (no pvetest).
    - ZFS
    - Samba
    - Added drivers for a Mellanox ConnectX-EN 10Gbe card

    All VMs are KVM. I don't even need OpenVZ at all. No containers used. VMs & ISOs are local disk on a ZFS pool.

    On shutdown it gets to "Shutting down OpenVZ: " and then hangs forever on the "modprobe -r vzrst".

    Would really like to get this resolved so that shutdowns could be clean.
     
  3. mir

    mir Active Member
    Proxmox VE Subscriber

    Joined:
    Apr 14, 2012
    Messages:
    2,664
    Likes Received:
    10
    Is the module loaded at all?

    On a running node do:
    lsmod | grep vzrst
     
  4. PigLover

    PigLover New Member

    Joined:
    Apr 8, 2013
    Messages:
    14
    Likes Received:
    0
    I'll check this evening. But normally, "modprobe -r <unloaded module>" simply returns immediately rather than hanging.

    Also - this is for shutdown on a system that doesn't even use OpenVZ. Do I risk anything by just commenting out the "modprobe -r" from the /etc/init.d/vz script? It can't do any harm not to remove a module from a system that is just about to power off - and the chance that I'd ever do a "vz stop" or "vz restart" is pretty much zero.

    Even if I just comment out the modprobe I'd really like to understand why it hangs...
     
  5. mir

    mir Active Member
    Proxmox VE Subscriber

    Joined:
    Apr 14, 2012
    Messages:
    2,664
    Likes Received:
    10
    If you are certain of that you will never need the driver you could blacklist it.

    create a file in /etc/modprobe.d/ named blacklist-vzrst.conf containing: blacklist vzrst

    Should prevent it from being autoloaded.
     
  6. e100

    e100 Active Member
    Proxmox VE Subscriber

    Joined:
    Nov 6, 2010
    Messages:
    1,129
    Likes Received:
    7
    I still see this problem all the time, it would be nice to see it fixed.

    I have a mix of openvz and kvm running but it does not seem to matter.
    Sometimes, but not always, the modprobe -r vzrst will use 100% cpu for some time, then finally exit.
     

Share This Page