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

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

GUI-Login on bookworm-VM in a cloud

Started byChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
First post2024-07-02 13:50 +0200
Last post2024-07-08 17:00 +0200
Articles 12 — 2 participants

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

Contents

  GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-02 13:50 +0200
    Re: GUI-Login on bookworm-VM in a cloud George at Clug <Clug@goproject.info> - 2024-07-03 06:30 +0200
      Re: GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-03 09:50 +0200
        Re: GUI-Login on bookworm-VM in a cloud  George at Clug <Clug@goproject.info> - 2024-07-04 03:10 +0200
          Re: GUI-Login on bookworm-VM in a cloud George at Clug <Clug@goproject.info> - 2024-07-04 04:40 +0200
            Re: GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-04 09:20 +0200
    Re: GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-04 17:20 +0200
      Re: GUI-Login on bookworm-VM in a cloud George at Clug <Clug@goproject.info> - 2024-07-05 10:40 +0200
        Re: GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-05 12:50 +0200
          Re: GUI-Login on bookworm-VM in a cloud George at Clug <Clug@goproject.info> - 2024-07-05 17:10 +0200
            Re: GUI-Login on bookworm-VM in a cloud Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de> - 2024-07-08 15:20 +0200
              Re: GUI-Login on bookworm-VM in a cloud George at Clug <Clug@goproject.info> - 2024-07-08 17:00 +0200

#270732 — GUI-Login on bookworm-VM in a cloud

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-02 13:50 +0200
SubjectGUI-Login on bookworm-VM in a cloud
Message-ID<IVKbf-79in-3@gated-at.bofh.it>

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

Hello,

I use the cloud solution OpenNebula to manage VMs in a cloud. There I
have several VMs with Debian 11 running successfully,
sddm, lightdm and gdm3 are installed as display managers. When I choose
one of them, the corresponding GUI login is displayed in the VNC
display of the VM.

However, after installing a VM with Debian 12, none of these three
display managers shows its GUI login screen after boot. With sddm it is
noticeable that the process sddm-helper crashes shortly after it is
started.

To get to the bottom of the problem, I upgraded a bullseye VM
to a bookworm VM step by step: first libc, then the Xorg-
packages, then the kernel, then sddm, lightdm and gdm3, and finally the
rest. Unfortunately, it was only after the rest that the GUI login no
longer appeared; therefore I am not really any further with the answer
to the question what exactly the problem is.

No matter what I tell qemu what video driver to use
(cirrus, vga, vmvga, virtio), the problem occurs with all of them.
On a real hardware the graphical login is displayed, with the same
software packages.

Can anyone help?

Regards
  Christoph

[toc] | [next] | [standalone]

#270752

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-03 06:30 +0200
Message-ID<IVZMZ-7jMk-3@gated-at.bofh.it>
In reply to#270732
> Can anyone help?
My first thoughts were firewall issues.

https://docs.opennebula.io/6.8/quick_start/deployment_basics/try_opennebula_on_kvm.html
open ports: 22 (SSH), 80 (Sunstone), 2616 (FireEdge), 5030 (OneGate).

https://docs.opennebula.io/6.8/installation_and_configuration/frontend_installation/install.html#frontend-fw
Firewall Configuration¶

The list below shows the ports used by OpenNebula. These ports need to be open for OpenNebula to work properly:

Port       Description
22         Front-end host SSH server
2474     OneFlow server
2616     Next-generation GUI server FireEdge
2633     Main OpenNebula Daemon (oned), XML-RPC API endpoint
4124     Monitoring daemon (both TCP/UDP)
5030     OneGate server
9869     GUI server Sunstone
29876   noVNC Proxy Server

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html#adding-security-group-rule


On Tuesday, 02-07-2024 at 21:38 Christoph Pleger wrote:
> Hello,
> 
> I use the cloud solution OpenNebula to manage VMs in a cloud. There I

I have not used OpenNebula so I cannot comment on this software. I have some experience with running VMs using VMware, KVM, and Hyper-V. I hope some of my comments may be useful.

I am curious, why do you use OpenNebula ? (I am not saying you should not use OpenNebula, I am just curious why this choice). 

What hypervisor is running your Debian VMs?

And can you use any other VM management tools? If so what happens when using those?  While it is unlikely to suite your needs, are you able to use Linux's Virt-Manager to connect without issues?.

As Virt-Manager does not need an endpoint to be installed, I have found it is effective for testing/working with KVM VMs.

https://opennebula.io/open-source-alternative-to-vmware/
OpenNebula helps you migrate your Enterprise Cloud from VMware to a cost-effective open source virtualization platform based on KVM.

https://docs.opennebula.io/6.8/installation_and_configuration/opennebula_services/onegate.html
OneGate Configuration¶
The OneGate server allows Virtual Machines to pull and push information from/to OpenNebula.



> have several VMs with Debian 11 running successfully,
> sddm, lightdm and gdm3 are installed as display managers. When I choose
> one of them, the corresponding GUI login is displayed in the VNC
> display of the VM.
> 
> However, after installing a VM with Debian 12, none of these three
> display managers shows its GUI login screen after boot. With sddm it is
> noticeable that the process sddm-helper crashes shortly after it is
> started.

In crashes, do you mean the server's log files show that the display manager has terminated due to some error?

I assume ssh to a terminal is still working, but it is worth me asking to be sure.

> 
> To get to the bottom of the problem, I upgraded a bullseye VM
> to a bookworm VM step by step: first libc, then the Xorg-
> packages, then the kernel, then sddm, lightdm and gdm3, and finally the
> rest. Unfortunately, it was only after the rest that the GUI login no
> longer appeared; therefore I am not really any further with the answer
> to the question what exactly the problem is.
> 
> No matter what I tell qemu what video driver to use
> (cirrus, vga, vmvga, virtio), the problem occurs with all of them.
> On a real hardware the graphical login is displayed, with the same
> software packages.
> 
> Can anyone help?
> 
> Regards
>   Christoph
>

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

#270755

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-03 09:50 +0200
Message-ID<IW2Ux-7lyE-13@gated-at.bofh.it>
In reply to#270752

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

Hello,

> My first thoughts were firewall issues.

It is not a connection problem. When I open a browser window to vnc
connect to the VM, I can even see the mouse pointer, what shows that
the VM Xorg server is still running, and sshing to the VM and doing a
ps confirms that.

> > 
> > However, after installing a VM with Debian 12, none of these three
> > display managers shows its GUI login screen after boot. With sddm
> > it is
> > noticeable that the process sddm-helper crashes shortly after it is
> > started.
> 
> In crashes, do you mean the server's log files show that the display
> manager has terminated due to some error?

Unfortunately, I could not find a log that tells what exactly happened.
But it is clear that sddm-helper crashes with a segmentation fault.

Regards
  Christoph

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

#270787

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-04 03:10 +0200
Message-ID<IWj8Z-7vEH-1@gated-at.bofh.it>
In reply to#270755
Christoph,

I do not have access to OpenNebula with which I could test.

I do have access to Virt-Manager and so I built up a Virtual Machine of Bookworm (Debian 12) with KDE so that I would have the sddm display manger.

Then I set the "graphics type" to VNC, but I could not start the VM until I removed any mention to spice (or otherwise I could not set the graphics type to VNC).

The below configuration for the VM I created, runs KDE display very well. I presume sound does not work with VNC.

Have you been able to try Virt-Manager to run your Debian VMs? 

FYI: I have found that Virt-Manger prefers to use use Spice more than VNC, and as spice gives me sound I normally use Spice for USB redirection and for Display with the display type.

I hope this information might be may be of help to you.

Regards,

George.


<domain type="kvm">
  <name>01-01-Deb-KDE-VNC</name>
  <uuid>4280bdf6-667b-407a-975d-3caea376172d</uuid>
  <metadata>
    <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
      <libosinfo:os id="http://debian.org/debian/12"/>
    </libosinfo:libosinfo>
  </metadata>
  <memory unit="KiB">8388608</memory>
  <currentMemory unit="KiB">8388608</currentMemory>
  <vcpu placement="static">4</vcpu>
  <os>
    <type arch="x86_64" machine="pc-q35-7.2">hvm</type>
    <boot dev="hd"/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <vmport state="off"/>
  </features>
  <cpu mode="host-passthrough" check="none" migratable="on"/>
  <clock offset="utc">
    <timer name="rtc" tickpolicy="catchup"/>
    <timer name="pit" tickpolicy="delay"/>
    <timer name="hpet" present="no"/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled="no"/>
    <suspend-to-disk enabled="no"/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type="file" device="disk">
      <driver name="qemu" type="qcow2" discard="unmap"/>
      <source file="/var/lib/libvirt/images/01-01-Deb-KDE-VNC.qcow2"/>
      <target dev="vda" bus="virtio"/>
      <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
    </disk>
    <disk type="file" device="cdrom">
      <driver name="qemu" type="raw"/>
      <target dev="sda" bus="sata"/>
      <readonly/>
      <address type="drive" controller="0" bus="0" target="0" unit="0"/>
    </disk>
    <controller type="usb" index="0" model="qemu-xhci" ports="15">
      <address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
    </controller>
    <controller type="pci" index="0" model="pcie-root"/>
    <controller type="pci" index="1" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="1" port="0x10"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0" multifunction="on"/>
    </controller>
    <controller type="pci" index="2" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="2" port="0x11"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x1"/>
    </controller>
    <controller type="pci" index="3" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="3" port="0x12"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x2"/>
    </controller>
    <controller type="pci" index="4" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="4" port="0x13"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x3"/>
    </controller>
    <controller type="pci" index="5" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="5" port="0x14"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x4"/>
    </controller>
    <controller type="pci" index="6" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="6" port="0x15"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x5"/>
    </controller>
    <controller type="pci" index="7" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="7" port="0x16"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x6"/>
    </controller>
    <controller type="pci" index="8" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="8" port="0x17"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x7"/>
    </controller>
    <controller type="pci" index="9" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="9" port="0x18"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0" multifunction="on"/>
    </controller>
    <controller type="pci" index="10" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="10" port="0x19"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x1"/>
    </controller>
    <controller type="pci" index="11" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="11" port="0x1a"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x2"/>
    </controller>
    <controller type="pci" index="12" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="12" port="0x1b"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x3"/>
    </controller>
    <controller type="pci" index="13" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="13" port="0x1c"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x4"/>
    </controller>
    <controller type="pci" index="14" model="pcie-root-port">
      <model name="pcie-root-port"/>
      <target chassis="14" port="0x1d"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x5"/>
    </controller>
    <controller type="sata" index="0">
      <address type="pci" domain="0x0000" bus="0x00" slot="0x1f" function="0x2"/>
    </controller>
    <controller type="virtio-serial" index="0">
      <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
    </controller>
    <interface type="network">
      <mac address="52:54:00:e7:bb:67"/>
      <source network="default"/>
      <model type="virtio"/>
      <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
    </interface>
    <serial type="pty">
      <target type="isa-serial" port="0">
        <model name="isa-serial"/>
      </target>
    </serial>
    <console type="pty">
      <target type="serial" port="0"/>
    </console>
    <channel type="unix">
      <target type="virtio" name="org.qemu.guest_agent.0"/>
      <address type="virtio-serial" controller="0" bus="0" port="1"/>
    </channel>
    <input type="tablet" bus="usb">
      <address type="usb" bus="0" port="1"/>
    </input>
    <input type="mouse" bus="ps2"/>
    <input type="keyboard" bus="ps2"/>
    <graphics type="vnc" port="-1" autoport="yes">
      <listen type="address"/>
    </graphics>
    <sound model="ich9">
      <address type="pci" domain="0x0000" bus="0x00" slot="0x1b" function="0x0"/>
    </sound>
    <audio id="1" type="none"/>
    <video>
      <model type="virtio" heads="1" primary="yes"/>
      <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
    </video>
    <memballoon model="virtio">
      <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
    </memballoon>
    <rng model="virtio">
      <backend model="random">/dev/urandom</backend>
      <address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/>
    </rng>
  </devices>
</domain>



On Wednesday, 03-07-2024 at 17:41 Christoph Pleger wrote:
> Hello,
> 
> > My first thoughts were firewall issues.
> 
> It is not a connection problem. When I open a browser window to vnc
> connect to the VM, I can even see the mouse pointer, what shows that
> the VM Xorg server is still running, and sshing to the VM and doing a
> ps confirms that.
> 
> > > 
> > > However, after installing a VM with Debian 12, none of these three
> > > display managers shows its GUI login screen after boot. With sddm
> > > it is
> > > noticeable that the process sddm-helper crashes shortly after it is
> > > started.
> > 
> > In crashes, do you mean the server's log files show that the display
> > manager has terminated due to some error?
> 
> Unfortunately, I could not find a log that tells what exactly happened.
> But it is clear that sddm-helper crashes with a segmentation fault.
> 
> Regards
>   Christoph
>

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

#270789

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-04 04:40 +0200
Message-ID<IWky5-7wsX-1@gated-at.bofh.it>
In reply to#270787
Christoph,

Not sure if this is relevant or not, sadly probably not useful.

https://libvirt.org/formatdomain.html
https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines
https://www.linux-kvm.org/page/VMchannel_Requirements
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-guest_virtual_machine_device_configuration-usb_devices#sect-USB_devices-Setting_a_limit_on_USB_device_redirection

https://www.spice-space.org/usbredir.html
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/chap-qemu_guest_agent#sect-QEMU_Guest_Agent-Set_Up_Communication_between_Guest_Agent_and_Host-Linux
Chapter 11. Enhancing Virtualization with the QEMU Guest Agent

 Add the following to the guest's XML file and save the changes:

<channel type='unix'>
   <target type='virtio' name='org.qemu.guest_agent.0'/>
</channel>


Below is what Virt-Manager created:

<channel type="unix">
  <source mode="bind" path="/var/lib/libvirt/qemu/channel/target/domain-7-01-01-Deb-KDE-VNC/org.qemu.guest_agent.0"/>
  <target type="virtio" name="org.qemu.guest_agent.0" state="connected"/>
  <alias name="channel0"/>
  <address type="virtio-serial" controller="0" bus="0" port="1"/>
</channel>

My test VM would need this port open "5900"
<graphics type="vnc" port="5900" autoport="yes" listen="127.0.0.1">
  <listen type="address" address="127.0.0.1"/>
</graphics>


I added a channel as per below, but I do not really know what it does. I am not able to copy to/from clipboard, maybe I need to enable something else as well?  I check the VM and it does have qemu-guest-agent installed. 

<channel type="qemu-vdagent">
  <source>
    <clipboard copypaste="yes"/>
  </source>
  <target type="virtio" name="org.libguestfs.channel.0" state="disconnected"/>
  <alias name="channel1"/>
  <address type="virtio-serial" controller="0" bus="0" port="2"/>
</channel>


https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-manipulating_the_domain_xml-devices#sect-Devices-Redirected_devices

redirdev 
This is the main container for describing redirected devices. bus must be usb for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host physical machine side of the tunnel: type='tcp' or type='spicevmc' (which uses the usbredir channel of a SPICE graphics device) are typical. 






On Thursday, 04-07-2024 at 11:08 George at Clug wrote:
> Christoph,
> 
> I do not have access to OpenNebula with which I could test.
> 
> I do have access to Virt-Manager and so I built up a Virtual Machine of Bookworm (Debian 12) with KDE so that I would have the sddm display manger.
> 
> Then I set the "graphics type" to VNC, but I could not start the VM until I removed any mention to spice (or otherwise I could not set the graphics type to VNC).
> 
> The below configuration for the VM I created, runs KDE display very well. I presume sound does not work with VNC.
> 
> Have you been able to try Virt-Manager to run your Debian VMs? 
> 
> FYI: I have found that Virt-Manger prefers to use use Spice more than VNC, and as spice gives me sound I normally use Spice for USB redirection and for Display with the display type.
> 
> I hope this information might be may be of help to you.
> 
> Regards,
> 
> George.
> 
> 
> <domain type="kvm">
>   <name>01-01-Deb-KDE-VNC</name>
>   <uuid>4280bdf6-667b-407a-975d-3caea376172d</uuid>
>   <metadata>
>     <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0">
>       <libosinfo:os id="http://debian.org/debian/12"/>
>     </libosinfo:libosinfo>
>   </metadata>
>   <memory unit="KiB">8388608</memory>
>   <currentMemory unit="KiB">8388608</currentMemory>
>   <vcpu placement="static">4</vcpu>
>   <os>
>     <type arch="x86_64" machine="pc-q35-7.2">hvm</type>
>     <boot dev="hd"/>
>   </os>
>   <features>
>     <acpi/>
>     <apic/>
>     <vmport state="off"/>
>   </features>
>   <cpu mode="host-passthrough" check="none" migratable="on"/>
>   <clock offset="utc">
>     <timer name="rtc" tickpolicy="catchup"/>
>     <timer name="pit" tickpolicy="delay"/>
>     <timer name="hpet" present="no"/>
>   </clock>
>   <on_poweroff>destroy</on_poweroff>
>   <on_reboot>restart</on_reboot>
>   <on_crash>destroy</on_crash>
>   <pm>
>     <suspend-to-mem enabled="no"/>
>     <suspend-to-disk enabled="no"/>
>   </pm>
>   <devices>
>     <emulator>/usr/bin/qemu-system-x86_64</emulator>
>     <disk type="file" device="disk">
>       <driver name="qemu" type="qcow2" discard="unmap"/>
>       <source file="/var/lib/libvirt/images/01-01-Deb-KDE-VNC.qcow2"/>
>       <target dev="vda" bus="virtio"/>
>       <address type="pci" domain="0x0000" bus="0x04" slot="0x00" function="0x0"/>
>     </disk>
>     <disk type="file" device="cdrom">
>       <driver name="qemu" type="raw"/>
>       <target dev="sda" bus="sata"/>
>       <readonly/>
>       <address type="drive" controller="0" bus="0" target="0" unit="0"/>
>     </disk>
>     <controller type="usb" index="0" model="qemu-xhci" ports="15">
>       <address type="pci" domain="0x0000" bus="0x02" slot="0x00" function="0x0"/>
>     </controller>
>     <controller type="pci" index="0" model="pcie-root"/>
>     <controller type="pci" index="1" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="1" port="0x10"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x0" multifunction="on"/>
>     </controller>
>     <controller type="pci" index="2" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="2" port="0x11"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x1"/>
>     </controller>
>     <controller type="pci" index="3" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="3" port="0x12"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x2"/>
>     </controller>
>     <controller type="pci" index="4" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="4" port="0x13"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x3"/>
>     </controller>
>     <controller type="pci" index="5" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="5" port="0x14"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x4"/>
>     </controller>
>     <controller type="pci" index="6" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="6" port="0x15"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x5"/>
>     </controller>
>     <controller type="pci" index="7" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="7" port="0x16"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x6"/>
>     </controller>
>     <controller type="pci" index="8" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="8" port="0x17"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x02" function="0x7"/>
>     </controller>
>     <controller type="pci" index="9" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="9" port="0x18"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x0" multifunction="on"/>
>     </controller>
>     <controller type="pci" index="10" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="10" port="0x19"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x1"/>
>     </controller>
>     <controller type="pci" index="11" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="11" port="0x1a"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x2"/>
>     </controller>
>     <controller type="pci" index="12" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="12" port="0x1b"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x3"/>
>     </controller>
>     <controller type="pci" index="13" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="13" port="0x1c"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x4"/>
>     </controller>
>     <controller type="pci" index="14" model="pcie-root-port">
>       <model name="pcie-root-port"/>
>       <target chassis="14" port="0x1d"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x03" function="0x5"/>
>     </controller>
>     <controller type="sata" index="0">
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x1f" function="0x2"/>
>     </controller>
>     <controller type="virtio-serial" index="0">
>       <address type="pci" domain="0x0000" bus="0x03" slot="0x00" function="0x0"/>
>     </controller>
>     <interface type="network">
>       <mac address="52:54:00:e7:bb:67"/>
>       <source network="default"/>
>       <model type="virtio"/>
>       <address type="pci" domain="0x0000" bus="0x01" slot="0x00" function="0x0"/>
>     </interface>
>     <serial type="pty">
>       <target type="isa-serial" port="0">
>         <model name="isa-serial"/>
>       </target>
>     </serial>
>     <console type="pty">
>       <target type="serial" port="0"/>
>     </console>
>     <channel type="unix">
>       <target type="virtio" name="org.qemu.guest_agent.0"/>
>       <address type="virtio-serial" controller="0" bus="0" port="1"/>
>     </channel>
>     <input type="tablet" bus="usb">
>       <address type="usb" bus="0" port="1"/>
>     </input>
>     <input type="mouse" bus="ps2"/>
>     <input type="keyboard" bus="ps2"/>
>     <graphics type="vnc" port="-1" autoport="yes">
>       <listen type="address"/>
>     </graphics>
>     <sound model="ich9">
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x1b" function="0x0"/>
>     </sound>
>     <audio id="1" type="none"/>
>     <video>
>       <model type="virtio" heads="1" primary="yes"/>
>       <address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/>
>     </video>
>     <memballoon model="virtio">
>       <address type="pci" domain="0x0000" bus="0x05" slot="0x00" function="0x0"/>
>     </memballoon>
>     <rng model="virtio">
>       <backend model="random">/dev/urandom</backend>
>       <address type="pci" domain="0x0000" bus="0x06" slot="0x00" function="0x0"/>
>     </rng>
>   </devices>
> </domain>
> 
> 
> 
> On Wednesday, 03-07-2024 at 17:41 Christoph Pleger wrote:
> > Hello,
> > 
> > > My first thoughts were firewall issues.
> > 
> > It is not a connection problem. When I open a browser window to vnc
> > connect to the VM, I can even see the mouse pointer, what shows that
> > the VM Xorg server is still running, and sshing to the VM and doing a
> > ps confirms that.
> > 
> > > > 
> > > > However, after installing a VM with Debian 12, none of these three
> > > > display managers shows its GUI login screen after boot. With sddm
> > > > it is
> > > > noticeable that the process sddm-helper crashes shortly after it is
> > > > started.
> > > 
> > > In crashes, do you mean the server's log files show that the display
> > > manager has terminated due to some error?
> > 
> > Unfortunately, I could not find a log that tells what exactly happened.
> > But it is clear that sddm-helper crashes with a segmentation fault.
> > 
> > Regards
> >   Christoph
> > 
> 
>

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

#270794

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-04 09:20 +0200
Message-ID<IWoV3-7zMA-3@gated-at.bofh.it>
In reply to#270789

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

Hello George,

> Not sure if this is relevant or not, sadly probably not useful.

It is helpful, though probably not in the matter from the email
subject. But I installed qemu-guest-agent package in a VM without
knowing that the virtual machine template should be made fit for it.

Regards
  Christoph

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

#270819

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-04 17:20 +0200
Message-ID<IWwpz-7Eht-7@gated-at.bofh.it>
In reply to#270732

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

Hello,
> To get to the bottom of the problem, I upgraded a bullseye VM
> to a bookworm VM step by step: first libc, then the Xorg-
> packages, then the kernel, then sddm, lightdm and gdm3, and finally
the
> rest. Unfortunately, it was only after the rest that the GUI login no
> longer appeared; therefore I am not really any further with the
answer
> to the question what exactly the problem is.


I can now tell that the problem is introduced when upgrading the
following packages from bullseye to their bookworm versions:

libglx-mesa0 libx11-xcb1 libgbm1 libgl1-mesa-dri libdrm-common
libglapi-mesa libdrm-amdgpu1 libdrm2 libegl-mesa0 libx11-6
libwayland-client0

Regards
  Christoph

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

#270859

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-05 10:40 +0200
Message-ID<IWME1-7OsO-1@gated-at.bofh.it>
In reply to#270819
Christoph,

What video device does your VM use?  Maybe it uses real hardware, or does it use a virtual device like QLX or Virtio?  I have been using virtio. I also tried QLX and it works.

See below for other questions.


On Friday, 05-07-2024 at 01:16 Christoph Pleger wrote:
> Hello,
> > To get to the bottom of the problem, I upgraded a bullseye VM
> > to a bookworm VM step by step: first libc, then the Xorg-
> > packages, then the kernel, then sddm, lightdm and gdm3, and finally
> the
> > rest. Unfortunately, it was only after the rest that the GUI login no
> > longer appeared; therefore I am not really any further with the
> answer
> > to the question what exactly the problem is.
> 
> 
> I can now tell that the problem is introduced when upgrading the
> following packages from bullseye to their bookworm versions:

Did you upgrade your full distribution or only these files?

I would never consider using packages from a different Debian version. I guess people do this?  But liking stability, it is not something I would do.

> 
> libglx-mesa0 libx11-xcb1 libgbm1 libgl1-mesa-dri libdrm-common
> libglapi-mesa libdrm-amdgpu1 libdrm2 libegl-mesa0 libx11-6
> libwayland-client0
> 
> Regards
>   Christoph
> 

I did a test, building a Bullseye VM and then totally upgrading to Bookworm and had no issues.

George.

See below for the steps I used:


Using Virt-Manager, create a Bullseye, KDE Virtual Machine using VNC to communcate to the virtio display device.

Upgrade Bullseye to Bookworm: https://wiki.debian.org/DebianUpgrade


nano /etc/apt/sources.list
(remark out Bullseye repositories and replace with the below Bookworm repositories)

deb https://deb.debian.org/debian/ bookworm main non-free non-free-firmware contrib
deb-src http://deb.debian.org/debian/ bookworm main non-free non-free-firmware contrib

deb https://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
deb-src https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware

# bookworm-backports, previously on backports.debian.org
deb https://deb.debian.org/debian/ bookworm-backports main contrib non-free non-free-firmware
deb-src https://deb.debian.org/debian/ bookworm-backports main contrib non-free non-free-firmware

apt update && apt update && apt full-upgrade -y

(allow the restart of services as the installation continues)

Let the installation run, then reboot and log back in...

A number of Errors were reported

rebooted when installation completed 

logged in and ran updates again, various packages were "Setting up" and there were a number of "Installing new version of " a config file".

rebooted when installation completed

logged back in and all worked.

Ran apt autoremove, rebooted and logged back in, all working well.

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

#270864

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-05 12:50 +0200
Message-ID<IWOFP-7PGT-1@gated-at.bofh.it>
In reply to#270859

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

Hello,

> What video device does your VM use?  Maybe it uses real hardware, or does it use a virtual device like QLX or Virtio?  I have been using virtio. I also tried QLX and it works.

It is the qemu vga driver. I already tried qemu virtio and qemu vmware
drivers, they have the same problem as the vga driver: No sddm GUI
login screen.

> > I can now tell that the problem is introduced when upgrading the
> > following packages from bullseye to their bookworm versions:
> 
> Did you upgrade your full distribution or only these files?
> 
> I would never consider using packages from a different Debian version. I guess people do this?  But liking stability, it is not something I would do.

Normally, I also do not do that. As I wrote, the GUI login was shown in
a bullseye VM (no packages from other origins), but it is not shown in
a bookworm VM (no packages from other origins). So, I upgraded a
bullseye VM step by step to find out where exactly the problem is and I
can tell now, that before upgrading   

libglx-mesa0 libx11-xcb1 libgbm1 libgl1-mesa-dri libdrm-common
libglapi-mesa libdrm-amdgpu1 libdrm2 libegl-mesa0 libx11-6
libwayland-client0
> 

 the GUI login was shown and after upgrading these packages, the GUI
login was not shown.

> I did a test, building a Bullseye VM and then totally upgrading to
> Bookworm and had no issues.

The same result for me after directly installing bookworm with virt-
manager. Obviously, there is a significant difference between a VM in
OpenNebula and a VM with the same software in virt-manager ...

Regards
  Christoph

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

#270871

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-05 17:10 +0200
Message-ID<IWSJr-12n-3@gated-at.bofh.it>
In reply to#270864

On Friday, 05-07-2024 at 20:46 Christoph Pleger wrote:
> Hello,
> 
> > What video device does your VM use?  Maybe it uses real hardware, or does it use a virtual device like QLX or Virtio?  I have been using virtio. I also tried QLX and it works.
> 
> It is the qemu vga driver. I already tried qemu virtio and qemu vmware
> drivers, they have the same problem as the vga driver: No sddm GUI
> login screen.
> 
> > > I can now tell that the problem is introduced when upgrading the
> > > following packages from bullseye to their bookworm versions:
> > 
> > Did you upgrade your full distribution or only these files?
> > 
> > I would never consider using packages from a different Debian version. I guess people do this?  But liking stability, it is not something I would do.
> 
> Normally, I also do not do that. As I wrote, the GUI login was shown in
> a bullseye VM (no packages from other origins), but it is not shown in
> a bookworm VM (no packages from other origins). So, I upgraded a
> bullseye VM step by step to find out where exactly the problem is and I
> can tell now, that before upgrading   
> 
> libglx-mesa0 libx11-xcb1 libgbm1 libgl1-mesa-dri libdrm-common
> libglapi-mesa libdrm-amdgpu1 libdrm2 libegl-mesa0 libx11-6
> libwayland-client0
> > 
> 
>  the GUI login was shown and after upgrading these packages, the GUI
> login was not shown.
> 
> > I did a test, building a Bullseye VM and then totally upgrading to
> > Bookworm and had no issues.
> 
> The same result for me after directly installing bookworm with virt-
> manager. Obviously, there is a significant difference between a VM in
> OpenNebula and a VM with the same software in virt-manager ...

Are you able to try Virt-Manager with your original VM that you are having issues with? If your VM is a KVM VM, then you should not need to install anything on the VM.

I might give setting up OpenNebula to see if I can replicate the issue. A good excuse for me to try an installation.

George.


> 
> Regards
>   Christoph
>

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

#270917

FromChristoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Date2024-07-08 15:20 +0200
Message-ID<IXWrE-GOG-3@gated-at.bofh.it>
In reply to#270871

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

Hello,

> > The same result for me after directly installing bookworm with virt-
> > manager. Obviously, there is a significant difference between a VM in
> > OpenNebula and a VM with the same software in virt-manager ...
> 
> Are you able to try Virt-Manager with your original VM that you are having issues with? If your VM is a KVM VM, then you should not need to install anything on the VM.
> 
> I might give setting up OpenNebula to see if I can replicate the issue. A good excuse for me to try an installation.

The problem does not occur in virt-manager. I did not import an
OpenNebula VM, but I can see that the problem occurs in a fresh
bookworm VM in Opennebula, while it does not on a fresh bookworm VM in
virt-manager (with the same VM software as in OpenNebula).

Regards
  Christoph

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

#270927

FromGeorge at Clug <Clug@goproject.info>
Date2024-07-08 17:00 +0200
Message-ID<IXY0q-HDp-21@gated-at.bofh.it>
In reply to#270917
Christoph,

I think this statement holds the answer:

https://opennebula.io/blog/announcements/new-maintenance-release-opennebula683/
New Features:
OpenNebula 6.8.3 introduces support for Debian 12 and removes support for Debian 10.

Thus my guess is that OpenNebula versions before 6.8.3 do not support Debian 12.

George

See below for further comments.

On Monday, 08-07-2024 at 23:10 Christoph Pleger wrote:
> Hello,
> 
> > > The same result for me after directly installing bookworm with virt-
> > > manager. Obviously, there is a significant difference between a VM in
> > > OpenNebula and a VM with the same software in virt-manager ...
> > 
> > Are you able to try Virt-Manager with your original VM that you are having issues with? If your VM is a KVM VM, then you should not need to install anything on the VM.
> > 
> > I might give setting up OpenNebula to see if I can replicate the issue. A good excuse for me to try an installation.

Thanks to "https://github.com/OpenNebula/minione" I now have a full OpenNebula 6.8.0 all in one installation running in a KVM VM.

I have been able to download a Debian 11 template from the OpenNebula Marketplace, then create a Debian 11 VM, and ssh into it.
https://marketplace.opennebula.io/appliance/8e015603-3dc2-4147-a25e-f58dced23e52

Next I want to learn how to create a Debian 11 VM with KDE installed.

I think I need to learn how to "the cloud administrator must prepare a set of Templates and Images to make them available to the cloud users".
https://docs.opennebula.io/6.8/management_and_operations/end-user_web_interfaces/cloud_view.html

Other pages that could help me.
https://docs.opennebula.io/6.8/management_and_operations/vm_management/vm_instances.html

I have much to learn.

> 
> The problem does not occur in virt-manager. I did not import an
> OpenNebula VM, but I can see that the problem occurs in a fresh
> bookworm VM in Opennebula, while it does not on a fresh bookworm VM in
> virt-manager (with the same VM software as in OpenNebula).

Thank you for testing the above. This indicates the issue you are having might not be directly a Debian Distribution issue. However more testing is required to find what is the issue.

What version of OpenNebula are you using?

My thoughts are that OpenNebula updates various settings in the VM as it creates/runs the VM, and since OpenNebula does not support Debian 12 as a OS for installing OpenNebula, maybe they have yet to design OpenNebula to create/manage Debian 12 instances? 

To backup this theory, it seems that Debian 12 support is introduced in version 6.8.3.

https://opennebula.io/blog/announcements/new-maintenance-release-opennebula683/
New Features:
OpenNebula 6.8.3 introduces support for Debian 12 and removes support for Debian 10. 



Thank you for introducing me to OpenNebula. It looks quite impressive.



> 
> Regards
>   Christoph
>

[toc] | [prev] | [standalone]

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

csiph-web