[vbox-dev] compile patch for 5.1.6

2017-08-06 Thread Reinoud Koornstra
Hello Everyone, Currently virtualbox 5.1.6 fails to compile for kernel version 4.9 and up. This is due to a change in get_user_pages api. The ints for write and force have changed to gup_flags. Please find the patch attach to fix this for linux 4.9 and up. Last time I tried to sent it, it wasn't

[vbox-dev] Fwd: Compiling dkms with linux 4.9 and up

2017-08-06 Thread Reinoud Koornstra
Hello Everyone, Currently virtualbox fails to compile for kernel version 4.9 and up. This is due to a change in get_user_pages api. The ints for write and force have changed to gup_flags. Please find the patch attach to fix this for linux 4.9 and up. Thanks, Reinoud. ---

Re: [vbox-dev] [PATCH 2/2] vgdrvLinuxIOCtl: Always return standard Linux errno values

2017-08-06 Thread Knut St. Osmundsen
Hi Hans, I'm with you on this not being entirely optimal. However 'man ioctl' (http://man7.org/linux/man-pages/man2/ioctl.2.html) documents it as sane behavior. So why change working code? As I mentioned, the ideal fix would be to pass the VBox status code back separately in the request

Re: [vbox-dev] [PATCH 2/2] vgdrvLinuxIOCtl: Always return standard Linux errno values

2017-08-06 Thread Hans de Goede
Hi, On 06-08-17 16:15, Knut St. Osmundsen wrote: Hi Hans, if I understand you correctly you suggest converting VBox status codes (currently around 2000) to linux errno.h (a few hundreds) in ring-0 and have ring-3 convert the errno.h back to VBox status codes. Yes that is what I propose.

Re: [vbox-dev] [PATCH 2/2] vgdrvLinuxIOCtl: Always return standard Linux errno values

2017-08-06 Thread Knut St. Osmundsen
Hi Hans, if I understand you correctly you suggest converting VBox status codes (currently around 2000) to linux errno.h (a few hundreds) in ring-0 and have ring-3 convert the errno.h back to VBox status codes. Because the potential information loss, that's not something I would like to do.

Re: [vbox-dev] How to test memory ballloon ?

2017-08-06 Thread Hans de Goede
Hi, On 25-07-17 12:01, Andreas Löffler wrote: Hello Hans, please have a look at the manual, section 4.9.1 "Memory ballooning" and commands like VBoxManage controlvm "VM name" guestmemoryballoon VBoxManage modifyvm "VM name" --guestmemoryballoon There is also a frontend called