XCP-ng 8.3 public alpha π
-
@Fungusware Hi!
Yes this feature is supported at XAPI level, the
VM.snapshot
method now has aignore_vdis
field which is a list of VDI ref to not include in the snapshot.
This also available throughxe
:xe vm-snapshot vm=... ignore-vdi-uuids=uuid1,uuid2...
Regards
-
@Fungusware Yes, @BenjiReis spent some time to make that contribution to XAPI upstream, see https://github.com/xapi-project/xen-api/pull/4563
-
Note: this is already implemented in Xen Orchestra since a while (by default we try to ignore the [NOBAK] disk if XAPI is able to do it, which is now the case for 8.3)
-
@BenjiReis Thanks for the info.
I'll see if I can support into the SDK also, at least for .NET anyway.
-
What is current status? What is the rough expectation of next alpha/beta release
-
What kind of status are you expecting?
-
@olivierlambert Yes, I had been doing this also for quite some time. It was certainly one of the most requested features. It also felt a bit 'brute force' to me so would be nice to use it built in.
-
@olivierlambert Well.. I have been doing the occasional "yum update" with no new problems. Everything is working great, but I still have that re-scanning of the FS every 30 seconds.. Not impacting anything but just a little weird...
-
@hoerup said in XCP-ng 8.3 public alpha :
What is current status? What is the rough expectation of next alpha/beta release
The next planned release should be the first beta. There's no precise ETA yet, but first quarter of 2023 is a likely window.
Applying updates regularly on top of the alpha will also give you the same end-result.
There are a lot of updated packages that are being prepared. They're currently in the
xcp-ng-testing
yum repository, because we haven't had time to test them all in our internal CI. All I could assess is that they install well (yum update --enablerepo=xcp-ng-testing
) and that the server I installed them to rebooted without any visible issue. Once tested, early January, they'll be moved to thexcp-ng-base
repository and offered as updates to anyone runningyum update
on their 8.3. If you want to give it a go ahead of time, you can install them and see if everything works well or not, so that we can quickly work on any issues early January.Recent work on 8.3 touched:
- the installer (soft RAID support improvements, IPv6 support, contribution of various small improvements to upstream repositories...)
- automated installation ISO generation
- adding memtest86+ to the installer, both in BIOS and UEFI modes
- upgrading all packages to the same level as Xenserver 8 Stream's (that's the new name for Citrix Hypervisor 8 Cloud) preview update channels - we had 4 months of changes to catch up with.
- redirecting
http://ip_or_name_of_xcpng_server/
tohttps://ip_or_name_of_xcpng_server/
- ongoing work with XenServer on the python2 to python3 transition
- work on UEFI certificate handling, to reach a stage where it answers both XenServer's and our needs
- and more.
-
Hello,
I have some trouble with update from 8.2 to 8.3I boot the installation from USB with Image xcp-ng-8.3.0-alpha2.
Everything works until I get to the installation. The backup of the old version is still made, then this error message appears:
Old partition layout is unsupported, run prepare_host_upgrade and try again. Reboot
The 8.2 installation is a 3 month old fresh installation, I doubt there is an old partition type in this 8.2 version.
I removed all disks except the boot disk which only contains the XCP-NG system. Still the same error.
The partition structure of the disk is as follows:Model: ATA TS512GSSD720 (scsi)
Disk /dev/sda: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_bootNumber Start End Size File system Name Flags
4 1049kB 538MB 537MB bios_grub, legacy_boot
1 538MB 4295MB 3757MB ext3
2 4296MB 8590MB 4294MB ext3
3 8591MB 512GB 504GB lvmDoes anyone have an idea what's going wrong.
I don't want to do a fresh installation because then I have to restore a lot of data. It's my test machine and I have a backup, but with 29 TB it takes days to restore and without data there is little point in testing 8.3.
regards Joerg
-
Hi,
Can you give the output of
lsblk
, it's more readable to me -
@olivierlambert
Does this help?sda 8:0 0 477G 0 disk ββsda4 8:4 0 512M 0 part ββsda2 8:2 0 4G 0 part ββsda3 8:3 0 469G 0 part β ββXSLocalEXT--d7a8bce5--29b3--5d83--f41f--5307f2e1b1bb-d7a8bce5--29b3--5d83--f41f--5307f2e1b1bb 253:0 0 468.9G 0 lvm /run/sr-mount/d7a8bce5-29b3-5d83-f41f-5307f2e1b1bb ββsda1
-
This is the old partition scheme
It can't be a fresh install, it's not possible.
edit: ah wait. Can you do a
mount
command?edit 2: a basic lsblk should display where the partition is mounted, did you copy/pasted everything?
-
@olivierlambert
Thanks for help by the wayI'am shure that it is a new installation from 3 month ago, it is a new Server and I bought it 3 month ago.
regards Joerg
-
@olivierlambert
Sorry I miss one line:
ββsda1 8:1 0 3.5G 0 part / -
You should have 2x 18G partitions (/ and a backup one), 1x 4G partition (/var/log) and a 512MB partition (/boot)
-
@olivierlambert
My
Boot has 537MB
/ has 3757MB
Backup 4294MB -
Okay so this is the old partition scheme. Can you repeat exactly what did you do with this machine? I mean initially. I don't know how to even get the old partition scheme in the first place with XCP-ng (there's 0 edition of XCP-ng with this old partition scheme, it's only before XenServer 6.5)
-
@olivierlambert
I disable all hard drives and put in a new sda and do a fresh installation.
So I can always go back if something doesn't work out.
In any case, thanks for the help.
Regards Joerg -
That's really weird, I don't understand how it's possible to install a fresh XCP-ng (without doing any upgrade) with the old partition layout