Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #275115 > unrolled thread

Re: SID KDE Plasma 6.2

Back to article view | Back to linux.debian.user

Contents

  Re: SID KDE Plasma 6.2 George at Clug <Clug@goproject.info> - 2024-12-02 00:10 +0100
    Re: SID KDE Plasma 6.2 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-12-02 05:00 +0100
      Re: SID KDE Plasma 6.2 Dominique Dumont <dominique.dumont@netc.fr> - 2024-12-06 20:20 +0100
        Re: SID KDE Plasma 6.2 George at Clug <Clug@goproject.info> - 2024-12-07 07:50 +0100
          Re: SID KDE Plasma 6.2 Adrian <vk4tux@gmail.com> - 2024-12-07 21:30 +0100
          Re: SID KDE Plasma 6.2 Dominique Dumont <dominique.dumont@netc.fr> - 2024-12-08 16:00 +0100
            Re: SID KDE Plasma 6.2 "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-08 16:30 +0100
            Re: SID KDE Plasma 6.2 George at Clug <Clug@goproject.info> - 2024-12-08 23:50 +0100
              Re: SID KDE Plasma 6.2 Dominique Dumont <dominique.dumont@netc.fr> - 2024-12-09 15:20 +0100
                Re: SID KDE Plasma 6.2 Richard Hector <richard@walnut.gen.nz> - 2024-12-09 18:30 +0100
                  Re: SID KDE Plasma 6.2 Dominique Dumont <dominique.dumont@netc.fr> - 2024-12-18 19:50 +0100
                Re: SID KDE Plasma 6.2 "Andrew M.A. Cater" <amacater@einval.com> - 2024-12-09 21:40 +0100
                Re: SID KDE Plasma 6.2 Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-12-10 07:20 +0100

#275115 — Re: SID KDE Plasma 6.2

[Multipart message — attachments visible in raw view] — view raw

On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:
> On Sun, Dec 1, 2024 at 10:12 AM George at Clug  wrote:
> 
> >
> >
> > On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
> > > All,
> > >
> > > You may want to avoid upgrading KDE Plasma to 6.2 in sid. I
upgraded it
> > > earlier and after a reboot I only get a black screen when
logging in.
> >
> > Whenever someone says, KDE Plasma and black screen together, I
think
> > "nvidia drivers".
> >
> >  I doubt that is your issue. But do you have an Nvidia GPU in
the computer?
> >
> > George.
> >
> 
> No, I do not have Nvidia. I have Sid in a VM. The black screen is
strange
> because I have a visible mouse pointer. I also get crash reporter
popups.
> 


"A black screen with only a visible mouse pointer" is one of the
issues I have seen on computers with an Nvidia GPU, hence to me it was
likely you had an Nvidia GPU, since you do not, then I suspect that
the issue is related to the Graphics type that you have selected for
your VM, maybe changing this to virtio and enabling OpenGL?


FYI: My Debian Testing VM with KDE Plasma Wayland is working well
after updates.



 What GPU does your computer have?, and what Graphics system is your
VM using? (Which graphics driver and Display protocol do you use ?)


Were you using a Wayland session or an X11 session?  



Do you get to see the SDDM login screen or is that black with a mouse
pointer, too?



I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice
server, Address, Hypervisor default, Port set to Auto. OpenGL is not
selected.

On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM
with Cinnamon, so I cloned this VM, ran updates and then installed
kde-full. During the installation I selected "sddm" for the default
display manager.  



When I rebooted I could see the SDDM login screen, and for the
"Session", I selected Plasma (Wayland), then logged in normally.
Everything was working as expected. 



If I selected the QXL video type, then when I booted up, the VM hung
during loading and no mouse pointer.  When I changed back to the
virtio driver, all worked well and I was able log in and watch youtube
videos.


Please let me know if I can help.


Here are my VM settings for the display



  
	* 
  




  
  
  



----------------------------------


When using Cinnamon I usually enable "OpenGL" too, so I tried this
too.




  
    
  
  




  
	* 
  
  



===========================================================================

# apt update && apt update && apt full-upgrade --autoremove -y && apt
autoremove -y && apt clean
Hit:1 http://security.debian.org/debian-security testing-security
InRelease
Hit:2 http://deb.debian.org/debian testing InRelease
Hit:3 http://deb.debian.org/debian testing-updates InRelease
Hit:4 http://deb.debian.org/debian testing-backports InRelease
All packages are up to date.
Hit:1 http://security.debian.org/debian-security testing-security
InRelease
Hit:2 http://deb.debian.org/debian testing InRelease
Hit:3 http://deb.debian.org/debian testing-updates InRelease
Hit:4 http://deb.debian.org/debian testing-backports InRelease
All packages are up to date.
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0

# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux trixie/sid
Release:        n/a
Codename:       trixie

# uname -r
6.11.10-amd64

# env | grep -E -i 'x11|xorg|wayland|plasma'
DESKTOP_SESSION=plasmawayland
MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/user@1004.service/session.slice/plasma-plasmashell.service/memory.pressure
WAYLAND_DISPLAY=wayland-0
PLASMA_USE_QT_SCALING=1
QT_WAYLAND_FORCE_DPI=96

# lspci -k | grep -A 2 -E '(3D|VGA)'
00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev
01)
        Subsystem: Red Hat, Inc. Device 1100
        Kernel driver in use: virtio-pci


===========================================================================

[toc] | [next] | [standalone]

#275120

[Multipart message — attachments visible in raw view] — view raw

On Sun, Dec 1, 2024 at 9:42 PM George at Clug <Clug@goproject.info> wrote:

> On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:
> > On Sun, Dec 1, 2024 at 10:12 AM George at Clug <Clug@goproject.info>
> wrote:
> >
> > >
> > >
> > > On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
> > > > All,
> > > >
> > > > You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded
> it
> > > > earlier and after a reboot I only get a black screen when logging in.
> > >
> > > Whenever someone says, KDE Plasma and black screen together, I think
> > > "nvidia drivers".
> > >
> > >  I doubt that is your issue. But do you have an Nvidia GPU in the
> computer?
> > >
> > > George.
> > >
> >
> > No, I do not have Nvidia. I have Sid in a VM. The black screen is strange
> > because I have a visible mouse pointer. I also get crash reporter popups.
> >
>
> "A black screen with only a visible mouse pointer" is one of the issues I
> have seen on computers with an Nvidia GPU, hence to me it was likely you
> had an Nvidia GPU, since you do not, then I suspect that the issue is
> related to the Graphics type that you have selected for your VM, maybe
> changing this to virtio and enabling OpenGL?
>
> FYI: My Debian Testing VM with KDE Plasma Wayland is working well after
> updates.
>
> What GPU does your computer have?, and what Graphics system is your VM
> using? (Which graphics driver and Display protocol do you use ?)
>

I have AMD with OpenAMD GPU Driver.


>
> Were you using a Wayland session or an X11 session?
>

Wayland


>
> Do you get to see the SDDM login screen or is that black with a mouse
> pointer, too?
>

SDDM works fine


>
> I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice server,
> Address, Hypervisor default, Port set to Auto. OpenGL is not selected.
>
> On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM with
> Cinnamon, so I cloned this VM, ran updates and then installed kde-full.
> During the installation I selected "sddm" for the default display manager.
>
> When I rebooted I could see the SDDM login screen, and for the "Session",
> I selected Plasma (Wayland), then logged in normally. Everything was
> working as expected.
>
> If I selected the QXL video type, then when I booted up, the VM hung
> during loading and no mouse pointer.  When I changed back to the virtio
> driver, all worked well and I was able log in and watch youtube videos.
>
> Please let me know if I can help.
>

I just use the VM to do testing of the installer and updates. I am just
going to waite a week or so then do a clean install.


>
> Here are my VM settings for the display
>
> <graphics type="spice" port="5900" autoport="yes" listen="127.0.0.1">
>   <listen type="address" address="127.0.0.1"/>
>   <image compression="off"/>
> </graphics>
>
> <video>
>   <model type="virtio" heads="1" primary="yes"/>
>   <alias name="video0"/>
>   <address type="pci" domain="0x0000" bus="0x00" slot="0x01"
> function="0x0"/>
> </video>
>
> ----------------------------------
>
> When using Cinnamon I usually enable "OpenGL" too, so I tried this too.
>
> <video>
>   <model type="virtio" heads="1" primary="yes">
>     <acceleration accel3d="yes"/>
>   </model>
>   <address type="pci" domain="0x0000" bus="0x00" slot="0x01"
> function="0x0"/>
> </video>
>
> <graphics type="spice">
>   <listen type="none"/>
>   <image compression="off"/>
>   <gl enable="yes" rendernode="/dev/dri/by-path/pci-0000:03:00.0-render"/>
> </graphics>
>
> ===========================================================================
>
> # apt update && apt update && apt full-upgrade --autoremove -y && apt
> autoremove -y && apt clean
> Hit:1 http://security.debian.org/debian-security testing-security
> InRelease
> Hit:2 http://deb.debian.org/debian testing InRelease
> Hit:3 http://deb.debian.org/debian testing-updates InRelease
> Hit:4 http://deb.debian.org/debian testing-backports InRelease
> All packages are up to date.
> Hit:1 http://security.debian.org/debian-security testing-security
> InRelease
> Hit:2 http://deb.debian.org/debian testing InRelease
> Hit:3 http://deb.debian.org/debian testing-updates InRelease
> Hit:4 http://deb.debian.org/debian testing-backports InRelease
> All packages are up to date.
> Summary:
>   Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
> Summary:
>   Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
>
> # lsb_release -a
> No LSB modules are available.
> Distributor ID: Debian
> Description:    Debian GNU/Linux trixie/sid
> Release:        n/a
> Codename:       trixie
>
> # uname -r
> 6.11.10-amd64
>
> # env | grep -E -i 'x11|xorg|wayland|plasma'
> DESKTOP_SESSION=plasmawayland
>
> MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/user@1004.service
> /session.slice/plasma-plasmashell.service/memory.pressure
> WAYLAND_DISPLAY=wayland-0
> PLASMA_USE_QT_SCALING=1
> QT_WAYLAND_FORCE_DPI=96
>
> # lspci -k | grep -A 2 -E '(3D|VGA)'
> 00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev 01)
>         Subsystem: Red Hat, Inc. Device 1100
>         Kernel driver in use: virtio-pci
>
>
> ===========================================================================
>
>
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [prev] | [next] | [standalone]

#275352

On Monday, 2 December 2024 04:56:09 CET Timothy M Butterworth wrote:
> Were you using a Wayland session or an X11 session?
> 
> Wayland

On my side, kde6 with wayland does not work in a VirtualBox VM.

I had to switch to X11

HTH

[toc] | [prev] | [next] | [standalone]

#275372

On Saturday, 07-12-2024 at 05:35 Dominique Dumont wrote:
> On Monday, 2 December 2024 04:56:09 CET Timothy M Butterworth wrote:
> > Were you using a Wayland session or an X11 session?
> > 
> > Wayland
> 
> On my side, kde6 with wayland does not work in a VirtualBox VM.
> 
> I had to switch to X11

Dominique,

Thanks for your comment. 

What GPU does the computer running the virtual machine use?  That is, what brand and model is the video card on the computer running Virtual Box?

What version of VirtualBox are you using?

I found a comment on the internet that suggests VirtualBox 7.1 under debian12 does not support 3D acceleration.  

$ vboxmanage modifyvm deb-cube --accelerate3d on
VBoxManage: error: The graphics controller does not support the given feature

As I use KVM, I am able to run KDE with Wayland on my computers which have AMD Radeon graphics cards, when enabling OpenGL support (Requires 'Listen type' to be set to None')

Has anyone had success with getting Mice to work correctly for 3D games run in VMs?

I installed Minecraft into a Debian Testing, KDE Wayland, VM and ran Minecraft, Minecraft runs, however the mouse did not work correctly, when in a game world, I could not use (move around with) the mouse inside the Minecraft World correctly.  When I tested X11, the mouse behaved differently but not correctly in X11 either.

After adding a second mouse to my PC, (a logitech USB Wireless mouse and keyboard), in Virt-Manager, I selected "Redirect USB device" and selected "Logitech USB receiver". Then the logitech USB Wireless mouse worked normally within the Minecraft game World, allowing me to move around normally. However the logitech USB Wireless mouse did not operate correctly in the KDE environment, and I had to use the PC's (normally used) mouse in KDE, to start the Minecraft Launcher and to select the Minecraft 'Play' button, and to select between "Singleplayer" and "Multiplayer" options to join the Minecraft World. Once in the World, it was only the logitech USB Wireless mouse which worked normally. My PC is not too powerful so while this worked, it is not something I want to do for "gaming", lol. 

I also tried TuxRacer. The USB redirected logitech USB Wireless mouse worked well for selecting options within the game. However the mouse is not required for playing this game, so it was not much of a test for mice functionality. 

I find this strange behaviour which I cannot easily explain.


Via Virt-Manager I tried to 'Remove' the virtual mouse , e.g. <input type="mouse" bus="ps2"/> but this option is greyed out, so I was not able to do so. I was hoping if I removed KVM's virtual mouse, the USB redirected mouse would work better. I what what others have tried and maybe succeeded in doing?




George.




> 
> HTH
> 
> 
> 
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#275385

Thankyou, however as it seems the konsole panel in dolphin is dependant 
on matching versions,

then konsole could also have been held back until dolphin was ready to go.


regards


Adrian Fewster

On 7/12/24 16:47, George at Clug wrote:
>
> On Saturday, 07-12-2024 at 05:35 Dominique Dumont wrote:
>> On Monday, 2 December 2024 04:56:09 CET Timothy M Butterworth wrote:
>>> Were you using a Wayland session or an X11 session?
>>>
>>> Wayland
>> On my side, kde6 with wayland does not work in a VirtualBox VM.
>>
>> I had to switch to X11
> Dominique,
>
> Thanks for your comment.
>
> What GPU does the computer running the virtual machine use?  That is, what brand and model is the video card on the computer running Virtual Box?
>
> What version of VirtualBox are you using?
>
> I found a comment on the internet that suggests VirtualBox 7.1 under debian12 does not support 3D acceleration.
>
> $ vboxmanage modifyvm deb-cube --accelerate3d on
> VBoxManage: error: The graphics controller does not support the given feature
>
> As I use KVM, I am able to run KDE with Wayland on my computers which have AMD Radeon graphics cards, when enabling OpenGL support (Requires 'Listen type' to be set to None')
>
> Has anyone had success with getting Mice to work correctly for 3D games run in VMs?
>
> I installed Minecraft into a Debian Testing, KDE Wayland, VM and ran Minecraft, Minecraft runs, however the mouse did not work correctly, when in a game world, I could not use (move around with) the mouse inside the Minecraft World correctly.  When I tested X11, the mouse behaved differently but not correctly in X11 either.
>
> After adding a second mouse to my PC, (a logitech USB Wireless mouse and keyboard), in Virt-Manager, I selected "Redirect USB device" and selected "Logitech USB receiver". Then the logitech USB Wireless mouse worked normally within the Minecraft game World, allowing me to move around normally. However the logitech USB Wireless mouse did not operate correctly in the KDE environment, and I had to use the PC's (normally used) mouse in KDE, to start the Minecraft Launcher and to select the Minecraft 'Play' button, and to select between "Singleplayer" and "Multiplayer" options to join the Minecraft World. Once in the World, it was only the logitech USB Wireless mouse which worked normally. My PC is not too powerful so while this worked, it is not something I want to do for "gaming", lol.
>
> I also tried TuxRacer. The USB redirected logitech USB Wireless mouse worked well for selecting options within the game. However the mouse is not required for playing this game, so it was not much of a test for mice functionality.
>
> I find this strange behaviour which I cannot easily explain.
>
>
> Via Virt-Manager I tried to 'Remove' the virtual mouse , e.g. <input type="mouse" bus="ps2"/> but this option is greyed out, so I was not able to do so. I was hoping if I removed KVM's virtual mouse, the USB redirected mouse would work better. I what what others have tried and maybe succeeded in doing?
>
>
>
>
> George.
>
>
>
>
>> HTH
>>
>>
>>
>>
>>
>>

[toc] | [prev] | [next] | [standalone]

#275402

On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:
> What GPU does the computer running the virtual machine use?  That is, what
> brand and model is the video card on the computer running Virtual Box?

AFAIK, there's no specific brand and model. Virtual box emulates VGA and SVGA 
[1].

> What version of VirtualBox are you using?

7.1

> I found a comment on the internet that suggests VirtualBox 7.1 under
> debian12 does not support 3D acceleration.
> 
> $ vboxmanage modifyvm deb-cube --accelerate3d on
> VBoxManage: error: The graphics controller does not support the given
> feature

I did not try that. I don't need it for work.

All the best

[1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html

[toc] | [prev] | [next] | [standalone]

#275403

On Sun, Dec 08, 2024 at 03:39:08PM +0100, Dominique Dumont wrote:
> On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:
> 
> > What version of VirtualBox are you using?
> 
> 7.1
> 
> > I found a comment on the internet that suggests VirtualBox 7.1 under
> > debian12 does not support 3D acceleration.
> > 

Debian does not support virtualbox in Debian stable because of a difference
of opinion with the upstream provider about the practicability of security
updates, as I understand it.

The version in sid is there to prove the practicability of packaging, I 
think. In any event, sid is not intended as a Debian release.

Can I suggest that you ask Oracle for help on this?

The alternative is to switch from Virtualbox (and now also Broadcom VMWare)
and use kvm/aqemu. For myself, I prefer to use virt-manager as a front end
to virtualisation.

With every good wish, as ever,

Andy
(amacater@debian.org)

> I did not try that. I don't need it for work.
> 
> All the best
> 
> [1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html
> 
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#275414

On Monday, 09-12-2024 at 01:39 Dominique Dumont wrote:
> On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:
> > What GPU does the computer running the virtual machine use?  That is, what
> > brand and model is the video card on the computer running Virtual Box?
> 
> AFAIK, there's no specific brand and model. Virtual box emulates VGA and SVGA 

Are you going to use Virtual Box on a number of different physical computers?

Sorry, I was not clear, "What physical video card/s are in the host (the computer acting as the hypervisor) ?" I am not asking about the guest's virtual video device.

This can make a difference. 
AFAIK, VMware Workstation cannot run 3D graphics if your host (physical computer) is using a Radeon video graphics card.
AFAIK, KVM/QEMU cannot run 3D graphics (OpenGL) if your host (physical computer) is using a Nvidia video graphics card.

I am considering installing both Nvidia and Radeon video cards in my host (e.g. my PC that is acting as a hypervisor) so I run both/either VMware and KVM.


> [1].
> 
> > What version of VirtualBox are you using?
> 
> 7.1

At least that is the latest, AFAIK.
> 
> > I found a comment on the internet that suggests VirtualBox 7.1 under
> > debian12 does not support 3D acceleration.
> > 
> > $ vboxmanage modifyvm deb-cube --accelerate3d on
> > VBoxManage: error: The graphics controller does not support the given
> > feature
> 
> I did not try that. I don't need it for work.

I hope you have success. The good thing about Virtual Box is you can run your VMs on either Windows or Linux computers. At least that is what I believe.

As I don't run Windows at this time, I use KVM/QEMU using Virt-Manager to manage the VMs. I do have VMware Player installed, for running a few old VMs that I created a number of years ago when I used to run Windows. Sadly because I currently only have a Radeon video card in my PC, I cannot enable WMware's 3D support.

I hope you have success in your efforts, whether you stay VirtualBox or change to KVM/QEMU. Please let us know if you do.

I will comment that I have not found enabling 3D support has been useful for anything other than running 'Cinnamon without software rendering'. I have not found virtualised 3D graphics useful for gaming, maybe for demonstration, but not actual use. For gaming, I understand that GPU passthrough is required, which I have not personally tried. For gaming, I would prefer to use Wine/Steam or to have a separate PC, or to Dual boot.

George.

> 
> All the best
> 
> [1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html
> 
> 
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#275419

On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
> Are you going to use Virtual Box on a number of different physical
> computers?

No. I use VirtualBox only on the compute of a customer that requires me to 
work on his Windows PC. VirtualBox is my preferred solution to work with Linux 
on a Windows machine. 

> Sorry, I was not clear, "What physical video card/s are in the host (the
> computer acting as the hypervisor) ?" I am not asking about the guest's
> virtual video device.

It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.

> I hope you have success in your efforts, whether you stay VirtualBox or
> change to KVM/QEMU. Please let us know if you do.

As the guest Pc runs Windows, I cannot try kvm/qemu.

All the best

[toc] | [prev] | [next] | [standalone]

#275435

On 10/12/24 02:59, Dominique Dumont wrote:

> As the guest Pc runs Windows, I cannot try kvm/qemu.

I've run Windows in kvm/qemu before.

Richard

[toc] | [prev] | [next] | [standalone]

#275893

On Monday, 9 December 2024 18:18:42 CET Richard Hector wrote:
> On 10/12/24 02:59, Dominique Dumont wrote:
> > As the guest Pc runs Windows, I cannot try kvm/qemu.
> 
> I've run Windows in kvm/qemu before.

Bummer, I got it wrong. 

The host PC is windows and the guest is Debian/sid.

Sorry for the blunder.

[toc] | [prev] | [next] | [standalone]

#275439

On Mon, Dec 09, 2024 at 02:59:48PM +0100, Dominique Dumont wrote:
> On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
> > Are you going to use Virtual Box on a number of different physical
> > computers?
> 
> > Sorry, I was not clear, "What physical video card/s are in the host (the
> > computer acting as the hypervisor) ?" I am not asking about the guest's
> > virtual video device.
> 
> It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.
> 

I only know these from trying to install Debian on high-end gamer laptops.
You get a choice of chipsets but it might be difficult to persuade this
to work straightforwardly for a VM

> > I hope you have success in your efforts, whether you stay VirtualBox or
> > change to KVM/QEMU. Please let us know if you do.
> 
> As the guest Pc runs Windows, I cannot try kvm/qemu.
> 

If the PC runs Windows, you could potentially use WSL2, I suppose.

All the very best, as ever,

Andy

> All the best
> 
> 
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#275451

[Multipart message — attachments visible in raw view] — view raw

On Mon, Dec 9, 2024 at 1:32 PM Dominique Dumont <dominique.dumont@netc.fr>
wrote:

> On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
> > Are you going to use Virtual Box on a number of different physical
> > computers?
>
> No. I use VirtualBox only on the compute of a customer that requires me to
> work on his Windows PC. VirtualBox is my preferred solution to work with
> Linux
> on a Windows machine.


I charge more per hour if I have to use Windows at work.


>
>
> > Sorry, I was not clear, "What physical video card/s are in the host (the
> > computer acting as the hypervisor) ?" I am not asking about the guest's
> > virtual video device.
>
> It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.
>
> > I hope you have success in your efforts, whether you stay VirtualBox or
> > change to KVM/QEMU. Please let us know if you do.
>
> As the guest Pc runs Windows, I cannot try kvm/qemu.
>
> All the best
>
>
>
>
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web