I am having a very hard time importing an OVF file to my XenServer 7 Pool.
After fumbling a few times and pouring over documentation I have been able to fix/determine a few things.
1. I have created an ISO Repository so that the Import Wizard can use the Operating System Fixup ISO while attempting to import the OVF file.
2. I have tested importing this OVF file from different source networks within my environment as well as placing the Transfer VM on different networks.
3. I have found that placing my transfer VM on a network that both XenCenter and XenServer can communicate the import fails after roughly 2 minutes (instead of 48 seconds). This seems to be related to iSCSI failing.
4. After dumping network traffic at my host machine it appears that iSCSI is failing to establish. This happens a number of times before the Transfer VM shuts down and the import fails. (See screenshot below)
.104 is the XenCenter.
.254 is the Transfer VM.
One question I have is this. My SAN is isolated from the rest of my environment (Only the SAN and Xen can communicate). According to documentation the Transfer VM just needs to be able to communicate with XenCenter and XenServer. However I am wondering if the Transfer VM needs direct communication with the SAN.
Question
Marcus Peterson
Hello All,
I am having a very hard time importing an OVF file to my XenServer 7 Pool.
After fumbling a few times and pouring over documentation I have been able to fix/determine a few things.
1. I have created an ISO Repository so that the Import Wizard can use the Operating System Fixup ISO while attempting to import the OVF file.
2. I have tested importing this OVF file from different source networks within my environment as well as placing the Transfer VM on different networks.
3. I have found that placing my transfer VM on a network that both XenCenter and XenServer can communicate the import fails after roughly 2 minutes (instead of 48 seconds). This seems to be related to iSCSI failing.
4. After dumping network traffic at my host machine it appears that iSCSI is failing to establish. This happens a number of times before the Transfer VM shuts down and the import fails. (See screenshot below)
.104 is the XenCenter.
.254 is the Transfer VM.
One question I have is this. My SAN is isolated from the rest of my environment (Only the SAN and Xen can communicate). According to documentation the Transfer VM just needs to be able to communicate with XenCenter and XenServer. However I am wondering if the Transfer VM needs direct communication with the SAN.
Either way. This has become a pressing issue.
Can someone please assist me with this situation?
Thanks in advance!
Link to comment
11 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now