Release Notes

VMM does not displays Windows Server 2012 in drop-
down list
Description: Virtual Machine Manager (VMM) does not display Windows Server 2012 in the drop-down list of a new
Virtual Machine window.
Applies to: Red Hat Enterprise Linux 7.0
Cause: There is no entry created for Windows Server 2012 in the VMM.
Workaround: There is no functionality loss. You can install Windows Server 2012 after selecting any generic windows
item from the drop-down list.
Ethtool link test fails in Offline mode despite the
cable being connected to the port
Description: Ethtool link test fails in Offline mode despite the cable being connected to the port.
Applies to: Red Hat Enterprise Linux 7.0
Cause: A PHY link require five seconds to enable the link.
Workaround: This error message can be ignored because there is no functionality loss.
PXE boot fails with a system crash when Red Hat
Enterprise Linux 7 is installed on local storage and the
tftp server has an invalid boot EFI file
Description:
When Red Hat Enterprise Linux 7.0 is installed on local storage and we try to boot through PXE in UEFI
mode, where the PXE setup has an invalid boot EFI file in tftp server, it is expected to boot from Red
Hat Enterprise Linux 7.0 on local storage, however it fails with Red Screen of Death (RSOD).
Applies to: Red Hat Enterprise Linux 7.0
Cause:
1. shim must load the grub from where the shim is loaded, currently there is no check for this.
2. RSOD occurs since there is no check against the pointer in the unhook system services, which is
responsible for loading the image.
Workaround: Ensure that the valid boot EFI file is configured in the tftp server.
NVMe driver reports I/O error on Surprise Removal or
Surprise Insertion
Description:
NVMe driver reports multiple buffer I/O errors on surprise removal and surprise insertion of a NVMe
device and the following error message is displayed Buffer I/O error on device nvme0n1,
logical block 0.
Applies to: Red Hat Enterprise Linux 7.0
Cause: Surprise Removal Surprise Insertion (SRSI) feature is not supported.
Workaround: This error message can be ignored because there is no functionality loss.
42 Known issues