@stormi
Fantastic and way to go...thanks for all your hard work!
Best posts made by archw
-
RE: XCP-ng 8.3 beta 🚀
-
RE: Import from VMware fails after upgrade to XOA 5.91
@florent
I's running it right now! -
RE: Backup fails with "VM_HAS_VUSBS" error
@Danp
80 to 84! Building science...never saw Bo but Lionel "Little Train" James was in the class I went to (he was leaving as I was walking in...nice dude!!!). -
RE: VM migration from esxi fails with "Cannot read properties of undefined (reading 'startsWith')"
@florent
For the heck of it, I made a new VM in esxi and pointed it to the vmdk file. At that point, xcp-ng would perform the loading conversion process using the new VM setup.I have no idea what was wrong with the original vmx setup file in esxi.
-
RE: XCP-ng 8.3 beta 🚀
@stormi
Sorry...I cliked reply to teh wrong post.Yes, I ran "yum update edk2 --enablerepo=xcp-ng-testing,xcp-ng-cii" and let it install. I then rebooted the VM (several of them) and tried to start them and none worked. I then ran "yum downgrade edk2-20180522git4b8552d-1.5.1.xcpng8.3" and the VM's fired right up.
-
RE: Import from VMware fails after upgrade to XOA 5.91
@florent
In the FWIW department, I get the same errors when trying to import with 5.91:result succeeded {} message "no opaque ref found" name "Error" stack "Error: no opaque ref found\n at importVm (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/xva/importVm.mjs:28:19)\n at processTicksAndRejections (node:internal/process/task_queues:95:5)\n at importVdi (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/xva/importVdi.mjs:6:17)\n at file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/migrate-vm.mjs:260:21\n at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:158:22)\n at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:141:20)"
The journalctl errors are as follows :
Feb 02 09:30:19 xoa xo-server[1178375]: 2024-02-02T14:30:19.498Z xo:xo-server WARN possibly unhandled rejection { Feb 02 09:30:19 xoa xo-server[1178375]: error: Error: already finalized or destroyed Feb 02 09:30:19 xoa xo-server[1178375]: at Pack.entry (/usr/local/lib/node_modules/xo-server/node_modules/tar-stream/pack.js:138:51) Feb 02 09:30:19 xoa xo-server[1178375]: at Pack.resolver (/usr/local/lib/node_modules/xo-server/node_modules/promise-toolbox/fromCallback.js:5:6) Feb 02 09:30:19 xoa xo-server[1178375]: at Promise._execute (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/debuggability.js:384:9) Feb 02 09:30:19 xoa xo-server[1178375]: at Promise._resolveFromExecutor (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:518:18) Feb 02 09:30:19 xoa xo-server[1178375]: at new Promise (/usr/local/lib/node_modules/xo-server/node_modules/bluebird/js/release/promise.js:103:10) Feb 02 09:30:19 xoa xo-server[1178375]: at Pack.fromCallback (/usr/local/lib/node_modules/xo-server/node_modules/promise-toolbox/fromCallback.js:9:10) Feb 02 09:30:19 xoa xo-server[1178375]: at writeBlock (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/xva/_writeDisk.mjs:11:22) Feb 02 09:30:19 xoa xo-server[1178375]: } Feb 02 09:30:21 xoa xo-server[1178375]: root@xx.xx.xx.xx Xapi#putResource /import/ XapiError: IMPORT_ERROR(INTERNAL_ERROR: [ Unix.Unix_error(Unix.ENOSPC, "write", "") ]) Feb 02 09:30:21 xoa xo-server[1178375]: at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12) Feb 02 09:30:21 xoa xo-server[1178375]: at default (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_getTaskResult.mjs:11:29) Feb 02 09:30:21 xoa xo-server[1178375]: at Xapi._addRecordToCache (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1006:24) Feb 02 09:30:21 xoa xo-server[1178375]: at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1040:14 Feb 02 09:30:21 xoa xo-server[1178375]: at Array.forEach (<anonymous>) Feb 02 09:30:21 xoa xo-server[1178375]: at Xapi._processEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1030:12) Feb 02 09:30:21 xoa xo-server[1178375]: at Xapi._watchEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1203:14) Feb 02 09:30:21 xoa xo-server[1178375]: at runNextTicks (node:internal/process/task_queues:60:5) Feb 02 09:30:21 xoa xo-server[1178375]: at processImmediate (node:internal/timers:447:9) Feb 02 09:30:21 xoa xo-server[1178375]: at process.callbackTrampoline (node:internal/async_hooks:130:17) { Feb 02 09:30:21 xoa xo-server[1178375]: code: 'IMPORT_ERROR', Feb 02 09:30:21 xoa xo-server[1178375]: params: [ 'INTERNAL_ERROR: [ Unix.Unix_error(Unix.ENOSPC, "write", "") ]' ], Feb 02 09:30:21 xoa xo-server[1178375]: call: undefined, Feb 02 09:30:21 xoa xo-server[1178375]: url: undefined, Feb 02 09:30:21 xoa xo-server[1178375]: task: task { Feb 02 09:30:21 xoa xo-server[1178375]: uuid: '37b70fee-d769-1b2a-864b-7e18bd6fcff6', Feb 02 09:30:21 xoa xo-server[1178375]: name_label: '[XO] VM import', Feb 02 09:30:21 xoa xo-server[1178375]: name_description: '', Feb 02 09:30:21 xoa xo-server[1178375]: allowed_operations: [], Feb 02 09:30:21 xoa xo-server[1178375]: current_operations: {}, Feb 02 09:30:21 xoa xo-server[1178375]: created: '20240202T13:57:21Z', Feb 02 09:30:21 xoa xo-server[1178375]: finished: '20240202T14:30:21Z', Feb 02 09:30:21 xoa xo-server[1178375]: status: 'failure', Feb 02 09:30:21 xoa xo-server[1178375]: resident_on: 'OpaqueRef:a482c281-bc5c-6aed-e5cc-91d43c02dc46', Feb 02 09:30:21 xoa xo-server[1178375]: progress: 1, Feb 02 09:30:21 xoa xo-server[1178375]: type: '<none/>', Feb 02 09:30:21 xoa xo-server[1178375]: result: '', Feb 02 09:30:21 xoa xo-server[1178375]: error_info: [ Feb 02 09:30:21 xoa xo-server[1178375]: 'IMPORT_ERROR', Feb 02 09:30:21 xoa xo-server[1178375]: 'INTERNAL_ERROR: [ Unix.Unix_error(Unix.ENOSPC, "write", "") ]' Feb 02 09:30:21 xoa xo-server[1178375]: ], Feb 02 09:30:21 xoa xo-server[1178375]: other_config: { object_creation: 'complete' }, Feb 02 09:30:21 xoa xo-server[1178375]: subtask_of: 'OpaqueRef:NULL', Feb 02 09:30:21 xoa xo-server[1178375]: subtasks: [], Feb 02 09:30:21 xoa xo-server[1178375]: backtrace: '(((process xapi)(filename lib/backtrace.ml)(line 210))((process xapi)(filename ocaml/xapi/import.ml)(line 2131))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 72)))' Feb 02 09:30:21 xoa xo-server[1178375]: } Feb 02 09:30:21 xoa xo-server[1178375]: }
Latest posts made by archw
-
RE: XCP-ng 8.3 beta 🚀
@stormi
Worked for me at the first site but it did one weird thing that its never done before.When I applied the patches to the pool master, it disappeared from the XOA GUI. Normally, after you apply the updates, all the hosts (including the master) disappear for a few minutes and then come back but this time they didn't. I had to just reboot it from the Dell Idrac GUI. It rebooted and then all the hosts came back.
-
RE: XCP-ng 8.3 beta 🚀
@stormi said in XCP-ng 8.3 beta :
yum update --enablerepo=xcp-ng-lab
After the new updates came out yesterday, I did the update but, this time, I did what you said (" yum update --enablerepo=xcp-ng-lab") and it worked perfectly...thanks!
-
RE: XCP-ng 8.3 beta 🚀
@stormi I didn't even think to try that I just did it and its rebooting.
-
RE: XCP-ng 8.3 beta 🚀
I think all of this is my fault and I wouldn't worry about it. After I left the last post, I went in and saw a but of stuff from the @xcp-ng-lab repo. I quasi fixed it doing a bunch of yum downgrades until I no longer got an error and and I think I fixed it. I had to remove a few things but I took a "yum list installed" from a good system and made everything the same. Again, its a dummy system that I don't really use except to test things.
Here is the output from "yum repolist --verbose"
Loading "fastestmirror" plugin Config time: 0.010 Yum version: 3.4.3 Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Setting up Package Sacks pkgsack time: 0.004 Repo-id : xcp-ng-base Repo-name : XCP-ng Base Repository Repo-revision: 1711706182 Repo-updated : Fri Mar 29 05:56:22 2024 Repo-pkgs : 3,599 Repo-size : 12 G Repo-baseurl : http://mirrors.xcp-ng.org/8/8.3/base/x86_64/, : http://updates.xcp-ng.org/8/8.3/base/x86_64/ Repo-expire : 21,600 second(s) (last: Sat Mar 30 15:37:49 2024) Filter : read-only:present Repo-filename: /etc/yum.repos.d/xcp-ng.repo Repo-id : xcp-ng-updates Repo-name : XCP-ng Updates Repository Repo-revision: 1693236966 Repo-updated : Mon Aug 28 11:36:06 2023 Repo-pkgs : 2 Repo-size : 4.6 k Repo-baseurl : http://mirrors.xcp-ng.org/8/8.3/updates/x86_64/, : http://updates.xcp-ng.org/8/8.3/updates/x86_64/ Repo-expire : 21,600 second(s) (last: Sat Mar 30 15:37:50 2024) Filter : read-only:present Repo-filename: /etc/yum.repos.d/xcp-ng.repo repolist: 3,601
-
RE: XCP-ng 8.3 beta 🚀
Hmmmm...while I'm gonna say a guarded "I don't think so", that is a junk machine that I use to test things so that may be a possibility.
How do I tell?
-
RE: XCP-ng 8.3 beta 🚀
I noteced new updates for 8.3 this morning. Oen of teh machines will not update. When you try to run it from XOA you get this error:
pool.installPatches { "hosts": [ "7ce4f772-4391-4982-a1f9-d1de86be92cb" ] } { "code": "-1", "params": [ "Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1", "", "Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator return func(*args, **kwargs) File \"/etc/xapi.d/plugins/updater.py\", line 182, in update return install_helper(session, args, 'update') File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper raise error CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1 " ], "call": { "method": "host.call_plugin", "params": [ "OpaqueRef:fab0b7b0-de37-a996-1760-92a38cf136c2", "updater.py", "update", {} ] }, "message": "-1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator return func(*args, **kwargs) File \"/etc/xapi.d/plugins/updater.py\", line 182, in update return install_helper(session, args, 'update') File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper raise error CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1 )", "name": "XapiError", "stack": "XapiError: -1(Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1, , Traceback (most recent call last): File \"/etc/xapi.d/plugins/xcpngutils/__init__.py\", line 119, in wrapper return func(*args, **kwds) File \"/etc/xapi.d/plugins/updater.py\", line 96, in decorator return func(*args, **kwargs) File \"/etc/xapi.d/plugins/updater.py\", line 182, in update return install_helper(session, args, 'update') File \"/etc/xapi.d/plugins/updater.py\", line 153, in install_helper raise error CalledProcessError: Command '['yum', 'update', '--disablerepo=*', '--enablerepo=xcp-ng-base,xcp-ng-updates', '-y']' returned non-zero exit status 1 ) at Function.wrap (file:///opt/xo/xo-builds/xen-orchestra-202403291838/packages/xen-api/_XapiError.mjs:16:12) at file:///opt/xo/xo-builds/xen-orchestra-202403291838/packages/xen-api/transports/json-rpc.mjs:38:21" If you go to the command line and do a "yum update" you get this: Transaction Summary =================================================================================================================================================================================== Install ( 1 Dependent package) Upgrade 21 Packages Total size: 84 M Is this ok [y/d/N]: y Downloading packages: Running transaction check Running transaction test Transaction check error: file /usr/lib64/python2.7/site-packages/xen/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/lowlevel/__init__.py from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/__init__.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/__init__.pyo from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/lowlevel/__init__.pyo from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python2.7/site-packages/xen/lowlevel/xc.so from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/__pycache__/__init__.cpython-36.opt-1.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/lowlevel/__pycache__/__init__.cpython-36.opt-1.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/__pycache__/__init__.cpython-36.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/lowlevel/__pycache__/__init__.cpython-36.pyc from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 file /usr/lib64/python3.6/site-packages/xen/lowlevel/xc.cpython-36m-x86_64-linux-gnu.so from install of xen-installer-files-4.13.5-10.42.3.xcpng8.3.x86_64 conflicts with file from package xen-dom0-tools-4.17.3-2.0.xen417.1.xcpng8.3.x86_64
Any ideas?
-
RE: VM performance VMWare 8 vs XCP-NG 8.2.1
I did disk speed tests on about thirty VMs as I moved from esxi 8 to XCP-NG (both 8.2.1 and 8.3). In about 60% of the tests esxi was faster and 40% XCP-NG was faster. I used Crystalmark in my tests. When the test disk was a 1gb disk, esxi was a lot faster but when I changed the test disks to 8gb the results were split and there was not much of a difference between winner and looser..
-
RE: XCP-ng 8.3 beta 🚀
Yesterday, as I was about to walk out of the office for a deposition, someone walked in and said the connection to oen of the VM's was dead.
I opened up Idrac to the Dell host (Dell Inc. PowerEdge R540) and found a black screen unlike any I've seen before with XCP-NG; my vague recollection was a standard linux screen with "system" or something like that. I had twenty minutes to get to the deposition so I didn't have time to do normal debugging so I rebooted the host and watched as it did a normal reboot. It came back and all was well.
Now that the dust has cleared, this is my first chance to look into what happened. Where do I start? /var/log/xensource.log? /var/log/kern.log? Something else?
Thanks!
-
RE: What are Unhealthy VDIs, Orphan VDIs, VDIs attached to Control Domain?
@olivierlambert
Thanks!I found out that the ones where nothing was happening would complete (and leave the Unhealthy VDI section) if I did a snapshot of the vm and then immediately deleted the snapshot.
-
RE: What are Unhealthy VDIs, Orphan VDIs, VDIs attached to Control Domain?
@olivierlambert
I clicked "forget" under all the SRs under VDIs attached to Control Domain and they immediately populated under Orphan VDIsTwo have this message "January 17, 2024 at 8:10 PM (last month)"
and one has this "February 19, 2024 at 8:10 PM (10 days ago)".One of the VM's SR's occurs with both the January 17, 2024 at 8:10 PM as well as the February 19, 2024 at 8:10 PM date.
Under Unhealthy VDIs there is still one VM listed (also in the list above).