Opened 6 years ago
Last modified 6 years ago
#18229 new defect
CentOS VM does not start after virtual guest additions 5.2.22 upgradation
| Reported by: | anupam.m | Owned by: | |
|---|---|---|---|
| Component: | guest additions/x11/graphics | Version: | VirtualBox 5.2.22 |
| Keywords: | Boot | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description
My CentOS VM was running fine in Windows 10, Virtualbox 5.2.18 . But after updating it to 5.2.22 and installing the guest additions 5.2.22, it does start. It gives error during boot : Job x11vnc.service/start deleted to break ordering cycle started with multi-user.target/start. My Caps lock led keeps blinking and I have to shutdown the VM.
Attachments (2)
Change History (3)
by , 6 years ago
| Attachment: | vm_boot_issue.png added |
|---|
comment:1 by , 6 years ago
- The CapsLock blinking is a sign that your kernel crashed.
- It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".
- You were supposed to follow these steps when you filed the bug, and provide a VBox.log:
Attach a (full) log file ("Machine" menu/"Show Log" in the main VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please do not cut and paste it.
Note:
See TracTickets
for help on using tickets.
Screenshot of VM