BRRABill's Field Report With XenServer

BRRABill

You know, this might belong in its own thread, but...

I know it's a terrible idea to restore a DC. Always better to reinstall and promote.

But what about moving one from one XS to another?

momurda

@BRRABill You mean just migrating a running vm that is a AD DC? Done it many times.

olivier

@BRRABill said in BRRABill's Field Report With XenServer:

You know, this might belong in its own thread, but...

I know it's a terrible idea to restore a DC. Always better to reinstall and promote.

But what about moving one from one XS to another?

I'm so happy in the Linux world. Not trolling about MS products, just facts about fragile some windows VMs can be when there is a problem.

My clients experiencing the VDI corrupt stuff:

3 Windows VMs, all corrupted
6 Linux VMs, some with database or web server: no problem

Can be a complete random (very small number to draw any conclusion), but still. That's very common.

BRRABill

@momurda said in BRRABill's Field Report With XenServer:

@BRRABill You mean just migrating a running vm that is a AD DC? Done it many times.

Or shutting it down and doing a full move.

BRRABill

@olivier said in BRRABill's Field Report With XenServer:

@BRRABill said in BRRABill's Field Report With XenServer:

You know, this might belong in its own thread, but...

I know it's a terrible idea to restore a DC. Always better to reinstall and promote.

But what about moving one from one XS to another?

I'm so happy in the Linux world. Not trolling about MS products, just facts about fragile some windows VMs can be when there is a problem.

My clients experiencing the VDI corrupt stuff:

3 Windows VMs, all corrupted

6 Linux VMs, some with database or web server: no problem

Can be a complete random (very small number to draw any conclusion), but still. That's very common.

I still don't understand why AD isn't smart enough to just fix itself.

olivier

@BRRABill It's a monolithic/packaged/all in one solution, with a lot of layers. So it makes sense in a way.

momurda

Try moving your vdi while vm is running, to another SR, very exciting as you dont know if you will get the dreaded, 'The VDI mirroring cannot be performed" and your vdi just disappears. Luckily it is just detached and back in its original SR. Seems to only happen with windows vms for me

olivier

@momurda said in BRRABill's Field Report With XenServer:

Try moving your vdi while vm is running, to another SR, very exciting as you dont know if you will get the dreaded, 'The VDI mirroring cannot be performed" and your vdi just disappears. Luckily it is just detached and back in its original SR. Seems to only happen with windows vms for me

Ouch. Tools installed I suppose. This error mean tapdisk failed to write new blocks to the destination (XenServer issue)

Danp

@olivier said in BRRABill's Field Report With XenServer:

@Danp Thanks. If you have any log, feel free to share

Just sent it to your support email address.

olivier

Thanks. But without the debug option, I'm afraid we won't spot anything.

Danp

@olivier Which debug option? I I already have "verboseApiLogsOnErrors": true in the config.json file.

olivier

@Danp Well, so we don't have enough to draw any conclusion

Danp

@olivier Ok... I'm sure there will be more patches soon to test again.

BRRABill

@olivier

I used XO tonight to reboot a XS and it got stuck in maintenance mode.

Think that was something strange on my end?

(I ended up using XC to reboot it afterwards.)

Danp

@BRRABill It's a bug. Here's the GH Issue.

BRRABill

Stupid GitHub.

Just. Don't. Get. It.

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill It's a bug. Here's the GH Issue.

So what causes that bug?

I was just trying to reboot after a patch update.

Danp

@BRRABill My take is that there are multiple issues at work here --

Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.
XO's implementation of host reboot is very different from that found in XC

BRRABill

@Danp said in BRRABill's Field Report With XenServer:

@BRRABill My take is that there are multiple issues at work here --

Coding error (host.enabled vs host.enable). This is fixed in xo-server next-release branch.

XO's implementation of host reboot is very different from that found in XC

Yeah I went to the server room and was surprised the XS was just sitting there. Then XC said it was i maintenance mode. I right clicked in XC and rebooted again, and it went to maintenance mode for a second and rebooted.

Very strange.

BRRABill

Anyone using XO...

When you run an update, do you have to reboot to get the next version to show up?

Or is there a service to restart?

xo-web always updates to the right version in the GUI. xo-server never does until I reboot.