virtualbox-4.3.0 has been officially released and is already in portage. So I removed the beta/rc ebuilds from poly-c overlay._________________The manual said "Requires Windows10 or better" so I installed GNU/Linux...

I've upgraded to 4.3.0.
I run Win 7 in it.
When I start Windows 7 I get an error immediately about something missing.
I downgraded to 4.2.18 and things run fine again.
I've upgraded before w/o any problem.
Gerard._________________To install Gentoo I use sysrescuecd.Based on Gentoo,has firefox to browse Gentoo docs and mc to browse (and edit) files.
The same disk can be used for 32 and 64 bit installs.
You can follow the Handbook verbatim.
http://www.sysresccd.org/Download

I am short on time.
I would have to re-upgrade again,sorry.
Gerard._________________To install Gentoo I use sysrescuecd.Based on Gentoo,has firefox to browse Gentoo docs and mc to browse (and edit) files.
The same disk can be used for 32 and 64 bit installs.
You can follow the Handbook verbatim.
http://www.sysresccd.org/Download

Not sure if it's appropriate to post this in this thread, but I'm not sure if this is a bug or a configuration issue on my side. Probably the latter. My compilation of the xf86-video-virtualbox-4.3.0 drivers is failing with this error:

P.S.: I've tried to reproduce your problem in my ~x86 Gentoo VM but the package compiled/installed successfully each time I re-emerged it._________________The manual said "Requires Windows10 or better" so I installed GNU/Linux...

I don't know if this is related but .. I just did an emerge --sync and now Portage wants to downgrade virtualbox-bin-4.2.16 to 4.1.26. I had to make a patched version of virtualbox-modules-4.2.16 to get them to compile properly. I'd prefer to not have to go through that exercise with 4.1.26. Both virtualbox-bin-4.2.16 and virtualbox-modules-4.2.16 are in my package.accept_keywords file. Why am I being forced to downgrade? It seems screwy.

I don't know if this is related but .. I just did an emerge --sync and now Portage wants to downgrade virtualbox-bin-4.2.16 to 4.1.26. I had to make a patched version of virtualbox-modules-4.2.16 to get them to compile properly. I'd prefer to not have to go through that exercise with 4.1.26. Both virtualbox-bin-4.2.16 and virtualbox-modules-4.2.16 are in my package.accept_keywords file. Why am I being forced to downgrade? It seems screwy.

Any suggestions?

Not sure what the relation is to VirtualBox 4.3.0, but okay. 4.2.16 has been removed from tree in favor of 4.2.18. If your patched version was to enable support for Linux 3.11+, that fix is already present in 4.2.18. If you only have 4.2.16 in your package.accept_keywords, then I would expect portage to offer 4.1.26 as the only alternative.