I've updated the app-emulation/virtualbox package to version 6.1.34-r4 and all my virtual machines stopped starting correctly. This message would show up in the logs: 00:00:00.390233 AssertLogRel /var/tmp/portage/app-emulation/virtualbox-6.1.34-r4/work/VirtualBox-6.1.34/src/VBox/Main/src-client/ConsoleImpl2.cpp(912) int Console::i_configConstructorInner(PUVM, PVM, util::AutoWriteLock*): !FAILED(hrc) If I revert to version 6.1.34-r1 everything works fine. Reproducible: Always I'm on kernel version 5.15.41 built from gentoo-sources. SecureBoot is enabled and VirtualBox modules are signed using the same key as the kernel; I'm unsure if this matters but it might be worth mentioning it.
Thanks. Do you get any other logs?
COuld you also share: 1. emerge --info 2. Confirm whether downgrading suddenly makes it work again? Or not?
Created attachment 790499 [details] `emerge --info` output
(In reply to Sam James from comment #1) > Thanks. Do you get any other logs? No, nothing else comes up in VirtualBox logs, when comparing with a successful run that line is the only difference between the two. I can attach the full logs if necessary. (In reply to Sam James from comment #2) > COuld you also share: > 1. emerge --info > 2. Confirm whether downgrading suddenly makes it work again? Or not? Yes, downgrading makes everything work again just fine.
I am experiencing the same issue with virtualbox-6.1.34-r5. Reverting to 6.1.34-r1 resolved the issue. What's changed between the two? 00:00:00.951137 VMSetError: /var/tmp/portage/app-emulation/virtualbox-6.1.34-r5/work/VirtualBox-6.1.34/src/VBox/VMM/VMMR3/VM.cpp(321) int VMR3Create(uint32_t, PCVMM2USERMETHODS, PFNVMATERROR, void*, PFNCFGMCONSTRUCTOR, void*, VM**, UVM**); rc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR 00:00:00.951140 VMSetError: The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. 00:00:00.951461 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={The configuration constructor in main failed due to a COM error. Check the release log of the VM for further details. (VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR)}, preserve=false aResultDetail=-6400 00:00:00.951524 Console: Machine state changed to 'PoweredOff' 00:00:00.999926 Power up failed (vrc=VERR_MAIN_CONFIG_CONSTRUCTOR_COM_ERROR, rc=NS_ERROR_FAILURE (0X80004005))
Created attachment 790502 [details] emerge --info
I gave 6.1.34-r5 a spin and it's also affected.
Same issue here: 6.1.34-r3 and 6.1.34-r5 are broken. The last functional version is 6.1.34-r1.
Good the 6.1.34-r1 still works :) I can confirm that 6.1.34-r5 has VM startup error. Emerged only 6.1.34-r1, and without restarting system - VM starts and works again.
Created attachment 790547 [details] vm error on startup log has some records - ERROR [COM]: aRC=NS_ERROR_INVALID_POINTER
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a91772f80e721b8bad806190a85242beb43ac832 commit a91772f80e721b8bad806190a85242beb43ac832 Author: David Seifert <soap@gentoo.org> AuthorDate: 2022-07-07 16:06:50 +0000 Commit: David Seifert <soap@gentoo.org> CommitDate: 2022-07-07 16:06:50 +0000 profiles: mask broken virtualbox revisions Bug: https://bugs.gentoo.org/856811 Signed-off-by: David Seifert <soap@gentoo.org> profiles/package.mask | 4 ++++ 1 file changed, 4 insertions(+)
(In reply to Alex Buell from comment #5) > I am experiencing the same issue with virtualbox-6.1.34-r5. Reverting to > 6.1.34-r1 resolved the issue. What's changed between the two? The source-level differences between -r1 and -r3, which has been reported as broken, are due to the following. 1) -r3 applies $FILESDIR/virtualbox-6.1.34-no-pam.patch; -r1 doesn't 2) -r3 applies $FILESDIR/virtualbox-6.1.34-r3-python.patch; -r1 doesn't The first of the above-mentioned patches is also applied to -r5.
Further, at the ebuild level, the marked changes between -r1 and -r3 are as follows. 1) the creation of LocalConfig.kmk (referencing bug 843437) 2) the creation of AutoConfig.kmk (referencing bug 856121 and bug 785835)
For either myself or someone else who looks into this more: I'm guessing one of the variables used is either exclusively used for, or at least partly (exclusive vs partly affects the best way to fix it) some object(s)/components that need to be built with some special flags because of their low level nature. It would be helpful if someone could bisect (not in the git sense) which of the changes Kerin listed actually cause the issue.
(In reply to Sam James from comment #14) > For either myself or someone else who looks into this more: I'm guessing one > of the variables used is either exclusively used for, or at least partly > (exclusive vs partly affects the best way to fix it) some > object(s)/components that need to be built with some special flags because > of their low level nature. > > It would be helpful if someone could bisect (not in the git sense) which of > the changes Kerin listed actually cause the issue. Oh, I should add: ceamac, I'd try to just cherry-pick the Python changes, and if they work, put them in a new revision, and then handle the flags later.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=605d086c0214e6ca8fa1ff5b62cc5d5e33a3aa47 commit 605d086c0214e6ca8fa1ff5b62cc5d5e33a3aa47 Author: Viorel Munteanu <ceamac.paragon@gmail.com> AuthorDate: 2022-07-11 08:17:07 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-07-12 03:09:58 +0000 app-emulation/virtualbox: revert QA fix for CFLAGS It causes worse issues (the virtual machines do not start at all) This is an emergency fix, so we can unmask the package Bug: https://bugs.gentoo.org/843437 Closes: https://bugs.gentoo.org/856811 Signed-off-by: Viorel Munteanu <ceamac.paragon@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/26342 Signed-off-by: Sam James <sam@gentoo.org> .../{virtualbox-6.1.34-r5.ebuild => virtualbox-6.1.34-r6.ebuild} | 7 ------- profiles/package.mask | 4 ---- 2 files changed, 11 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6b0dfde061d0197475629f95aa5d575b56c919e8 commit 6b0dfde061d0197475629f95aa5d575b56c919e8 Author: Viorel Munteanu <ceamac.paragon@gmail.com> AuthorDate: 2022-08-10 15:45:43 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-08-13 19:23:14 +0000 app-emulation/virtualbox: filter flags With some combinations of CFLAGS/CXXFLAGS, the VM doesn't start Bug: https://bugs.gentoo.org/856811 Closes: https://bugs.gentoo.org/864274 Signed-off-by: Viorel Munteanu <ceamac.paragon@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/26814 Signed-off-by: Sam James <sam@gentoo.org> .../virtualbox/virtualbox-6.1.36-r1.ebuild | 648 +++++++++++++++++++++ 1 file changed, 648 insertions(+)
