|
Bugzilla – Full Text Bug Listing |
| Summary: | Files in virtualbox shared folder (on the guest) show wrong timestamp | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Bit Juggler <suse.junky> |
| Component: | Virtualization:Tools | Assignee: | Larry Rainey <llrainey15> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | Larry.Finger, zorrinski |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bit Juggler
2024-02-28 09:06:06 UTC
Considering the fact that host: MS Windows 10 (“pure” Oracle VirtualBox 7.0.14) guest: Kubuntu 23.10 (“pure” Oracle VirtualBox GuestAdditions 7.0.14) works fine I think there is some strong evidence that openSUSE Tumbleweed (as guest) might be the cause of the problem. I have no idea how to debug this any further. But if I can be of any assistance ... It appears that this is a kernel problem in an OBS build. If I build a kernel from the latest source using the factory configuration, it works. The "same" kernel loaded from a TW repository fails! (In reply to Larry Finger from comment #2) > If I build a kernel from the latest source ... Is that the sources for kernel-default-6.8~rc7 ? It does not matter whether I use 6.8-rcX or 6.7.7. If I generate the kernel, it works. If OBS makes the kernel, it fails and I do not know why. No, I was working with 6.7.7. I just installed 6.8.0-1.ga551d7b-default and it shows the faulty behavior. All directories in the shared folder had a Dec. 1, 1969 date, and most data files show the current date. My locally generated copy also showed the same problem. I still have more work to do. I just updated to virtualbox-kmp-default 7.0.14_k6.8.2_1-7.2 with virtualbox-guest-tools 7.0.14-7.1 from "openSUSE Tumbleweed Oss" repository and the issue is still there. Are there any news in which version the issue is fixed? Unfortunately, this bug is not yet fixed. I am working on it now, but I still do not know where it happens. As Leap 15.4 and Fedora 39 are both OK as guests, my inclination is that something in the guest code is wrong. This bug is now fixed. The revised code has been submitted to Factory, and should be released within the next few days. This is an autogenerated message for OBS integration: This bug (1220524) was mentioned in https://build.opensuse.org/request/show/1172997 15.5 / virtualbox openSUSE-RU-2024:0134-1: An update that has three recommended fixes can now be installed. Category: recommended (important) Bug References: 1211941,1217824,1220524 CVE References: JIRA References: Sources used: openSUSE Leap 15.5 (src): virtualbox-7.0.18-lp155.2.24.1, virtualbox-kmp-7.0.18-lp155.2.24.1 |