Discuss the VirtualBox 7.1.0_BETA2 release here

[FranceBB]

I installed the new development snapshot from September 4th, namely 7.1.0 r164699 with the generic .run file on Fedora 40 x64.
It did complete successfully, but there were a few errors return by the terminal nonetheless.

Code: Select all

[FranceBB@router-localhost ~]$ cd "/home/FranceBB/Downloads/"
[FranceBB@router-localhost Downloads]$ sudo ./VirtualBox-7.1.0_BETA2-164699-Linux_amd64.run
Verifying archive integrity...  100%   MD5 checksums are OK. All good.
Uncompressing VirtualBox for Linux installation  100%  
VirtualBox Version 7.1.0_BETA2 r164699 (2024-09-04T17:13:34Z) installer
Removing previous installation of VirtualBox 7.1.0_BETA2 r164448 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python2.7, installing bindings...
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 1011, in __init__
    self.platform.getVirtualBox()
  File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 747, in getVirtualBox
    return client.virtualBox
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 381, in __getattr__
    return getattr(interface, attr)
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 467, in __getattr__
    return XPTC_InvokeByIndex(self._comobj_, method_index, args)
Exception: 0x80004005 (Failed to load user language instance)
Traceback (most recent call last):
  File "./vboxapisetup.py", line 41, in <module>
    sys.exit(setup.main())
  File "vboxapi/setup.py", line 306, in main
  File "vboxapi/setup.py", line 136, in testVBoxAPI
  File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 1044, in getVirtualBox
    return self.platform.getVirtualBox()
  File "/usr/lib/python2.7/site-packages/vboxapi/__init__.py", line 747, in getVirtualBox
    return client.virtualBox
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 381, in __getattr__
    return getattr(interface, attr)
  File "/opt/VirtualBox/sdk/bindings/xpcom/python/xpcom/client/__init__.py", line 467, in __getattr__
    return XPTC_InvokeByIndex(self._comobj_, method_index, args)
xpcom.Exception: 0x80004005 (Failed to load user language instance)
Python found: python3.6, installing bindings...
Python found: python3.11, installing bindings...
Python found: python3.12, installing bindings...
/tmp/selfgz4506018530/routines.sh: line 408: 48159 Segmentation fault      (core dumped) $SHELL -c "cd ${PYTHON_INSTALLER_PATH} && ${PYTHON_BIN} ./vboxapisetup.py install                    --record $CONFIG_DIR/python-$CONFIG_FILES"

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

You have new mail in /var/spool/mail/FranceBB
[FranceBB@router-localhost Downloads]$ 

[111andre111]

I use the BETA2 version on MacOS Silicon.

I like to use Kickstart configuration with Oracle64.
However it seems I always run into this error:

                  detectedOSTypeId = Oracle_64
                 detectedOSVersion = 8.7.0
                  detectedOSFlavor = 
               detectedOSLanguages = en-US
                   detectedOSHints = 
VBoxManage: info: Waiting for VM '1234' to power on...
VBoxManage: error: VISO: Error setting name '/ks.cfg' on '/.../Unattended-4a94faeb-4de8-409f-8d2b-7a2a622be169-ks.cfg': VERR_ALREADY_EXISTS (VERR_ALREADY_EXISTS).
VBoxManage: error: VD: error VERR_ALREADY_EXISTS opening image file '/.../Unattended-4a94faeb-4de8-409f-8d2b-7a2a622be169-aux-iso.viso' (VERR_ALREADY_EXISTS).
VBoxManage: error: Failed to open image '/.../Unattended-4a94faeb-4de8-409f-8d2b-7a2a622be169-aux-iso.viso' in read-only mode (VERR_ALREADY_EXISTS).
VBoxManage: error: PIIX3 cannot attach drive to the Primary Master (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

I used as a test the meanwhile existing Version 7.1.2 which did even a lesser Job and din't even show up the detection overview but before that stopped with error

VBoxManage: info: Starting unattended installation of RedHat_64 in machine '1234' (4390a59d-9198-4416-a0cd-753ab7ae6d74).
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: "Prepare()" at line 2571 of file VBoxManageMisc.cpp

Any idea what that might be when executing `VBoxManage unattended install`? I am not sure as well if I have any change to fix this.
Note: There is not ISO before that connected, hence I don't understand why the message about PIIX3 cannot attach... Or is that probably a red herring because of the other errors before that?

[klaus]

I use the BETA2 version on MacOS Silicon.

I like to use Kickstart configuration with Oracle64.
[...]

First of all: 7.1.x doesn't officially support guest OSes with CPU architecture amd64 (or x64 or x86-64). Just arm64 (or aarch64) VMs are supported, and for that you need a suitable ISO which will be detected as Oracle_arm64.

Your immediate issue causing the error message is unrelated: you're having trouble with leftover files from a previous unattended setup. Either you didn't delete the previous VM at all or you used the wrong VBoxManage command to delete everything (the GUI had a bug, and left the unattended files behind, this is fixed in 7.1.2).

[111andre111]

Thank you for the answer.
By setting

VBoxInternal2/EnableX86OnArm

it does work smoothely to boot X86 ISO files.

Would be good to know where I would need to remove these files. Ok, in the VM folder there were still some Unattended-... files but removing these didn't solve the issue at all. The update to version 7.1.2 ends up with the error message

VBoxManage: info: Starting unattended installation of Oracle_64 in machine '1234' (66988e8f-a055-446f-89ff-3255490d7eba).
VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: "Prepare()" at line 2571 of file VBoxManageMisc.cpp

like I wrote.

And interestingly when I boot a Redhat_64 based machine it's completely working - no issues at all.
So these errors happen both only with the `Oracle_64` system.

That's where it comes into play I would be curios to know why that might happen and look for a debug possibility.

One thing I realized is that for Beta2 `VBoxManage unattended detect --iso=<isofile>` ends up with this

VBoxManage: error: Code NS_ERROR_NOT_IMPLEMENTED (0x80004001) - Not implemented (extended info not available)
VBoxManage: error: Context: "DetectIsoOS()" at line 2198 of file VBoxManageMisc.cpp
OSTypeId="Oracle_64"
OSVersion="8.7.0"
OSFlavor=""
OSLanguages="en-US"
OSHints=""
IsInstallSupported="on"

however in 7.1.2 it ends up with this

VBoxManage: error: Code NS_ERROR_FAILURE (0x80004005) - Operation failed (extended info not available)
VBoxManage: error: Context: "DetectIsoOS()" at line 2216 of file VBoxManageMisc.cpp
OSTypeId=""
OSVersion=""
OSFlavor=""
OSLanguages=""
OSHints=""
IsInstallSupported="off"

[klaus]

Final 7.1.0 and later only allows unattended installs for the supposedly working guest OSes - which should include amd64 if you have the extradata in place. Odd.

[111andre111]

Unfortunately this command doesn't allow to add `--verbose` or `--debug` flag, while other commands do...
I've tried environment variables VBOX_RELEASE_LOG_DEST, VBOX_RELEASE_LOG and VBOX_RELEASE_LOG_FLAGS, but that didn't seem to do anything as well for `VBoxManage unattended install`.

[111andre111]

Is it possible to get a DEBUG enabled version from Virtualbox? I tried to compile one by myself but seems I don't succeed as I always get on MacOS ARM

Checking for environment: 
  ** Cannot determine system!

when executing `./configure` or `./configure --disable-hardening`...

EDIT:

Meanwhile I found out that right after `VBoxManage unattended install` and running into the issue, I found out that `vboxmanage startvm -E VBOX_RELEASE_LOG="all=~0" <vm>` left a log file.

Maybe that helps to identify what might happen?

VD#0: Cancelling all active requests
DrvVD: Flushes will be ignored
DrvVD: Async flushes will be passed to the disk
VISO: Handling file '/Volumes/.../Aux-aux-iso.viso'
rtFsIsoImport/Rock: Rock Ridge 'ER' entry: v1 id='RRIP_1991A' desc='THE ROCK RIDGE INTERCHANGE PROTOCOL PROVIDES SUPPORT FOR POSIX FILE SYSTEM SEMANTICS' source='PLEASE CONTACT DISC PUBLISHER FOR SPECIFICATION SOURCE.  SEE PUBLISHER IDENTIFIER IN PRIMARY VOLUME DESCRIPTOR FOR CONTACT INFORMATION.'
ISO imported statistics for '/Users/.../1234.iso'
    cAddedNames:                  1 970
    cAddedDirs:                      26
    cbAddedDataBlocks:    5 607 958 528 bytes
    cAddedFiles:                    972
    cAddedSymlinks:                   0
    cBootCatEntries:                  1
    cbSysArea:                        0
    cErrors:                          0
visoOpenWorker: RTFsIsoMakerCmdEx failed: VERR_ALREADY_EXISTS - Error setting name '/ks.cfg' on '/Volumes/.../Aux-ks.cfg': VERR_ALREADY_EXISTS
VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Storage/VISO.cpp(390) int visoOpenWorker(PVISOIMAGE); rc=VERR_ALREADY_EXISTS
VMSetError: VISO: Error setting name '/ks.cfg' on '/Volumes/.../Aux-ks.cfg': VERR_ALREADY_EXISTS
VISO: Handling of file '/Volumes/.../Aux-aux-iso.viso' failed with VERR_ALREADY_EXISTS
VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Storage/VD.cpp(5608) int VDOpen(PVDISK, const char *, const char *, unsigned int, PVDINTERFACE); rc=VERR_ALREADY_EXISTS
VMSetError: VD: error VERR_ALREADY_EXISTS opening image file '/Volumes/.../Aux-aux-iso.viso'
VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Storage/DrvVD.cpp(5339) int drvvdConstruct(PPDMDRVINS, PCFGMNODE, uint32_t); rc=VERR_ALREADY_EXISTS
VMSetError: Failed to open image '/Volumes/.../Aux-aux-iso.viso' in read-only mode
VD: Opening the disk took 6080750 ns
VMSetError: /Users/vbox/tinderbox/mac-rel/src/VBox/Devices/Storage/DevATA.cpp(8292) int ataR3Construct(PPDMDEVINS, int, PCFGMNODE); rc=VERR_ALREADY_EXISTS
VMSetError: PIIX3 cannot attach drive to the Primary Master
PDM: Failed to construct 'piix3ide'/0! VERR_ALREADY_EXISTS (-105) - The object in question already exists.
Display::i_drvDestruct: iInstance=0
GIM: KVM: Resetting MSRs
ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={VISO: Error setting name '/ks.cfg' on '/Volumes/.../Aux-ks.cfg': VERR_ALREADY_EXISTS (VERR_ALREADY_EXISTS).
VD: error VERR_ALREADY_EXISTS opening image file '/Volumes/.../Aux-aux-iso.viso' (VERR_ALREADY_EXISTS).
Failed to open image '/Volumes/.../Aux-aux-iso.viso' in read-only mode (VERR_ALREADY_EXISTS).
PIIX3 cannot attach drive to the Primary Master (VERR_ALREADY_EXISTS)}, preserve=false aResultDetail=-105
Console: Machine state changed to 'PoweredOff'

Important to mention this is a custom Oracle 8.7.0 ISO, but when I am using a normal Oracle ISO https://yum.oracle.com/ISOS/OracleLinux ... 64-dvd.iso then it seems to work. However I'd like to know what might go wrong, but probably that needs to be forked out to another thread?

[klaus]

The error message is actually quite clear: your custom ISO already has a /ks.cfg file.

visoOpenWorker: RTFsIsoMakerCmdEx failed: VERR_ALREADY_EXISTS - Error setting name '/ks.cfg' on '/Volumes/.../Aux-ks.cfg': VERR_ALREADY_EXISTS

The VirtualBox unattended install feature assumes that there is no kickstart configuration because it adds one.

You can either use a "more vanilla" ISO with VirtualBox unattended install or use the ISO as is for booting (and also kickstart file based installing). Not both.

[111andre111]

Ah, you are right from that point of view. Are there any plans to have the possibility to overwrite an existing kickstart file that exists on a bootable medium?
Probably that could be done if there was the possibility to manipulate `inst.ks` kernel parameters of the bootable medium.