Description of problem: Windows 10 is not supported by libosinfo. So `osinfo-detect win10.iso` 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): libosinfo-0.2.12-1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. get windows iso 2. in terminal run command `osinfo-detect windows10.iso` Actual results: Only "Media is bootable" is print out Expected results: OS info is print on terminal screen
Can you provide the output of isoinfo -d -i win81.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_10_enterprise_x86_dvd_6851156.iso CD-ROM is in ISO 9660 format System id: Volume id: J_CENA_X86FREV_EN-US_DV5 Volume set id: J_CENA_X86FREV_EN-US_DV5 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: 1420691 El Torito VD version 1 found, boot catalog is in sector 22 NO Joliet present NO Rock Ridge present Eltorito validation header: Hid 1 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 Nsect 8 Bootoff 222 546
Should be fixed by https://www.redhat.com/archives/libosinfo/2015-September/msg00029.html
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 mmccune 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. https://rhn.redhat.com/errata/RHBA-2016-2367.html