From alexander.rudnev at oracle.com Tue Jan 18 17:16:05 2022 From: alexander.rudnev at oracle.com (Alexander Rudnev) Date: Tue, 18 Jan 2022 20:16:05 +0300 Subject: [vbox-dev] Announcement: VirtualBox 6.1.32 released Message-ID: <04d8c731-ed98-78ee-6258-1ca0b7087655@oracle.com> Hello, Today Oracle released VirtualBox 6.1.32, a maintenance release of VirtualBox 6.1 which improves stability and fixes regressions. See the change log at https://www.virtualbox.org/wiki/Changelog for a list of changes. From martin.fleisz at thincast.com Thu Jan 20 10:09:32 2022 From: martin.fleisz at thincast.com (Martin Fleisz) Date: Thu, 20 Jan 2022 11:09:32 +0100 Subject: [vbox-dev] Issue building latest OSE source on Windows Message-ID: <9c98dc72-b262-da26-d661-af6c4a7b26e5@thincast.com> Hi there, I just updated to the latest OSE source code (r93349) but I can't get it to compile on Windows. I receive following error: Build x86 additions C:/kBuild/kBuild/footer-inherit-uses-tools.kmk:1012: *** kBuild: Cannot find include file for the SDK 'WINPSDK71-INCS'! Searched:? C:/kBuild/kBuild/sdks .? Stop. I checked in the kbuild folder (also updated to r3541) and I see a WINPSDK71INCS.kmk there. Renaming the file to WINPSDK71-INCS.kmk fixes the issue above but soon after compilation fails with tons of compiling errors in the Windows 10 SDK headers. The last version that did compile for me was r92744 Any help is highly appreciated! Thanks, Martin From al4321 at gmail.com Thu Jan 20 19:02:41 2022 From: al4321 at gmail.com (Alexey Eromenko) Date: Thu, 20 Jan 2022 21:02:41 +0200 Subject: [vbox-dev] Announcement: VirtualBox 6.1.32 released In-Reply-To: <04d8c731-ed98-78ee-6258-1ca0b7087655@oracle.com> References: <04d8c731-ed98-78ee-6258-1ca0b7087655@oracle.com> Message-ID: Thanks. I need some kind of non-hardened build for Windows. I have a strange problem on my Windows 7 PC, where ALL hardened builds fail to run. On Tue, Jan 18, 2022 at 7:17 PM Alexander Rudnev wrote: > > Hello, > > Today Oracle released VirtualBox 6.1.32, a maintenance release of > VirtualBox 6.1 which improves stability and fixes regressions. > > See the change log at > > https://www.virtualbox.org/wiki/Changelog > > for a list of changes. > _______________________________________________ > vbox-dev mailing list > vbox-dev at virtualbox.org > https://www.virtualbox.org/mailman/listinfo/vbox-dev -- -Alexey Eromenko "Technologov" From robert at dakota.org Tue Jan 25 04:57:22 2022 From: robert at dakota.org (Robert Nielsen) Date: Mon, 24 Jan 2022 20:57:22 -0800 Subject: [vbox-dev] Introducing Vaark Message-ID: Dear VirtualBox developers... The Vaark maintainers are happy to announce Vaark?s first public pre-release (version 0.9.0) at https://vaark.org/ *Thanks! *to all of you who have provided early feedback. *In a Nutshell ? *We like to call Vaark ?*The Missing Command Line Interface for VirtualBox*? but it?s also ?*The Missing Build System for VirtualBox clusters.*? *Reproducible Builds ? *Vaark lets you quickly build *and reproducibly re-build *and configure any modern Linux distros. You can define your VM or a whole cluster of VMs with a very expressive ?project file? declaring as many VMs, networks, and drives as you need to develop your project. *Minimal Rebuilds **? *Internally, Vaark uses *make*, so in a complex project, it rebuilds only the VMs that are absolutely necessary based on your configuration changes. *Fast Cloning **? *Vaark is amazingly fast ? with Vaark, you can often rebuild an entire VMs from scratch in 20-30 seconds. It can even build multiple VMs in parallel when building or rebuilding a project. *Simple Implementation **? *Vaark is written entirely in bash, making it easy to use simple scripting to do almost all system configuration operations. *Secure **? *Vaark itself runs entirely in user space on the host ? you don?t need sudo or an admin password to install and use it. *Extensible **? *Vaark has a simple but powerful ?hooks? approach giving you several different ways to configure the build process for a VM. You can either script the configuration yourself, or you should also be able apply any standard configuration tool such as chef, puppet, ansible, etc. Vaark also provides runtime integrations for configuration scripts written in python, perl, ruby, and really, any language that can parse JSON. *Quick to Try **? *Especially if you already have VirtualBox installed, you can build your first VM very quickly. *Lots of Cool Examples **? *Have a look at some small-to-large example projects to get ideas for how you might use it: https://gitlab.com/robertnielsen/vaark/-/tree/master/examples *Free, Open Source **? *Check out our project at https://gitlab.com/robertnielsen/vaark *Open to Contributors * *? *Think you can help? We?d love to hear from you. *Ready for Feedback * *? *Questions or bug reports? Please email robert at dakota.org Enjoy! Robert Vaark lead engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaus.espenlaub at oracle.com Thu Jan 27 15:41:06 2022 From: klaus.espenlaub at oracle.com (Klaus Espenlaub) Date: Thu, 27 Jan 2022 16:41:06 +0100 Subject: [vbox-dev] Issue building latest OSE source on Windows In-Reply-To: <9c98dc72-b262-da26-d661-af6c4a7b26e5@thincast.com> References: <9c98dc72-b262-da26-d661-af6c4a7b26e5@thincast.com> Message-ID: <17a3ba90-a7e9-c92b-1ef5-3f13dfc1fb94@oracle.com> Hi Martin, On 2022-01-20 11:09, Martin Fleisz wrote: > Hi there, > > I just updated to the latest OSE source code (r93349) but I can't get it > to compile on Windows. I receive following error: > > Build x86 additions > C:/kBuild/kBuild/footer-inherit-uses-tools.kmk:1012: *** kBuild: Cannot > find include file for the SDK 'WINPSDK71-INCS'! Searched: > C:/kBuild/kBuild/sdks .? Stop. Yes, sorry about that. Known issue. We're currently working on updating the build tools and SDKs for Windows, and so far we didn't find time to adapt the OSE build. Suspect it'll need a mix of adapting the configure.vbs script and (hopefully not that much) updating the list of build prerequisites. > I checked in the kbuild folder (also updated to r3541) and I see a > WINPSDK71INCS.kmk there. Renaming the file to WINPSDK71-INCS.kmk fixes > the issue above but soon after compilation fails with tons of compiling > errors in the Windows 10 SDK headers. This is old stuff, getting phased out. Unlikely that it'll be possible to get it working again. I think few people will miss the eliminated "old (P)SDK" requirement in the list of prerequisites. > The last version that did compile for me was r92744 Suspect you mean that you were not trying to build anything between this repository state and the current one... pretty sure that revisions in between would build just fine, but that's not really the point. The latest code should be buildable for everyone. Hope we'll get there within less than a week... Klaus > Any help is highly appreciated! > > Thanks, Martin From klaus.espenlaub at oracle.com Thu Jan 27 19:18:42 2022 From: klaus.espenlaub at oracle.com (Klaus Espenlaub) Date: Thu, 27 Jan 2022 20:18:42 +0100 Subject: [vbox-dev] Issue building latest OSE source on Windows In-Reply-To: <17a3ba90-a7e9-c92b-1ef5-3f13dfc1fb94@oracle.com> References: <9c98dc72-b262-da26-d661-af6c4a7b26e5@thincast.com> <17a3ba90-a7e9-c92b-1ef5-3f13dfc1fb94@oracle.com> Message-ID: turned out to be along the expected lines... configure.vbs needed a now obsolete functionality removed (dealing with the old Platform SDK, option --with-sdk is now ignored but of course for clarity it's best to remove it entirely). This is the problem you ran into, and your attempt was in the totally wrong direction. Also the build prerequisites needed some touch-ups. For building trunk the shopping list is now a lot less unusual (and doesn't need visiting the museum as much): Visual Studio 2019 Version 16.11 is now the recommended compiler, and the Windows 11 SDK and Windows 11 WDK will get you rather far. Hope you'll have more luck with r93465. For me it builds again. Klaus On 2022-01-27 16:41, Klaus Espenlaub wrote: > Hi Martin, > > On 2022-01-20 11:09, Martin Fleisz wrote: >> Hi there, >> >> I just updated to the latest OSE source code (r93349) but I can't get it >> to compile on Windows. I receive following error: >> >> Build x86 additions >> C:/kBuild/kBuild/footer-inherit-uses-tools.kmk:1012: *** kBuild: Cannot >> find include file for the SDK 'WINPSDK71-INCS'! Searched: >> C:/kBuild/kBuild/sdks .? Stop. > > Yes, sorry about that. Known issue. We're currently working on updating > the build tools and SDKs for Windows, and so far we didn't find time to > adapt the OSE build. > > Suspect it'll need a mix of adapting the configure.vbs script and > (hopefully not that much) updating the list of build prerequisites. > >> I checked in the kbuild folder (also updated to r3541) and I see a >> WINPSDK71INCS.kmk there. Renaming the file to WINPSDK71-INCS.kmk fixes >> the issue above but soon after compilation fails with tons of compiling >> errors in the Windows 10 SDK headers. > > This is old stuff, getting phased out. Unlikely that it'll be possible > to get it working again. I think few people will miss the eliminated > "old (P)SDK" requirement in the list of prerequisites. > >> The last version that did compile for me was r92744 > > Suspect you mean that you were not trying to build anything between this > repository state and the current one... pretty sure that revisions in > between would build just fine, but that's not really the point. The > latest code should be buildable for everyone. > > Hope we'll get there within less than a week... > > Klaus > >> Any help is highly appreciated! >> >> Thanks, Martin From al4321 at gmail.com Sat Jan 29 05:53:22 2022 From: al4321 at gmail.com (Alexey Eromenko) Date: Sat, 29 Jan 2022 07:53:22 +0200 Subject: [vbox-dev] Please produce a non-hardened build for Windows Message-ID: on my system, Windows 7, for some reason all the hardened builds fail to run. Latest that is known to run is VirtualBox 4.1.6, from a decade ago. Because it is non-hardened. And let's try to debug the actual issue with hardening too (harded build with extra-debug-logs) -- -Alexey Eromenko "Technologov" From al4321 at gmail.com Sat Jan 29 05:53:59 2022 From: al4321 at gmail.com (Alexey Eromenko) Date: Sat, 29 Jan 2022 07:53:59 +0200 Subject: [vbox-dev] Please produce a non-hardened build for Windows In-Reply-To: References: Message-ID: NOTE: This problem only occur with Windows 7 + large SSDs, 8 TB each. On Sat, Jan 29, 2022 at 7:53 AM Alexey Eromenko wrote: > > on my system, Windows 7, for some reason all the hardened builds fail to run. > > Latest that is known to run is VirtualBox 4.1.6, from a decade ago. > Because it is non-hardened. > > And let's try to debug the actual issue with hardening too (harded > build with extra-debug-logs) > -- > -Alexey Eromenko "Technologov" -- -Alexey Eromenko "Technologov" From martin.fleisz at thincast.com Mon Jan 31 08:37:45 2022 From: martin.fleisz at thincast.com (Martin Fleisz) Date: Mon, 31 Jan 2022 09:37:45 +0100 Subject: [vbox-dev] Issue building latest OSE source on Windows In-Reply-To: References: <9c98dc72-b262-da26-d661-af6c4a7b26e5@thincast.com> <17a3ba90-a7e9-c92b-1ef5-3f13dfc1fb94@oracle.com> Message-ID: Hi Klaus! Thank a lot for looking into this issue - I can confirm r93465 works perfectly fine again :-) Thanks also for the heads up on the updated toolchain - good to see the build system can finally be upgraded to some recent build tool versions! Cheers, Martin On 27.01.2022 20:18, Klaus Espenlaub wrote: > turned out to be along the expected lines... > > configure.vbs needed a now obsolete functionality removed (dealing > with the old Platform SDK, option --with-sdk is now ignored but of > course for clarity it's best to remove it entirely). This is the > problem you ran into, and your attempt was in the totally wrong > direction. > > Also the build prerequisites needed some touch-ups. For building trunk > the shopping list is now a lot less unusual (and doesn't need visiting > the museum as much): Visual Studio 2019 Version 16.11 is now the > recommended compiler, and the Windows 11 SDK and Windows 11 WDK will > get you rather far. > > Hope you'll have more luck with r93465. For me it builds again. > > Klaus > > On 2022-01-27 16:41, Klaus Espenlaub wrote: >> Hi Martin, >> >> On 2022-01-20 11:09, Martin Fleisz wrote: >>> Hi there, >>> >>> I just updated to the latest OSE source code (r93349) but I can't >>> get it >>> to compile on Windows. I receive following error: >>> >>> Build x86 additions >>> C:/kBuild/kBuild/footer-inherit-uses-tools.kmk:1012: *** kBuild: Cannot >>> find include file for the SDK 'WINPSDK71-INCS'! Searched: >>> C:/kBuild/kBuild/sdks .? Stop. >> >> Yes, sorry about that. Known issue. We're currently working on >> updating the build tools and SDKs for Windows, and so far we didn't >> find time to adapt the OSE build. >> >> Suspect it'll need a mix of adapting the configure.vbs script and >> (hopefully not that much) updating the list of build prerequisites. >> >>> I checked in the kbuild folder (also updated to r3541) and I see a >>> WINPSDK71INCS.kmk there. Renaming the file to WINPSDK71-INCS.kmk fixes >>> the issue above but soon after compilation fails with tons of compiling >>> errors in the Windows 10 SDK headers. >> >> This is old stuff, getting phased out. Unlikely that it'll be >> possible to get it working again. I think few people will miss the >> eliminated "old (P)SDK" requirement in the list of prerequisites. >> >>> The last version that did compile for me was r92744 >> >> Suspect you mean that you were not trying to build anything between >> this repository state and the current one... pretty sure that >> revisions in between would build just fine, but that's not really the >> point. The latest code should be buildable for everyone. >> >> Hope we'll get there within less than a week... >> >> Klaus >> >>> Any help is highly appreciated! >>> >>> Thanks, Martin > _______________________________________________ > vbox-dev mailing list > vbox-dev at virtualbox.org > https://www.virtualbox.org/mailman/listinfo/vbox-dev -- Martin Fleisz, Development Manager Thincast Technologies GmbH Tel: +43-720-699 844-70 Bahnhofplatz 7/3 Fax: +43-2236-328 311 2340 Moedling, Austria http://www.thincast.com From klaus.espenlaub at oracle.com Mon Jan 31 16:58:11 2022 From: klaus.espenlaub at oracle.com (Klaus Espenlaub) Date: Mon, 31 Jan 2022 17:58:11 +0100 Subject: [vbox-dev] Please produce a non-hardened build for Windows In-Reply-To: References: Message-ID: <80e1d6e3-ee13-e2ff-c5f1-f9d990478e40@oracle.com> Hello Alexey, if you expect to get an Oracle signed non-hardened build: forget it. This would be the dream of people creating malware. Working on the hardening issue could be the right way to go. Any place we can get a log file showing the failure? Wondering if it's worth the effort, given that Windows 7 is out of support for 2 years now. Using an OS with known (and even more unknown) unfixed security issues as the host OS for running VMs doesn't sound like a good idea to me. No matter what cool hardware you're using with it. Klaus On 2022-01-29 06:53, Alexey Eromenko wrote: > NOTE: This problem only occur with Windows 7 + large SSDs, 8 TB each. > > On Sat, Jan 29, 2022 at 7:53 AM Alexey Eromenko wrote: >> >> on my system, Windows 7, for some reason all the hardened builds fail to run. >> >> Latest that is known to run is VirtualBox 4.1.6, from a decade ago. >> Because it is non-hardened. >> >> And let's try to debug the actual issue with hardening too (harded >> build with extra-debug-logs) >> -- >> -Alexey Eromenko "Technologov" From alexander.rudnev at oracle.com Mon Jan 31 17:15:48 2022 From: alexander.rudnev at oracle.com (Alexander Rudnev) Date: Mon, 31 Jan 2022 20:15:48 +0300 Subject: [vbox-dev] Please produce a non-hardened build for Windows In-Reply-To: <80e1d6e3-ee13-e2ff-c5f1-f9d990478e40@oracle.com> References: <80e1d6e3-ee13-e2ff-c5f1-f9d990478e40@oracle.com> Message-ID: <97c3a44e-4834-0944-5919-5bdc343c2521@oracle.com> Hi Alexey, the alternative solution is to privately build VirtualBox without hardening. You can do it using sources from https://www.virtualbox.org/browser/trunk Build instructions: https://www.virtualbox.org/wiki/Build_instructions On 31/01/2022 19:58, Klaus Espenlaub wrote: > Hello Alexey, > > if you expect to get an Oracle signed non-hardened build: forget it. > This would be the dream of people creating malware. > > Working on the hardening issue could be the right way to go. Any place > we can get a log file showing the failure? > > Wondering if it's worth the effort, given that Windows 7 is out of > support for 2 years now. Using an OS with known (and even more unknown) > unfixed security issues as the host OS for running VMs doesn't sound > like a good idea to me. No matter what cool hardware you're using with it. > > Klaus > > On 2022-01-29 06:53, Alexey Eromenko wrote: >> NOTE: This problem only occur with Windows 7 + large SSDs, 8 TB each. >> >> On Sat, Jan 29, 2022 at 7:53 AM Alexey Eromenko wrote: >>> >>> on my system, Windows 7, for some reason all the hardened builds fail >>> to run. >>> >>> Latest that is known to run is VirtualBox 4.1.6, from a decade ago. >>> Because it is non-hardened. >>> >>> And let's try to debug the actual issue with hardening too (harded >>> build with extra-debug-logs) >>> -- >>> -Alexey Eromenko "Technologov" > _______________________________________________ > vbox-dev mailing list > vbox-dev at virtualbox.org > https://www.virtualbox.org/mailman/listinfo/vbox-dev -- Alexander Rudnev | VirtualBox | work +7 (812) 334 60 01 | cell +7 (921) 951 82 04 Oracle Development SPB Chkalovsky pr. 50, Saint-Petersburg, 197136, Russia