Hi Pat

I have successfully installed 7.2 alpha as a KVM guest on a SL6.7 host.
Also the yum update worked OK.
Just one point. There is a /etc/yum.repos.d/redhat.repo file generated. Should this be suppressed?

I also tried  to install 7.2 alpha on a host machine from USB, but it failed to boot with kernel panic.
This is the same machine that failed to boot on SL7.1 with the new kernel.
(Motherboard M4A87TD/USB3 with CPU AMD Phenom II X4 955)
Is there a way to add boot parameters to the USB boot process?
I need to add the initcall_blacklist=clocksource_done_booting parameter.

Cheers, and have a Happy Christmas, Hanukkah, Xmas or whatever you celebrate at this time.
Bill
 
-----Original message-----
> From:Pat Riehecky <[log in to unmask]>
> Sent: Wednesday 23rd December 2015 5:00
> To: [log in to unmask]
> Subject: Posted for testing: Scientific Linux 7.2 x86_64 ALPHA
> 
> Scientific Linux 7.2 x86_64 ALPHA - Dec 22, 2015
> 
> == Information ==
> 
> THIS IS NOT A PRODUCTION RELEASE OF SCIENTIFIC LINUX 7.2
> 
> NOTE: Please review the SL Release Notes along with
> The Upstream Vendor's Release Notes:
> 
> http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/release-notes/
> 
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/index.html
> 
> There is a great deal of information within those documents not listed here.
> 
> Send comments/issues/test reports to:
> [log in to unmask]
> 
> == Media ==
> You can find the release media at:
> http://ftp.scientificlinux.org/linux/scientific/7rolling/x86_64/iso/
> 
> Alternatively the livecd-iso-to-disk utility is able to convert
> this to USB successfully. A USB device of sufficient size is
> required.
> 
> Alternatively you can utilize the dd command to write the
> raw image to a USB device.
> 
> http://ftp.scientificlinux.org/linux/scientific/7/x86_64/release-notes/#_how_to_make_a_bootable_usb_installer
> 
> == SL Specific Updates ==
> .External Repos
> With SL 7.2, yum-conf files pointing to non-base SL (such as EPEL,
> ELRepo, SL-Extras, SL-SoftwareCollections, ZFS) have moved to a
> central location.
> A repo definition pointing to the new location is contained in
> yum-conf-repos.
> Since these repos are not specific to individual releases of SL, the
> separate location will allow for easier adding and removing of these
> resources for SL7 going forward.
> 
> .OpenAFS
> For the SL 7.2 pre-release we are shipping OpenAFS 1.6.16-pre a later
> version of SL 7.2 will feature the upstream release of OpenAFS 1.6.16
> 
> .Yum behavior update
> Backported patch from upstream for yum fs-vars, per BZ#1281593
> Now yum vars set in /etc/yum/vars will be checked even in an
> alternate yum-root.
> Thanks for the bug report Lincoln Bryant!
> 
> .Updates to sl-release
> Updated to use the 7.2 pre-release repos
> 
> .IPA customizations
> The IPA packages have been customized to remove the upstream links to 
> their support services.
> 
> .Build Fixes
> The curl and mariadb packages were modified to ensure their unit tests 
> for date validation worked after Oct 2015
> 
> .Scientific Linux Contexts
> SL 7.2 includes initial support for Scientific Linux Contexts which
> should allow for ease of creating local customization for specific
> computing needs.  The supporting code is contained in 
> anaconda-addon-org_scientificlinux_contexts but is not currently activated.
> More details on this will be published in the future.
> 
> == Known Bugs ==
> 
> 
> 
> == UEFI Secure Boot ==
> The status of UEFI Secure Boot for Scientific Linux is noted in detail at:
> 
> http://ftp.scientificlinux.org/linux/scientific/7/x86_64/release-notes/#_about_uefi_secure_boot
> 
> Booting SL7 with Secure Boot enabled works but requires a manual step.
> This is because the "shim" has not been signed by the UEFI CA.
> Instructions are included within the SL7 Release Notes.
> 
>