[Misc] Clean up Aimv2 config registration in Ovis config

[Isotr0py]

Essential Elements of an Effective PR Description Checklist

• The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
• The test plan, such as providing test command.
• The test results, such as pasting the results comparison before and after, or e2e results
• (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

• On Transformers main branch, AimV2 has been supported with model conversion, so we need to remove the original AIMv2Config registration in Ovis config porting to avoid duplicate model name:

ValueError: 'aimv2' is already used by a Transformers config, pick another name.

• Clean up aimv2 model config registry to make GLM-4 Update #20736 work.

Test Plan

uv pip install git+https://github.com/huggingface/transformers
python examples/offline_inference/vision_language.py -m ovis

Test Result

• Example should still work after installing transformers main branch

(Optional) Documentation Update

[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 @Isotr0py, 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 resolves a configuration conflict with the aimv2 model, which is now natively supported in the transformers library's main branch. It cleans up the Ovis configuration by removing a redundant aimv2 registration and adjusts the model configuration loading logic to correctly instantiate AIMv2Config for aimv2 models, thereby preventing duplicate name errors and ensuring proper integration with the upstream transformers library.

Highlights

• Configuration Conflict Resolution: Removed the explicit AutoConfig.register("aimv2", AIMv2Config) call in vllm/transformers_utils/configs/ovis.py. This change directly addresses a ValueError that would occur due to aimv2 being pre-registered in the upstream transformers library, ensuring compatibility when using the transformers main branch.
• Conditional AIMv2Config Instantiation: Modified the OvisConfig's __init__ method to specifically handle aimv2 backbone configurations. Instead of relying on AutoConfig.for_model (which would now pick up the upstream transformers library's aimv2 config), AIMv2Config is now directly instantiated for aimv2 models, while other model types continue to use AutoConfig.for_model for dynamic loading.

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 removes the original AIMv2Config registration in Ovis config, resolving a duplicate model name issue. I've suggested a minor improvement for code consistency.

[gemini-code-assist]

Consider popping model_type from backbone_config before the conditional check for consistency. This ensures backbone_config is handled the same way in both branches and avoids passing unexpected keys to constructors.

Suggested change

	if model_type != "aimv2":
	backbone_config.pop('model_type')
	backbone_config = AutoConfig.for_model(model_type, **backbone_config)
	else:
	backbone_config = AIMv2Config(**backbone_config)
	model_type = backbone_config.pop('model_type')
	if model_type != "aimv2":
	backbone_config = AutoConfig.for_model(model_type, **backbone_config)
	else:
	backbone_config = AIMv2Config(**backbone_config)