Created attachment 13299 [details]
Virtualbox log file

Here is also Virtualbox log file.

I don't get the vboxdrvu error in the log after starting my Mageia 8 x86_64
guests. It and an i586 guest are both working ok.

Any idea what vb setting is triggering it's access?

CC: (none) => davidwhodgins

Is the situation the same with update kernel 5.15.46 and our previous, 5.15.43?
(as host kernel)

Some of us experience various issues with .46, i.e me in Bug 30536 comment 1.

CC: (none) => fri

Yes i have try older kernel also but same problem.

(In reply to Dave Hodgins from comment #2)
> I don't get the vboxdrvu error in the log after starting my Mageia 8 x86_64
> guests. It and an i586 guest are both working ok.
> 
> Any idea what vb setting is triggering it's access?

Did you check log file inside guest or outside? /home/x/.config/Virtualbox log file? this is host os problem....

Also network install fails Mageia and also Debian some reasons.....Debian guest get installed but when update or install packages get apt errors some Hash sum mismatch error....

I checked VBox.log in the host's log directory for that vb guest.

https://bugs.mageia.org/show_bug.cgi?id=30535 is for the cauldron network
installer failing to set up dns. The m8 network installer is still working
according to latest tests.

My system Mga8 fails but when stage2 install packages,Cauldron fails stage1 network configuration trying to resolve dns...I don't think this problem has nothing to do with dns.

(In reply to Otto Leipälä from comment #0)
> Virtualbox can't access anymore to /dev/vboxdrvu
> there need fix udev rules file user can't acess to vboxdrvu....local fixes
> is working change 0600 to 0666 permission so user/vboxusers can acess it
> KERNEL=="vboxdrvu", OWNER="root", GROUP="root", MODE="0600"
> it need to be
> KERNEL=="vboxdrvu", OWNER="root", GROUP="root", MODE="0666"


Never going to happend.
Setting mode to 0666 would open up a big security hole.

okay?

It seems problem is not udev rule????
I just looked rpmfusion package changed udev rule....
https://github.com/rpmfusion/VirtualBox/blob/master/VirtualBox-60-vboxdrv.rules

Same problem updated Virtualbox updates testing.....

Created attachment 13302 [details]
Another log file

Log file updated Virtualbox tesing......
Still it complains permissions....
01:12:16.576247 nspr-8   Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE

Other then generating the message, does it have any impact creating or running
the guest?

installing guest

(In reply to Otto Leipälä from comment #15)
> installing guest

I installed today successfully a MGA8 guest (Mageia-8-x86_64.iso) on a MGA8 host for other testing purposes. This message didn't have any impact on installation or running of the guest.

Created attachment 13306 [details]
Screenshot netinstall fails

Did you read comment 7? Cauldron netinstall is broken in general at the moment. It is not related to VirtualBox!

Yes but in my system whole Virtualbox is broken all distros netinstall Mageia 8 Debian etc many others......this is nothing to do with Cauldron as there is dns broken this is totally different problem

(In reply to sturmvogel from comment #18)
> Did you read comment 7? Cauldron netinstall is broken in general at the
> moment. It is not related to VirtualBox!

You may read bugreport lot more better as i have never said anything about Cauldron,also i have added bugreport against Mageia 8.

This has become confused. Can we clarify things? State what you are doing.
* Mageia 8, not Cauldron, sure.
* Running a VB host.
Does the reported error (attached VB logs) happen just when starting the VB host?
Or when trying to do something specific under it?
How is Netinstall involved? Is Otto's problem (comment 17) really about a Netinstall failure:
 https://bugs.mageia.org/attachment.cgi?id=13306
rather than VB itself?

Comment 14
> Other then generating the message, does it have any impact creating
> or running the guest?
Comment 15
> installing guest
What guest?

Comment 16
> I installed today successfully a MGA8 guest (Mageia-8-x86_64.iso)
> on a MGA8 host
> This message didn't have any impact on installation or running of the guest.
Which implies that sturmvogel also saw it, but it did not matter.

CC: (none) => lewyssmith

(In reply to Lewis Smith from comment #21)
> This has become confused. Can we clarify things? State what you are doing.
> * Mageia 8, not Cauldron, sure.
> * Running a VB host.
> Does the reported error (attached VB logs) happen just when starting the VB
> host?
> Or when trying to do something specific under it?
> How is Netinstall involved? Is Otto's problem (comment 17) really about a
> Netinstall failure:
>  https://bugs.mageia.org/attachment.cgi?id=13306
> rather than VB itself?
> 
> Comment 14
> > Other then generating the message, does it have any impact creating
> > or running the guest?
> Comment 15
> > installing guest
> What guest?
> 
> Comment 16
> > I installed today successfully a MGA8 guest (Mageia-8-x86_64.iso)
> > on a MGA8 host
> > This message didn't have any impact on installation or running of the guest.
> Which implies that sturmvogel also saw it, but it did not matter.

It fails to install any guest system Mageia Debian Archlinux any can't even finish install....
Log is created when it try to install guest,it never installs as it will fails when trying to install.

5.15.43-desktop-1.mga8 works but .46 not working.

I'm not computer engineer so i have only basic knowledge....This have to be kernel side problem,one kernel point release works but not newest,there have to be some changes broken Virtualbox host...
I'm not very good to see what real changes in kernel been made....Maybe Thomas (Tmb) can explain it more better....

Created attachment 13310 [details]
Inxi full output

Here is full inxi what hardware my system if it helps more...

It seems updates testing .48/5.15.48-desktop-1.mga8 kernel works with virtualbox....

Thank you for the kernel details, and your encouraging previous comment.
> 5.15.43-desktop-1.mga8 works but [5.15].46 not working
> 5.15.48-desktop-1.mga8 kernel works with virtualbox....
If you have installed, and are running with 5.15.48 (from updates_testing), we can close this once that kernel gets OK'd.
Please say what exact version of VB you are using: the current issued one (in Source RPM at head), or that you tried from updates_testing (comment 12). You said that made no difference.

CC'ing tmb since this looks very much his territory.

CC: (none) => tmb
Summary: Virtualbox problem udev rules => Virtualbox problem with kernel 5.15.46
Source RPM: (none) => virtualbox-6.1.34-1.8.mga8.src.rp

It no matters anymore what version Vb as problem is kernel not Vb...It works testing or updates version....

I noticed another problem that guest fails to build 5.18 kerne it needs more new Virtualbox 6.1.35 testing,if older Vbox it fails to build Additions Kernel 5.18
can you Tmb make Rpm testimg build of Vbox?

Um, considering I've built several kmods for 5.18 series kernels both in Cauldron and mga8 backports... the build works..

so if you have some issue, show the buildlogs

I noticed another problem that guest fails to build 5.18 kerne it needs more new Virtualbox 6.1.35 testing,if older Vbox it fails to build Additions Kernel 5.18
can you Tmb make Rpm testimg build of Vbox?

Yes logs if needed,need to first test updates_testing build of Virtualbox as there is patch added support 5.18 5.19 kernel.

Created attachment 13321 [details]
Virtualbox guest additions log Debian/Sid

Here is Virtualbox log file when trying to build Debian Sid kernel additions inside guest system,it fails to build.

kernel-desktop-5.15.50-1.mga8
kernel-desktop-devel-5.15.50-1.mga8
virtualbox-kernel-5.15.50-desktop-1.mga8
Virtualbox  6.1.34-1.10.mga8

(In reply to Otto Leipälä from comment #32)
> Created attachment 13321 [details]
> Virtualbox guest additions log Debian/Sid
> 
> Here is Virtualbox log file when trying to build Debian Sid kernel additions
> inside guest system,it fails to build.


and thats a debian bug, not a mageia one.

and you dont need vboxadditions on recent kernels as they are already in upstream kernel.org kernels

Okay good to know.

So when installing a Mageia guest with kernel-linus we need not install vboxadditions?
Is the automatic selection to install it or not adapted?

https://wiki.mageia.org/en/VirtualBox#On_guests

Currently it say:
"On the guest, if it is Mageia, make sure virtualbox-guest-additions is installed. Mageia installer normally detects if it is run inside VirtualBox and installs it automatically, but check! This provides the guest with the ability to share files and sync time with the host."

So it should tell vboxadditions is not needed for kernel-linus from version <which?>  ?

If so it could also be mentioned at
https://wiki.mageia.org/en/Kernel_flavours#kernel-linus

(In reply to Morgan Leijström from comment #35)
> So when installing a Mageia guest with kernel-linus we need not install
> vboxadditions?
> Is the automatic selection to install it or not adapted?
> 
> https://wiki.mageia.org/en/VirtualBox#On_guests
> 
> Currently it say:
> "On the guest, if it is Mageia, make sure virtualbox-guest-additions 

Read again: :)

it talks about virtualbox-*guest*-additions 

I was talking about the vboxadditions (as earlier provided by dkms-vboxadditions and kmod-vboxadditions)

Yeah, I know it's a somewhat subtle difference...
 
the *guest* package only adds a couple of binaries, some udev rules and some services, and that is not kernel version specific... as those kernel bits are in upstream kernels nowdays...

Ah OK

Just trying to make sure we supply correct info :)

- while my brain is swamped by another project... :/

Assigning to Thomas as he is the best placed to judge this bug - if indeed it is one. No point now in leaving it with bugsquad.

CC: lewyssmith, tmb => (none)
Assignee: bugsquad => tmb

There is really a major problem since kernel 5.15.46, also with kernel 5.15.50. (with 5.15.43 everything is fine)
Situation here:
Mageia 8 as host system
Windows 10 as guest system
Virtualbox 6.1.34 downloaded directly from virtualbox.org

The Problem:
Windows crashes during boot or soon after it, mostly reboots into the bue screen with repairing tools, but none of the repairing tool finds any errors.

CC: (none) => egc

fwiw, Windows 7 64 bit runs perfect on my workstation, since our virtualbox update.
(but I have only booted it maybe ten times since, for half hour sessions, with kernel .46 and on. Recently 5.15.50, and since a few days .51.

I use the Mageia packaged VirtualBox, but extpack from upstream.

mga8-64, on an old intel i7, nvidia-current.

(In reply to egc from comment #39)
> There is really a major problem since kernel 5.15.46, also with kernel
> 5.15.50. (with 5.15.43 everything is fine)
> Situation here:
> Mageia 8 as host system
> Windows 10 as guest system
> Virtualbox 6.1.34 downloaded directly from virtualbox.org
> 

this it the problem.

Upstream 6.1.34 is not adapted for the hardening done to the random subsystem.

Upstream will only fix it in 6.1.36 that should be released on July 19th, 2022

Yes great work Thomas :)

Can we close this bug now, or is there any issue left with the Mageia packages?

No answer, thus closing.

New VirtualBox to test in Bug 30657

Resolution: (none) => FIXED
Status: NEW => RESOLVED