|
Bugzilla – Full Text Bug Listing |
| Summary: | VirtualBox shared folders no longer working in Tumbleweed 20230915 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Ian Laurie <nixuser> |
| Component: | Virtualization:Other | Assignee: | Larry Rainey <llrainey15> |
| Status: | CONFIRMED --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | Larry.Finger, mail, suse.junky |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Journalctl entries from such a "Killed" command run on vboxsf | ||
|
Description
Ian Laurie
2023-09-18 23:34:56 UTC
Created attachment 869593 [details]
Journalctl entries from such a "Killed" command run on vboxsf
I second this bug report. $ findmnt -T . TARGET SOURCE FSTYPE OPTIONS /host/c_drive c_drive vboxsf rw,nodev,relatime,iocharset=utf8,uid=717,gid=100,dmode=0700,fmode=0700,dmask=077,fmask=077 $ echo hello | dd of=x status=none $ ls -log x -rwx------ 1 6 Sep 19 2023 x $ cat x Killed $ strace cat x 2>&1 | tail -n4 fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0 mmap(NULL, 1056768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f72382fe000 read(3, <unfinished ...>) = ? +++ killed by SIGKILL +++ See attached kernel log: https://bugzilla.opensuse.org/attachment.cgi?id=869593 And also a colleague of mine with VirtualBox-7.0.10 has the same issue after he updated TW (after a longer pause, so moving from kernel 6.1.3 to 6.5.3-1. Drag and drop is broken in all Virtualbox 7 version I just mounted from a host Tumbleweed to a guest Tumbleweed automounted to /mnt and it worked fine. I added and delete files from the share. So shared folders works in both directions. There is no ETA for when Drag and Drop will be fixed. To be clear, my bug report wasn't about drag and drop and I don't use automount. I mount using something like this: sudo mount -t vboxsf -o rw,uid=$(id -u),gid=$(id -g) sharename ~/mynount This currently mounts the share, I can "ls" the files, but any attempt to copy or read a file results in "killed" (as per comment#2). This has been working for ages, and broke about a week ago. (In reply to Ian Laurie from comment #4) > ... I can "ls" the files, but any attempt to > copy or read a file results in "killed" (as per comment#2). > > This has been working for ages, and broke about a week ago. Same problem here (openSUSE Tumbleweed 20230915 as host and guest). The share is set to be mounted automatically to "/mnt/SHARE". The share can be browsed but any attempt to access the files on the share or create a new file on the share will fail. This is an autogenerated message for OBS integration: This bug (1215463) was mentioned in https://build.opensuse.org/request/show/1112825 15.4 / virtualbox https://build.opensuse.org/request/show/1112830 15.5 / virtualbox https://build.opensuse.org/request/show/1112832 15.6 / virtualbox With openSUSE Tumbleweed 20230921 (host + guest) there was an update (?) for virtualbox-kmp-default but the problem is still the same. In forum https://forums.opensuse.org/t/virtualbox-7-0-1-on-leap-15-5-can-not-assign-usb-devices-to-guests/169319 larryr said: the 5.14.21-150500.55.22.1 kernel is bad use the kernel 5.14.21-150500.55.19.1 kernel. Something got built wrong but got past QA. Indeed going back to 5.14.21-150500.55.19.1 resolved my issue. larryr asked me to file a bug, so here it is.... It is not Virtualbox - it is the 5.14.21-150500.55.22.1 kernel is defective on USB devices. go back to supported 5.14.21-150500.55.19.1 kernel, (In reply to Larry Rainey from comment #8) > In forum > https://forums.opensuse.org/t/virtualbox-7-0-1-on-leap-15-5-can-not-assign- > usb-devices-to-guests/169319 larryr said: > the 5.14.21-150500.55.22.1 kernel is bad use the kernel > 5.14.21-150500.55.19.1 kernel. > Something got built wrong but got past QA. > > Indeed going back to 5.14.21-150500.55.19.1 resolved my issue. larryr asked > me to file a bug, so here it is.... > > It is not Virtualbox - it is the 5.14.21-150500.55.22.1 kernel is defective > on USB devices. > go back to supported 5.14.21-150500.55.19.1 kernel, Please be aware that this bug report is not about USB-devices! It is about the fact that accessing the shared folder does not work. And it is not about kernel 5.14.x but about kernel 6.5.4 in openSUSE Tumbleweed. Share folders and USB are broken in 55.21 - All the code that do both are botched in that kernel - Please use 55.19. until they fix the 55.21 - The 55.21 kernel has been retracted. It is the 55.21 kernel - works fine with 55.19. (In reply to Larry Rainey from comment #11) > It is the 55.21 kernel - works fine with 55.19. Again. Please be aware this bug report is about openSUSE Tumbleweed which is currently using kernel 6.5.4. There is no Kernel 55.19 for Tumbleweed and I do not see how to get back to any kernel before 6.4. Retested - both with leap and tumbleweed hosts to tumbleweed guest Tumbleweed 6.5.4 host to Leap 15.4 55.22 - works Tumbleweed 6.5.4 host to Tumbleweed 6.5.3 gets Killed on cat Tumbleweed 6.5.4 host to Tumbleweed 6.5.4 gets Killed on cat Retested - both with leap and tumbleweed hosts to tumbleweed guest Leap 15.5 55.19 host to Leap 15.5 55.22 - works Leap 55.5 55.22 host to Leap 15.5 all - get Killed on cat Leap all host to Tumbleweed 6.5.3 gets Killed on cat Leap all host to Tumbleweed 6.5.4 gets Killed on cat Works on Local built 6.5 kernels - seeing what changed. This might be kernel issue. (In reply to Larry Rainey from comment #13) > Retested - both with leap and tumbleweed hosts to tumbleweed guest > Tumbleweed 6.5.4 host to Leap 15.4 55.22 - works > Tumbleweed 6.5.4 host to Tumbleweed 6.5.3 gets Killed on cat > Tumbleweed 6.5.4 host to Tumbleweed 6.5.4 gets Killed on cat I just tested MS Windows 10 host to Tumbleweed 6.4.12 works MS Windows 10 host to Tumbleweed 6.5.2 dolphin freezes on opening the share MS Windows 11 host to Tumbleweed 6.4.12 works MS Windows 11 host to Tumbleweed 6.5.2 dolphin freezes on opening the share latest Tumbleweed host to latest Tumbleweed dolphin freezes on opening the share The fix for Tumbleweed hosts is in the pipeline. In fact, the update was released to Staging I at about 1900 UTC today. Once a fix reaches staging, it usually appears in TW within 2-3 days. To get it immediately, download virtualbox-kmp-default-7.0.10_k6.5.4_1-Virt.1699.718.3.x86_64.rpm from https://build.opensuse.org/projects/Virtualization/packages/virtualbox:kmp/repositories/openSUSE_Tumbleweed/binaries and install it manually with 'sudo zypper in --force virtualbox-kmp-default...". Neither the package not the modules will be signed, thus they will not work with secure boot, and you will need to be running kernel 6.5.4. Just an additional clarification. The new kmp code needs to be installed in both TW hosts and guests after the upgrade of the kernels to 6.5.4. I am not sure when it broke, but with the new kmp package install on both, it works (again). In my case I don't have an openSUSE host. However I can confirm that in my case, installing the linked rpm in just the guest has fixed the problem on both a Win10 host and a Fedora 39 beta branch host (the later is running VirtualBox from RPMFusion, not Oracle, in case that matters). Thank you for the fast fix. (In reply to Larry Finger from comment #16) > The fix for Tumbleweed hosts is in the pipeline. In fact, the update was > released to Staging I at about 1900 UTC today. Once a fix reaches staging, > it usually appears in TW within 2-3 days. To get it immediately, download > virtualbox-kmp-default-7.0.10_k6.5.4_1-Virt.1699.718.3.x86_64.rpm from > https://build.opensuse.org/projects/Virtualization/packages/virtualbox:kmp/ > repositories/openSUSE_Tumbleweed/binaries and install it manually with 'sudo > zypper in --force virtualbox-kmp-default...". Neither the package not the > modules will be signed, thus they will not work with secure boot, and you > will need to be running kernel 6.5.4. I installed the package mentioned above in my openSUSE Tumbleweed 20230921 (host and guest) and can confirm that now it is possible again to access and use the shared folder in the guest. Thank you very much for your prompt reaction and all your efforts ! openSUSE-RU-2023:0284-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1212761,1214391,1215463 CVE References: JIRA References: Sources used: openSUSE Leap 15.4 (src): virtualbox-7.0.10-lp154.2.38.1, virtualbox-kmp-7.0.10-lp154.2.38.1 openSUSE-RU-2023:0286-1: An update that has three recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1212761,1214391,1215463 CVE References: JIRA References: Sources used: openSUSE Leap 15.5 (src): virtualbox-7.0.10-lp155.2.8.1, virtualbox-kmp-7.0.10-lp155.2.8.1 openSUSE-SU-2023:0352-1: An update that solves three vulnerabilities and has one errata is now available. Category: security (important) Bug References: 1215463,1216363,1216364,1216365 CVE References: CVE-2023-22098,CVE-2023-22099,CVE-2023-22100 JIRA References: Sources used: openSUSE Leap 15.5 (src): virtualbox-7.0.12-lp155.2.13.1, virtualbox-kmp-7.0.12-lp155.2.13.1 |