Custom Query (16363 matches)
Results (1297 - 1299 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17960 | duplicate | VirtualBox guest additions for Linux fail to build with kernel v4.18.5 -> duplicate of #17981 | ||
| Description |
There is an issue with building the vboxsf module when the guest runs 64 bits kernel v4.18.5 (and probably older v4.18.x versions): the timespec structure was renamed timespec64 and so you need to test the kernel versions in vboxsf/utils.c and use timespec64 instead of timespec in the sf_ftime_from_timespec() and sf_timespec_from_ftime() functions. Neither the test build additions nor the development snapshot additions seem to be fixed in this respect (I just checked them). |
|||
| #17958 | fixed | VirtualBox on Solaris 11.4 systems with Intel Haswell or later causes host panic due to an SMAP violation => fixed in svn/6.1.x x>18 | ||
| Description |
Hello, is Solaris 11.4 beta supported please as host OS ? VirtualBox-5.2.18-SunOS-amd64-r124319.pkg cat /etc/release
Oracle Solaris 11.4 X86
Copyright (c) 1983, 2018, Oracle and/or its affiliates. All rights reserved.
Assembled 02 July 2018
pkg list entire
NAME (PUBLISHER) VERSION IFO
entire 11.4-11.4.0.0.1.10.0 i--
When installing on Solaris 11.4 beta I get a FAILED message :
Detected Solaris 11 Version 175
Loading VirtualBox kernel modules...
- Added: Host driver
- Added: NetAdapter driver
- Added: NetFilter (Crossbow) driver
- Added: USBMonitor driver
- Added: USB driver
Configuring services...
svcadm: svc:/application/virtualbox/zoneaccess:default is misconfigured ("restar
ter" property group lacks "state" property).
* Warning!! Enabling Zone access service ...FAILED.
* Warning!! Refer /var/svc/log/application-virtualbox-zoneaccess:default.log
for details.
Installing MIME types and icons...
Installing Python bindings...
- Installed: Bindings for Python 2.7
Updating the boot archive...
Installation of <SUNWvbox> was successful.
Unfortunately while trying to create a VM guest , the host panics:
vmcore.0> ::stack
0xfffffffff835a391()
0xfffffffff8354ae5()
0xfffffffff8355e6a()
0xfffffffff83fefa6()
0xfffffffff8356a30()
supdrvIOCtl+0x156f()
VBoxDrvSolarisIOCtl+0x375()
cdev_ioctl+0x67(10f00000003, c0185687, 7fffbcffec50, 202003, ffffa1c0215441a0,
ffffe330027dde14)
spec_ioctl+0x62(ffffa1c020d90880, c0185687, 7fffbcffec50, 202003,
ffffa1c0215441a0, ffffe330027dde14)
fop_ioctl+0xf1(ffffa1c020d90880, c0185687, 7fffbcffec50, 202003,
ffffa1c0215441a0, ffffe330027dde14)
ioctl+0x18a(f, ffffffffc0185687, 7fffbcffec50)
sys_syscall+0x247()
Is this a known issue please ? I could try a test build ... Thank you David |
|||
| #17957 | duplicate | The latest VirtualBox version 5.2.18 is not available in the RPM repo | ||
| Description |
The latest VirtualBox version 5.2.18 is missing from the following location: http://download.virtualbox.org/virtualbox/rpm/fedora/26/x86_64/ As a result, the "dnf update" cannot update the VirtualBox application. |
|||

