> In other words, everything will work perfectly with the 32-bit kernel,
> but not necessarily with the 64-bit kernel since that's not supported.
> Only missing out on the display management (resize host window => change
> guest's resolution) and clipboard sharing in the latter case isn't so
> bad, when we get back file sharing and a greater selection of
> resolutions. Heck, it's probably more secure that way (and host -> guest
> clipboard sharing is a pretty obvious leak)! :)
About the screen resolutions and direction of the clipboard, see also my
last comment on #5730, that I reopened:
https://labs.riseup.net/code/issues/5730#change-20929
>> Even more weird, I tried to start this working VM with that last ISO
>> image and the resizing worked! Then I tried to create another fresh VM
>> from scratch with no disk and started it from that ISO image and the
>> resizing didn't work. I tried to compare the config file for both VMs
>> and didn't find anything relevant.
>
> Probably the "working VM" was 32-bit, and the "fresh VM" was 64-bit.
Yes, that was it.
>> Anyway, I'm absolutely not sure I'll be able to fix that before the
>> freeze. I'd rather concentrate on the documentation upgrades. So if any
>> VirtualBox user want to have a look...
>
> I haven't done a code review yet, but it looks very promising to me so
> expect this to be merged in time for 1.1. Thanks for working on this!
>
> A potential follow-up is how to document the shortcomings. Known issue,
> perhaps?
Ah yes, I should do that so I'm marking them as "Dev needed".
--
sajolida
