Custom Query (16363 matches)
Results (1042 - 1044 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18561 | worksforme | cpu miscount -> not a bug | ||
| Description |
Why is it that virtual box only recognizes one(1) CPU, some other programs see 2 cpu's. For example VMWare. Release:"5.2.26r128414 (QT5.6.2)" the picture (attached) shows invalid settings detected |
|||
| #18555 | invalid | Virtualbox 6 - vboxadd.service -> please use forums | ||
| Description |
Hello, I use Virtualbox a lot because it gives me the freedom to try anything without worrying that I broke my OS. But that stopped ever since VB version 6. Since than my shared folders broke. First of all this issue can be reproduces if the guest is Manjaro Linux and the Virtualbox version is at least v.6. It's the same if the host is Windows 7, 10 or Linux Manjaro. Also this problem does not occur if the guest is Linux Mint for example. From this I understand that the problem is in Manjaro but on forums I cannot find any solution. Including my post there : https://forum.manjaro.org/t/virtulbox-host-w10-guest-manjaro-kde-share-folders/78754/5 Until VB v.6, on a new guest I have always followed this 4 steps the share folders between host and guest.
and voila ! I had acces to the Media folder into the guest After v.6xx it only works if I try like this
After this, 99% work fine, except I get the 2 minutes waiting time when restarting the guest because of vboxadd.service. And if I disable the service, I cannot change the resolution from the guest, bigger than 800x600. But cliboard and shared folder are working. Also I'm kinda still a newbie in linux world so I don't know what should I try next. Can you point me in the right direction maybe ? |
|||
| #18553 | invalid | VirtualBox Manager exits on 1st startup but works 2nd time | ||
| Description |
Each day when I log in to my laptop, and start up VirtualBox Manager, it briefly opens and after maybe 1-2 seconds it disappears. If I restart it a 2nd time, it opens and works ok...until the issue is repeated the following day, and the following day. Restarts of my laptop have not fixed the issue. I previously had VirtualBox v5.2.18-124319 installed which worked fine, but I am encountering this issue all the time since I upgraded to v6.0.4-128413. Host VM is Windows 10, v1809. VMs are all Windows variations. |
|||

