Bug 243713
| Summary: | BHyve VM name length | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | misho | ||||
| Component: | bhyve | Assignee: | freebsd-virtualization (Nobody) <virtualization> | ||||
| Status: | Closed DUPLICATE | ||||||
| Severity: | Affects Many People | CC: | markj, meka | ||||
| Priority: | --- | ||||||
| Version: | CURRENT | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
I'm just curious, how did you decide what the new length should be? Our colleagues from different department tries to request from server VM instance through RPC service. They wants to have name of VM built from UUID string. I check that isn't impossible for creation and found that 32 bytes are created without problem. I offer to them to remove dashes from UUID. Then they will have 32 chars name. Ok ... tools can handle it, but kernel cannot start it. Then I found that if the name is 31 chars all is ok. This is brake point which drive me to start chasing of this issue. I found where are made checks for length of VM name and variable which contains the name of VM. Decision was based on several considerations - I like all my variables to be rounded of machine word. - We should not grow up to much, because I predict that many users already have something like monitoring software which drawing something in tables. This is something like explanation ... :) I believe this has already been fixed: https://svnweb.freebsd.org/changeset/base/349948 Note that the length on stable/12 is still quite small. *** This bug has been marked as a duplicate of bug 234134 *** |
Created attachment 211175 [details] Patch to extend name of VMs I believe that is good idea to have more than 31 chars for VM name.