Custom Query (16363 matches)
Results (427 - 429 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12019 | obsolete | 4.2.14-ose and 4.2.16-ose always Autoprobing vrde port (VNC TCP/5900) | ||
| Description |
VBoxManage modifyvm "TEST" --vrde on --vrdeport 6000 --vrdeproperty VNCPassword="password" and however I find the option '--vrde port 6000' is no longer work in 4.2.14, it always using Autoprobing TCP port and always starting with port 5900, does any one know how to over ride this? "--vrdeport 6000" set port to 6000, but after manual start I see in console: $ VBoxHeadless --startvm TEST Oracle VM VirtualBox Headless Interface 4.2.16_OSE (C) 2008-2013 Oracle Corporation All rights reserved. 08/08/2013 17:37:23 Autoprobing TCP port 08/08/2013 17:37:23 Autoprobing selected TCP port 5900 08/08/2013 17:37:23 Autoprobing TCP6 port 08/08/2013 17:37:23 Autoprobing selected TCP6 port 5900 VRDE server is listening on port 5900. And vnc://SERVER_IP:5900 work fine, but I want my custom port 6000 as on older versions of VirtualBox-ose. Discussion in forum: https://forums.virtualbox.org/viewtopic.php?f=1&t=56311 |
|||
| #12068 | duplicate | 4.2.16 and Kernel 3.11.0 | ||
| Description |
Hello all, I sure wish I could give you more information, but if I do, I no longer have a Virtualized system. I upgraded my systems to Kernel 3.11 and restarted. I performed /etc/init.d/vboxdrv setup as none of my systems would start automatically. I usually do this any time I upgrade my kernels as well just to ensure I have good module support throughout. However, when I upgraded to linux-3.11, none of my Virtual Boxes would start. I Booted to linux-3.10.10 and all worked perfectly fine. It seems that with linux-3.11, the systems interfaces are not recognized, though the system still see's them as normal. From my VBox.log for one of my VM's this is what was causing the failure. 00:00:00.408464 Chipset cannot do MSI: VERR_NOT_IMPLEMENTED 00:00:00.418100 VMSetError: /home/vbox/vbox-4.2.16/src/VBox/Devices/Network/DrvIntNet.cpp(1718) int drvR3IntNetConstruct(PDMDRVINS*, CFGMNODE*, uint32_t); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:00.418194 VMSetError: /home/vbox/vbox-4.2.16/src/VBox/Devices/Network/DevE1000.cpp(7680) int e1kConstruct(PDMDEVINS*, int, CFGMNODE*); rc=VERR_INTNET_FLT_IF_NOT_FOUND 00:00:00.424019 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found. 00:00:00.434457 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-br0' (VERR_INTNET_FLT_IF_NOT_FOUND). 00:00:00.434475 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false 00:00:00.445971 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=NS_ERROR_FAILURE (0X80004005)) I tried vboxmanage modifyvm <vmname> --nic1 bridged --bridgeadapter br<0-6> and nothing would work. I verified my system did have the adapters available and it did. I then rebooted to 3.10.10 and reran /etc/init.d/vboxdrv setup and all VMS started automatically and perfectly fine. Just thought you should be aware. Thank you, |
|||
| #12139 | fixed | 4.2.18 GAs: Left mouse click lost with WDDM in Win 7 and Win 8 | ||
| Description |
After updating to 4.2.18, Windows 7 & 8 guests lose their left mouse functionality after some unknown time (around 30 minutes or so). I believe the issue to be with the WDDM component, because it does NOT happen with Windows XP and (more importantly) with Windows 7 when the GAs are installed without WDDM support. Keyboard input, right-click, scroll-wheel, hovering, work OK. In all guests that I tried, the screensaver is set to 'Blank Screen', but it doesn't have to kick in for the issue to appear. The tests were done with no programs running, just an Explorer window open just to try the hover-over functionality. The only way to restore normal functionality is to go full-screen and back or (Windows 7 only) send a Ctrl-Alt-Del. Other <Host>+<Key> combinations do not seem to fix the issue (kinda makes sense). See also reports at:
Attaching VBox logs for Win7 (with WDDM) and Win8. Note that just before shutting down the guests, a resize command was issued. |
|||

