Custom Query (16363 matches)
Results (751 - 753 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19271 | fixed | OSX 5.2.36 master is not the good version! | ||
| Description |
Hi, Your download link for OS X VirtualBox 5.2.36 is in fact the 5.2.35 version! Please update your master. Regards |
|||
| #19265 | duplicate | "Low Host Memory" crashes Guest when accessing large file in shared folder | ||
| Description |
Possible duplicate (marked solved in 6.0.14): https://www.virtualbox.org/ticket/18766?cversion=0&cnum_hist=26 Host OS:
Guest OS:
Machine specs
Description to reproduce:
The command copies 1.8GB out of 1.9GB in 107s then the guest gets paused and a pop-up error message appears with the following information:
After inspecting the log file, I found the following line which indicates an out-of-date version of guest additions: 00:00:17.736846 VMMDev: Guest Additions information report: Version 6.0.0 r127566 '6.0.0' This is in contrast however to what VBoxClient and vboxservice.service report on the Guest: VBoxClient -V
6.1.2r135662
sudo systemctl status vboxservice
● vboxservice.service - VirtualBox Guest Service
Loaded: loaded (/usr/lib/systemd/system/vboxservice.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2020-01-24 14:23:37 PST; 14min ago
Process: 395 ExecStartPre=/usr/bin/modprobe vboxguest (code=exited, status=0/SUCCESS)
Process: 400 ExecStartPre=/usr/bin/modprobe vboxvideo (code=exited, status=0/SUCCESS)
Process: 402 ExecStartPre=/usr/bin/modprobe vboxsf (code=exited, status=0/SUCCESS)
Main PID: 403 (VBoxService)
Tasks: 9 (limit: 9523)
Memory: 3.2M
CGroup: /system.slice/vboxservice.service
└─403 /usr/bin/VBoxService -f
Jan 24 14:23:37 viper-arch systemd[1]: Started VirtualBox Guest Service.
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802052 main VBoxService 6.1.2 r135662 (verbosity: 0) linux.amd64 (Jan 14 2020 22:33:16) release log
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802056 main Log opened 2020-01-24T22:23:37.801171000Z
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802493 main OS Product: Linux
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802552 main OS Release: 5.4.13-arch1-1
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802601 main OS Version: #1 SMP PREEMPT Fri, 17 Jan 2020 23:09:54 +0000
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802655 main Executable: /usr/bin/VBoxService
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802656 main Process ID: 403
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.802657 main Package type: LINUX_64BITS_GENERIC (OSE)
Jan 24 14:23:37 viper-arch VBoxService[403]: 22:23:37.806732 main 6.1.2 r135662 started. Verbose level = 0
Is this possibly a problem with my Guest Utils installation seeing as how the related bug was marked solved in 6.0.14? Thank you for your time. |
|||
| #19263 | fixed | Possibility to infect VMs BIOS | ||
| Description |
This issue was initially reported to the security team, but after some discussion it was mentioned that I should open this in the public bug tracking system (seems strange to me, but...). Just for reference, follow the final conclusion from the security team: "Admin rights give a user the power to do anything on the system. An "evil admin" is more a social component of this bug than a product's security abilities (or its lack thereof). However, we get your point and think that the "validation/check" proposed by you may be an enhancement feature in the product. Since our team (SecAlert) only deals with security vulnerabilities in the product, we will not be able to help you on this further. You could log an enhancement request on VirtualBox's public bug tracker: https://www.virtualbox.org/wiki/Bugtracker " So the bad use of this knowledge is not my fault. The case is that it is possible to replace the BIOS that is going to be used by all VMs, and with this all of them would be infected, in a way that the host system and the guest would not detect. It is possible to add a service to run in parallel with the OS, like a RuntimeService or a SMM Interrupt. This affects all versions 6.0.x and 5.x. The attached file has the details about how to do it. |
|||

