[Bug]: Unattended Guest OS Installation Domain Name Entry results in error while completing field value

Open
#994 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c, cpp
Domain
desktop

Research direction

The behaviour lives in the Qt GUI's unattended-install wizard, not in the VM backend: find the handler that validates the guest hostname/domain name and emits the "trailing dot not permitted" message, then see what triggers it on each keystroke of the Domain Name field. Change it to validate on commit (focus loss or Next) rather than on text change, and confirm the error no longer appears while typing myhome.local but still fires for a genuinely invalid value. The issue names no file, so expect to search the GUI unattended-install sources for the message text first.

Written by the indexing model from the issue text.

Description

bug
Version

7.2.22

Host OS Type

Windows

Host OS name + version

Windows 11 Build 26300

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

N/A

Component

Other

What happened?

When creating a new VM, I am getting a "Can't run guest install..." error that says "Failed to run unattended guest installation. ... Invalid hostname ..... - trailing dot not permitted." with some error codes. This occurs while typing the "Domain Name" in the unattended config. I expect it to wait for me to finish typing before evaluating whether it will work. I'm not sure how it determines that it failed to run the installation when the Guest VM hasn't been created yet.

How can we reproduce this?

Begin creating a new VM. Go to Set up unattended guest OS installation, and type "myhome.local". You'll see the error appear on the right panel as soon as "myhome." has been typed, before finishing the rest of the domain.

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Dominant language
C
Stars
1.4k
Forks
219
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from VirtualBox/virtualbox

All issues in VirtualBox/virtualbox

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.