@gduperrey, I suspected that was the case after seeing that message but wanted to make sure. Thanks!
Posts made by JeffBerntsen
-
RE: XCP-ng 8.2 updates announcements and testing
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi said in XCP-ng 8.2 updates announcements and testing:
@JeffBerntsen Do you have XOSTOR on the pool?
Not yet, but was planning to add it to this test pool so thought I should downgrade beforehand. Does that particular patch only apply to systems with XOSTOR already installed?
-
RE: XCP-ng 8.2 updates announcements and testing
@gduperrey, that doesn't seem to work for me. I receive an error from yum:
No Match for available package: http-nbd-transfer-1.3.0-1.xcpng8.2.x86_64
Nothing to do -
RE: XCP-ng 8.2 updates announcements and testing
Seems to be working well on my test servers.
-
RE: XCP-ng 8.2 updates announcements and testing
This seems to be working well for me too.
-
RE: Is it possible to do this with VM list filters?
@Danp You're right, I missed the question mark on it when I tried it before. With the question mark, it works. Thank you for your help.
-
RE: Is it possible to do this with VM list filters?
@Danp I've tried that and it doesn't seem to work. Entering hasVendorDevice into the filter box whether followed with nothing, with :true or :false, leaves the filtered VM list completely empty. I'm running on xoa updated to the latest stable channel version, 5.99.1.
-
Is it possible to do this with VM list filters?
I'm trying to filter the VM list to show only Windows servers that are set to receive drivers via Windows update and don't seem to be able to do it. As far as I know, the property is called hasVendorDevice but using either hasVendorDevice:true or hasVendorDevice:false ends up showing no VMs at all? Am I doing something wrong and, if so, what or is it just not possible to filter on this? I'm also trying to filter based on the secure boot setting and having the same problem with that.
Any help would be greatly appreciated.
-
RE: XCP-ng 8.2 updates announcements and testing
@bleader They're installed and running well on my test lab systems.
-
RE: XOSTOR and mdadm software RAID
@OhSoNoob I've used XOSTOR on top of MDRAID and it seemed to work well for me during my testing. I ran tests of it on top of MD RAID 1, 5, and 10 (MDRAID's "RAID 10" which isn't really RAID 10) and had good luck with it. The XOSTOR is really adding a second layer of redundancy at that point, similar to MDRAID 5+1 builds so is almost overkill. Almost.
Where I see the most benefit from XOSTOR on MDRAID would be on top of RAID 10 or RAID 0 arrays. Depending on the speed of your drives, you might get some benefit from the increased read speed (and read/write speed for RAID 0). In addition, RAID 10 would give you some additional redundancy so that losing a drive wouldn't mean the loss of that node for XOSTOR's purposes, possibly making recovery easier.
The ability for some redundancy might also be useful for a stretched cluster or some other situation where your network links between XOSTOR nodes isn't as fast as it should be; The ability to recover at the RAID level might be much faster than recovering or rebuilding an entire node over a slow link.
@ronan-a, I'm not sure if you remember, but the very first test of XOSTOR I ran, shortly after it was introduced,, were on top of RAID 10 arrays. I kept that test cluster alive and running until equipment failure (failed motherboards, nothing related to XOSTOR or MDRAID) forced me to scrap it. I had similar teething pains to others while XOSTOR was being developed and debugged during the test phase, but nothing related to running on top of MDRAID as far as I could tell.
-
RE: XCP-ng 8.2 updates announcements and testing
@stormi Not a problem. I just wanted to make sure I hadn't done something wrong. As it is, the system is working with all of the updates but that one in place.
-
RE: XCP-ng 8.2 updates announcements and testing
Only one of my two systems will take the complete update, but that one is working just fine.
The other which I had used in the past as a test server for XOSTOR will not install the sm-2.30.8-12.1.xcpng8.2.x86_64 package looking for a dependency on sm-linstor and not finding it.
-
RE: XOSTOR hyperconvergence preview
@flibbi, @olivierlambert RAID shouldn't be problem for XOSTOR. During some of my testing shortly after the preview was released, I was running it on software RAID 10 arrays on each of my test servers. As long as the RAID isn't some sort of "fake RAID" and is done in hardware, it should work fine.
-
RE: Xen 4.17 on XCP-ng 8.3!
@stormi None of the other things I tried fixed the problems with left over update artifacts but running a normal yum update after this did. Thanks!
-
RE: XCP-ng 8.2 updates announcements and testing
@bleader Seems to be running just fine on my test servers as well.
-
RE: XCP-ng 8.2 updates announcements and testing
They're running without problems for me on my test systems
-
RE: XCP-ng 8.2 updates announcements and testing
This is installed and working on my two test systems but they're both AMD so I'm not able to test the updated microcode.
-
RE: Xen 4.17 on XCP-ng 8.3!
@stormi
I've tried that and also yum-complete-transaction --enablerepo=xcp-ng-lab to see if that would make a difference but no change in the problem. I've also tried to revert the patches with the yum downgrade command from the first message here and see similar problems. -
RE: Xen 4.17 on XCP-ng 8.3!
Hmm. I'm getting the following errors when I try to install the update with the yum update --enablerepo=xcp-ng-lab command
Loaded plugins: fastestmirror 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-lab: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org Resolving Dependencies --> Running transaction check ---> Package forkexecd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package forkexecd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package forkexecd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package gpumon.x86_64 0:0.25.0-6.1.xcpng8.3 will be updated ---> Package gpumon.x86_64 0:0.25.0-6.1.0.xen417.1.xcpng8.3 will be updated ---> Package gpumon.x86_64 0:0.25.0-6.1.0.xen417.2.xcpng8.3 will be an update ---> Package libblkid.x86_64 0:2.23.2-52.el7_5.1 will be updated ---> Package libblkid.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update ---> Package libmount.x86_64 0:2.23.2-52.el7_5.1 will be updated ---> Package libmount.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update ---> Package libuuid.x86_64 0:2.23.2-52.el7_5.1 will be updated ---> Package libuuid.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update ---> Package message-switch.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package message-switch.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package message-switch.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package python2-xapi-storage.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package python2-xapi-storage.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package rrdd-plugins.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package rrdd-plugins.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package sm.x86_64 0:3.0.12-6.1.xcpng8.3 will be updated ---> Package sm.x86_64 0:3.0.12-6.2.xcpng8.3 will be an update ---> Package sm-cli.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package sm-cli.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package sm-cli.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package squeezed.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package squeezed.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package util-linux.x86_64 0:2.23.2-52.el7_5.1 will be updated ---> Package util-linux.x86_64 0:2.23.2-52.1.xcpng8.3 will be an update ---> Package varstored-guard.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package varstored-guard.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package varstored-guard.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package vhd-tool.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package vhd-tool.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package vhd-tool.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package wsproxy.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package wsproxy.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package wsproxy.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-core.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xapi-core.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-core.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-nbd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xapi-nbd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-nbd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-rrd2csv.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-storage-script.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xapi-storage-script.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-storage-script.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-tests.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-tests.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xapi-xe.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xapi-xe.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xapi-xe.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xcp-networkd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xcp-networkd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xcp-networkd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xcp-ng-xapi-plugins.noarch 0:1.9.1-1.xcpng8.3 will be updated ---> Package xcp-ng-xapi-plugins.noarch 0:1.10.0-1.xcpng8.3 will be an update ---> Package xcp-rrdd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xcp-rrdd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xen-dom0-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated --> Processing Dependency: libxenctrl.so.4.13()(64bit) for package: 1:kexec-tools-2.0.15-18.xcpng8.3.x86_64 --> Processing Dependency: libxenctrl.so.4.13()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 --> Processing Dependency: libxenguest.so.4.13()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 ---> Package xen-dom0-libs.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-dom0-libs.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xen-dom0-tests.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated ---> Package xen-dom0-tests.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-dom0-tests.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xen-dom0-tools.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated ---> Package xen-dom0-tools.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-dom0-tools.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xen-hypervisor.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated ---> Package xen-hypervisor.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-hypervisor.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xen-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: blktap-3.54.6-2.1.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: vncterm-10.2.0-3.xcpng8.3.x86_64 ---> Package xen-libs.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-libs.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xen-tools.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated ---> Package xen-tools.x86_64 0:4.17.3-1.0.xen417.1.xcpng8.3 will be updated ---> Package xen-tools.x86_64 0:4.17.3-3.0.xen417.0.xcpng8.3 will be an update ---> Package xenopsd.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xenopsd.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xenopsd.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xenopsd-cli.x86_64 0:23.31.0-1.1.xcpng8.3 will be updated ---> Package xenopsd-cli.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xenopsd-cli.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xenopsd-xc.x86_64 0:23.31.0-1.1.0.xen417.2.xcpng8.3 will be updated ---> Package xenopsd-xc.x86_64 0:23.31.0-1.6.0.xen417.0.xcpng8.3 will be an update ---> Package xsconsole.x86_64 0:10.1.14-2.1.xcpng8.3 will be updated ---> Package xsconsole.x86_64 0:10.1.14-2.2.xcpng8.3 will be an update --> Running transaction check ---> Package xen-installer-files.x86_64 0:4.13.5-10.42.3.xcpng8.3 will be installed ---> Package xen-libs.x86_64 0:4.13.5-10.58.xcpng8.3 will be updated --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: blktap-3.54.6-2.1.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 --> Processing Dependency: libxenstore.so.3.0()(64bit) for package: vncterm-10.2.0-3.xcpng8.3.x86_64 --> Finished Dependency Resolution Error: Package: vncterm-10.2.0-3.xcpng8.3.x86_64 (@xcp:main/$releasever) Requires: libxenstore.so.3.0()(64bit) Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenstore.so.3.0()(64bit) Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed) Not found Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab) Not found Error: Package: xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 (@xcp:main/$releasever) Requires: libxenstore.so.3.0()(64bit) Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenstore.so.3.0()(64bit) Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed) Not found Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab) Not found Error: Package: blktap-3.54.6-2.1.xcpng8.3.x86_64 (@xcp-ng-base) Requires: libxenstore.so.3.0()(64bit) Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenstore.so.3.0()(64bit) Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed) Not found Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab) Not found Error: Package: 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 (@xcp-ng-base) Requires: libxenstore.so.3.0()(64bit) Removing: xen-libs-4.13.5-10.58.xcpng8.3.x86_64 (@xcp-ng-base) libxenstore.so.3.0()(64bit) Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.13.4-10.27.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.35.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.4-10.36.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.40.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.1.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.42.3.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Available: xen-libs-4.13.5-10.51.xcpng8.3.x86_64 (xcp-ng-base) libxenstore.so.3.0()(64bit) Removing: xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 (installed) Not found Updated By: xen-libs-4.17.3-3.0.xen417.0.xcpng8.3.x86_64 (xcp-ng-lab) Not found Available: xen-libs-4.17.3-2.0.xen417.1.xcpng8.3.x86_64 (xcp-ng-lab) Not found You could try using --skip-broken to work around the problem ** Found 28 pre-existing rpmdb problem(s), 'yum check' output follows: blktap-3.54.6-2.1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with blktap-3.54.6-2.1.xcpng8.3.x86_64 forkexecd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with forkexecd-23.31.0-1.1.xcpng8.3.x86_64 gpumon-0.25.0-6.1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with gpumon-0.25.0-6.1.xcpng8.3.x86_64 1:kexec-tools-2.0.15-18.0.xen417.1.xcpng8.3.x86_64 is a duplicate with 1:kexec-tools-2.0.15-18.xcpng8.3.x86_64 message-switch-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with message-switch-23.31.0-1.1.xcpng8.3.x86_64 2:qemu-4.2.1-5.2.4.0.xen417.1.xcpng8.3.x86_64 is a duplicate with 2:qemu-4.2.1-5.2.4.xcpng8.3.x86_64 sm-cli-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with sm-cli-23.31.0-1.1.xcpng8.3.x86_64 varstored-guard-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with varstored-guard-23.31.0-1.1.xcpng8.3.x86_64 varstored-tools-1.2.0-1.3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with varstored-tools-1.2.0-1.3.xcpng8.3.x86_64 vhd-tool-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with vhd-tool-23.31.0-1.1.xcpng8.3.x86_64 vncterm-10.2.0-3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with vncterm-10.2.0-3.xcpng8.3.x86_64 wsproxy-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with wsproxy-23.31.0-1.1.xcpng8.3.x86_64 xapi-core-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-core-23.31.0-1.1.xcpng8.3.x86_64 xapi-nbd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-nbd-23.31.0-1.1.xcpng8.3.x86_64 xapi-rrd2csv-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-rrd2csv-23.31.0-1.1.xcpng8.3.x86_64 xapi-storage-script-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-storage-script-23.31.0-1.1.xcpng8.3.x86_64 xapi-xe-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xapi-xe-23.31.0-1.1.xcpng8.3.x86_64 xcp-clipboardd-1.0.3-7.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xcp-clipboardd-1.0.3-7.xcpng8.3.x86_64 xcp-featured-1.1.6-3.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xcp-featured-1.1.6-3.xcpng8.3.x86_64 xcp-networkd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xcp-networkd-23.31.0-1.1.xcpng8.3.x86_64 xen-dom0-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-libs-4.13.5-10.58.xcpng8.3.x86_64 xen-dom0-tests-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-tests-4.13.5-10.58.xcpng8.3.x86_64 xen-dom0-tools-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-dom0-tools-4.13.5-10.58.xcpng8.3.x86_64 xen-hypervisor-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-hypervisor-4.13.5-10.58.xcpng8.3.x86_64 xen-libs-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-libs-4.13.5-10.58.xcpng8.3.x86_64 xen-tools-4.17.3-1.0.xen417.1.xcpng8.3.x86_64 is a duplicate with xen-tools-4.13.5-10.58.xcpng8.3.x86_64 xenopsd-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xenopsd-23.31.0-1.1.xcpng8.3.x86_64 xenopsd-cli-23.31.0-1.1.0.xen417.2.xcpng8.3.x86_64 is a duplicate with xenopsd-cli-23.31.0-1.1.xcpng8.3.x86_64
-
Cannot deploy new XOA with a static IP address
I just tried deploying a new XOA VM to test out the new XO 5.92 and ran into problems trying to deploy it with a static IP address.
No errors are given deploying either via the web form or the deployment script and I can specify static addressing, IP, gateway, netmask, and DNS without any problem. No matter what I enter, the XOA always uses DHCP addressing.
The next thing I tried was deploying via an import of the XVA file and setting the addresses as VM parameters which also had the same problem.
My next attempt was to deploy using DHCP addressing and enabling SSH (which did work) then log in via SSH and use the xoa network static cli command and had the same problem.
I eventually looked at the /etc/network/interfaces file and output from the ip addr command and discovered that the network interface is named enX0 while the parameters are being set for network interface eth0. Manually editing the file and changing eth0 to enX0 corrected the problem and now the static address assignment is working.
I suspect either whatever configuration script or program is there is always setting a configuration for the wrong network interface name, eth0 instead of enX0 or there is something configured to rename the network interface to eth0 that isn't working correctly.