Custom Query (16363 matches)
Results (1561 - 1563 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6108 | obsolete | infinite resolution switching loop - WinXP Guest on WinXP x64 or Ubuntu 9.10 AMD64 Host | ||
| Description |
I faced this bug with VirtualBox 2.x and it is still there with 3.x. I'm running a WinXP Pro Guest under both - WinXP x64 and Ubuntu 9.10 AMD64. Certain applications like Internet Explorer (e.g. when opening an xps document) and FritzBox USB-over-LAN (.NET application) put VirtualBox into some endless resolution switching loop - it permanently switches the screen resolution of the Guest, causing screen flickering and window resizing and it is very hard to get control over the virtual machine. Enabling/Disabling 2D/3D acceleration, Automatic Window Resize, Seamless or Fullscreen mode does not help. Guest Tools are up to date. The only thing that ends this killing the application inside the Guest OS via Alt-F4. |
|||
| #9782 | fixed | infinite mirror effect in IE9 | ||
| Description |
This happens with the WDDM drivers: http://www.webalice.it/micioptah/IE9bug.mkv I didn't check if it happens without guest additions or with the non-WDDM version. It happens in every mode: fullscreen, transparent, windowed. Guest is Win7 starter x86, host is Ubuntu 11.10 x64. |
|||
| #13545 | invalid | incredibly slow network access from Windows 7 host to guest NAT network services | ||
| Description |
I observe really slow network connectivity from a Windows 7 Enterprise host to several Linux guests with NAT networking. I forward a local port (i.e. 2222) to a guest port (ie. 22) and get very slow (multiple seconds) initial ssh connections and after an established connection it is still incredibly slow. Typed characters are echoed back to the terminal only after several seconds. If I directly use the guest system via its console or graphical desktop it is fast and responsive. Neither the guest nor the host are under load. I already discussed this issue in IRC yesterday. Here is a transcript of the IRC session: 11:55 < jandd> I have a strange latency problem with ssh to a NAT forwarded ssh guest (VirtualBox 4.3.18 on Windows 7 host with CentOS 6.5 guest). Not only connecting is slow (looked at all the DNS advice already) but typing too (multiple seconds until a typed character appears in the terminal window). Typing in the guest console is fast and neither the host nor the guest are under load. Logs in the guest contain no information. I also tried a Debian guest and observed the same behaviour. I first observed this with the Boot2Docker VM a while ago but obviously this is a more general issue. Do you have any ideas where to look? 11:59 <@klaus-vb> DNS problems can't explain such extreme latency, so trying to poke around those areas won't help 12:00 <@klaus-vb> it's probably a regression due to the recent NAT code changes, backfiring on windows host 12:01 <@klaus-vb> jandd: just to make sure we'll look in the right place: this is with NAT, not with NAT Network, right? 12:02 <@klaus-vb> jandd: do you have an older data point which worked? was 4.3.16 also affected? 12:10 < jandd> yes this is a NAT issue 12:10 < jandd> I have no older data points 12:11 < jandd> the tests with Boot2Docker where in Juli with the VirtualBox version that was the current release at that time 12:11 <@klaus-vb> it's quite likely that this is a recent regression... 12:12 < jandd> 4.3.12 or 4.3.14 where current in July 12:12 < jandd> I can do another test with some older version, any suggestions which one to try? 12:13 <@klaus-vb> 4.3.16 and maybe 4.3.14... 12:13 < jandd> ok, I'll test these and come back afterwards 12:14 <@klaus-vb> thanks! 12:18 <@klaus-vb> I'll be afk for a bit, but back later. will read whatever you write... 12:55 < jandd> 4.3.16 is slow too ... continuing with 4.3.14 12:58 < jandd> 4.3.14 ... same :-( 13:09 <@klaus-vb> back... hmm. doesn't sound good. 4.3.12 would be quite a bit older. 13:11 < jandd> same with 4.2.26 13:12 <@klaus-vb> that's almost proof that something very bad is happening on your system, related to hardening of the VBox for Windows code 13:13 <@klaus-vb> 4.2.26 is quite recent actually, from July. 13:14 <@klaus-vb> would be great if you could try 4.3.12 or 4.2.24 - those predate the hardening effort. 13:15 < jandd> ok, I'll try 4.3.12 13:16 < jandd> the Windows version is Windows 7 Enterprise Version 5.1 (Build 7601: Service Pack 1) with all the latest patches applied if this matters 13:20 <@fmehnert> A VBoxStartup.log file from 4.3.18 could also help. 13:21 <@klaus-vb> would be of course by now overwritten by the older packages... 13:21 < jandd> ok, I'll do the test with 4.3.12 and will install 4.3.18 afterwards to provide the logs 13:33 < jandd> 4.3.12 is slow too 13:33 < jandd> I'll do another test with 4.3.18 and provide the logs afterwards. I just saved the VBox.log from the 4.3.12 test 13:35 < jandd> ... another Windows reboot :-/ 13:44 < jandd> https://www.dropbox.com/sh/uru57dbky4sc18m/AACst6LMfbXQBWAqHNzGSdv1a/VirtualBox-Slowness?dl=0 ... there are the logs 13:52 <@fmehnert> Let me check the log. Well, if 4.3.12 is affected as well, it cannot be the Windows hardening which we introduce with 4.3.14 13:58 <@fmehnert> I cannot spot any problem in the VBoxStartup.log. wintab32.dll couldn't be opened but that's probably not a problem. 13:58 <@fmehnert> I guess only a wireshark trace could help here. 13:59 < jandd> ok, I'll try that 14:32 < jandd> fmehnert: I used rawcap to get a dump because Wireshark does not support captures on Loopback on Windows 14:32 < jandd> the dump is in the same dropbox folder as the logs 14:34 < jandd> I used 2222 as forwarded port and "tcp.port == 22" in the Wireshark filter input field finds my ssh session 14:34 <@fmehnert> jandd: Hmm, in that folder I can only see the three older log files... 14:40 < jandd> fmehnert: sorry ... put it in the virtualbox logs folder instead of Dropbox ... should be there now 14:40 < jandd> dumpfile.pcap 14:42 <@fmehnert> Have it, thanks. Analyzing will take some time. I don't have time to look myself but I have created an internal issue for that problem and added your files there. 14:46 < jandd> ok, thanks 17:39 <@klaus-vb> jandd: I think this needs to become an official bug ticket... it's not a quick issue which can be resolved over IRC. http://www.virtualbox.org/wiki/Bugtracker I attach the logfiles and package capture from yesterday to this ticket. |
|||

