Bug 1565431

Tried to reproduce,

* boot up windows guest with virtio serial driver and qemu-ga-win installed.
* issue fsfreeze cmd from host {"execute":"guest-fsfreeze-freeze"} it didnt return what was stated by the you, it returned the number of disks frozen {"return": 2}, Which is supposed to be correct according to the qemu-ga documentation.

* issue get-fsinfo {"execute":"guest-get-fsinfo"} DID get something similar, (GuestFilesystemInfo object), and Disk is []

NOTE: couldn't run get-fsinfo when the fs was frozen, had to thaw the fs then run get-fsinfo.
NOTE: in the documentation of get-fsinfo it is state that Disk will be empty if the disk type is not supported

Reference https://qemu.weilnetz.de/doc/qemu-ga-ref.html

(In reply to Sameeh Jubran from comment #2)
> Tried to reproduce,
> 
> * boot up windows guest with virtio serial driver and qemu-ga-win installed.
> * issue fsfreeze cmd from host {"execute":"guest-fsfreeze-freeze"} it didnt
> return what was stated by the you, it returned the number of disks frozen
> {"return": 2}, Which is supposed to be correct according to the qemu-ga
> documentation.
> 
> * issue get-fsinfo {"execute":"guest-get-fsinfo"} DID get something similar,
> (GuestFilesystemInfo object), and Disk is []
> 
> NOTE: couldn't run get-fsinfo when the fs was frozen, had to thaw the fs
> then run get-fsinfo.
> NOTE: in the documentation of get-fsinfo it is state that Disk will be empty
> if the disk type is not supported
> 
> Reference https://qemu.weilnetz.de/doc/qemu-ga-ref.html

First, sorry to confuse you from comment 0, I just issue {"execute":"guest-get-fsinfo"} cmd not {"execute":"guest-fsfreeze-freeze"} cmd.

And the disk is local disk but not Network filesystems (such as CIFS and NFS).

Test it again and get the same result, so I think "disk": [] is not correct.

# nc -U /tmp/qga-win7 
 {"execute":"guest-get-fsinfo"}
{"return": [{"name": "\\\\?\\Volume{4d9a17d1-707c-11e8-8573-806e6f6e6963}\\", "mountpoint": "F:\\", "disk": [], "type": "CDFS"}, {"name": "\\\\?\\Volume{4d9a17d0-707c-11e8-8573-806e6f6e6963}\\", "mountpoint": "E:\\", "disk": [], "type": "CDFS"}, {"name": "\\\\?\\Volume{3475515e-708c-11e8-bc41-806e6f6e6963}\\", "mountpoint": "C:\\", "disk": [], "type": "NTFS"}, {"name": "\\\\?\\Volume{4d9a17ca-707c-11e8-8573-806e6f6e6963}\\", "mountpoint": "D:\\", "disk": [], "type": "NTFS"}, {"name": "\\\\?\\Volume{3475515d-708c-11e8-bc41-806e6f6e6963}\\", "mountpoint": "S:\\", "disk": [], "type": "NTFS"}]}

(In reply to xiagao from comment #3)
> (In reply to Sameeh Jubran from comment #2)
> > Tried to reproduce,
> > 
> > * boot up windows guest with virtio serial driver and qemu-ga-win installed.
> > * issue fsfreeze cmd from host {"execute":"guest-fsfreeze-freeze"} it didnt
> > return what was stated by the you, it returned the number of disks frozen
> > {"return": 2}, Which is supposed to be correct according to the qemu-ga
> > documentation.
> > 
> > * issue get-fsinfo {"execute":"guest-get-fsinfo"} DID get something similar,
> > (GuestFilesystemInfo object), and Disk is []
> > 
> > NOTE: couldn't run get-fsinfo when the fs was frozen, had to thaw the fs
> > then run get-fsinfo.
> > NOTE: in the documentation of get-fsinfo it is state that Disk will be empty
> > if the disk type is not supported
> > 
> > Reference https://qemu.weilnetz.de/doc/qemu-ga-ref.html
> 
> First, sorry to confuse you from comment 0, I just issue
> {"execute":"guest-get-fsinfo"} cmd not {"execute":"guest-fsfreeze-freeze"}
> cmd.
> 
> And the disk is local disk but not Network filesystems (such as CIFS and
> NFS).
> 
> Test it again and get the same result, so I think "disk": [] is not correct.
> 
> # nc -U /tmp/qga-win7 
>  {"execute":"guest-get-fsinfo"}
> {"return": [{"name":
> "\\\\?\\Volume{4d9a17d1-707c-11e8-8573-806e6f6e6963}\\", "mountpoint":
> "F:\\", "disk": [], "type": "CDFS"}, {"name":
> "\\\\?\\Volume{4d9a17d0-707c-11e8-8573-806e6f6e6963}\\", "mountpoint":
> "E:\\", "disk": [], "type": "CDFS"}, {"name":
> "\\\\?\\Volume{3475515e-708c-11e8-bc41-806e6f6e6963}\\", "mountpoint":
> "C:\\", "disk": [], "type": "NTFS"}, {"name":
> "\\\\?\\Volume{4d9a17ca-707c-11e8-8573-806e6f6e6963}\\", "mountpoint":
> "D:\\", "disk": [], "type": "NTFS"}, {"name":
> "\\\\?\\Volume{3475515d-708c-11e8-bc41-806e6f6e6963}\\", "mountpoint":
> "S:\\", "disk": [], "type": "NTFS"}]}

C: D: S: is in local and filesystem is NTFS.

Hi,

The issue should be fixed in the following build, can you please confirm this?

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16818633

(In reply to Sameeh Jubran from comment #5)
> Hi,
> 
> The issue should be fixed in the following build, can you please confirm
> this?
> 
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16818633

Qemu guest agent service will be stopped status after issuing  {"execute":"guest-get-fsinfo"} cmd. I take a screenshot about qemu-ga service in attachment.

Created attachment 1453655 [details]
qemu-ga service status

qemu-ga service status after trigger get fsinfo cmd

(In reply to xiagao from comment #7)
> Created attachment 1453655 [details]
> qemu-ga service status
> 
> qemu-ga service status after trigger get fsinfo cmd

The crash seems to be fixed by this commit:
https://github.com/qemu/qemu/commit/9bd8e9330ade42878b19a5172131087220d590d5#diff-7f29c3e51a7b387cc7717e7be4f6e205

I'll apply it and build a version to test it :)

Can you please confirm that in this build the issue is fixed?

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16850812

Created attachment 1454223 [details]
event viewer log

Still hit this issue. Service is stopped status after run get-fsinfo cmd.

The issue should be fixed in the following build:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=16889965

I have sent two patches upstream which fix the issue:
https://lists.gnu.org/archive/html/qemu-devel/2018-06/msg07500.html

Can you please confirm that the issue is fixed?

Thanks :)

Test mingw-qemu-ga-win-7.6.0-2.el7ev, but still hit this issue like comment 10.

(In reply to xiagao from comment #12)
> Test mingw-qemu-ga-win-7.6.0-2.el7ev, but still hit this issue like comment
> 10.

I have just tested it and it seems to be working for me. No crashes what so ever. Are you sure that you did uninstall the earlier version that was installed?

(In reply to Sameeh Jubran from comment #13)
> (In reply to xiagao from comment #12)
> > Test mingw-qemu-ga-win-7.6.0-2.el7ev, but still hit this issue like comment
> > 10.
> 
> I have just tested it and it seems to be working for me. No crashes what so
> ever. Are you sure that you did uninstall the earlier version that was
> installed?

I tried twice, it actually hit crash.You can check the attachment about my test pkg info.

Created attachment 1458338 [details]
pkg info

(In reply to xiagao from comment #15)
> Created attachment 1458338 [details]
> pkg info

Can you please give me access to the machine??

Also failed.

# yum install http://download.eng.bos.redhat.com/brewroot/work/tasks/9252/17189252/mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm -y
Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm                                                                                                                                                     |  47 MB  00:00:15     
Examining /var/tmp/yum-root-tvI1YW/mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm: mingw-qemu-ga-win-7.6.0-2.el7ev.src
Cannot add package http://download.eng.bos.redhat.com/brewroot/work/tasks/9252/17189252/mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm to transaction. Not a compatible architecture: src
Error: Nothing to do

(In reply to xiagao from comment #28)
> Also failed.
> 
> # yum install
> http://download.eng.bos.redhat.com/brewroot/work/tasks/9252/17189252/mingw-
> qemu-ga-win-7.6.0-2.el7ev.src.rpm -y
> Loaded plugins: product-id, search-disabled-repos, subscription-manager
> This system is not registered with an entitlement server. You can use
> subscription-manager to register.
> mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm                                     
> |  47 MB  00:00:15     
> Examining /var/tmp/yum-root-tvI1YW/mingw-qemu-ga-win-7.6.0-2.el7ev.src.rpm:
> mingw-qemu-ga-win-7.6.0-2.el7ev.src
> Cannot add package
> http://download.eng.bos.redhat.com/brewroot/work/tasks/9252/17189252/mingw-
> qemu-ga-win-7.6.0-2.el7ev.src.rpm to transaction. Not a compatible
> architecture: src
> Error: Nothing to do

You should be using the following rpm as it is the one that has the binaries. The one that you were using has the sources:

http://brew-task-repos.usersys.redhat.com/repos/scratch/sjubran/mingw-qemu-ga-win/7.6.0/2.el7ev/noarch/qemu-ga-win-7.6.0-2.el7ev.noarch.rpm

Tested the temp build, there is no qemu-ga crashed and can get result.

{"execute":"guest-get-fsinfo"}
{"return": [{"name": "\\\\?\\Volume{7d9c10b7-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint": "E:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "target": 0}], "type": "CDFS"}, {"name": "\\\\?\\Volume{7d9c10b6-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint": "D:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "target": 0}], "type": "CDFS"}, {"name": "\\\\?\\Volume{3eb920f1-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint": "C:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 2}, "target": 0}], "type": "NTFS"}, {"name": "\\\\?\\Volume{3eb920f0-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint": "S:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 1}, "target": 0}], "type": "NTFS"}]}

But bus-type is "unknown", I think it's not correct.
Use the same qemu cmd line for rhel guest,get the following result. 


{"execute":"guest-get-fsinfo"}
{"return": [{"name": "sda1", "mountpoint": "/boot", "disk": [{"bus-type": "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": 0, "slot": 5, "domain": 0, "function": 0}, "target": 0}], "type": "xfs"}, {"name": "dm-0", "mountpoint": "/", "disk": [{"bus-type": "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": 0, "slot": 5, "domain": 0, "function": 0}, "target": 0}], "type": "xfs"}]}

(In reply to xiagao from comment #30)
> Tested the temp build, there is no qemu-ga crashed and can get result.
> 
> {"execute":"guest-get-fsinfo"}
> {"return": [{"name":
> "\\\\?\\Volume{7d9c10b7-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> "E:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> "target": 0}], "type": "CDFS"}, {"name":
> "\\\\?\\Volume{7d9c10b6-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> "D:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> "target": 0}], "type": "CDFS"}, {"name":
> "\\\\?\\Volume{3eb920f1-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> "C:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 2},
> "target": 0}], "type": "NTFS"}, {"name":
> "\\\\?\\Volume{3eb920f0-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> "S:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 1},
> "target": 0}], "type": "NTFS"}]}
> 
> But bus-type is "unknown", I think it's not correct.
> Use the same qemu cmd line for rhel guest,get the following result. 
> 
> 
> {"execute":"guest-get-fsinfo"}
> {"return": [{"name": "sda1", "mountpoint": "/boot", "disk": [{"bus-type":
> "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": 0, "slot": 5,
> "domain": 0, "function": 0}, "target": 0}], "type": "xfs"}, {"name": "dm-0",
> "mountpoint": "/", "disk": [{"bus-type": "scsi", "bus": 0, "unit": 0,
> "pci-controller": {"bus": 0, "slot": 5, "domain": 0, "function": 0},
> "target": 0}], "type": "xfs"}]}

Some bus types are not identified by Windows. Is this virtio-scsi?

Anyways we query Windows for the bus type and Windows returns the bus type, if it is unknown by Windows API we can do nothing about it as from qemu-ga we send an ioctl through Windows to the disk itself. You can see that done in the qemu-ga here: https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L586

If this is indeed the virtio-scsi then the Windows driver should support the ioctl "IOCTL_STORAGE_QUERY_PROPERTY" along with STORAGE_PROPERTY_QUERY.

Vadim can you please confirm this? Does the virtio-scsi support this IRP?

(In reply to Sameeh Jubran from comment #31)
> (In reply to xiagao from comment #30)
> > Tested the temp build, there is no qemu-ga crashed and can get result.
> > 
> > {"execute":"guest-get-fsinfo"}
> > {"return": [{"name":
> > "\\\\?\\Volume{7d9c10b7-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> > "E:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> > "target": 0}], "type": "CDFS"}, {"name":
> > "\\\\?\\Volume{7d9c10b6-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> > "D:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> > "target": 0}], "type": "CDFS"}, {"name":
> > "\\\\?\\Volume{3eb920f1-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> > "C:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 2},
> > "target": 0}], "type": "NTFS"}, {"name":
> > "\\\\?\\Volume{3eb920f0-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> > "S:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 1},
> > "target": 0}], "type": "NTFS"}]}
> > 
> > But bus-type is "unknown", I think it's not correct.
> > Use the same qemu cmd line for rhel guest,get the following result. 
> > 
> > 
> > {"execute":"guest-get-fsinfo"}
> > {"return": [{"name": "sda1", "mountpoint": "/boot", "disk": [{"bus-type":
> > "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": 0, "slot": 5,
> > "domain": 0, "function": 0}, "target": 0}], "type": "xfs"}, {"name": "dm-0",
> > "mountpoint": "/", "disk": [{"bus-type": "scsi", "bus": 0, "unit": 0,
> > "pci-controller": {"bus": 0, "slot": 5, "domain": 0, "function": 0},
> > "target": 0}], "type": "xfs"}]}
> 
> Some bus types are not identified by Windows. Is this virtio-scsi?
> 
> Anyways we query Windows for the bus type and Windows returns the bus type,
> if it is unknown by Windows API we can do nothing about it as from qemu-ga
> we send an ioctl through Windows to the disk itself. You can see that done
> in the qemu-ga here:
> https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L586
> 
> If this is indeed the virtio-scsi then the Windows driver should support the
> ioctl "IOCTL_STORAGE_QUERY_PROPERTY" along with STORAGE_PROPERTY_QUERY.
> 
> Vadim can you please confirm this? Does the virtio-scsi support this IRP?

Technically a storage miniport doesn't deal with IOCTL_STORAGE_QUERY_PROPERTY IRP directly. It is a class driver job. But yes, class should return the relevant information collected from virtio-scsi miniport driver (and not only)  in response to such request. In case of virtio-scsi the bus type should be BusTypeSas (0x0A).

(In reply to Vadim Rozenfeld from comment #32)
> (In reply to Sameeh Jubran from comment #31)
> > (In reply to xiagao from comment #30)
> > > Tested the temp build, there is no qemu-ga crashed and can get result.
> > > 
> > > {"execute":"guest-get-fsinfo"}
> > > {"return": [{"name":
> > > "\\\\?\\Volume{7d9c10b7-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> > > "E:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > > "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> > > "target": 0}], "type": "CDFS"}, {"name":
> > > "\\\\?\\Volume{7d9c10b6-8914-11e8-81e7-806e6f6e6963}\\", "mountpoint":
> > > "D:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > > "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1},
> > > "target": 0}], "type": "CDFS"}, {"name":
> > > "\\\\?\\Volume{3eb920f1-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> > > "C:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > > "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 2},
> > > "target": 0}], "type": "NTFS"}, {"name":
> > > "\\\\?\\Volume{3eb920f0-898f-11e8-ae9d-806e6f6e6963}\\", "mountpoint":
> > > "S:\\", "disk": [{"bus-type": "unknown", "bus": 0, "unit": 0,
> > > "pci-controller": {"bus": -1, "slot": -1, "domain": 0, "function": 1},
> > > "target": 0}], "type": "NTFS"}]}
> > > 
> > > But bus-type is "unknown", I think it's not correct.
> > > Use the same qemu cmd line for rhel guest,get the following result. 
> > > 
> > > 
> > > {"execute":"guest-get-fsinfo"}
> > > {"return": [{"name": "sda1", "mountpoint": "/boot", "disk": [{"bus-type":
> > > "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": 0, "slot": 5,
> > > "domain": 0, "function": 0}, "target": 0}], "type": "xfs"}, {"name": "dm-0",
> > > "mountpoint": "/", "disk": [{"bus-type": "scsi", "bus": 0, "unit": 0,
> > > "pci-controller": {"bus": 0, "slot": 5, "domain": 0, "function": 0},
> > > "target": 0}], "type": "xfs"}]}
> > 
> > Some bus types are not identified by Windows. Is this virtio-scsi?
> > 
> > Anyways we query Windows for the bus type and Windows returns the bus type,
> > if it is unknown by Windows API we can do nothing about it as from qemu-ga
> > we send an ioctl through Windows to the disk itself. You can see that done
> > in the qemu-ga here:
> > https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L586
> > 
> > If this is indeed the virtio-scsi then the Windows driver should support the
> > ioctl "IOCTL_STORAGE_QUERY_PROPERTY" along with STORAGE_PROPERTY_QUERY.
> > 
> > Vadim can you please confirm this? Does the virtio-scsi support this IRP?
> 
> Technically a storage miniport doesn't deal with
> IOCTL_STORAGE_QUERY_PROPERTY IRP directly. It is a class driver job. But
> yes, class should return the relevant information collected from virtio-scsi
> miniport driver (and not only)  in response to such request. In case of
> virtio-scsi the bus type should be BusTypeSas (0x0A).


Issue of "Disk is []" is resolved, will verify it in official build.

I create another bug to track "bus-type is 'unknown'" issue. 
https://bugzilla.redhat.com/show_bug.cgi?id=1607841

Thanks.

Created attachment 1470966 [details]
qemu-ga service stop

Test qemu-ga-win-7.6.1-2.el7ev.noarch, after run {"execute":"guest-get-fsinfo"}, qemu-ga crashed like comment 10.

Even though  the issue should be fixed, this might be a different issue that causes the crash. I want to currently disable the Disk parameter for this release as it doesn't seem stable and move this to 7.7

I'll have a build which disables the disk and returns [] as it originally was.

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17384847

Just make sure that this version returns [] as it did before.

(In reply to Sameeh Jubran from comment #38)
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17384847
> 
> Just make sure that this version returns [] as it did before.

Test mingw-qemu-ga-win-7.6.2-2.el7ev, get the error response of get-fsinfo.

{"execute":"guest-get-fsinfo"}
{"error": {"class": "GenericError", "desc": "failed to get volume info: The volume does not contain a recognized file system.\r\nPlease make sure that all required file system drivers are loaded and that the volume is not corrupted."}}


Guest file volume: see attachment

Created attachment 1471416 [details]
file system of guest

move to rhel7.7 according to comment#37

(In reply to xiagao from comment #39)
> (In reply to Sameeh Jubran from comment #38)
> > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17384847
> > 
> > Just make sure that this version returns [] as it did before.
> 
> Test mingw-qemu-ga-win-7.6.2-2.el7ev, get the error response of get-fsinfo.
> 
> {"execute":"guest-get-fsinfo"}
> {"error": {"class": "GenericError", "desc": "failed to get volume info: The
> volume does not contain a recognized file system.\r\nPlease make sure that
> all required file system drivers are loaded and that the volume is not
> corrupted."}}
> 
> 
> Guest file volume: see attachment


Sorry for the late reply. I have taken a look at the error and it is caused by the call to GetVolumeInformation function in qemu-ga [1]. This error is thrown because some volumes in the VM are not formatted, can you please confirm that all of your volumes are formatted to a known file system such as FAT or NTFS and re run the command?

Thanks!

[1] - https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L692

(In reply to Sameeh Jubran from comment #42)
> (In reply to xiagao from comment #39)
> > (In reply to Sameeh Jubran from comment #38)
> > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=17384847
> > > 
> > > Just make sure that this version returns [] as it did before.
> > 
> > Test mingw-qemu-ga-win-7.6.2-2.el7ev, get the error response of get-fsinfo.
> > 
> > {"execute":"guest-get-fsinfo"}
> > {"error": {"class": "GenericError", "desc": "failed to get volume info: The
> > volume does not contain a recognized file system.\r\nPlease make sure that
> > all required file system drivers are loaded and that the volume is not
> > corrupted."}}
> > 
> > 
> > Guest file volume: see attachment
> 
> 
> Sorry for the late reply. I have taken a look at the error and it is caused
> by the call to GetVolumeInformation function in qemu-ga [1]. This error is
> thrown because some volumes in the VM are not formatted, can you please
> confirm that all of your volumes are formatted to a known file system such
> as FAT or NTFS and re run the command?
> 
> Thanks!
> 
> [1] - https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L692

Yes,there is one disk is not fully formated from comment 40.
Try it again,can get the correct result.

{"execute":"guest-get-fsinfo"}
{"return": [{"name": "\\\\?\\Volume{58e2967a-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint": "E:\\", "disk": [], "type": "CDFS"}, {"name": "\\\\?\\Volume{58e29679-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint": "D:\\", "disk": [], "type": "UDF"}, {"name": "\\\\?\\Volume{58e2967b-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint": "A:\\", "disk": [], "type": "FAT"}, {"name": "\\\\?\\Volume{a93e5c1d-0000-0000-0000-602200000000}\\", "mountpoint": "C:\\", "disk": [], "type": "NTFS"}, {"name": "\\\\?\\Volume{a93e5c1d-0000-0000-0000-100000000000}\\", "mountpoint": "System Reserved", "disk": [], "type": "NTFS"}]}

(In reply to xiagao from comment #43)
tted to a known file system such
> > as FAT or NTFS and re run the command?
> > 
> > Thanks!
> > 
> > [1] - https://github.com/qemu/qemu/blob/master/qga/commands-win32.c#L692
> 
> Yes,there is one disk is not fully formated from comment 40.
> Try it again,can get the correct result.
> 
> {"execute":"guest-get-fsinfo"}
> {"return": [{"name":
> "\\\\?\\Volume{58e2967a-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint":
> "E:\\", "disk": [], "type": "CDFS"}, {"name":
> "\\\\?\\Volume{58e29679-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint":
> "D:\\", "disk": [], "type": "UDF"}, {"name":
> "\\\\?\\Volume{58e2967b-9a38-11e8-8bf8-806e6f6e6963}\\", "mountpoint":
> "A:\\", "disk": [], "type": "FAT"}, {"name":
> "\\\\?\\Volume{a93e5c1d-0000-0000-0000-602200000000}\\", "mountpoint":
> "C:\\", "disk": [], "type": "NTFS"}, {"name":
> "\\\\?\\Volume{a93e5c1d-0000-0000-0000-100000000000}\\", "mountpoint":
> "System Reserved", "disk": [], "type": "NTFS"}]}

Test version is: mingw-qemu-ga-win-7.6.2-2.el7ev

Test it with mingw-qemu-ga-win-100.0.0.0-3.el7ev
Can get disk info.So verify this bug.

{"return": [{"name": "\\\\?\\Volume{e3e1648f-0242-11e9-a67e-806e6f6e6963}\\", "total-bytes": 4843268096, "mountpoint": "E:\\", "disk": [{"bus-type": "sata", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "dev": "\\\\?\\Volume{e3e1648f-0242-11e9-a67e-806e6f6e6963}", "target": 0}], "used-bytes": 4843268096, "type": "UDF"}, {"name": "\\\\?\\Volume{e3e1648e-0242-11e9-a67e-806e6f6e6963}\\", "total-bytes": 567863296, "mountpoint": "D:\\", "disk": [{"bus-type": "sata", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "dev": "\\\\?\\Volume{e3e1648e-0242-11e9-a67e-806e6f6e6963}", "target": 0}], "used-bytes": 567863296, "type": "CDFS"}, {"name": "\\\\?\\Volume{26a1eeb5-0000-0000-0000-602200000000}\\", "total-bytes": 20897067008, "mountpoint": "C:\\", "disk": [{"serial": "MYDISK-1", "bus-type": "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "dev": "\\\\.\\PhysicalDrive0", "target": 0}], "used-bytes": 17327181824, "type": "NTFS"}, {"name": "\\\\?\\Volume{7a6cbe5e-0000-0000-0000-010000000000}\\", "total-bytes": 1070592000, "mountpoint": "F:\\", "disk": [{"serial": "MYDISK-2", "bus-type": "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "dev": "\\\\.\\PhysicalDrive1", "target": 0}], "used-bytes": 17690624, "type": "NTFS"}, {"name": "\\\\?\\Volume{26a1eeb5-0000-0000-0000-100000000000}\\", "mountpoint": "System Reserved", "disk": [{"serial": "MYDISK-1", "bus-type": "scsi", "bus": 0, "unit": 0, "pci-controller": {"bus": -1, "slot": -1, "domain": -1, "function": -1}, "dev": "\\\\.\\PhysicalDrive0", "target": 0}], "type": "NTFS"}]}