Custom Query (16363 matches)
Results (1855 - 1857 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9635 | obsolete | VDE parameters cause VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES error | ||
| Description |
Two bugs: Bug #1: virtualbox is looking for "libvdeplug.so", however on Ubuntu natty 64bit, the stock vde packages do NOT create that, only libvdeplug.so.2 (which is a symlink to the specific version of the lib). Recent tarballs of vde create libvdeplug.so.3, so it may be worth it to probe for any of the above names (libvdeplug.so, libvdeplug.so.2 and libvdeplug.so.3) to handle the various possible cases out in the wild. The current workaround is to symlink /usr/lib/libvdeplug.so -> /usr/lib/libvdeplug.so.2 or 3 dependign on which version of VDE is present. Bug#2 When attempting to configure a VM connected to a VDE switch, setting any parameters in the "Generic Properties", like the path to the switch socket causes the Virtualbox VM to be unable to start with the following error in the VM log: 00:00:00.393 VMSetError: /home/vbox/vbox-4.1.2/src/VBox/Devices/Network/DrvVDE.cpp(558) int drvVDEConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_PDM_DRVINS_UNKNOWN_CFG_VALUES 00:00:00.393 VMSetError: As long as vde_switch is started with NO SOCKET NAME specified (no -s option). and the Generic Properties box is left emtpy, virtualbox will start and connect to vde. However this doesn't let a user specific a specific port (to line up with vlan config), or a specific vswitch (of more than one are active) The GUI pops up a very nondescript error as well: Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} |
|||
| #9638 | obsolete | Unable to login to a VPN when bridge is done by WIFI adapter | ||
| Description |
Unable to login to a VPN when bridge is done by WIFI adapter or dialup (USB device 3G wireless). Notebook computer ASUS UL30A Series :: HOST: Windows 7 x64 GUEST: Windows XP SP3 x86 I tried the following 3 combinations on the notebook (only the first is successfull). 1 - I can properly connect to the VPN when the connection is bridged to the NIC adapter by CABLE with NAT or bridge. 2 - I cannot connect to the VPN when the connection is bridged to the WIFI adapter with NAT or bridge. (Even with the same IP address and configuration by CABLE connection.) 3 - I also cannot connect to the VPN when the connection is done by NAT and the notebook is connected to 3G wireless device. On the 3 methods, the VBOX GUEST always have Internet connection and can ping the VPN gateway (the returned error is an #721 The remote computer did not respond). |
|||
| #9644 | obsolete | segfault in VBoxHeadless 4.1.2 while doing clonehd | ||
| Description |
Hi! I was executing a "clonehd" command. While the system was under that load a segfault occured in VBoxHeadless. Host is a FC15 X64 system with several guest on it. Linux guests showed ATA bus resets when the error occurred, some windows guests were aborted. I wonder if this line in the logs might be connected with that? EXT4-fs (dm-2): Unaligned AIO/DIO on inode 12845094 by VBoxHeadless; performance will be poor. The same configuration worked flawlessly with FC12 - VBox 3.2.12 Any hints / workarounds? Thanks a lot! Cheers Martin |
|||

