Re: [vbox-dev] "Disgruntled Security Researcher Publishes Major VirtualBox 0-Day Exploit"

Hi, According to the same researcher, Virtualbox 5.2.22 fixes the vulnerability: https://github.com/MorteNoir1/virtualbox_e1000_0day/issues/12 Regards, Mihai On Sat, 10 Nov 2018, 23:26 Stéphane Charette This just hit Slashdot: "According to a text file uploaded on GitHub, > Saint

Re: [vbox-dev] How to populate a Linux VM with the items requested by a dmidecode -t 17

Hi, Why is it necessary for the guest? Run this command and see if it does what you want: VBoxManage setextradata "VM name" VBoxInternal/Devices/pcbios/0/Config/DmiExposeMemoryTable 1 Source: www.virtualbox.org/ticket/12017?cversion=0_hist=1#comment:5 Regards, Mihai On Fri, 9 Nov 2018 at

Re: [vbox-dev] getting object name in VirtualBox gui

nough (see > the comment about the possibility to go for the separate UI option). > > Your help is much appreciated in this thread. > > Klaus > > On 26.09.2018 19:10, Mihai Hanor wrote: > > Hi, > > There's a difference between the VirtualBox Manager window and the V

Re: [vbox-dev] getting object name in VirtualBox gui

On Wed, Sep 26, 2018 at 3:24 PM Klaus Espenlaub wrote: > Hi Mihai, > > On 25.09.2018 20:21, Mihai Hanor wrote: > > Hi Klaus, > > When you say that the devs have been working on it, are you referring to > the 5.2.18 release build, the testing builds or the svn? I've build tod

Re: [vbox-dev] getting object name in VirtualBox gui

process" option which VirtualBox has already. Would bring some minor > feature losses, but if that would bring back full accessibility I can see a > good justification for spending the necessary time. > > Klaus > > On 25.09.2018 19:26, Mihai Hanor wrote: > > Hell

Re: [vbox-dev] getting object name in VirtualBox gui

made a move to separate the VM process, but I'm don't know to what end. The frontend still runs in a hardened process. Regards, Mihai Hanor On Fri, Sep 21, 2018 at 12:30 PM Илья Пащук wrote: > helo. > > > I'm a nvda (nvaccess.org) screenreader addon developer > > I need the way

[vbox-dev] sanity check for VBOX_ONLY_ADDITIONS

Hello, Please add a sanity check in Config.kmk for the case VBOX_ONLY_ADDITIONS=1 && !defined(VBOX_WITH_ADDITIONS). In this case, building the additions starts, but fails at some point due to missing dependencies. Regards, Mihai ___ vbox-dev mailing

Re: [vbox-dev] VirtualBox official debug builds/debug symbols

e using a debug version. > That said, you can also build your own release version. Building with > "VBOX_WITHOUT_HARDENING=1" set will probably make you happier either way. > > Regards > Michael > > 10.04.2018 22:35, Mihai Hanor wrote: > > Hi Samuel, > > >

Re: [vbox-dev] VirtualBox official debug builds/debug symbols

Hi Samuel, The VirtualBox debug build is not for regular usage. The debug build runs unoptimized code and some of its code paths may differ from a release build. This includes debug assertions, that will stop your VM or even the host OS without warning, if they trigger. On Windows, at least, an

[vbox-dev] Răspuns: configure.vbs missing

Hello, Either your VirtualBox source repository is incomplete, or you're not looking in the right place. The configure.vbs file resides in the root source path. Best regards,Mihai De la: "yug...@telincn.com" Către: vbox-dev Trimis:

Re: [vbox-dev] Build on Windows: Sanity test failed

g++.exe is probably not found. Check the path. ___ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev

Re: [vbox-dev] Working build environment for VBox windows?

Hello, You misread my comment, CrTdBltDataCleanup(pTex) is to be called right after CrTdBltDataRelease(pTex) -- Mihai From: Minhae Lee fluffyter...@gmail.com To: vbox-dev@virtualbox.org Sent: Tuesday, May 12, 2015 6:25 AM Subject: [vbox-dev] Working build environment for VBox windows?

[vbox-dev] VBoxVideoW8 null pointer dereference (test build)

Hello, I want to report an issue I have encountered with the latest test build, VirtualBox-4.3.21-97963-Win. The host OS is Windows 8.1 x64, so is the guest. I can reproduce the issue with the 4.3.21-97963, 4.3.20-96996 and 4.3.21-97986 Guest Additions. It doesn't seem to happen when running

Re: [vbox-dev] Call for testing, second try (Linux and Solaris Guest Additions)

Using the previous guest additions (such as 4.3.21-97052 and older), my Ubuntu 14.04 VMs retained the resolution even at login screen (though no resizing was possible), which was a nice thing. This doesn't happen with the test guest additions. The VM starts with a fixed resolution (1024x768 in

[vbox-dev] uninitialized variables

Hello, Looking at src\VBox\Main\src-server\win\HostDnsServiceWin.cpp The HostDnsServiceWin::updateInfo() function should initialize the variables abDomain, abNameServers, abSearchList. I was trying to understand why VboxSVC crashes at startup (stack corruption), with a recent SVN

Re: [vbox-dev] bad address causes host DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

Are my explanations wrong? However, the BSOD is real. --- On Sun, 12/16/12, Mihai Hanor mha...@yahoo.com wrote: From: Mihai Hanor mha...@yahoo.com Subject: bad address causes host DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD To: vbox-dev@virtualbox.org Date: Sunday, December 16, 2012, 11:25 AM Hello

[vbox-dev] bad address causes host DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD

Hello, I can reproduce a DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD on my host (Windows 7 64 bit SP1), using a debug build of VirtualBox svn44137, while a guest is booting (Windows 7 64 bit SP1, unpatched, 2 CPUs). It is caused by the code line: VMMR0!pgmPhysAllocLargePage

Re: [vbox-dev] VM Memory space: region in BIOS - patching/override possible?

You can download the VirtualBox source and check the \src\VBox\Devices\PC\BIOS\rombios.c file. The lines you're interested in start with .org 0xfff0 (the far jump), .org 0xfff5 (the bios date) and .org 0xfffe (the system model id) - without the quotes. After modifying what you need, compile

Re: [vbox-dev] latest svn build failure on Windows

The fix was suggested by someone else, last year, on december, after I've tried to get it to work with __pragma and type casting. But I'm not using it, because it offsets the lines. I'm still commenting out VBOX_VCC_WERR ?= -WX --- On Thu, 2/3/11, Huihong Luo huisi...@yahoo.com wrote: From:

[vbox-dev] an assert that requires a small fix

Hello, vbox\src\VBox\Main\src-all\eventimpl.cpp The iterator used at line 901: Assert(pit-second = 0); is invalid if we previously executed the erase map method, included by the if branch: mOwner-m-mPendingMap.erase(pit); // line 898 With page heap enabled, it always complains

[vbox-dev] small correction for one Makefile.kmk script

Hello. A small issue (svn changeset 30537): src\VBox\HostDrivers\Support\Makefile.kmk line 158: SUPR0IdcClient_SDKS.win = W2K3DDK WINPSDKINCS It should be: SUPR0IdcClient_SDKS.win = $(VBOX_WINDDK) WINPSDKINCS Otherwise, the compilation process stops because of bad DDK path passed to cl.exe.