Custom Query (16363 matches)
Results (1129 - 1131 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1953 | fixed | Segmentation fault on Ubuntu AMD64 with VRDP external authentication -> Fixed in 1.6.6 | ||
| Description |
I'm running VBox 1.6.4 on Ubuntu desktop 8.04.1 AMD64 updated @ Aug 13 2008. I've enabled auth logging with export VRDP_AUTH_DEBUG_FILENAME=/home/vbox/log I started VM with VBoxHeadless -s dev & and in log I obtained: u[vbox], d[dev2.lan], p[4] vrdpauth_pam_init: dlopen libpam.so failed vrdpauth_pam_init failed 4 I made ln -s /lib/libpam.so.0 /lib/libpam.so, and it worked u[vbox], d[dev2.lan], p[4] init ok Using PAM service: vrdpauth start ok conv: num 1 u[vbox] p[4] conv: 0 returning password [4] auth ok access granted vrdpauth_pam_close completed After this I tried unhautorized userid/pwd, and I got segmentation faults [1]+ Segmentation fault VBoxHeadless -s dev in all casese below: u[leo], d[], p[0] init ok Using PAM service: vrdpauth start ok conv: num 1 u[leo] p[0] conv: 0 returning password [0] u[leo], d[], p[6] init ok Using PAM service: vrdpauth start ok conv: num 1 u[leo] p[6] conv: 0 returning password [6] u[vbox], d[], p[0] init ok Using PAM service: vrdpauth start ok conv: num 1 u[vbox] p[0] conv: 0 returning password [0] In other words , if user is allowed, all is ok, but if user si NOT allowed the VM crashes with segmenattion fault. It looks a Virtualbox bug. p.s. I rebooted whole system, and now I get segfault even for authorized userid/passwords. |
|||
| #1955 | fixed | USB 2.0 aka EHCI does not work | ||
| Description |
I have a problem with EHCI in respect to USB 2.0. As long as EHCI remains unactivated, the access from VirtualBox to all USB-Devices are without any problem. However when I activate EHCI nothing seems to fuction at all. For e.g: USB Stick is plugged, Guestsystem (WinXP) tries to install the matching Drive but fails bringing the Error "An error is found and the Device may eventually not function properly" and the access to USB-Stick is not possible. In the Systemcontrol of WinXP, you can find the Device, furnished with Exclamation mark! Deinstallation of Device followed by renewed installation of the Drive etc. do not bring the needed result. So the Device remains inaccessible. I use following Configuration:
VirtualBox 1.6.2 My Hardware supports USB 2.0. I have tried in two different machines without any USB Hub. I posted this to different forums, only a few answers, most of them with the same problem. |
|||
| #1957 | fixed | DMI default processing is wrong => Fixed in 1.6.6 | ||
| Description |
My system is a home built one and as such the Mortheboard BIOS DmiSystemVendor is an empty string. In order to avoid reactivation on Dual Native/VM boot, I therefore need my VM DmiSystemVendor to be empty also. However in src/VBox/Devices/PC/DevPcBios.cpp we have #define READCFGSTR(name, variable, default_value) \
do { \
rc = CFGMR3QueryStringAlloc(pCfgHandle, name, & variable); \
if (rc == VERR_CFGM_VALUE_NOT_FOUND) \
variable = MMR3HeapStrDup(PDMDevHlpGetVM(pDevIns), MM_TAG_CFGM, default_value); \
else if (VBOX_FAILURE(rc)) \
return PDMDevHlpVMSetError(pDevIns, rc, RT_SRC_POS, \
N_("Configuration error: Querying \"" name "\" as a string failed")); \
} while (0)
...
READCFGSTR("DmiSystemVendor", pszDmiSystemVendor, "innotek GmbH");
and in src/VBox/VMM/CFGM.cpp CFGMR3DECL(int) CFGMR3QueryStringAlloc(PCFGMNODE pNode, const char *pszName, char **ppszString)
{
size_t cch;
int rc = CFGMR3QuerySize(pNode, pszName, &cch);
if (VBOX_SUCCESS(rc))
{
char *pszString = (char *)MMR3HeapAlloc(pNode->pVM, MM_TAG_CFGM_USER, cch);
if (pszString)
{
rc = CFGMR3QueryString(pNode, pszName, pszString, cch);
if (VBOX_SUCCESS(rc))
*ppszString = pszString;
else
MMR3HeapFree(pszString);
}
else
rc = VERR_NO_MEMORY;
}
return rc;
}
Hence VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" ""
|
|||

