| Summary: | Vbox installs fine but won't launch client | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | William Kenney <wilcal.int> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, ftg, ouaurelien |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
Vbox installed packages list
Vbox M7 installed packages list |
||
|
Description
William Kenney
2020-06-28 02:49:46 CEST
Created attachment 11724 [details]
Vbox installed packages list
I've found that installing VBox does not enable or start it. Try doing that with systemctl enable/start. CC:
(none) =>
ftg (In reply to Frank Griffin from comment #2) > I've found that installing VBox does not enable or start it. Try doing that > with systemctl enable/start. Thanks for looking at this. I will continue to gather info on this in the next days. Let me clarify. The error messages are displayed when you attempt to launch an already set up client. In this case the M8 x86_64 Plasma Live-DVD. Installing, launching Vbox from a desktop icon and the setup of a client all worked just fine. Also I want to note that my two primary computers are both Intel I5, running M7 and use a UEFI boot. Vbox runs just fine on those platforms. The test platform here is a very new Dell Laptop, I5 also with a UEFI boot. Virtualbox still uses rc.d scripts, so the systemd services are generated at boot time. On my system ... # chkconfig --list 2>/dev/null|grep virtualbox virtualbox 0:off 1:off 2:on 3:on 4:on 5:on 6:off What's the result on that system? CC:
(none) =>
davidwhodgins (In reply to Dave Hodgins from comment #4) > On my system ... > # chkconfig --list 2>/dev/null|grep virtualbox > virtualbox 0:off 1:off 2:on 3:on 4:on 5:on 6:off > > What's the result on that system? [root@localhost wilcal]# chkconfig --list 2>/dev/null|grep virtualbox virtualbox 0:off 1:off 2:off 3:on 4:off 5:on 6:off Just to make sure I spun up an M7 Plasma install on the same platform and installed Vbox to it. And sure enough it installed cleanly then created and booted to a working desktop a client M8 x86_64 Plasam Live-DVD So to my relief it does not appear to be this new Dell laptop I've attached the installed list_m7_installed_packages_list.txt Created attachment 11725 [details]
Vbox M7 installed packages list
Hold the phone Unconfirmed for now. Still work'n on it Ever confirmed:
1 =>
0
Aurelien Oudelet
2020-09-02 17:48:59 CEST
CC:
(none) =>
ouaurelien Virtualbox runs fine on M8 Cauldron since last update. I always restart host system before really using VBOX. M7 client is OK. On M7, Virtualbox is OK too on x86_64 Closing this. Feel free to reopen if such bug occurs again. Resolution:
(none) =>
WORKSFORME |