Custom Query (16363 matches)
Results (592 - 594 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2241 | invalid | uuid not shown as process info (linux) with VBoxHeadless | ||
| Description |
When a session is started with VBoxManage, this is shown as process info: $ ps -ef | grep "JeOS"
user 7085 6439 7 11:51 ? 00:00:02 /usr/lib/virtualbox/VBoxHeadless -comment Ubuntu JeOS -startvm 1fff150e-cdcb-4502-9aac-09f0506c298d}}}
When a session is started with VBoxHeadless, the uuid in not shown as process info:
{{{
user 7541 6636 34 11:58 pts/1 00:00:02 /usr/lib/virtualbox/VBoxHeadless -startvm Ubuntu JeOS}}}
This (showing the uuid as prcess info) is much needed because otherwise it is virtually impossible to identify the session pid when there are multiple sessions running.
}}}
|
|||
| #5437 | obsolete | using win7-32guest on win7-64 host crash all systems | ||
| Description |
I'm using win7 64bit as host and win7 32bit as guest. I have no problem for some days and after it my system go in deadlock and crash: guest and host! It seems that it doesn't like my wireless mouse.... |
|||
| #20988 | duplicate | using virtualbox 6.1.34 with kernels 5.17.12-300.fc36.x86_64 and 5.17.13-300.fc36.x86_64 results in many errors and major corruption of linux and windows guests | ||
| Description |
i also entered this on rpmfusion bugzilla as: https://bugzilla.rpmfusion.org/show_bug.cgi?id=6334 Using virtualbox 6.1.34 with kernels 5.17.12-300.fc36.x86_64 and 5.17.13-300.fc36.x86_64 results in many errors and major corruption of linux and windows guests whereby they must be restored from backups. The last kernel that i know that worked with virtualbox is 5.17.11-300.fc36.x86_64. This is true for both the RPMFUSION distributed virtualbox and the oracle distributed virtualbox. Errors in guests are widespread and non deterministic (repeating boot results in different errors). many systemd services crashing. systemd itself sometimes failing early during boot. rpm database corruption which seems not reparable. booting the damaged guests with a working virtualbox configuration shows they are very damaged. This seems 100% reproducible at will and certainly tracks with kernel version. |
|||

