Alexey,
On 08.06.2015 16:04, Alexey Eromenko wrote:
>>> 2. Compatibility with Oracle VirtualBox is unstable: I defined new VM
>>> types for Red Hat guests, like RHEL7_64, which Oracle VirtualBox fails
>>> to understand and renders RHEL VMs inaccessible.
>>
>> It also changes the API (and forgets t
Hi,
On Friday 05 June 2015 08:38:14 Moez Roy wrote:
> It doesn't matter if the kernel modules cannot be compiled with PIC,
> right? Because the kernel modules are compiled using DKMS when you
> install VBox. So then why is there a -fno-PIC in various locations in
> the Config.kmk file?
>
> Why is
Hi,
I wrote a VBox host-service for my company (since 2 years) using the HGCM API
to do data exchange (1K-64K size) between host/guest. We have chosen HGCM since
it's the only host/guest API provided so far and we don't wanna do changes with
later VBox versions. (Note: data exchange via netw
>> 2. Compatibility with Oracle VirtualBox is unstable: I defined new VM
>> types for Red Hat guests, like RHEL7_64, which Oracle VirtualBox fails
>> to understand and renders RHEL VMs inaccessible.
>
> It also changes the API (and forgets to change the UUID of IMachine,
> which means that compiled
All,
On 06.05.2015 22:17, Alexey Eromenko wrote:
> 0. Unattended core functionality itself *is* stable.
>
> What isn't stable:
> 1. Installer needs work; For now installing unattended templates is a
> manual task.
> I couldn't figure out how Oracle kmk Makefile system works.
> Is there any documen
Ian,
On 01.06.2015 08:54, Ian Chapman wrote:
> Hi Devs,
>
> I believe there's a few API bugs (via the web service interface) which
> have existed for a while, which I could probably demonstate by writing
> some test code in Perl.
Hmmm... the Perl interface to the web service API is extremely limi
