This message was deleted.
# harvester
a
This message was deleted.
m
Hey! I hope you don't mind me reaching out - I'm Alex, one of the product managers for Harvester here at SUSE. I'm interested in talking to some folks who have been using Windows with Harvester. Would you be open to providing some feedback on the experience? πŸ™‚
(also, no, I haven't seen this error before, I'll ask around for you πŸ™‚ )
g
Thanks Alex, I'd really appreciate that. I don't know how much feedback I can provide. But I'll be happy to give you what I can. β€’ If you do find someone to ask around, this might help them. (See attached photo) β€’ If you could ask if the 550.90.05 nvidia kvm drivers are compatible with harvester.
m
Hiya! Sorry this took a while, so: we do not test each version of Nvidia driver as it comes out, but our engineers were sure that one worked because we tested A2 with that driver. There is a lot that could happen in VM definitions and there are different vGPU profiles are for different workloads. This issue might help: https://github.com/harvester/harvester/issues/6192
Any feedback is valid at this point πŸ™‚ I'll send you a DM with some questions - thank you!
If you are unable to resolve the issue yourself, I'd recommend opening an issue with the team via GitHub and ensure you include a support bundle. If you don't know how to do that, here are the instructions: https://docs.harvesterhci.io/v1.3/troubleshooting/harvester/#generate-a-support-bundle
g
a support bundle would be a good starting point as we can see the info about the vm spec
βœ… 1
g
IT WORKED!!!
How do I get this documented for the next person that runs into this?
m
Raise an issue in GitHub but specifically details that it's a docs bug and what you need fixed and where 😊
πŸ‘ 1