Some message formats changed between the two releases, so VMs started before the update (with an 11.3 tapdisk and tapback) can’t understand some of the changed commands. Rebooting XCP-ng or doing an RPU should work. Since not every command is affected, restarting tapback is usually enough: systemctl restart tapback.service
We're going to work to avoid that.
E
Offline
Emmanuel V
@Emmanuel V
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
I have uploaded the raw kern.log.1 file directly to the shared folder.
From that log it seems that just before the reboot your NFS server wasn't responding, which that explain that your guests were freezed. Maybe that was coming from your previous switch ?
Please let us know if any new issues arise. -
RE: XCP-ng 8.3 updates announcements and testing
Some message formats changed between the two releases, so VMs started before the update (with an 11.3 tapdisk and tapback) can’t understand some of the changed commands. Rebooting XCP-ng or doing an RPU should work. Since not every command is affected, restarting tapback is usually enough: systemctl restart tapback.service
We're going to work to avoid that. -
RE: VDI export to VMDK results in a corrupted disk
It might be worth adding a message in XO at export, or in the documentation ?
-
RE: Low end devices , share your experiences
I wonder to which extend we could lower dom0 memory, eventually reduce the set of features for this kind of usecases.
I can definitely see a pool of machines (x86 or ARM) for industrial purpose where that could make sense, and that could be managed and update through XOA.