Re: Restart failed: Resource temporarily unavailable

From: Paul H. Hargrove (PHHargrove_at_lbl_dot_gov)
Date: Tue Jul 03 2007 - 11:30:56 PDT

  • Next message: Paul H. Hargrove: "Re: Q: Status of integration with Torque?"
    Nick Couchman wrote:
    > Well, I'm running openSuSE 10.2, kernel, with blcr 0.5.5.  I 
    > didn't see this error message in any of the FAQs or users guide.  I'm 
    > being a little ambitious here trying to checkpoint and restore the 
    > vmware-vmx process that backs VMware Server 1.0.3.  I've used lsof to 
    > verify that the library is preloading correctly.  Anyone have 
    > any ideas as to why this isn't working?
    > Thanks,
    > Nick
      Sorry for the slow response, I've just returned from vacation.
      There are no "normal" ways in which "Resource temporarily unavailable" 
    should be generated by BLCR itself on restart.  So, I think it most 
    likely that BLCR has received this error code from some call it has made 
    to the kernel and passed it back to the restart requester.  It is 
    possible that this is related to the specifics of the vmware-vmx process.
      You could gather more information by rebuilding blcr passing 
    --enable-debug to configure.  That will generate some verbose debugging 
    output from the kernel (to dmesg and/or syslog).  If you could send this 
    tracing output for a failed restart of vmaware-vmx, I might be able to 
    narrow down the cause of the failure.
      However, I am guessing that something like vmware is going to be doing 
    a lot of "weird stuff" that BLCR doesn't support.
    Paul H. Hargrove                          PHHargrove_at_lbl_dot_gov
    Future Technologies Group                 
    HPC Research Department                   Tel: +1-510-495-2352
    Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

  • Next message: Paul H. Hargrove: "Re: Q: Status of integration with Torque?"