Seems to work fine on my old test rig i7-4710MQ
with NFS
Best posts made by ph7
-
RE: XCP-ng 8.3 updates announcements and testing
-
RE: XCP-ng 8.3 updates announcements and testing
I updated my test host and all seems to work fine.
But I have 1 question:
Do I need to disable the testing repo or is it removed at the reboot?yum clean metadata --enablerepo=xcp-ng-testing
yum update --enablerepo=xcp-ng-testing
reboot[10:33 x1 ~]# yum repolist Inlästa insticksmoduler: 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-updates: mirrors.xcp-ng.org förråds-id förrådsnamn status xcp-ng-base XCP-ng Base Repository 4 376 xcp-ng-updates XCP-ng Updates Repository 125 repolist: 4 501
-
RE: XCP-ng 8.3 updates announcements and testing
Tested OK on
Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz -
RE: XCP-ng 8.3 betas and RCs feedback 🚀
I powered on my spare test "server" and ran this update.
All went fine.
After the reboot I started the fully updated XOA (local installed) and ran it for a few minutes.
then I shut it down but it sat for a few minutes so I did a force shut down from xsconsole.
Rebooted the host again and started the XOA, shut it down and it worked fine
Tested one more time and it went OK. -
RE: XCP-ng 8.3 betas and RCs feedback 🚀
Upgrade to RC2 worked fine so far with netinstall ISO in ventoy on a 8 gen i5 HP laptop. And a "full" ISO on its own USB on a Lenovo Thinkcentre Ryzen 5 2400GE
-
RE: Performance-Plugin is showing the wrong SR on resolution
@olivierlambert
I have reported a similar issue with the cpu report:
Lots of performance alerts after upgrading XO to commit aa490
https://xcp-ng.org/forum/topic/9658/lots-of-performance-alerts-after-upgrading-xo-to-commit-aa490/14#
-
RE: Weird performance alert. Start importing VM for no reason.
I increased the dom0 RAM from default 1.75 to 2 GiB
Hopefully this will do. -
RE: Disk exclusion from backup
yes there is, in the docs
https://docs.xen-orchestra.com/backups#exclude-disks
Latest posts made by ph7
-
RE: XCP-ng 8.3 updates announcements and testing
Seems to work fine on my old test rig
i7-4710MQ
withNFS
-
RE: Feedback XO v6
@ph7 said in Feedback XO v6:
I have 2 pools and XO CE says I have 4 ( 2 unreachable)
Again I'm a total idiot
I had two old test hosts remaining underSettings/Servers
Once I removed them thePool status
in XO CE is correct.
-
RE: Feedback XO v6
And... during the replication job:
Haven't tested during backup
-
RE: Feedback XO v6
Did some more testing and removed one VM from the replication job
.
The VM is still in a backup job under
Sequencies
and should be green /In at least 1 job & protected
-
RE: ConBee II USB passthrough
@GTwannabe
Have You tried PCI pass through
It worked well for my Sonoff Zigbee 3.0 USB Dongle Plus V2 -
Feedback XO v6
I can't find a kind of feedback thread for the new XO version 6.
Maybe You already have one, but anyhow, here is a my input.
I am comparing XO CE72f3c
and XOA105.0
I have 2 pools and XO CE says I have 4 ( 2 unreachable)
XOA seems to be correct:
I have 4 backup jobs, 5 VMs & 1 cont/metadata, 1 of the jobs has 2 scedules and 4 of the VMs are also in a replication job
The backup jobs are disabled and scheduled underSequences
The replication job is scheduled underBackup Overview
I also have 7 test VMs without any job and 8 powered off replicationsXO CE,
Disabled 3
, are scheduled underSequences
and should also be green /running good
.
And it would be nice to have the possibility to add atag
to my 7 test VMs so they don't appear underin no job
But so far it's an improvement over to XOA
-
RE: Upgrade to XO v5.105 seems broken
@irtaza9
My updates (from docs) work, except the v6
https://xcp-ng.org/forum/topic/10685/xo-ce-82ed2-and-5c390-update. -
RE: XO CE 82ed2 and 5c390 update.
I did run the update again
root@XO:~# cd ~/xen-orchestra/ && git checkout . && git pull --ff-only && yarn && yarn build --force && yarn run turbo run build --filter @xen-orchestra/web && systemctl restart xo-server.service && cd
The commit is latest:
a420a
But the /v6 don't show the
New VM
button
As it does in XOA 5.105.0
Have there been a change in this part of the update procedure that has updated the /v6 earlier ?
yarn run turbo run build --filter @xen-orchestra/web
-
XO CE 82ed2 and 5c390 update.
Running the update from docs give me a
ERROR run failed: command exited (1)
, but when checking in xo it gives the right commithere is some of the output from cli:
@xen-orchestra/web:build: vite v6.2.1 building for production... src/pages/vm/new.vue:60:63 - error TS2339: Property 'id' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 60 <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id"> @xen-orchestra/web:build: ~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:60:79 - error TS2339: Property 'id' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 60 <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id"> @xen-orchestra/web:build: ~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:61:34 - error TS2339: Property 'name_label' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 61 {{ vdi.name_label }} @xen-orchestra/web:build: ~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:121:63 - error TS2339: Property 'id' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 121 <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id"> @xen-orchestra/web:build: ~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:121:79 - error TS2339: Property 'id' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 121 <option v-for="vdi in vdis" :key="vdi.id" :value="vdi.id"> @xen-orchestra/web:build: ~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:122:34 - error TS2339: Property 'name_label' does not exist on type 'never'. @xen-orchestra/web:build: @xen-orchestra/web:build: 122 {{ vdi.name_label }} @xen-orchestra/web:build: ~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:285:46 - error TS2339: Property '$SR' does not exist on type '{ name_label: string; name_description: string; size: number; sr: Branded<"sr"> | undefined; }'. @xen-orchestra/web:build: @xen-orchestra/web:build: 285 <select v-model="vdi.$SR"> @xen-orchestra/web:build: ~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:315:47 - error TS2339: Property 'sr' does not exist on type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 315 <select v-model="disk.sr"> @xen-orchestra/web:build: ~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:329:46 - error TS2339: Property 'name_label' does not exist on type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 329 <UiInput v-model="disk.name_label" :placeholder="$t('disk-name')" accent="brand" /> @xen-orchestra/web:build: ~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:332:46 - error TS2339: Property 'size' does not exist on type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 332 <UiInput v-model="disk.size" :placeholder="$t('size')" accent="brand" /> @xen-orchestra/web:build: ~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:335:46 - error TS2339: Property 'name_description' does not exist on type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 335 <UiInput v-model="disk.name_description" :placeholder="$t('description')" accent="brand" /> @xen-orchestra/web:build: ~~~~~~~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:583:7 - error TS7053: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'. @xen-orchestra/web:build: No index signature with a parameter of type 'string' was found on type '{}'. @xen-orchestra/web:build: @xen-orchestra/web:build: 583 result[key] = filteredList @xen-orchestra/web:build: ~~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:600:21 - error TS2345: Argument of type '{ name_label: string; name_description: string; sr: Branded<"sr"> | undefined; size: number; }' is not assignable to parameter of type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 600 vmState.vdis.push({ @xen-orchestra/web:build: ~ @xen-orchestra/web:build: 601 name_label: (vmState.name || 'disk') + '_' + generateRandomString(4), @xen-orchestra/web:build: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @xen-orchestra/web:build: ... @xen-orchestra/web:build: 604 size: 0, @xen-orchestra/web:build: ~~~~~~~~~~~~ @xen-orchestra/web:build: 605 }) @xen-orchestra/web:build: ~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:698:5 - error TS2322: Type '({ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; } | null)[]' is not assignable to type 'NetworkInterface[]'. @xen-orchestra/web:build: Type '{ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; } | null' is not assignable to type 'NetworkInterface'. @xen-orchestra/web:build: Type 'null' is not assignable to type 'NetworkInterface'. @xen-orchestra/web:build: @xen-orchestra/web:build: 698 return template.VIFs.map(ref => { @xen-orchestra/web:build: ~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:701:29 - error TS2677: A type predicate's type must be assignable to its parameter's type. @xen-orchestra/web:build: Property 'id' is missing in type 'NetworkInterface' but required in type '{ id: Branded<"vif">; interface: string | Branded<"network">; macAddress: string; }'. @xen-orchestra/web:build: @xen-orchestra/web:build: 701 }).filter((vif): vif is NetworkInterface => Boolean(vif)) @xen-orchestra/web:build: ~~~~~~~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:700:22 @xen-orchestra/web:build: 700 return vif ? { id: vif.id, interface: getNetwork(vif.$network)?.id || '', macAddress: vif.MAC } : null @xen-orchestra/web:build: ~~~~~~~~~~ @xen-orchestra/web:build: 'id' is declared here. @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:719:5 - error TS2322: Type 'string | Branded<"network">' is not assignable to type 'Branded<"network">'. @xen-orchestra/web:build: Type 'string' is not assignable to type 'Branded<"network">'. @xen-orchestra/web:build: Type 'string' is not assignable to type '{ [__brand]: "network"; }'. @xen-orchestra/web:build: @xen-orchestra/web:build: 719 interface: defaultNetwork?.id || '', @xen-orchestra/web:build: ~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/types/xo/new-vm.type.ts:16:3 @xen-orchestra/web:build: 16 interface: XoNetwork['id'] @xen-orchestra/web:build: ~~~~~~~~~ @xen-orchestra/web:build: The expected type comes from property 'interface' which is declared here on type '{ interface: Branded<"network">; macAddress: string; }' @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:774:24 - error TS18048: 'vmState.new_vm_template' is possibly 'undefined'. @xen-orchestra/web:build: @xen-orchestra/web:build: 774 const templateVifs = vmState.new_vm_template.VIFs @xen-orchestra/web:build: ~~~~~~~~~~~~~~~~~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:785:7 - error TS2698: Spread types may only be created from object types. @xen-orchestra/web:build: @xen-orchestra/web:build: 785 ...disk, @xen-orchestra/web:build: ~~~~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:786:29 - error TS2339: Property 'size' does not exist on type 'string'. @xen-orchestra/web:build: @xen-orchestra/web:build: 786 size: giBToBytes(disk.size), @xen-orchestra/web:build: ~~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: src/pages/vm/new.vue:793:18 - error TS18048: 'vif' is possibly 'undefined'. @xen-orchestra/web:build: @xen-orchestra/web:build: 793 device = vif.device @xen-orchestra/web:build: ~~~ @xen-orchestra/web:build: @xen-orchestra/web:build: @xen-orchestra/web:build: Found 20 errors. @xen-orchestra/web:build: error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. @xen-orchestra/web:build: ERROR: "type-check" exited with 2. error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. @xen-orchestra/web:build: ERROR: command finished with error: command (/root/xen-orchestra/@xen-orchestra/web) /tmp/yarn--1743427189862-0.2226594809552045/yarn run build exited (1) @xen-orchestra/web#build: command (/root/xen-orchestra/@xen-orchestra/web) /tmp/yarn--1743427189862-0.2226594809552045/yarn run build exited (1) Tasks: 0 successful, 1 total Cached: 0 cached, 1 total Time: 33.216s Failed: @xen-orchestra/web#build ERROR run failed: command exited (1) error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
It seems like there is some problem with the new VM create in v6.
edit: 3f565 was fine but not 82ed2