BRRABill's Field Report With XenServer
-
Result:
"Migrate failed for unknown reason"
Next test is to see if I can migrate the non-XO VMs. Perhaps it is just me.
-
@BRRABill said:
Result:
"Migrate failed for unknown reason"
Next test is to see if I can migrate the non-XO VMs. Perhaps it is just me.
I had a similar error when trying to build a new VM in XO yesterday - I found I picked the wrong network... but XO just failed for unknown reason. XC actually told me bad NIC choice.
-
@Dashrender Here's a related XO issue on GH.
-
@Danp said:
@Dashrender Here's a related XO issue on GH.
I'm not sure if that is my issue.
I wonder if you can migrate from one standalone XS to another standalone. I am checking with @scottalanmiller on that one and will report back.
-
@BRRABill said:
I wonder if you can migrate from one standalone XS to another standalone. I am checking with @scottalanmiller on that one and will report back.
I can answer that for you. Yes, you can migrate between hosts in separate pools (technically, a lone XS is in it's own pool).
-
@Danp said:
@Dashrender Here's a related XO issue on GH.
Oh my issue had nothing to do with XenMotion - I was simply building a new VM - there were (are) a ton of network options.
Time to learn what they all mean.
-
@Danp said:
I can answer that for you. Yes, you can migrate between hosts in separate pools (technically, a lone XS is in it's own pool).
But only if they share storage, correct?
-
@BRRABill said:
@Danp said:
I can answer that for you. Yes, you can migrate between hosts in separate pools (technically, a lone XS is in it's own pool).
But only if they share storage, correct?
If it is using Xen's migrate system, yes.
-
I exported my XO VM from my test server, and imported onto the production server.
Came right back up. Awesome.
-
@BRRABill said:
I exported my XO VM from my test server, and imported onto the production server.
Came right back up. Awesome.
That is how it's supposed to work, all of the time.
Congratulations.
-
@DustinB3403 said:
@BRRABill said:
I exported my XO VM from my test server, and imported onto the production server.
Came right back up. Awesome.
That is how it's supposed to work, all of the time.
Congratulations.
With any Hypervisor.
-
Yes, but things always seem to have a habit of ... not working properly.
-
@scottalanmiller said:
@BRRABill said:
But only if they share storage, correct?
If it is using Xen's migrate system, yes.
XO will migrate a VM between local storage on two XS.
-
Figure 1: me actually lurking in this thread
-
So, what is the official answer from up there?
-
Can XO migrate a VM fro one standalone XS to another XS?
-
Can you migrate the VM that XO is running on? (That gave me a "no can do" error.)
-
-
The VM that I exported seems to have created a vApp.
What is that?
-
- Yup
- Yup
But you need to define a default SR on any pool you got. Eg:
xe pool-param-set uuid=<pool-uuid> default-SR=<sr-uuid>(with the SR UUID of the local storage if you don't have a shared storage).You can also do it with XenCenter or XO (see https://xen-orchestra.com/blog/set-the-xenserver-default-sr/ )
A live migration won't interrupt the VM, so even with XO on it: doesn't matter.
-
@olivier said:
But you need to define a default SR on any pool you got. Eg:
xe pool-param-set uuid=<pool-uuid> default-SR=<sr-uuid>(with the SR UUID of the local storage if you don't have a shared storage).You can also do it with XenCenter or XO (see https://xen-orchestra.com/blog/set-the-xenserver-default-sr/ )
But to clarify ... you DON'T need a pool? or do you?
-
-
Yes, as @Danp said, there is always a pool: a "single" host is by default in a pool with no name label.
XenCenter choose to hide this, not us.
