-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John,
The partimageng postscript mounts an image store via NFS at /install. The NFS
server and path are specified in the xCAT site table as IMAGELIBSERVER and
IMAGELIBINSTALLDIR. More info about this part is at the bottom of our wiki
page explain
Josh,
I added the debugging code. It turned out NFS looks fine. I also manually
verified the NFS share:
[root@blade14 ~]# mkdir nfstest
[root@blade14 ~]# mount 172.20.0.1:/opt/image/x86 nfstest/
[root@blade14 ~]# cd nfstest/
[root@blade14 nfstest]# mkdir writetest
How to debug the par
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John,
Do you have IMAGELIBINSTALLDIR set to /opt or to /opt/image/x86? It needs to
be /opt.
One thing to try is changing usepartimageng to 1 on line 147. That will
switch to using partimageng instead of partimage and tell us if it is
something s
Thanks Gerhard,
That was my problem. I put the image into VCL the manual way, like you would
for version 2.1 so that file never got created. I made a new image from the
base image and it put the file in it for me.
Thanks again,
-Patrick
On Mar 31, 2011, at 1:30 PM, Hartl, Gerhard L. wrote:
Since upgrading to 2.2, when a user browses to the 'connect' page, I've noticed
that the clients ip is captured and the management node then ssh's to the vm
and opens up the port for the clients ip on 3389. While I understand this is
best practice, I have noticed that if they user is to quick
(disregard previous, forgot to retitle)
Since upgrading to 2.2, when a user browses to the 'connect' page, I've noticed
that the clients ip is captured and the management node then ssh's to the vm
and opens up the port for the clients ip on 3389. While I understand this is
best practice, I ha
I'm still trying to debug why my image capturing keeps failing and I noticed
that might be a problem but I'm not sure... I have my virtual machines all
set up with static IP address because I am not able to use DHCP in my
current situation. Well I noticed that once I try to capture an image and it
