Offline
Hello,
I'm just curious if there is any easier way to setup VM boot order (after powerloss/shutdown), other then setting the delayed startup time on each VM?
Currently, there is no easy way to check the overall-pool boot order of VMs (that I can find).
Hello,
I know this seems dumb, but could we add a paste function into the XOA console.
I try using the copy/multiline copy, but that never seems to work.
@AtaxyaNetwork First, I want to say, THANK YOU!!! for putting this together! Legit, kudo's.
I ran into one problem in your article:
"for xen-blkfront.ko
mv xen-blkfront.ko /lib/modules/5.14.21-150400.24.108-default/kernel/block/
for xen-netfront.ko
mv xen-netfront.ko /lib/modules/5.14.21-150400.24.108-default/kernel/net/"
If I try the MV command after the for line, I get MV is an invalid command. I simply bypassed the for lines, and did a pure MV.
It seems to have worked (I can now boot, and get into it).
Second related question: Is there any way to install the XCPNG Client drivers at the same time, so this VM responds to XCPNG commands (shutdown/etc) ?
@jcdick1 Are you fully firmware patched (BIOS microcode)?
@Danp Turns out, I was missing the UEFI Secure boot certificates on my hosts. Odd how this never came up as an issue prior, but now it seems "required". At least its an easy fix:
@ronivay You make a good Point.
What I didn't know, that I do now, I wasn't "naming" my schedules. Once you do that, it replaces the Cron time. So I called my things like "Daily @ 4:30 - Diff" but obviously naming schemes are broad.
Hello,
This is more of a minor feature request, but could we have the backup schedules converted from cron time, to actual clock time? I have no problem writing cron time when creating the backups, but when reading through the backups, its rather challenging to re-read the times in a quick view to allow for easier management (I'm documenting all of my backups, and this is an exercise in frustration).
this is what I'm talking about btw:
Is there a way for us to create our own templates in hub, or remove some that we never want deployed?
Hello,
I read that you are currently testing alpha stage for qcow2 format (Yes, I know it will be awhile before this hits production). But would that mean then at that time, that we can import KVM vm's, directly into XOA ?
@olivierlambert Hello Olivier,
Any update on the status of this?
@AtaxyaNetwork I tried the same edits, and I received the same errors btw. After looking at the instructions further, Dell's KVM user guide says there should be two hard drives as part of the VM.
First drive is for the OS/Base system, second hard drive is for plugins and any related data.
It does say it will boot without the second drive, but basically wont be useable without it. I tried re-doing the instructions but converting the second drive at the same time, and the problem persists. So I think there is a step somewhere after the ko driver install to help it "see" the second drive at all, not really sure how to fix that.
@AtaxyaNetwork First, I want to say, THANK YOU!!! for putting this together! Legit, kudo's.
I ran into one problem in your article:
"for xen-blkfront.ko
mv xen-blkfront.ko /lib/modules/5.14.21-150400.24.108-default/kernel/block/
for xen-netfront.ko
mv xen-netfront.ko /lib/modules/5.14.21-150400.24.108-default/kernel/net/"
If I try the MV command after the for line, I get MV is an invalid command. I simply bypassed the for lines, and did a pure MV.
It seems to have worked (I can now boot, and get into it).
Second related question: Is there any way to install the XCPNG Client drivers at the same time, so this VM responds to XCPNG commands (shutdown/etc) ?
@DustinB Luckily in this case, I dont need to kill the original, so if something goes wrong, I can always flip back. I guess I'll give this a try.
@DustinB That seems fraught with failure. Have you ever done this successfully? From what I understand, restoring XOA meta data isn't that straight forward (but I've never done it, so I'm talking hearsay).
@manilx - This is why we run a separate host just for XOA (and a few other IT specific tools). But after almost 3 years, its time to upgrade our IT pool host, and it has all new networking so much easier to migrate then it is to run multiple copies.
However, after this re-structure of our host configurations, I might just do that, and stand up a second copy of XOA for this type of scenario. I've never run multiple XOA instances though, so I need to read up on the best way to do this.
Hello,
So we have just stood up a new pool, and want/need to migrate our XOA to this new pool (the old one is being shutdown).
What is the best way to migrate XOA to a new pool (preferably without needing to do this via CLI) ?
Hello,
We have 4 Dell R7525 hosts, each with Dual 100G QSFP+ nics running LACP bonded connections to two Dell Z9100 switches running a VLT domain.
I had to setup the host using one of the onboard 1G nics initially, and then once it was setup and joined to the pool, I switched the management interface to the bonded vlan (that matches my management network vlan).
I can get to the test host, and everything seems to work.
I still have to finish making the same changes to the sub-and master in this pool, but I dont foresee any real issue.
However, I'm not certain of two things: