Bug 2068173 - libguests v1.46 virt-inspector and guestfish inspect-os functions do not return values for Windows 2019 dynamic disks
Summary: libguests v1.46 virt-inspector and guestfish inspect-os functions do not retu...
Keywords:
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libguestfs
Version: unspecified
Hardware: All
OS: Windows
unspecified
high
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-24 15:05 UTC by roy.lemmon
Modified: 2023-04-26 10:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-31 07:42:57 UTC
Embargoed:


Attachments (Terms of Use)

Description roy.lemmon 2022-03-24 15:05:27 UTC
Description of problem:

We are trying to use virt-inspector to get Windows OS information for a Windows guest that utilizes a Dynamic boot disk.  These commands work fine for Basic disks.


Version-Release number of selected component (if applicable): 
1.46


How reproducible:
100%


Steps to Reproduce:
1. Run virt-inspector against a Windows 2019 dynamic disk image
2. Use the inspect-os command to get OS information


Actual results:
Nothing is returned.


Expected results:
The Windows guest OS type should be returned just as is seen with a Basic disk type.


Additional info:

[root]# cat /etc/redhat-release
Fedora release 35 (Thirty Five)

[rootl-images]# uname -r
5.16.13-200.fc35.x86_64

With w2k19 basic disks:

[root]# guestfish --ro -a win2k19.img

<fs> run
<fs> inspect-os
/dev/sda2

<fs> inspect-get-distro /dev/sda2
windows
<fs>
<fs> inspect-get-osinfo /dev/sda2
win2k19

<fs> inspect-get-product-name /dev/sda2
Windows Server 2019 Standard Evaluation
<fs>

Now we change the disk from Basic to Dynamic

[root]# guestfish --ro -a win2k19.img

<fs> run
<fs> inspect-os
<fs>

Here we see nothing is getting returned. We expected /dev/sda2 (Like for Basic Disk Type).

Comment 1 Richard W.M. Jones 2022-03-31 07:42:57 UTC
Interesting reading:

https://bugzilla.redhat.com/show_bug.cgi?id=2012658#c2

*** This bug has been marked as a duplicate of bug 2012658 ***

Comment 2 Richard W.M. Jones 2022-04-08 08:53:36 UTC
Unduplicating, see https://bugzilla.redhat.com/show_bug.cgi?id=2012658#c6

Comment 3 roy.lemmon 2022-04-08 10:52:11 UTC
Thank you for reopening this bug.  Is there an estimated fix date for this?

Comment 4 Richard W.M. Jones 2022-04-08 12:39:29 UTC
This isn't a priority for me.  There was a message posted
on the mailing list last month which might relate to this bug:

https://listman.redhat.com/archives/libguestfs/2022-March/028493.html

Comment 5 Ben Cotton 2023-04-25 16:56:26 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.


Note You need to log in before you can comment on or make changes to this bug.