@stormi Microcode updated on affected Gen11 i7. Running normally.
Andrew
@Andrew
Best posts made by Andrew
-
RE: Updates announcements and testing
-
RE: Updates announcements and testing
@gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.
-
RE: Can I just say thanks?
I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!
-
RE: Updates announcements and testing
@bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.
-
RE: Updates announcements and testing
@bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.
-
RE: Updates announcements and testing
@bleader Updated an running on newer and older Intel machines. Running normally so far.
-
RE: Updates announcements and testing
@stormi Updated all my normal 8.2 systems updated. All working normally.
-
RE: Xen 4.17 on XCP-ng 8.3!
@stormi Thanks! 4.17 Installed and running on a NUC10. Things seem to be working, but it's just a test... And for everyone who will ask... No, Windows Hyper-V server does not work (as expected).
-
RE: XCP-ng 8.3 betas and RCs feedback 🚀
@stormi New update version
edk2-20220801-1.7.3.xcpng8.3.x86_64
fixed my FreeBSD UEFI boot problem (stuck on boot countdown). XCP reboot NOT required after install. Windows 10 and Ubuntu boot correctly also (but did before too). I did not test secure boot or bitlocker.
Latest posts made by Andrew
-
Guest VM UEFI NVRAM not saved / not persistent
@olivierlambert I enabled UEFI boot for an existing Debian Linux VM but XCP does not save the UEFI boot variable NVRAM in the XAPI database. The next time the VM cold boots (or is migrated and reboots) it forgets what to do an just drops to the UEFI shell because the UEFI NVRAM is blank (hardware emulated).
XO should automatically enable NVRAM saving to the XAPI database when UEFI is enabled. It would be good to have a clear NVRAM button too (or just turn off UEFI and back on).
How do I manually enable persistent NVRAM saving in XCP for existing VMs?
I find that UEFI VMs can boot a lot faster than BIOS VMs.... when they boot.
-
RE: CBT: the thread to centralize your feedback
@Tristis-Oris This is a known issue from before and not related to CBT backups.
Message Posting File restore error on LVMs
File level restoration not working on LVM partition #7029
(https://github.com/vatesfr/xen-orchestra/issues/7029) -
RE: CBT: the thread to centralize your feedback
@Tristis-Oris Is your backed up VM using LVM for it's root filesystem?
-
RE: CBT: the thread to centralize your feedback
@julien-f @florent @olivierlambert I'm using XO source master (commit c5f6b). Running Continuous Replication with NBD+CBT and Purge Snapshot. With a single (one) NBD connection on the backup job, things work correctly. With two NBD connections I see some Orphan VDIs left almost every time after the backup job runs. They are different ones each time.
-
RE: Xen Orchestra from source with Let's Encrypt certificates
@fohdeesha Does a HUP signal reload the config? Can it also check for updated certs?
It's not a restart it's just a config change check.
-
RE: CBT: the thread to centralize your feedback
@olivierlambert Using current XO (07024). I'm having problems with one VM and hourly Continuous Replication (Delta, CBT/NBD). The VM has three VDIs attached. Sometimes it works just fine. But it does error out at least once a day and transferring hundreds of gigs of data for its retries.
stream has ended with not enough data (actual: 446, expected: 512) Couldn't deleted snapshot data Disk is still attached to DOM0 VM
On the next CR job it works (and deletes snapshots) but normally leaves a task running from before on the pool master for the export (that's doing nothing, stuck at 0%). A tool stack restart is required to free it.
It's odd that it complains about the disk attached to Dom0 on a run where it leaves a Dom0 export task but then on the next run it works without error (and the VDI task still attached to Dom0).
I can't force the problem to happen, but it keeps happening.
-
RE: Updates announcements and testing
@bleader Updated an running on newer and older Intel machines. Running normally so far.
-
RE: Multiple VM migration (on maintenance)
@BenjiReis I added
evacuation-batch-size = 4
to the end of/etc/xapi.conf
and then did axe-toolstack-restart
but it did not change from only one at a time. What did I miss? -
RE: can't start vm after host disconnect
Correct, NO master = NO pool management (the VMs keep running).
- If HA is enabled, another master is elected automatically.
- If HA is not enabled, each member waits for the master to return.
I deleted the dead host (old master) because cause even when I marked it as dead (from the new master) the VMs from it would not restart and the backups were still trying to communicate with it. Deleting it from the pool seemed the only way, or at least the quickest, to restore functionality.
I'll have to look into HA a little more and it's issues. It's simple to turn on, but has a few complications/consequences in normal use...