Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....
Hi there; I'm running multiple hosts using a boot-over-the-wire RO (NFS) PXE boot. The user that's part of vboxusers, the VM directories, NFS, NIS are all configured correctly. The user that runs it all has r/w access to its home directory. All servers appear with all the VM's as they should. I create one, refresh a host, and it's there. What I can't figure out is what "lockfile" is being used when a particular VM host creates a running VM. I know it's somewhere, a status in the user's home directory....