[Docs] Update supported models documentation with missing models

[luccafong]

Added missing models from registry.py to supported_models.md with accurate example models and feature support information.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[gemini-code-assist]

Summary of Changes

Hello @luccafong, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on keeping the project's documentation up-to-date by incorporating recently supported models into the supported_models.md file. The changes ensure that users have accurate and comprehensive information regarding available models and their capabilities, improving the overall clarity and utility of the documentation.

Highlights

• Documentation Update: Added several new model entries to the supported_models.md file, ensuring the documentation reflects the latest supported models from registry.py.
• New Model Support: Specifically, new entries for Fairseq2LlamaForCausalLM, InternLM2VEForCausalLM, MiMoForCausalLM, and QuantMixtralForCausalLM have been added, complete with example model names and feature support information.
• Minor Formatting Fix: A small whitespace issue was resolved in the documentation file.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the documentation for supported models by adding several new entries. The additions are mostly correct, but I've identified a minor sorting issue in the table and a potential formatting problem due to the removal of trailing whitespace in the footnotes section. My review includes suggestions to address these points to ensure documentation clarity and consistency.

[Isotr0py]

I think Prithvi is not a text generation model.

[DarkLight1337]

It is image-to-image model. I think only the model vendor is really using this, we should not advertise support for it at this stage because it's far from being optimized.

[luccafong]

I see, let me remove it

[DarkLight1337]

Suggested change

	| `Fairseq2LlamaForCausalLM` | Fairseq2Llama | `mgleize/fairseq2-dummy-Llama-3.2-1B`, etc. | ✅︎ | ✅︎ | ✅︎ |
	| `Fairseq2LlamaForCausalLM` | Llama (fairseq2 format) | `mgleize/fairseq2-dummy-Llama-3.2-1B`, etc. | ✅︎ | ✅︎ | ✅︎ |

cc @houseroad is there a better name to describe this model?

[DarkLight1337]

Suggested change

	| `InternLM2VEForCausalLM` | InternLM2VE | `OpenGVLab/Mono-InternVL-2B`, etc. | ✅︎ | ✅︎ | ✅︎ |
	| `InternLM2VEForCausalLM` | Mono-InternVL | `OpenGVLab/Mono-InternVL-2B`, etc. | ✅︎ | ✅︎ | ✅︎ |

[DarkLight1337]

Actually, I think this should not be included in the list as it's only meant to be used as text backbone of Mono-InternVL

[DarkLight1337]

This is an internally defined model. We list the models on this page by their HF Hub model architecture (which is MixtralForCausalLM in this case) so there is no need to include this as a separate entry.