Unable to attach my ISO files to VM or create VM from uploaded template
Text added to previous post
Edited by Bruce Hellstrom, 08 February 2015 - 05:56 AM.
Bruce Hellstrom
MEMBERS
댓글 작업
Community
Other links
CloudPlatform 4.x
Unable to attach my ISO files to VM or create VM from uploaded template
Unable to attach my ISO files to VM or create VM from uploaded template
I uploaded 3 different ISO images to our CCP environment. One was a Clonezilla live CD, one was the Ubuntu 14.04 server ISO, and one was another system rescue CD.
The uploading process went fine with no errors and the new ISO's appeared in the list of available ISO images, however I was unable to attach any of those ISO's to a test Centos VM that I had created. Whenever I would try, it would just attempt for about 5 minutes, then give me a generic error "could not attach iso image". I also tried creating a new VM using the Clonezilla ISO as the template and that failed as well.
On our old XenServer/XenCenter setup, I had no problem using Clonezilla on the VMs.
I tried deleting and re-uploading the Clonezilla ISO several times using different OS Types. The first time I told it to use Debian 7, as the Clonezilla ISO is the Debian based one. The second time, I tried to use Centos 5.2 to match the VM (based on something I saw in the Cloud Stack docs regarding ISO's), and the third time, I just tried Other Linux 64 bit. None of those worked.
What am I missing? Shouldn't I be able to attach just about any ISO to a VM?
Bruce
Edit:
The problem seems to be related to a new problem I see today which is that I cannot create any VM from one of my uploaded templates either. The error in the XenServer and management server logs indicates that it's unable to mount secondary storage (192.168.4.3/secondary), which is the correct address. The secondary storage VM also mounts that NFS share and it has no trouble with it. Only the XenServer seems to be having trouble with it.
Bruce
Edited by Bruce Hellstrom, 08 February 2015 - 05:55 AM.
Bruce Hellstrom
MEMBERS
Previous 댓글 3개
Bruce, have you been able to resolve the issue with mounting the secondary storage on Xenserver? I believe it was working earlier so could not have been the permissions on the NFS share but doesn't hurt to double check.
Somesh Naidu
CITRIX EMPLOYEES
댓글 작업
Our service provider determined that the problem lies with the iptables, though the rules look fine. When the firewall is turned off, then the XenServer could connect to the management server. It was very odd since it worked when they originally setup the system. We did a full reboot of the full metal box and CloudPlatform a couple days earlier and that might have been when this problem started. The tech tried to revamp the iptables rules, but still the management server would not connect unless he had the firewall completely off. I need to check back with him to see if he did some more with it.
The strange thing is that with the firewall on in it's previous configuration, the secondary storage VM had no problem mounting that same NFS share.
When I would try and mount the NFS share from XenServer manually, it would just timeout. Here's a sample of the output from my trying to mount manually. It does seem to be able to find the correct UDP port for NFS that's being broadcast. I saw that after restarting the management server service, that port would change, but the mount command would show the correct one.
[root@xxxx-hypervisor1 log]# mount -v 192.168.4.3:/secondary /var/cloud_mount/3b162557-e476-348f-a3c8-adb5431b9f17
mount: no type was given - I'll assume nfs because of the colon
mount: trying 192.168.4.3 prog 100003 vers 3 prot tcp port 2049
mount: trying 192.168.4.3 prog 100005 vers 3 prot udp port 36147
mount: mount to NFS server '192.168.4.3' failed: timed out (retrying).
mount: trying 192.168.4.3 prog 100003 vers 3 prot tcp port 2049
mount: trying 192.168.4.3 prog 100005 vers 3 prot udp port 36147
Bruce
Bruce Hellstrom
MEMBERS
댓글 작업
Participate
Ask, Discuss, Answer