Win 7 VM slows down when presenting in GoToMeeting

[Mark Knecht]

This bug has been on-going for me since the January time frame. The basic issue is that when using GoToMeeting in a Win7 VM, and if my VM is made the presenter, then graphics slow down to the point where the VM becomes unusably slow. The VM can be in a meeting with someone else presenting and it's fine. Only slow when the VM becomes the presenter. Slow means the cursor is unresponsive, gui interaction inside the Win 7 VM is very slow, cursor flicker. Pause the screen so that it's not being updated and the VM becomes fast again.

I've seen this problem on 3 Win 7 VMs, two on this machine and one on my laptop. Both hosts are Gentoo Linux 64-bit, mostly stable and completely up to date.

Both machines can boot Win 7 natively and have not problems. VMWare running Win XP on the same machines has no problems.

I am going to attempt to attach a log file of the VM booting, starting Google Chrome, starting G2M, having the problems and then shutting down the VM.

[Mark Knecht]

Log file when using GoToMeeting & having slow graphics

[Mark Knecht]

Gentoo made Virtualbox-4.2.10 available today. I updated. The problem is worse than before.

1) Join a GoToMeeting session or GoToWebinar event and everything is fine.

2) In GoToMeeting become the presenter. The cursor in Windows almost disappears. It's flickering on and off if the mouse is still. When I move the mouse the cursor becomes essentially invisible. Trying to do ANYTHING in Windows is completely hindered and very, very slow.

3) Stop being the presenter or pause my screen and Windows acts normally.

I see this problem on all 3 of my VB VMs on two different machines.

I do not see this problem in VMWare Player running Win XP.

[Frank Mehnert]

Could you try the following:

1. Disable 3D support for this VM. Any improvement?
2. Test the test build from #11615. I know, the error description there is completely different but the fix could you still affect.

[Mark Knecht]

Replying to frank:

Could you try the following:

1. Disable 3D support for this VM. Any improvement?
2. Test the test build from #11615. I know, the error description there is completely different but the fix could you still affect.

Frank,

Thanks for the response.

As best I can tell 3D is disabled already. It's a Win 7 VM on a Gentoo Linux host. I don't think 3D can be enabled. When I attempt to install the VB additions 3D is not checked by default and if I try to enable it I get a message telling me I cannot.

As for the build you suggested, is that from SVN? If so does that mean building from source or where you pointing me toward this file in a link at the very end?

​http://www.virtualbox.org/download/testcase/VirtualBox-4.2.11-84452-Linux_amd64.run

I need to 1) do backups of my VMs and 2) find instructions on how to load this run file.

I'll try to do that and get back to you.

Again thanks!

• Mark

[Mark Knecht]

Frank,

OK, I loaded the test version from the link above using 'sh file'. No change to the problem. The VM is fine in GoToMeeting when I am just part of the meeting and watching someone else. As soon as I start presenting the cursor starts blinking, slows down and doesn't track my mouse movements very well, and takes a _really_ long time calling up things like menus in Windows apps in the VM. If I pause the presentation everything is fine. When I stop presenting everything is fine. When I exit the meeting everything.

One thing I was unsure of: I did an emerge -C virtualbox to get rid of the Gentoo supplied 4.2.10 version but I did not specifically remove anything else, so there is still some 4.2.10 stuff on the system:

mark@c2stable ~ $ eix -Ic virtualbox [I] app-emulation/virtualbox-additions (4.2.10{tbz2}@03/15/2013): CD image containing guest additions for VirtualBox [I] app-emulation/virtualbox-extpack-oracle (4.2.10{tbz2}@03/15/2013): PUEL extensions for VirtualBox [I] app-emulation/virtualbox-modules (4.2.10{tbz2}@03/15/2013): Kernel Modules for Virtualbox Found 3 matches. mark@c2stable ~ $

If you think I should remove that also let me know and I will. (Seems like I probably should...)

I will attempt to attach this morning's log file to this post so you can look that over.

I appreciate your help. If I've not done something right please let me know.

Also, I did not select 3D when updating the Guest Additions as I think that's what you wanted.

Cheers, Mark

[Mark Knecht]

Log file for 4.2.11 test version - problem still persists

[Mark Knecht]

Went ahead and removed the older modules ebuild and reinstalled the 4.2.11 test build. modinfo says all the modules loaded are part of 4.2.11. Problem persists.

I tried looking through the vbox.log file myself but I don't see anything. I started wondering if there was possibly some Windows benchmark program that I might download and run that could tell us anything? Nothing I run so far seems to leave any tracks in the log file and nothing special seems to happen there when I run GoToMeeting so I don't know what other info to provide.

Is there a way to run Virtualbox with more enhanced logging that could give you more info?

Thanks, Mark

[Mark Knecht]

As I stated in the initial post, I believe this problem has been with me since January. It appears that the first 4.2 version came out around that time. For lack of any other ideas at this time I think I'll try bisecting the problem using older versions of Virtualbox to see if it showed up with a specific version. I'll report back what I find, if anything.

[Mark Knecht]

OK, assuming I'm not making a stupid mistake because I'm not used these VB image installs before I've tested back as far as VirtuaBox4.2.4-81684-Linux_amd64.run and they all fail. I cannot go earlier (apparently) as the install fails to build the kernel modules. The log files all have something like this when the install fails:

c2stable VBTest # cat /var/log/vbox-install.log 
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.7.10-gentoo/build modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || (                \
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ;                                                      \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0

I've not used 'make prepare' before and am unsure if I need to rebuild the kernel in that case so I'll wait for some input here or hope I find some info elsewhere in the VB forums.

At this point I'm fairly well confused. 4.2.4 was released in October, 2012 and I certainly haven't had the problem that long. This next part is rather long but it's my emerge history of virtualbox back for a year. From this info I'm pretty sure the problem started here most likely with version 4.2.6 which occurred Feb. 9th & again on the 13th:

1347662087: Started emerge on: Sep 14, 2012 15:34:47
1347662194:  >>> emerge (7 of 9) app-emulation/virtualbox-4.2.0-r1 to /
1347662194:  === (7 of 9) Cleaning (app-emulation/virtualbox-4.2.0-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.0-r1.ebuild)
1347662196:  === (7 of 9) Compiling/Packaging (app-emulation/virtualbox-4.2.0-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.0-r1.ebuild)
1347662438:  === (7 of 9) Merging (app-emulation/virtualbox-4.2.0-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.0-r1.ebuild)
1347662444:  === (7 of 9) Post-Build Cleaning (app-emulation/virtualbox-4.2.0-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.0-r1.ebuild)
1347662444:  ::: completed emerge (7 of 9) app-emulation/virtualbox-4.2.0-r1 to /


1351258207: Started emerge on: Oct 26, 2012 06:30:07
1351258284:  >>> emerge (5 of 6) app-emulation/virtualbox-4.2.2 to /
1351258284:  === (5 of 6) Cleaning (app-emulation/virtualbox-4.2.2::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.2.ebuild)
1351258289:  === (5 of 6) Compiling/Packaging (app-emulation/virtualbox-4.2.2::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.2.ebuild)
1351258570:  === (5 of 6) Merging (app-emulation/virtualbox-4.2.2::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.2.ebuild)
1351258574:  === Unmerging... (app-emulation/virtualbox-4.2.0-r1)
1351258577:  >>> unmerge success: app-emulation/virtualbox-4.2.0-r1
1351258578:  === (5 of 6) Post-Build Cleaning (app-emulation/virtualbox-4.2.2::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.2.ebuild)
1351258578:  ::: completed emerge (5 of 6) app-emulation/virtualbox-4.2.2 to /


1352648818: Started emerge on: Nov 11, 2012 07:46:57
1352648887:  >>> emerge (3 of 4) app-emulation/virtualbox-4.2.4 to /
1352648887:  === (3 of 4) Cleaning (app-emulation/virtualbox-4.2.4::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4.ebuild)
1352648889:  === (3 of 4) Compiling/Packaging (app-emulation/virtualbox-4.2.4::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4.ebuild)
1352649128:  === (3 of 4) Merging (app-emulation/virtualbox-4.2.4::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4.ebuild)
1352649133:  === Unmerging... (app-emulation/virtualbox-4.2.2)
1352649136:  >>> unmerge success: app-emulation/virtualbox-4.2.2
1352649139:  === (3 of 4) Post-Build Cleaning (app-emulation/virtualbox-4.2.4::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4.ebuild)
1352649139:  ::: completed emerge (3 of 4) app-emulation/virtualbox-4.2.4 to /
1352730487: Started emerge on: Nov 12, 2012 06:28:07
1352759506: Started emerge on: Nov 12, 2012 14:31:45
1352760626: Started emerge on: Nov 12, 2012 14:50:25
1352760661:  >>> emerge (1 of 1) app-emulation/virtualbox-4.2.4-r1 to /
1352760661:  === (1 of 1) Cleaning (app-emulation/virtualbox-4.2.4-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4-r1.ebuild)
1352760663:  === (1 of 1) Compiling/Packaging (app-emulation/virtualbox-4.2.4-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4-r1.ebuild)
1352760915:  === (1 of 1) Merging (app-emulation/virtualbox-4.2.4-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4-r1.ebuild)
1352760923:  === Unmerging... (app-emulation/virtualbox-4.2.4)
1352760926:  >>> unmerge success: app-emulation/virtualbox-4.2.4
1352760930:  === (1 of 1) Post-Build Cleaning (app-emulation/virtualbox-4.2.4-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.4-r1.ebuild)
1352760930:  ::: completed emerge (1 of 1) app-emulation/virtualbox-4.2.4-r1 to /


1356199700: Started emerge on: Dec 22, 2012 10:08:19
1356199803:  >>> emerge (6 of 7) app-emulation/virtualbox-4.2.6 to /
1356199803:  === (6 of 7) Cleaning (app-emulation/virtualbox-4.2.6::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6.ebuild)
1356199806:  === (6 of 7) Compiling/Packaging (app-emulation/virtualbox-4.2.6::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6.ebuild)
1356200046:  === (6 of 7) Merging (app-emulation/virtualbox-4.2.6::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6.ebuild)
1356200049:  === Unmerging... (app-emulation/virtualbox-4.2.4-r1)
1356200052:  >>> unmerge success: app-emulation/virtualbox-4.2.4-r1
1356200054:  === (6 of 7) Post-Build Cleaning (app-emulation/virtualbox-4.2.6::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6.ebuild)
1356200054:  ::: completed emerge (6 of 7) app-emulation/virtualbox-4.2.6 to /



1360456765: Started emerge on: Feb 09, 2013 16:39:25
1360457242:  >>> emerge (4 of 4) app-emulation/virtualbox-4.2.6-r1 to /
1360457242:  === (4 of 4) Cleaning (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360457244:  === (4 of 4) Compiling/Packaging (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360457487:  === (4 of 4) Merging (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360457492:  === Unmerging... (app-emulation/virtualbox-4.2.6)
1360457495:  >>> unmerge success: app-emulation/virtualbox-4.2.6
1360457497:  === (4 of 4) Post-Build Cleaning (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360457497:  ::: completed emerge (4 of 4) app-emulation/virtualbox-4.2.6-r1 to /



1360892894: Started emerge on: Feb 14, 2013 17:48:14
1360893112:  >>> emerge (10 of 14) app-emulation/virtualbox-4.2.6-r1 to /
1360893112:  === (10 of 14) Cleaning (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360893114:  === (10 of 14) Compiling/Packaging (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360893417:  === (10 of 14) Merging (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360893420:  === Unmerging... (app-emulation/virtualbox-4.2.6-r1)
1360893422:  >>> unmerge success: app-emulation/virtualbox-4.2.6-r1
1360893424:  === (10 of 14) Post-Build Cleaning (app-emulation/virtualbox-4.2.6-r1::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.6-r1.ebuild)
1360893424:  ::: completed emerge (10 of 14) app-emulation/virtualbox-4.2.6-r1 to /



1362168675: Started emerge on: Mar 01, 2013 12:11:14
1362168747:  >>> emerge (3 of 4) app-emulation/virtualbox-4.2.8 to /
1362168747:  === (3 of 4) Cleaning (app-emulation/virtualbox-4.2.8::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.8.ebuild)
1362168751:  === (3 of 4) Compiling/Packaging (app-emulation/virtualbox-4.2.8::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.8.ebuild)
1362168999:  === (3 of 4) Merging (app-emulation/virtualbox-4.2.8::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.8.ebuild)
1362169003:  === Unmerging... (app-emulation/virtualbox-4.2.6-r1)
1362169005:  >>> unmerge success: app-emulation/virtualbox-4.2.6-r1
1362169008:  === (3 of 4) Post-Build Cleaning (app-emulation/virtualbox-4.2.8::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.8.ebuild)
1362169008:  ::: completed emerge (3 of 4) app-emulation/virtualbox-4.2.8 to /



1363379734: Started emerge on: Mar 15, 2013 13:35:33
1363379953:  >>> emerge (12 of 17) app-emulation/virtualbox-4.2.10 to /
1363380185:  === (12 of 17) Cleaning (app-emulation/virtualbox-4.2.10::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.10.ebuild)
1363380190:  === (12 of 17) Compiling/Packaging (app-emulation/virtualbox-4.2.10::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.10.ebuild)
1363380493:  === (12 of 17) Merging (app-emulation/virtualbox-4.2.10::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.10.ebuild)
1363380497:  === Unmerging... (app-emulation/virtualbox-4.2.8)
1363380499:  >>> unmerge success: app-emulation/virtualbox-4.2.8
1363380502:  === (12 of 17) Post-Build Cleaning (app-emulation/virtualbox-4.2.10::/usr/portage/app-emulation/virtualbox/virtualbox-4.2.10.ebuild)
1363380502:  ::: completed emerge (12 of 17) app-emulation/virtualbox-4.2.10 to /



1364061305: Started emerge on: Mar 23, 2013 10:55:04
1364061310: === Unmerging... (app-emulation/virtualbox-4.2.10)
1364061315:  >>> unmerge success: app-emulation/virtualbox-4.2.10

At this point I'm lost for ideas, other than possibly this is some nvidia-driver problem which only shows up with VirtualBox running Win 7 & GoToMeeting, but that's pretty remote in my mind.

Thanks, Mark

[Mark Knecht]

The problems continue. I've tried to go back through any changes made to the system since the first of the year and haven't been able to find anything that fixes this.

Again, the ONLY problem I'm reporting here is the cursor blinking weirdly and the all mouse actions going very slowly when GoToMeeting is in presentation mode. I know this is a corner case issue but it's really killing me and my work. I've used G2M for 4-5 years now and never had a problem until the last few months.

That said, I appreciate the help I've received so far and hope someone out there has some new ideas for me to try.

Thanks

[Mark Knecht]

MORE NOTES:

Yesterday I continued to try out different changes in the Settings area. (PAE/NX, Vt-x, Nested Paging) No change produced better results.

I did find one interesting piece of info. If I set up two VMs, both running Win 7 64-bit, but on different machines then I am able to see both sides of the GoToMeeting session. What I found was strange. The Virtualbox VM that is the presenter is actually updating it's screen more slowly than the VM at the other end which is receiving the session.

What I mean is this:

1) Set up GoToMeeting on both ends. One machine is presenter. Nothing on his desktop. On the other machine I see the presenter's desktop.

2) On the presenter double click 'Computer' to open Windows Explorer. Nothing happens.

3) On the far end I see explorer open. On the presenting machine still nothing has happened.

4) Finally, 2-3 seconds later I see explorer open on the presenting machine.

Essentially, the Explorer window got to the receiving end before it existed on the transmitting end!

Same thing happen with any application on the presenter. I always see it at the far end before I see it where the application is running. This is true both opening and closing applications.

This makes me think the problem might be the Virtualbox graphics driver? Does the application GUI, like the Explorer window, exist in video memory and hence get transmitted, long before the local graphics driver updates the virtual monitor?

I don't know. I'm talking to the ether here until someone with some technical knowledge gets involved.

Cheers

[Mark Knecht]

To whom it may concern,

After 1 response 7 weeks ago and no follow-up to the work I did answering that post I'll continue to watch this bug report and respond if anyone cares to ask future questions. Unfortunately this problem is major enough for me that I'm being driven to purchase VMWare which doesn't exhibit the problem. Earlier versions of Virtualbox didn't either but no one seems to be working on this I see no solutions other than the sad one of paying money to get closed source software so I can do my work This has been a VERY unfortunate regression, at least for me.

Cheers, Mark

[Jerry_J]

I am having the same problem connecting to any Win 7 machine with GoToMeeting. They are not VM's. These are standalone Win 7 Professional 64 bit machines.

GoToMeeting lags incredibly. Mouse moves and click take seconds to respond, and keyboard entry also has several second delay.

So, this may not be a VBox problem.

[Mark Knecht]

Completely a VBox problem here. My laptop dual boots Gentoo & Win 7. No problem in Win 7. G2M as presenter in VBox in Gentoo is messed up as reported. Same on my server. I've tested 3 machines here. They are all bad.

I've taken to running a native Windows machine as G2M presenter and then connecting to the VBox VM I want to display using Remote Desktop. That works fine as the G2M presenter is native Windows.

I don't like that complexity but it saves me spending $300 on VMware for now.

[Bugsy]

I'm experiencing exactly same problem with the only difference that I'm running the system on W7 host.

Any help would be more than appreciated.

In my case problem too hits my work related activities and should I not find any solution will be forced to move away to VmWare unfortunately.

Please have a look at this problme.

Thanks.

[Mark Knecht]

Replying to Bugsy:

I'm experiencing exactly same problem with the only difference that I'm running the system on W7 host.

Any help would be more than appreciated.

In my case problem too hits my work related activities and should I not find any solution will be forced to move away to VmWare unfortunately.

Please have a look at this problme.

Thanks.

I _may_ have a solution that works for you because your host is Windows based and but not for me as my host is Linux based.

1) Start Go2Meeting in the host Win7 environment.

2) Run your Windows VMs as normal.

3) Run Remote Desktop Protocol inside the VM an allow connections to the VM

4) Connect to the VM from your Win 7 host.

Basically, G2M Is running in native Windows and doesn't suffer this Virtualbox problem. RDP allows the native Win 7 environment, and hence anyone you are sharing with via G2M, to see the VM. We do not see a slowdown when operating this way.

If you're not familiar with RDP but, like me, are a Google Chrome user, then you can get both sides of RDP setup inside of Chrome by going to the App Store and downloading the RDP app.

HTH

[Bugsy]

Hi LGTrader,

Whilst our issue hasn't been fixed, your workaround works perfectly!

I'm not sure what DE you're running but for Linux you can find RDP client's too to use the same workaround.

It would be great if problem could be fixed finally.

[Mark Knecht]

Glad it works for you. Not sure what version you're running. I'm currently on 4.3.8 on Gentoo amd64. I find that while the problem is certainly not fixed it is a lot better than at the time I originally wrote this report. (Maybe a year ago?) Anyway, I'm able to use G2M as presenter now without the workaround, and the speed is OK, but the cursor in my Win 7 VM still blinks at a very high speed in the VM. On the receiving end the blinking isn't visible so it's more an annoyance than a real problem.

The most disappointing aspect of this problem to me has been the complete lack of interest by VB developers, but alas, it's Open Source so that's life.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.

[sbrunov]

Hello, Everyone!

It seems that the problem still persists.

When being presenter with enabled screen sharing, the CPU is being consumed heavily: for example, the voice from the local microphone becomes breaking.

It would be great to have this defect resolved.

Context

Hardware

Virtual machine settings:

• CPU: 4 processors (of 8 processors in total), 80% execution cap.
• RAM: 8192 Mb.

Software

• VirtualBox: 5.1.22 r115126.
• Host OS: macOS 10.12.4 (16E195).
• Guest OS: Microsoft Windows Server 2016 Standard 10.0.14393 N/A Build 14393 x64.
• Browser: Google Chrome 57.0.2987.133.

Best regards,
Sergey Brunov.

[sbrunov]

Hello, Everyone!

Here is an additional reference:

• Sharing my screen Win8.1 VM VirtualBox causes windows to slow to a crawl. | GoToMeeting Customer Community: ​https://community.gotomeeting.com/gotomeeting/topics/sharing-my-screen-win8-1-vm-virtualbox-causes-windows-to-slow-to-a-crawl.

Best regards,
Sergey Brunov.

[sbrunov]

Hello, Everyone!

It seems the same problem persists with Skype screen sharing.

Skype: 7.35.66.102.

Best regards,
Sergey Brunov.

[Mark Knecht]

OK, I actually haven't had this problem for awhile. I'm not sure what fixed it exactly for Win 7 but try the following if you can determine what's what for your version of Windows:

Control Panel -> System and Security -> System

On the left choose Advanced System Settings which opens a tabbed window called System Properties

Choose the Advanced tab

Choose Performance button

Choose Visual Effects tab

Choose Custom settings

Disable the three Fade effects, two Show Shadow effect and Translucent Selection Rectangle

I know these changes helped with a problem specific to another program. They may have been involved in Go2Meeting also. I don't remember.

Good luck

[sbrunov]

Hello, @LGTrader!

Thank you for the piece of advice.

Have just tried it.
It seems it has not helped: the CPU is still being consumed heavily.

Best regards,
Sergey Brunov.

[MarkD89]

I see this behavior with both Gotomeeting and Webex.

I am running a Windows 7-32 bit guest under a Debian 9 host. Webex is fine to view someone else's screen share but if I try to share the one in the VM, I get the behavior listed. I am using Vbox 5.2.0

I suspect there is a conflict between the virtual video card in the guest and the way that Gotomeeting and Webex try to scrape the screen.

The other people in my meeting do see the screen I share but the results are very choppy with many hangs to the point that it's not usable. This gives me some hope that since it's not completely borked that there may be a fix some day.