XCP-ng 8.1 Release Candidate now available!

stormi

@mortenchristensn said in XCP-ng 8.1 Release Candidate now available!:

The homepage welcome-screen on a 8.1.0 server point to download of XCP-ng Center 8.0.1.26.
That xcp-ng-center version cannot connect to a 8.1 server.

Thanks. I think that's because there's no officially stable release of XCP-ng Center out yet due do the fact that @borzel is alone to maintain is and doesn't have time for it. Either there will be a stable release of the center before our final release, or we'll update the welcome page to point to the latest dev release (with a warning).

olivierlambert

We can also link the GitHub repo directly

borzel

@olivierlambert I would prefer that

dariosplit

"Existing SRs are untouched (so remain formatted to EXT3)" How to convert existing Local storage? I upgraded to 8.1, but Local storage is Ext3.

stormi

@dariosplit said in XCP-ng 8.1 Release Candidate now available!:

"Existing SRs are untouched (so remain formatted to EXT3)" How to convert existing Local storage? I upgraded to 8.1, but Local storage is Ext3.

Quoting further:

There is no easy way to convert an existing SR created with our driver, so those using it will need to move the VDIs out (to another SR or to export them), destroy the SR and create an EXT SR instead. Make sure to do this on XCP-ng 8.1.

So is your question about how to create a SR and how to destroy one? What about @Biggen's link shared above?

mortenchristensn

@stormi said in :

I'm not sure that your test for the file type is valid.

You are right. Running your test on my server gives same answer
Linux rev 1.0 ext4 filesystem data

mortenchristensn

@stormi said in :

So is your question about how to create a SR and how to destroy one? What about @Biggen's link shared above?

The link is not telling, how to change the Local Storage.
As far as I can see, Local Storage is not a partition like SR's on other physical disks.

peder

@mortenchristensn Local storage is an SR.

The commands below will remove the SR named "Local storage" and create a new one with the same name on the same device

If you have a pool with several hosts you need to run these commands on each host and, as stormi points out in the comment below, you need to move any VMs out of the Local SR before removing it.

# Get the IDs and device path to the current Local SR :
# xe host-list | grep -B1 $HOSTNAME | grep ^uuid| cut -d\: -f2 | cut -d" " -f2 > HostUuid.txt
# xe pbd-list sr-name-label=Local\ storage host-uuid=`cat HostUuid.txt` | grep sr-uuid | cut -d\: -f2 | cut -d" " -f2 > SR-Uuid.txt
# xe pbd-list sr-name-label=Local\ storage host-uuid=`cat HostUuid.txt` | grep ^uuid | cut -d\: -f2 | cut -d" " -f2 > Uuid.txt
# xe pbd-list sr-name-label=Local\ storage host-uuid=`cat HostUuid.txt` | grep device-config| cut -d\: -f3 | cut -d" " -f2 > Device.txt
# Unplug and destroy the Local SR : 
# xe pbd-unplug uuid=`cat Uuid.txt | egrep "*-*-*-*-*" `
# xe sr-forget uuid=`cat SR-Uuid.txt | egrep "*-*-*-*-*" `
# Create the new Local SR : 
# xe sr-create content-type=user device-config:device=`cat Device.txt` host-uuid=`cat HostUuid.txt` name-label=Local\ storage shared=false type=ext

stormi

Of course, move the VMs out of the SR before destroying it

dariosplit

@peder Dosen't work. My version is 8.1 Build date: 2020-02-19 and reciveed the resoult " Name: Local storage Type: Ext3."

Danp

@dariosplit What exactly doesn't work? Where did you receive that output?

dariosplit

@Danp I got Ext3 again instead of Ext4.

stormi

@dariosplit said in XCP-ng 8.1 Release Candidate now available!:

@Danp I got Ext3 again instead of Ext4.

How do you check exactly? (you haven't answered to @Danp's "Where did you receive that output?")

dariosplit

@stormi cat /etc/fstab
LABEL=root-penujp / ext3 defaults 1 1
LABEL=swap-penujp swap swap defaults 0 0
LABEL=logs-penujp /var/log ext3 defaults 0 2

stormi

That's / and /var/log, not a local storage repository. Just read the other messages of this thread for a way to find the local SR and test its FS type.

Andrew

After an ISO upgrade to RC1 from 8.0 it booted... so that's good.

Using XCP-ng Center 99.99.99.28:
Changing "Control Domain Memory" does not take effect.
SMB ISO fails "SM has thrown a generic python exception" for existing SR.
I deleted the ISO SR and can't create a new one (same error):
SMB ISO fails "SM has thrown a generic python exception" for new SR.

Python errors at boot:
Traceback (most recent call last):
File "/usr/lib64/xsconsole/XSConsole.py", line 46, in <module> main()
File "/usr/lib64/xsconsole/XSConsole.py", line 37, in main app.Enter()
File "/usr/lib64/xsconsole/XSConsoleTerm.py", line 57, in Enter Data.Inst(),Up
date()
File "/usr/lib64/xsconsole/XSConsoleData.py", line 343, in Update self.DeriveDa
ta()
File "/usr/lib64/xsconsole/XSConsoleData.py", line 361, in DeriveData name = "
".join(cpu['modelname'].split()))
TypeError: string indices must be integers, not str

I did not have the problems with 8.0.

I had one VM that will no longer boot because of a missing disk. After attaching the disk there was a message about a PV error (it's not set for PV) and it still fails.

As a test system there may have been some issues left over but it was all working with 8.0.

So as a "production ready" upgrade. No.

stormi

Thanks for the feedback.

What's the output of uname -a?

@Andrew said in XCP-ng 8.1 Release Candidate now available!:

After an ISO upgrade to RC1 from 8.0 it booted... so that's good.

Using XCP-ng Center 99.99.99.28:
Changing "Control Domain Memory" does not take effect.

We do not support XCP-ng Center. The community as a whole can. Can you reproduce with other methods of changing dom0 memory? See https://support.citrix.com/article/CTX134951

SMB ISO fails "SM has thrown a generic python exception" for existing SR.
I deleted the ISO SR and can't create a new one (same error):
SMB ISO fails "SM has thrown a generic python exception" for new SR.

Does it work from Xen Orchestra? From command line using xe? Can you extract the errors at the time of the action from /var/log/SMlog, /var/log/daemon.log and /var/log/xensource.log?

Python errors at boot:
Traceback (most recent call last):
File "/usr/lib64/xsconsole/XSConsole.py", line 46, in <module> main()
File "/usr/lib64/xsconsole/XSConsole.py", line 37, in main app.Enter()
File "/usr/lib64/xsconsole/XSConsoleTerm.py", line 57, in Enter Data.Inst(),Up
date()
File "/usr/lib64/xsconsole/XSConsoleData.py", line 343, in Update self.DeriveDa
ta()
File "/usr/lib64/xsconsole/XSConsoleData.py", line 361, in DeriveData name = "
".join(cpu['modelname'].split()))
TypeError: string indices must be integers, not str

Where is that error seen? Is it visible directly in the console in place of XSConsole? It's like the value of cpu is a string instead of a dict. Weird.

I did not have the problems with 8.0.

I had one VM that will no longer boot because of a missing disk. After attaching the disk there was a message about a PV error (it's not set for PV) and it still fails.

I've never seen upgrades detach disks from VMs. I suggest to open a separate thread for discussing and debugging the issue about this VM. Please give as much information as possible in that thread, including errors from logs (see https://github.com/xcp-ng/xcp/wiki/Logfiles).

peder

@dariosplit I made a new 8.1-RC1 install and had the installer set up the Local SR as LVM.
After the installation I ran the commands in my previous example and afterwards 'mount' and 'file -sL' show that it's ext4.

HOWEVER; xsconsole still claims "Type : Ext3" so the console seems to have hard coded that "ext = ext3".
Something for RC2 sort out.

Andrew

Linux node2 4.19.102 #1 SMP Thu Mar 5 19:21:42 CET 2020 x86_64 x86_64 x86_64 GNU/Linux

I like XCP-ng better... but I use XO too. The both have different advantages and issues.

Using xen-cmdline --set-xen dom0_mem changes the grub.cfg entries EXCEPT the default (first) kernel-alt entry. So yes, it works, but not for the alt kernel install. Not the end of the world, I can edit the file and move on. But, should it modify all xen config lines or just the default/first one?

I am able to create the SMB ISO SR using XO. The big issue is the old one (that I deleted) worked in 8.0 but did not work after the upgrade. Not a big deal the recreate it, but not good for an upgrade. There is some compatibility issue behind the scenes that now fails where it did not before.

Mar 10 23:25:06 node2 SM: [4467] self.dconf['vers'] = 3.0
Mar 10 23:25:06 node2 SM: [4467] Exception while attempting to append mount options
Mar 10 23:25:06 node2 SM: [4467] ***** generic exception: sr_attach: EXCEPTION <type 'exceptions.KeyError'>, 'username'
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 110, in run
Mar 10 23:25:06 node2 SM: [4467] return self._run_locked(sr)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 159, in _run_locked
Mar 10 23:25:06 node2 SM: [4467] rv = self._run(sr, target)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 349, in _run
Mar 10 23:25:06 node2 SM: [4467] return sr.attach(self.params['sr_uuid'])
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/ISOSR", line 286, in attach
Mar 10 23:25:06 node2 SM: [4467] self.appendCIFSMountOptions(mountcmd)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/ISOSR", line 430, in appendCIFSMountOptions
Mar 10 23:25:06 node2 SM: [4467] cifutils.splitDomainAndUsername(self.dconf['username'])
Mar 10 23:25:06 node2 SM: [4467]
Mar 10 23:25:06 node2 SM: [4467] ***** ISO: EXCEPTION <type 'exceptions.KeyError'>, 'username'
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 372, in run
Mar 10 23:25:06 node2 SM: [4467] ret = cmd.run(sr)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 110, in run
Mar 10 23:25:06 node2 SM: [4467] return self._run_locked(sr)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 159, in _run_locked
Mar 10 23:25:06 node2 SM: [4467] rv = self._run(sr, target)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/SRCommand.py", line 349, in _run
Mar 10 23:25:06 node2 SM: [4467] return sr.attach(self.params['sr_uuid'])
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/ISOSR", line 286, in attach
Mar 10 23:25:06 node2 SM: [4467] self.appendCIFSMountOptions(mountcmd)
Mar 10 23:25:06 node2 SM: [4467] File "/opt/xensource/sm/ISOSR", line 430, in appendCIFSMountOptions
Mar 10 23:25:06 node2 SM: [4467] cifutils.splitDomainAndUsername(self.dconf['username'])
Mar 10 23:25:06 node2 SM: [4467]

It looks like XCP-ng Center created the SMB ISO SR as a guest login without a username/password (empty/blank). Adding "guest/guest" in XO seems to resolve the problem. The issue is it worked before in 8.0 but not in 8.1.

The errors at boot are seen in the console after boot and login prompt but before the XSConsole screen.

As for the disk problem... I have been messing around a LOT with everything (local storage, iscsi, 7.6, 8.0, and back). I'm would not be happy to see these strange these strange things in a production system but I have been messing with the hosts in the lab more than a normal setup.

I'm new to XCP and trying to help the community so I can benefit from improved software too.

stormi

@Andrew said in XCP-ng 8.1 Release Candidate now available!:

Linux node2 4.19.102 #1 SMP Thu Mar 5 19:21:42 CET 2020 x86_64 x86_64 x86_64 GNU/Linux

That is a very important information: you are using the alternate kernel (on purpose, I suppose? The installer is not supposed to make it the default kernel for you). Pinging @r1 to take your feedback into account and debug.