Custom Query (16363 matches)
Results (1951 - 1953 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11407 | obsolete | Virtualbox 4.2.6 crashes frequently in libQtCoreVBox | ||
| Description |
I observer many crashes with virtualbox on S11.1 SRU3.4. MDB shows the following:
ffff80ffbfffe320 libc.so.1`realfree+0x3c() ffff80ffbfffe350 libc.so.1`cleanfree+0x4a() ffff80ffbfffe380 libc.so.1`_malloc_unlocked+0xdc() ffff80ffbfffe3a0 libc.so.1`malloc+0x2c() ffff80ffbfffe3c0 libstdc++.so.6.0.14`_Znwm+0x1e() ffff80ffbfffe3f0 libQtCoreVBox.so.4`_ZN11QThreadPoolC1EP7QObject+0x24() ffff80ffbfffe410 libQtCoreVBox.so.4`_ZN11QThreadPool14globalInstanceEv+0x4e() ffff80ffbfffe430 libQtCoreVBox.so.4`_ZN16QCoreApplicationD2Ev+0x4d() ffff80ffbfffe4e0 libQtGuiVBox.so.4`_ZN12QApplicationD1Ev+0x572() ffff80ffbfffe690 VirtualBox.so`TrustedMain+0x3da() ffff80ffbffff710 SUPR3HardenedMain+0x2e0() ffff80ffbffff720 _start+0x6c()
debugging core file of VirtualBox (64-bit) from boot198 file: /opt/VirtualBox/amd64/VirtualBox initial argv: /opt/VirtualBox/amd64/VirtualBox -session 10bdb5d90dcd9499d71354191836699892000 threading model: native threads status: process terminated by SIGSEGV (Segmentation Fault), addr= ffff80ffbf4efcf8 |
|||
| #11534 | fixed | vnic VID property is misteriously zeroed on Solaris 11.1 after VM start | ||
| Description |
I use VB 4.2.8 On Solaris 11.1 SRU1.4 VID property for vnic interface is zeroed after VM start. ORACLE VB uses that vnic interface. vnic created on the base of dot1Q trunk. The same problem was observed for vlan interfaces too. How to reproduce:
Workaround: After VM start restore VID setting: dladm modify-vnic -v 998 v4vid998link0 That helps to restore IP connectivity for that VM. NOTE 1: the issue appears for the first time after VM started. VM reboot process doesn't affect IP connectivity. Only VM poweroff makes the issue to appear again. NOTE 2: vlan interfaces are affected by the issue too. NOTE 3: Seen the problem in 4.1.x and 4.2.x builds. |
|||
| #9998 | obsolete | perfectly installed Solaris 10 (no GUI) impossible to type into login prompt | ||
| Description |
DEFECT: Login impossible, guest OS is deaf to keyboard hits of any kind. No known workaround, since no unprivileged users are available in the system for remote login. Root remote login is forbidden by default in Solaris. |
|||

