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

VM: Correct QEMU device ID max length #13672

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

hamistao
Copy link
Contributor

@hamistao hamistao commented Jun 26, 2024

I don't think this is currently causing any bugs, but the correct limit for QEMU IDs is 63, not 64. If longer than that, QEMU truncates the ID internally.

Signed-off-by: hamistao <pedro.ribeiro@canonical.com>
@hamistao hamistao force-pushed the correct_device_id_max_lenght branch from 61baf1b to 86cad43 Compare June 26, 2024 22:33
@tomponline
Copy link
Member

@hamistao to be comfortable with this change please can you double check that the /dev/disk/by-id names do not change for block disk device passthroughs. Cheers

@hamistao
Copy link
Contributor Author

hamistao commented Jun 27, 2024

I beleive this is safe to merge. Both entries for the device on /dev/disk/by-id are generated from the serial name (and not the device ID), so this could not affect them

@tomponline
Copy link
Member

I beleive this is safe to merge. Both entries for the device on /dev/disk/by-id are generated from the block node name (and not the device ID), so this could not affect them

Ok cool ill wait for the lxd-ci disk by id tests to be merged and passed, then merge this to check for regressions

@tomponline tomponline changed the title Correct QEMU device ID max length` Correct QEMU device ID max length Jun 28, 2024
@tomponline tomponline changed the title Correct QEMU device ID max length VM: Correct QEMU device ID max length Jun 28, 2024
@tomponline tomponline merged commit 4243e60 into canonical:main Jul 3, 2024
29 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants