BRRABill's Field Report With XenServer

Dashrender

@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.

BRRABill

@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?

scottalanmiller

@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.

BRRABill

I exported my XO VM from my test server, and imported onto the production server.

Came right back up. Awesome.

DustinB3403

@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.

JaredBusch

@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.

BRRABill

Yes, but things always seem to have a habit of ... not working properly.

Danp

@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.

olivier

Figure 1: me actually lurking in this thread

BRRABill

@olivier

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.)

BRRABill

The VM that I exported seems to have created a vApp.

What is that?

olivier

@BRRABill

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.

BRRABill

@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?

Danp

@BRRABill said:

But to clarify ... you DON'T need a pool? or do you?

@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).

olivier

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.

BRRABill

@Danp @olivier

Thanks @Danp ... I think the thing that was throwing us here (who thought it was not possible outside a pool) was that a standalone is actually a pool

BRRABill

Converted my first physical server to a production XS this morning.

So far, so good.

BRRABill

Question:

On the new production server, it is not reporting the space taken by my new VM.

This is what is says:

Total: 871.8 GiB
Currently used: 5.2 GiB
Available: 866.5 GiB

But for example the new VM I migrated over has at least 100GB.

Why would it not be reporting this?

BRRABill

Danp

Thin provisioning?