XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. gskger
    • Profile
    • Following 0
    • Followers 1
    • Topics 3
    • Posts 146
    • Best 72
    • Controversial 0
    • Groups 1

    gskger

    @gskger

    Top contributor 💪

    196
    Reputation
    136
    Profile views
    146
    Posts
    1
    Followers
    0
    Following
    Joined Last Online

    gskger Unfollow Follow
    Top contributor 💪

    Best posts made by gskger

    • RE: Backup reports on Microsoft Teams

      You could at least send the backup reports (requires backup-reports and transport-email plugin on XOA) to a Microsoft Teams channel of your choice (Channel - More options - Get email adress).

      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @gduperrey Updated my two host playlab without a problem. Installed and/or update guest tools (now reporting 7.30.0-11) on some mainstream Linux distros worked as well as the usual VM operations in the pool. Looks good 👍

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @stormi Did not even know the problem existed 😇 . Anyway, added a new (second) DNS server (9.9.9.9) to the DNS server list via xsconsole and rebooted the host (XCP-ng 8.2.0 fully patched).

      Before update: DNS 9.9.9.9 did not persist, only the previous settings are shown
      After update: DNS 9.9.9.9 did persist the reboot and is listed together with the previous settings

      Deleting DNS 9.9.9.9 worked as well, so the xsconsole update worked for me.

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @stormi Updated my two host playlab (8.2.0 fully patched, the third host currently serves as a Covid-19 homeoffice workstation) with no error. Rebooted and ran the usual tests (create, live migrate, copy and delete a linux and a windows 10 VM as well as create / revert snapshot (with/without ram) ). Fooled myself with a VM_LACKS_FEATURE error on the windows 10 VM until I realized that I forgot to install the Guest tools 🤕 - I need more sleep. Will try a restore after tonights backup.

      Edit: restore from backup worked as well 👍

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      Updated my playlab and nothing to report. Looks good.

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @gduperrey Rolling update of my homelab through Xen Orchestra worked flawlessly. Thanks!

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @gduperrey Updated my playlab and did some basic tests (create, copy, snapshot, (life-) migrate VMs and disks). Looking good so far.

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @gduperrey Update installed successfully on my 2 host playlab with shared NFS TrueNAS Core storage on a 10G network. Let's see how VM usage works during the next days.

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @stormi Again more a regression test for the basic things. Tested Debian and Ubuntu VMs (create, live migrate with/-out guest tools (now at 7.20.0-9), start/stop/reboot, snapshot with/-out RAM and revert, storage migrate from/to shared and local SR). Imported Centos and Ubuntu VMs and restored a Windows 10 and a Debian VM from backup. No issues so far. Nice work.

      posted in News
      gskgerG
      gskger
    • RE: Updates announcements and testing

      @stormi Did the update on my two host playlab, which worked well. Do not use secureboot/UEFI or QNAP, so this is more a regression test for the usual stuff. I tested Debian, Centos and Ubuntu VMs (create, live migrate with/-out guest tools (now at 7.20.0-8), start/stop/reboot, snapshot with/-out RAM and revert, storage migrate from/to shared and local SR) and restored a Windows 10 and a Debian VM from backup. As for now, everthing is working. I will see how backup runs tonight.

      posted in News
      gskgerG
      gskger

    Latest posts made by gskger

    • RE: XCP-ng 8.3 public alpha 🚀

      @stormi No problem with a rolling pool update of my two playlab host. Pool reports up-to-date and healthy (XO from source). Basic VM and VDI tasks work as expected. Looking good 👍

      posted in News
      gskgerG
      gskger
    • RE: NFS for ISO and VDI doesn't recognize subdirectory path

      @Darkbeldin Mh, in the SMlog it is ls /tmp/nfs -1 --color=never. Thats the number one but should that be the letter l? With the number one, lsreturns.

      [17:31 h01 ~]# ls /tmp/nfs -1 --color=never
      test
      textfile
      
      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: NFS for ISO and VDI doesn't recognize subdirectory path

      @Darkbeldin If you rebuild the probing from SMlog and repeat that on the XCP-ng host, you can see the subdirectory (and a textfile I put there)

      [17:16 H01 ~]# mount -o soft,proto=tcp,vers=3,acdirmin=0,acdirmax=0 10.10.70.143:/tmp/srv/nfs/ /tmp/nfs
      [17:16 h01 ~]# ls /tmp/nfs -l --color=never
      drwxr-xr-x 2 root root 4096 20. Apr 16:41 test
      -rw-r--r-- 1 root root    0 20. Apr 17:16 textfile
      [17:21 h01 ~]# umount /tmp/nfs
      

      H01 is the XCP-ng host and 10.10.70.143 the NFS server.
      Or should that be done from XOA?

      Edit: I was lazy and entered the commands, automaticaly using the letter l in the ls command while the SMlog says 1. Maybe that is related.

      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: NFS for ISO and VDI doesn't recognize subdirectory path

      @Darkbeldin Tried to search the subdirectory like described in this github post with XOA free and a Debian 11 NFS server, but it does indeed not show the subdirectory.

      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: 10 gig secondary network

      @abelaguilar Not sure if I understood your question correctly, so I hope my example helps a little.

      I have two 1G switches in my homelab (Cisco SG300-28). SW01 is for management and VM traffic, SW02 is for storage traffic only. All storage ports on SW02 are on VLAN 100 which only exists on this switch. Only the management network is allowed between SW01 and SW02.

      Each host has 4 ports (either quad port or two internal plus one dual port NIC), giving all hosts eth0, eth1, eth2 and eth3. eth2 and eth3 are in a bond for storage with a Synology as shared storage.

      5698e975-bbca-40c8-bad7-9def701c8419-grafik.png

      From the picture you see that I don't need a DNS and Gateway for the storage network to work and I can ping the storage network from the hosts. So as Olivier said, it is possible.

      Can you share the layout of your storage network with more details on switches and NICs? That would help to track down possible configuration issues.

      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: XO Dashboard

      @fred974 Yes, that is correct. It is the same color and graph as on the VMs general tab.

      posted in Xen Orchestra
      gskgerG
      gskger
    • RE: XCP-ng 8.3 public alpha 🚀

      @stormi
      Probably more a fun test than a real world test. I installed XCP-ng 8.3 alpha2 run on a

      HP T620 PLUS Thin Client
      AMD GX-420CA @ 2GHz low power APU SoC (Jaguar)
      16 GB RAM

      According to Art of Server on Youtube, this Thin Client supports up to 32GB RAM. It idles around 14-17W with XCP-ng and one Debian VM running. It also features a low profile PCI-e slot that I use with a Intel Pro / 1000 PT quad port LP card.

      [21:58 xcp83 xtf]# ./xtf-runner selftest -q --host
      Combined test results:
      test-hvm32-selftest                      SUCCESS
      test-hvm32pae-selftest                   SUCCESS
      test-hvm32pse-selftest                   SUCCESS
      test-hvm64-selftest                      SUCCESS
      test-pv64-selftest                       SUCCESS
      
      
      [21:58 xcp83 xtf]# ./xtf-runner -aqq --host
      Combined test results:
      test-pv64-cpuid-faulting                 SKIP
      test-pv64-pv-fsgsbase                    SKIP
      test-hvm32-umip                          SKIP
      test-hvm64-umip                          SKIP
      test-pv64-xsa-167                        SKIP
      test-pv64-xsa-182                        SKIP
      [21:59 xcp83 xtf]# echo $?
      3
      
      
      [21:59 xcp83 xtf]# /usr/libexec/xen/bin/test-cpu-policy
      CPU Policy unit tests
      Testing CPU vendor identification:
      Testing CPUID serialise success:
      Testing CPUID deserialise failure:
      Testing CPUID out-of-range clearing:
      Testing MSR serialise success:
      Testing MSR deserialise failure:
      Testing policy compatibility success:
      Testing policy compatibility failure:
      Done: all ok
      [22:00 xcp83 xtf]# echo $?
      0
      
      
      posted in News
      gskgerG
      gskger
    • RE: XCP-ng 8.3 public alpha 🚀

      @stormi Of course! Picked up that habit from other posts. Should I correct my post to improve readability?

      posted in News
      gskgerG
      gskger
    • RE: XCP-ng 8.3 public alpha 🚀

      @stormi
      Going back in time with my first Intel NUC. Had to switch EPT superpages to secure mode to prevent host crashing.

      Intel D54250WYK
      Intel Core i5-4250U [MT]
      16GB RAM

      [17:43 xcp83 xtf]# ./xtf-runner selftest -q --host
      Combined test results:
      test-hvm32-selftest                      SUCCESS
      test-hvm32pae-selftest                   SUCCESS
      test-hvm32pse-selftest                   SUCCESS
      test-hvm64-selftest                      SUCCESS
      test-pv64-selftest                       SUCCESS
      
      
      [18:08 xcp83 xtf]# ./xtf-runner -aq --host
      Combined test results:
      test-hvm32-cpuid-faulting                SUCCESS
      test-hvm32pae-cpuid-faulting             SUCCESS
      test-hvm32pse-cpuid-faulting             SUCCESS
      test-hvm64-cpuid-faulting                SUCCESS
      test-pv64-cpuid-faulting                 SUCCESS
      test-hvm64-fpu-exception-emulation       SUCCESS
      test-hvm32-invlpg~hap                    SUCCESS
      test-hvm32-invlpg~shadow                 SUCCESS
      test-hvm32pae-invlpg~hap                 SUCCESS
      test-hvm32pae-invlpg~shadow              SUCCESS
      test-hvm64-invlpg~hap                    SUCCESS
      test-hvm64-invlpg~shadow                 SUCCESS
      test-hvm64-lbr-tsx-vmentry               SUCCESS
      test-hvm32-livepatch-priv-check          SUCCESS
      test-hvm64-livepatch-priv-check          SUCCESS
      test-pv64-livepatch-priv-check           SUCCESS
      test-hvm32pae-memop-seg                  SUCCESS
      test-hvm64-memop-seg                     SUCCESS
      test-pv64-memop-seg                      SUCCESS
      test-hvm32pae-nmi-taskswitch-priv        SUCCESS
      test-pv64-pv-fsgsbase                    SUCCESS
      test-pv64-pv-iopl~hypercall              SUCCESS
      test-pv64-pv-iopl~vmassist               SUCCESS
      test-hvm32-swint-emulation               SUCCESS
      test-hvm32pae-swint-emulation            SUCCESS
      test-hvm32pse-swint-emulation            SUCCESS
      test-hvm64-swint-emulation               SUCCESS
      test-hvm32-umip                          SKIP
      test-hvm64-umip                          SKIP
      test-hvm32-xsa-122                       SUCCESS
      test-hvm32pae-xsa-122                    SUCCESS
      test-hvm32pse-xsa-122                    SUCCESS
      test-hvm64-xsa-122                       SUCCESS
      test-pv64-xsa-122                        SUCCESS
      test-hvm32-xsa-123                       SUCCESS
      test-pv64-xsa-167                        SKIP
      test-hvm64-xsa-168                       SUCCESS
      test-hvm64-xsa-170                       SUCCESS
      test-hvm64-xsa-173                       SUCCESS
      test-pv64-xsa-182                        SKIP
      test-hvm32-xsa-186                       SUCCESS
      test-hvm64-xsa-186                       SUCCESS
      test-hvm32-xsa-188                       SUCCESS
      test-hvm32pae-xsa-188                    SUCCESS
      test-hvm32pse-xsa-188                    SUCCESS
      test-hvm64-xsa-188                       SUCCESS
      test-pv64-xsa-188                        SUCCESS
      test-hvm32-xsa-191                       SUCCESS
      test-hvm32-xsa-192                       SUCCESS
      test-pv64-xsa-193                        SUCCESS
      test-hvm64-xsa-195                       SUCCESS
      test-hvm64-xsa-196                       SUCCESS
      test-hvm32-xsa-200                       SUCCESS
      test-hvm32-xsa-203                       SUCCESS
      test-hvm64-xsa-204                       SUCCESS
      test-pv64-xsa-212                        SUCCESS
      test-pv64-xsa-213                        SUCCESS
      test-hvm64-xsa-221                       SUCCESS
      test-pv64-xsa-221                        SUCCESS
      test-pv64-xsa-224                        SUCCESS
      test-pv64-xsa-227                        SUCCESS
      test-hvm64-xsa-231                       SUCCESS
      test-pv64-xsa-231                        SUCCESS
      test-hvm64-xsa-232                       SUCCESS
      test-pv64-xsa-232                        SUCCESS
      test-pv64-xsa-234                        SUCCESS
      test-hvm32-xsa-239                       SUCCESS
      test-pv64-xsa-255                        SUCCESS
      test-pv64-xsa-259                        SUCCESS
      test-pv64-xsa-260                        SUCCESS
      test-hvm64-xsa-261                       SUCCESS
      test-pv64-xsa-265                        SUCCESS
      test-hvm64-xsa-269                       SUCCESS
      test-hvm64-xsa-277                       SUCCESS
      test-hvm64-xsa-278                       SUCCESS
      test-pv64-xsa-279                        SUCCESS
      test-pv64-xsa-286                        SUCCESS
      test-pv64-xsa-296                        SUCCESS
      test-pv64-xsa-298                        SUCCESS
      test-hvm64-xsa-304                       SUCCESS
      test-hvm64-xsa-308                       SUCCESS
      test-pv64-xsa-316                        SUCCESS
      test-hvm32-xsa-317                       SUCCESS
      test-hvm32pae-xsa-317                    SUCCESS
      test-hvm32pse-xsa-317                    SUCCESS
      test-hvm64-xsa-317                       SUCCESS
      test-pv64-xsa-317                        SUCCESS
      test-pv64-xsa-333                        SUCCESS
      test-pv64-xsa-339                        SUCCESS
      test-hvm32pae-xsa-consoleio-write        SUCCESS
      
      [18:08 xcp83 xtf]# echo $?
      3
      
      [18:10 xcp83 xtf]# /usr/libexec/xen/bin/test-cpu-policy
      CPU Policy unit tests
      Testing CPU vendor identification:
      Testing CPUID serialise success:
      Testing CPUID deserialise failure:
      Testing CPUID out-of-range clearing:
      Testing MSR serialise success:
      Testing MSR deserialise failure:
      Testing policy compatibility success:
      Testing policy compatibility failure:
      Done: all ok
      
      [18:10 xcp83 xtf]# echo $?
      0
      
      posted in News
      gskgerG
      gskger
    • RE: XCP-ng 8.3 public alpha 🚀

      @stormi

      One of my first playlab XCP-ng hosts. Clean 8.3.0-alpha2 install had some hickups where the installer did not complete (twice) and demanded a reboot. Did a clean 8.2.1 install to verify and that went well. Repeated a clean 8.3.0-alpha2 install after that and strangely that worked 🤔 . Can investigate a bit more if helpfull, but to lazy right now 😇 .

      Intel NUC6i5SYK
      Intel Core i5-6260U [MT]
      32GB RAM

      [15:46 xcp83 xtf]# ./xtf-runner selftest -q --host
      Combined test results:
      test-hvm32-selftest                      SUCCESS
      test-hvm32pae-selftest                   SUCCESS
      test-hvm32pse-selftest                   SUCCESS
      test-hvm64-selftest                      SUCCESS
      test-pv64-selftest                       SUCCESS
      
      [15:46 xcp83 xtf]# ./xtf-runner -aq --host
      Combined test results:
      test-hvm32-cpuid-faulting                SUCCESS
      test-hvm32pae-cpuid-faulting             SUCCESS
      test-hvm32pse-cpuid-faulting             SUCCESS
      test-hvm64-cpuid-faulting                SUCCESS
      test-pv64-cpuid-faulting                 SUCCESS
      test-hvm64-fpu-exception-emulation       SUCCESS
      test-hvm32-invlpg~hap                    SUCCESS
      test-hvm32-invlpg~shadow                 SUCCESS
      test-hvm32pae-invlpg~hap                 SUCCESS
      test-hvm32pae-invlpg~shadow              SUCCESS
      test-hvm64-invlpg~hap                    SUCCESS
      test-hvm64-invlpg~shadow                 SUCCESS
      test-hvm64-lbr-tsx-vmentry               SUCCESS
      test-hvm32-livepatch-priv-check          SUCCESS
      test-hvm64-livepatch-priv-check          SUCCESS
      test-pv64-livepatch-priv-check           SUCCESS
      test-hvm32pae-memop-seg                  SUCCESS
      test-hvm64-memop-seg                     SUCCESS
      test-pv64-memop-seg                      SUCCESS
      test-hvm32pae-nmi-taskswitch-priv        SUCCESS
      test-pv64-pv-fsgsbase                    SUCCESS
      test-pv64-pv-iopl~hypercall              SUCCESS
      test-pv64-pv-iopl~vmassist               SUCCESS
      test-hvm32-swint-emulation               SUCCESS
      test-hvm32pae-swint-emulation            SUCCESS
      test-hvm32pse-swint-emulation            SUCCESS
      test-hvm64-swint-emulation               SUCCESS
      test-hvm32-umip                          SKIP
      test-hvm64-umip                          SKIP
      test-hvm32-xsa-122                       SUCCESS
      test-hvm32pae-xsa-122                    SUCCESS
      test-hvm32pse-xsa-122                    SUCCESS
      test-hvm64-xsa-122                       SUCCESS
      test-pv64-xsa-122                        SUCCESS
      test-hvm32-xsa-123                       SUCCESS
      test-pv64-xsa-167                        SKIP
      test-hvm64-xsa-168                       SUCCESS
      test-hvm64-xsa-170                       SUCCESS
      test-hvm64-xsa-173                       SUCCESS
      test-pv64-xsa-182                        SKIP
      test-hvm32-xsa-186                       SUCCESS
      test-hvm64-xsa-186                       SUCCESS
      test-hvm32-xsa-188                       SUCCESS
      test-hvm32pae-xsa-188                    SUCCESS
      test-hvm32pse-xsa-188                    SUCCESS
      test-hvm64-xsa-188                       SUCCESS
      test-pv64-xsa-188                        SUCCESS
      test-hvm32-xsa-191                       SUCCESS
      test-hvm32-xsa-192                       SUCCESS
      test-pv64-xsa-193                        SUCCESS
      test-hvm64-xsa-195                       SUCCESS
      test-hvm64-xsa-196                       SUCCESS
      test-hvm32-xsa-200                       SUCCESS
      test-hvm32-xsa-203                       SUCCESS
      test-hvm64-xsa-204                       SUCCESS
      test-pv64-xsa-212                        SUCCESS
      test-pv64-xsa-213                        SUCCESS
      test-hvm64-xsa-221                       SUCCESS
      test-pv64-xsa-221                        SUCCESS
      test-pv64-xsa-224                        SUCCESS
      test-pv64-xsa-227                        SUCCESS
      test-hvm64-xsa-231                       SUCCESS
      test-pv64-xsa-231                        SUCCESS
      test-hvm64-xsa-232                       SUCCESS
      test-pv64-xsa-232                        SUCCESS
      test-pv64-xsa-234                        SUCCESS
      test-hvm32-xsa-239                       SUCCESS
      test-pv64-xsa-255                        SUCCESS
      test-pv64-xsa-259                        SUCCESS
      test-pv64-xsa-260                        SUCCESS
      test-hvm64-xsa-261                       SUCCESS
      test-pv64-xsa-265                        SUCCESS
      test-hvm64-xsa-269                       SUCCESS
      test-hvm64-xsa-277                       SUCCESS
      test-hvm64-xsa-278                       SUCCESS
      test-pv64-xsa-279                        SUCCESS
      test-pv64-xsa-286                        SUCCESS
      test-pv64-xsa-296                        SUCCESS
      test-pv64-xsa-298                        SUCCESS
      test-hvm64-xsa-304                       SUCCESS
      test-hvm64-xsa-308                       SUCCESS
      test-pv64-xsa-316                        SUCCESS
      test-hvm32-xsa-317                       SUCCESS
      test-hvm32pae-xsa-317                    SUCCESS
      test-hvm32pse-xsa-317                    SUCCESS
      test-hvm64-xsa-317                       SUCCESS
      test-pv64-xsa-317                        SUCCESS
      test-pv64-xsa-333                        SUCCESS
      test-pv64-xsa-339                        SUCCESS
      test-hvm32pae-xsa-consoleio-write        SUCCESS
      
      [15:47 xcp83 xtf]# echo $?
      3
      
      [15:49 xcp83 xtf]# /usr/libexec/xen/bin/test-cpu-policy
      CPU Policy unit tests
      Testing CPU vendor identification:
      Testing CPUID serialise success:
      Testing CPUID deserialise failure:
      Testing CPUID out-of-range clearing:
      Testing MSR serialise success:
      Testing MSR deserialise failure:
      Testing policy compatibility success:
      Testing policy compatibility failure:
      Done: all ok
      
      [15:49 xcp83 xtf]# echo $?
      0
      
      posted in News
      gskgerG
      gskger