docs: add simulated GPU scheduling troubleshooting

[Samkeliso-dube00]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Adds a troubleshooting guide for GPU pod scheduling failures when using HAMi with simulated/fake GPUs.

When users deploy GPU workloads with simulated GPUs (like GPU Operator's mock devices), pods can remain Pending even though Kubernetes advertises GPU resources. This guide explains the root cause (HAMi requires device information in JSON format) and provides step-by-step recovery procedures.

Which issue(s) this PR fixes:
Fixes #656

Checklist:

• npm run lint and npm run format:check pass
• npm run build succeeds for both en and zh
• Chinese translation updated if English docs changed (or noted why not)
• Commits are signed off (git commit -s)

Note: This PR adds troubleshooting content only. Chinese translation can be added in a follow-up PR.

[netlify]

✅ Deploy Preview for project-hami ready!

Name	Link
🔨 Latest commit	e3af87a
🔍 Latest deploy log	https://app.netlify.com/projects/project-hami/deploys/6a84313408056600081082f0
😎 Deploy Preview	https://deploy-preview-788--project-hami.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hami-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Samkeliso-dube00
Once this PR has been reviewed and has the lgtm label, please assign windsonsea for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Important

Review available on request

• 🔍 Trigger review

Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment @coderabbitai review to review the latest changes. For a full review, comment @coderabbitai full review.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 038adafb-c973-4544-bca7-4a9c96bfe117

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Samkeliso-dube00]

Hi @rootsongjc and HAMi maintainers,

This PR adds troubleshooting documentation for GPU pod scheduling failures with simulated GPUs. It addresses issue #656 by providing diagnostic steps and recovery procedures for a common user pain point.

This is submitted as part of my LFX Mentorship application for the "Expand HAMi GPU-sharing tutorials, labs, and troubleshooting guides" project.

Looking forward to your feedback.

[mesutoezdil]

useful guide and the recovery flow matches the registration protocol docs. fixes #656 would close the lfx umbrella issue, use part of. all four checklist boxes are empty and the docs health ci did not run on this pr, please rebase and run lint, format and the full build. the zh follow up note is fine.

[mesutoezdil]

missing space after the comma.

[mesutoezdil]

heads up: #741, #773, #779 and #783 all append sections to this same file, and #767 covers the filtering events in depth. coordinate merge order to avoid conflicts and duplication.

[Samkeliso-dube00]

Thanks for the feedback, @mesutoezdil. I see PRs #741, #773, #779, #783
are also updating troubleshooting.md. Happy to coordinate on merge order
to avoid conflicts. Should I rebase after those land, or does the team
prefer a specific sequence?