Bug 28040

Summary:	VBoxClient --vmsvga fails to start on i586 systems
Product:	Mageia	Reporter:	Martin Whitaker <mageia>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	virtualbox-6.1.16-10.mga8	CVE:
Status comment:

Description Martin Whitaker 2021-01-08 12:30:09 CET

This is the background task that supports automatic display resizing in a VirtualBox guest when using the VMSVGA display controller. Both autostart and manually starting from the command line fail in the same way. dmesg shows

[  247.553285] Service: Display SVGA X11
[  247.579050] Starting DRM client.
[  247.580820] execve for eturns the following error -1079741204 <NULL>
[  248.047518] Running service failed: VERR_NOT_AVAILABLE

The error number is different every time, so is probably meaningless.

Comment 1 Martin Whitaker 2021-01-08 13:01:55 CET

Note this is the same error that occurs when running 'VBoxClient --vmsvga' when using GNOME on Wayland. It appears that on 64-bit systems VBoxClient use the old X11-only method but on 32-bit systems it uses the new DRM method.

Comment 2 Lewis Smith 2021-01-08 21:00:28 CET

Thank you for another learned report. Can you confirm:
- 32-bit VB host running a 32-bit client ?

Again it seems best to give this directly to tmb.

Assignee: bugsquad => tmb

Comment 3 Thomas Backlund 2021-01-08 21:02:08 CET

(In reply to Lewis Smith from comment #2)
> Thank you for another learned report. Can you confirm:
> - 32-bit VB host running a 32-bit client ?
> 

There is no 32bit host anymore, only 64bit

Comment 4 Thomas Backlund 2021-01-10 02:00:47 CET

please try with virtualbox-6.1.16-12.mga8

it provides VBoxDRMClient and systemd integration

Comment 5 Martin Whitaker 2021-01-10 22:46:27 CET

No joy. vmboxdrmclient.service is a static service, and there doesn't seem to be anything that enables it. I had a quick look at the Fedora package, and they have a udev rule to do that - tried adding it to vbox-additions to rules, but it didn't help. I'll have another look tomorrow when I'm less tired.

You also seem to have lost the startup of the other VBoxClient services.

Comment 6 Thomas Backlund 2021-01-10 22:49:13 CET

if you enable it manually and reboot, does it work then ?

the problem is that presets only trigger on package install, not updates...

I will add more triggers tomorrow to fix upgrade path

Comment 7 Martin Whitaker 2021-01-10 22:52:55 CET

Nope, you can't enable it because it is a static service (not Wanted by anything).

Manually starting it does work.

Comment 8 Thomas Backlund 2021-01-10 22:57:43 CET

(In reply to Martin Whitaker from comment #7)
> Nope, you can't enable it because it is a static service (not Wanted by
> anything).

Ah, indeed... I'll think about if/how to handle it tomorrow...

> 
> Manually starting it does work.

And the auto-resizing work ?

Comment 9 Martin Whitaker 2021-01-10 23:32:46 CET

Yes, once started, auto-resizing worked.

Comment 10 Thomas Backlund 2021-01-10 23:40:52 CET

(In reply to Martin Whitaker from comment #9)
> Yes, once started, auto-resizing worked.

great, then I should be able to fix it up tomorrow... I'm way too tired at this point...

Comment 11 Thomas Backlund 2021-01-11 12:55:49 CET

please try with   virtualbox-6.1.16-14.mga8

Comment 12 Martin Whitaker 2021-01-11 14:53:22 CET

Yes, that fixes the auto-resizing - and it now works on the DM login screen as well which is a bonus.

We need to run

  /usr/bin/VBoxClient --clipboard
  /usr/bin/VBoxClient --checkhostversion
  /usr/bin/VBoxClient --seamless
  /usr/bin/VBoxClient --draganddrop

manually though. I guess they still need to be part of the user session startup.

Comment 13 Thomas Backlund 2021-01-11 16:55:31 CET

virtualbox-6.1.16-15.mga8 currently building should hopefylly resolve the last missing bits.

Comment 14 Martin Whitaker 2021-01-11 22:14:08 CET

Works for me.

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