Hello,
This is with FreeBSD 10-CURRENT, SVN revision r255948 with ports as r328930
(all around 1st of October) on i386 architecture;
making emulators/virtualbox-ose gives:
# make install clean BATCH=yes USE_GCC=any
...
kBuild: Pass - Build Programs
kBuild: Pass - Libraries
kBuild: Pass - DLLs
k
Hello,
On 15/11/13 04:30, magicdmer wrote:
> I read the codes of UIMouseHandler.cpp and find this function :
> void UIMouseHandler::releaseMouse()
> It can release the mouse from guest os
>
> But I look up the VirtualBox SDK help ,can't find any reference functions
> about releaseMouse .
>
> Can s
I read the codes of UIMouseHandler.cpp and find this function :
void UIMouseHandler::releaseMouse()
It can release the mouse from guest os
But I look up the VirtualBox SDK help ,can't find any reference functions
about releaseMouse .
Can someone help me?
__
On 13-11-14 04:38 AM, Klaus Espenlaub wrote:
The chipset isn't relevant, but any VM which needs to be teleported
across CPU types has to be configured properly, limiting the CPUID
features to a compatible subset of both CPUs*before* starting the VM on
the original system.
If that's done properl
I've fixed the bug in SVN. Should be part of the next maintenance
release of VirtualBox 4.3 branch.
Thanks & Regards,
Ram.
On 11/12/2013 09:06 PM, Konrad Kuźmiński wrote:
Hi,
I agree that your approach seems to be better. I played around with
the patch and it solves the problem. I share your
Hi Geoff,
On 12.11.2013 20:14, Geoff Nordli wrote:
>
> Any thoughts on how teleporting works across different chipsets/cpu types?
The chipset isn't relevant, but any VM which needs to be teleported
across CPU types has to be configured properly, limiting the CPUID
features to a compatible subse
