Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VCSim does not support QueryVirtualDiskInfo_Task #3000

Closed
namra98 opened this issue Nov 28, 2022 · 3 comments
Closed

VCSim does not support QueryVirtualDiskInfo_Task #3000

namra98 opened this issue Nov 28, 2022 · 3 comments

Comments

@namra98
Copy link

namra98 commented Nov 28, 2022

Is your feature request related to a problem? Please describe.
It is throwing error. no vmomi type defined for 'QueryVirtualDiskInfo_Task' when I try to query disk info.
govmomi func call: https://github.com/vmware/govmomi/blob/master/object/virtual_disk_manager_internal.go#L79

Describe the solution you'd like
func call: https://github.com/vmware/govmomi/blob/master/object/virtual_disk_manager_internal.go#L79
It should return disk info like it does against real vCenter.
image

@github-actions
Copy link
Contributor

Howdy 🖐   namra98 ! Thank you for your interest in this project. We value your feedback and will respond soon.

If you want to contribute to this project, please make yourself familiar with the CONTRIBUTION guidelines.

@deas
Copy link

deas commented Jan 17, 2023

I looked into this a bit and I am trying to fix it. Got it working to the point that I get valid responses for govc datastore.disk.info.

However, I feel I must be missing something. Many symbols are not exported and the filename also hints at "internal". Also, it appears there is no method QueryVirtualDiskInfo<something> for vim.VirtualDiskManager documented in the API docs.

Still, clients such as the VSphere Terraform Provider appear to be using this method.

Would be great to get a little guidance. I may be able to contribute the missing bits here.

@github-actions
Copy link
Contributor

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants