Custom Query (16363 matches)
Results (340 - 342 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #20572 | fixed | vboxmanage documentation bug | ||
| Description |
Command vboxmanage.exe export no longer support option --iso but this option is still mented in command help (and possibly in web documentation - I am not check this). |
|||
| #20567 | fixed | Linux 5.14 Host & Guest - vboxsf intermittant guest addition build failures | ||
| Description |
Per the bug-request from thread: Re: [VBox-users] [External] : Linux 5.14 with Testbuild 6.1.x revision 146688 - no vboxsf? After installing testbuild revision 146688 and updating to Linux 5.14 on Archlinux and after updating the kernel on the Archlinux guest as well, the guest shared folders were not present and the following error was received: /usr/bin/mount.vboxsf: mounting failed with error: No such device As explained in the thread, Archlinux also updated dkms (2.8.5-1 -> 2.8.6-1) along with this kernel update. (there were dkms problems with it not removing old virtualbox driver directories for versions that were no longer present) A couple of days later dkms was updated to 2.8.6-2 and another kernel update was applied. After the kernel update, dkms ran and updated all modules on the host. Then after applying the kernel update on the guest, rebuilding the guest addition modules and restarting, the shared-folders were working and all appeared well. At that point I chocked the problems up to the flaky dkms behavior -- but that apparently wasn't the total story. A second server with the same host/guest config was updated directly to Linux 5.14.3 with dkms 2.8.6-2 present - and the shared-folder problem appeared on the second server -- but this time the vboxsf device was found -- only the shared folder was empty on access. Per the request in the thread, I preserved dmesg and vboxadd-setup.log from the guest in the state where the shared-folders were empty (attached as after_5.14.3.tar.bz2) In the interim, Archlinux updated to Linux 5.14.5 and updating both host and guest on the second server succeeded (same files from that update are attached as after_5.14.5.tar.bz2) What looks to have happened to the second server, even though it updated to what was a good setup with testbuild revision 146688 on the first server, was an autoconf error along with an error on struct iov_iter preventing the guest addition build from completing. The error (included in the vboxadd-setup.log) was echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
...
/tmp/vbox.0/regops.c: In function ‘vbsf_iter_lock_pages’:
/tmp/vbox.0/regops.c:2129:15: error: ‘struct iov_iter’ has no member named ‘type’
2129 | if (!(iter->type & ITER_KVEC)) {
| ^~
/tmp/vbox.0/regops.c: In function ‘vbsf_iter_max_span_of_pages’:
/tmp/vbox.0/regops.c:2376:37: error: ‘struct iov_iter’ has no member named ‘type’
2376 | if (iter_is_iovec(iter) || (iter->type & ITER_KVEC)) {
| ^~
/tmp/vbox.0/regops.c:2439:28: error: ‘struct iov_iter’ has no member named ‘type’
2439 | size_t cSegs = iter->type & ITER_BVEC ? RT_MAX(1, iter->nr_segs) : 1;
| ^~
/tmp/vbox.0/regops.c: At top level:
/tmp/vbox.0/regops.c:3796:23: error: ‘simple_write_end’ undeclared here (not in a function); did you mean ‘simple_write_begin’?
3796 | .write_end = simple_write_end,
| ^~~~~~~~~~~~~~~~
| simple_write_begin
make[2]: *** [scripts/Makefile.build:271: /tmp/vbox.0/regops.o] Error 1
This was odd because the exact same packages had been used on the first server and there the guest additions build on 5.14.3. On update of the second server to 5.15.5, this error was not triggered and the guest additions built successfully. Bottom line, I can't tell if this is an intermittent problem with the current guest additions build or some strange set of issues that effected server 1 and server 2 in slightly different ways both causing the loss of shared folders. Both of these servers have run Virtualbox since version 4.X and have both been updated though 5.X and now 6.X, so they have gone through the update process some 50+ times and this was an odd set up issues affecting the guest addition shared-folder update. All is working now, but after explaining this on vbox-users list there was a request that I open this bug so a more careful look can be had. Let me know if you need any additional information. |
|||
| #20565 | duplicate | VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension | ||
| Description |
hi Team, While importing the OVA file into Virtual box, an error in being popped up with "VBOX_E_FILE_ERROR (0x80BB0004):Disk has no extension" I already verified, of having the disk with its proper extensions in .ovf file. But still having the issues whereas when I import the same ova file in VMware, it did worked at its pace and can start the VM. Please help on this asap ? |
|||

