Red Hat Bugzilla – Bug 1257865
Missing support for Windows Server 2012 R2
Last modified: 2016-11-04 00:42:34 EDT
Description of problem:
Windows Server 2012 R2 is not supported by libosinfo. So `osinfo-detect win.img` shows only "Media is bootable". OS info is missing.
Also gnome-boxes failed to create new box.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. get windows iso
2. in terminal run command `osinfo-detect windows.iso`
Only "Media is bootable" is print out
OS info is print on terminal screen
Can you provide the output of isoinfo -d -i win.iso ? If you have a f22 (or newer) install available, could you test if your iso is correctly identified there?
isoinfo -d -i en_windows_server_2012_r2_with_update_x64_dvd_6052708.iso
CD-ROM is in ISO 9660 format
Volume id: IR5_SSS_X64FRE_EN-US_DV9
Volume set id: IR5_SSS_X64FRE_EN-US_DV9
Publisher id: MICROSOFT CORPORATION
Data preparer id: MICROSOFT CORPORATION, ONE MICROSOFT WAY, REDMOND WA 98052, (425) 882-8080
Application id: CDIMAGE 2.53 (01/01/2005 TM)
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 2635688
El Torito VD version 1 found, boot catalog is in sector 22
NO Joliet present
NO Rock Ridge present
Eltorito validation header:
Arch 0 (x86)
ID 'Microsoft Corporation'
Key 55 AA
Eltorito defaultboot header:
Bootid 88 (bootable)
Boot media 0 (No Emulation Boot)
Load segment 0
Sys type 0
Bootoff 876 2166
Fixed by https://git.fedorahosted.org/cgit/libosinfo.git/commit/?id=f688b844ccd551d9c5748c6f31114f4e58c7c931
I suggest a rebase of libosinfo to 0.3.0 release.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
Switching to another advisory.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.