• GUI-Login on bookworm-VM in a cloud

    From Christoph Pleger@21:1/5 to All on Tue Jul 2 13:50:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaD5rUACgkQcOXIip7d 3fHokg/7BzP3PFzw4tCTkB4dIhn5HANWLQZzhrJFVZWwNYeblTA41JmcQY3xwk4D kAJWp2vVH853tUyjjheHVHoKRXWSDpMDz8VGgkArB8wWWfa3Xnnzwlg50WWzLftj YVjM0pQ9ldjT729gCxxN30jfMxvfTUfR8qgAL5jUNZLgs7myTy6u15ZzDUQeXSdG QvKHJcRsNC2nwaPFM+jjV+M/D7AsDNPTC7IJQJeDBr0m1L/OruX/4p2Y+FGESWi7 45ezcYlUNAD3JjIOMvHlaiEyGMPCwEUbAd6vtJ9yx1byzAveIajhssawqRfr6xW6 xd0almnCtLxkYM0f4aaVl8Q+eZM5PdEzr7H2KGFntji+ZMlj5sGMOYb30Q5aTMzQ fJ1/1B1OcKYH+Y4ygOEG8qfEGrWkp+XbIo2oYpoAnHPl3APNcKUF6jvn2dvW/k6s YMQoZHF4QSHPx/mZHZVJzH6rFlvgjSVRXDNT7W+kxTVSezxp5M/Jz3IasXVZqV6G 3vIKsRzXR2ajTpvsVnfNNcBgHSUO0Nt3S+NpKRXWwAm5l0KP2YyIBSUCqn3VGc59 g17xJdxtn/OKX9O7sH8ST240wUbstB8dC9QMRU0BUFO3WVNuPKlXb+nJXYAEHbHp UQSPZq62Yx+goYn72bJ82CgHP0KYAlHFtm10fqnUCOOn28kHjnQ=
    =rrjx
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Wed Jul 3 06:30:01 2024
    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


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Pleger@21:1/5 to All on Wed Jul 3 09:50:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaFALcACgkQcOXIip7d 3fEHSRAAiFikeAGfkttKtjHjKYaHVxP+vRQjW6pZB1Prt55jy0CQg7jri3KYupv+ 7q78uOGmAN/ZZDR7qpruT6EM1xu3LaTZtP9fQIyhSR/sof5f6BE8AQHhcAkUbreW LkvaFt0SAkP+X6nMJW7SuBYK9Yi3u0H+DPCOoql9zaoqQC24HNdMo59ZHZOrK8j0 Jibeo/4sMyYJ0knqRcYSrKVuoIyf6kI65uZHcy5/Onwpasb4u8LaYnCpeLN00lKD +COYojH/n3MF3bao1s1qjM40rlHqkT6/L1WOij6BpseZpPfN6oBcBnk4XKalcyJY KyNP6IWr0ZdvhprQmHU8sX8YiRq0j8oHPAJ8E0piV9Drbhy88zNywHQusBZCLAoT O8qK6OIJaBdAOrLvnXahAEIsbg8tqQ4AgC5N3RHVGiq08iOFQP0B1WJx4F2FXZlR BR0lMCpf0kAFbB/+cMud97FpQ703QUrBJxVF9I97UhdUMr3jG6tsuf3dRCglbzdo 75fpNjrchPXwx7EnEk9ntGR+kFoW1WhYlTCPm1AoUqsKBi0mM3Cs2uChNq/FI45G EvdseRr+eOQ3DIxFfGgkG/Q3lQ9bZlsEt504P5sCasLJmYD0a5iIoOWsicdbRUG8 5NdOrII7wCJmlZxVHRgHoaat/0oJVbp/O/VktN0wa8PryG7gcVE=
    =AIuo
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Thu Jul 4 03:10:01 2024
    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


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Thu Jul 4 04:40:01 2024
    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




    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Pleger@21:1/5 to All on Thu Jul 4 09:20:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaGSvUACgkQcOXIip7d 3fGNbg//RtW79AT+um0kR4QrA9Hov1njNbcSufjDtXPEqAaqEtm+4tsbQgygq9Tx lJz0bDLWd6ZRJZ3jsAF2vw1lIVkjuWgJ178F7U4vr0MbkCP0aJZgS4OKPnUjGpBo 2uRUcsp70uJhbg3M8WRjgj0+mJPhwY8y3XRxFJLttXuGyKlx9CtM/GnHlrtrxnQh IpcNqZY2nCXp2SOfveuKCEmLcr2ksi+BnZQ8O3QsA8wEe6Wyn+rsxJ12a4iWxd/l Q5j5KDlLBed/3C+LlWQEojYNdVG+Znnucqngy3291NNNFzA4wRV22+1S/l0I414m qbZvaZMSpgMhDP1C1RbzDBdYyVgGlOp9LfFsS45+2gwRfQXYXCH9GojYtdvZY0hB vbi55w3kxaSJHSAL7wlRxObD1XzCmIKdtwRPT8gBlUZwlAtCL4Lk24f2TDNKJvRF YTPBN4nUuXpZtgSpvMPMrut9VwiuB752SWG5b9rrgw94Py4mrihcaqYEyQXsgGmt cRS37N4Pz0AcNEUpA+Wu5ZecWSe+ezzM/6nTAs7MsjrS3ytOOk98kqaLXRYngCgV Ie1cfSTHcVxoab0UNIIXKCeoaBkp5RQ/3+DDqZwCslLw5hm1oRLS/wwMvgMmIW/I b1sIa8ptbD6Hl1o5ROrsZHQSsjBAGDeDd4bj3oW2/w0NtyYuX1w=
    =j4ia
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Pleger@21:1/5 to All on Thu Jul 4 17:20:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaGvM8ACgkQcOXIip7d 3fEYZA/+NOTChwsfS9TytzLyCYOk8uvUcEK+QWwACBm1gUDt5ErV5F2ho22p2RN0 w+5Uddbm5z9VurnrMBvk81jocHkethe4N76wRiF1+eyUYfJ9LZCJVRUhZutkOdx6 Qo0XjGQ8f7QBbJ7TyqdcA/CZkM9Nzqlih01o+JOcEw5gQDV5MxSsQ8wEI2iNrEMS DsBP3hV9SDHOpszqYNPYC9hkx2Mm+EIIxwJV1v24iP7d4lvg8cuVDAuHRPVn7Rz1 z/3FSMpWyh+DAZMARsdX4UCQV6fWRX4L2Wbwm/s648UX+W3CQJ04akJ/oJh0eNol qSUop/BG+jprXRmoRtLcTCFzBQo79j25/+CPiBv1D2TCdBKiwiYJ+lVKx9eR7ChX KT6XIAKNHHixU3GJmPgbagp1cBnc57Kybcmx/+HZFVfMmE51GOrA8tV0zDbVds5d iKAPpqoC7ELC+MplEAFIjofjV9GYKgMJhfjcgOckkObsO9RzcPsuNR8jU3hz3oez v+xx9mwDP5bnC836IF8FBPRdp6x3X+a3hTLxHmeLAKgr9UzksF0pLbdM6yjUxQts HvPSeem3W7mBSfICjxH2j6Bj/Yg3Q1j0w0dwF5/ZzHDrgwXueN+IbXzBttn5gGn0 fkEQy8h1W5nb7CrnSb380GqdSfJh6789Jc3oxUTp4Vj7zMSCwSQ=
    =KA0F
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Fri Jul 5 10:40:01 2024
    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.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Pleger@21:1/5 to All on Fri Jul 5 12:50:01 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaHzxgACgkQcOXIip7d 3fGekw/5AQJT2Tj43BR7vWIMi1QJHQtSDHJ2vU5VDiK5DWLgqEzGBfYx8IUudu9h v6LGlr4idEw4L7FAkRsEoW05ZTEGlkYPgRXzomakAUtCluo0Upeei4MgeAg8g81w 3oObdlmzu5f/MvdBWHEkW1sVJcPlnzTP53tUHAzlovNYmaU5Cja8EpGWIpBlCan+ b732ukTzzXl1n2POqPCtzt+XJtubGW8UojLVK7o0TBFUAcoSKesCZtL5417DdTfJ oXiqSF8nNZtcgkFa/tMLBVJqXCotVSfv5fR1B42VhUmpgqYJlWYMhpBTWIBFrJqM xvM86lnj6u/AsA2VTTOjV2HNFZkLzfJI1c0aRKp/ZtDkdPdNsxWzFwB1DxQSGXcs UyetX5lSkWPHNwcKeBFChA6Wi0k4IsSNfZjqH2vsm99IbAZ+TD1g1b031NhGTUuH KbGJ+XbrhuVzT47lPG1z5CNEMbKvifHR2FqQ/avvVD1G0uhJw+xUy/nRPGMoGCa+ EReWUiVW4PCshxrKe7oIf7BXhzWDj2VudyuP5OIm2NhtiBlx60XvSZo4I7sVFfmA Fgl7+lNbjXyhXxi0BlcfZ7lFjOTM2qxGsdAmC+gsj9xjcSHrHxs6QgkXnOGL4yuC Ul63EvPV1Zc7hsKaGeFxqeypIijjaKvA6Ozus6GRaWwBr+XKm9A=
    =yBTx
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Fri Jul 5 17:10:01 2024
    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


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Christoph Pleger@21:1/5 to All on Mon Jul 8 15:20:02 2024
    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

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEHeqYcooFjlnR4zwFcOXIip7d3fEFAmaL5VIACgkQcOXIip7d 3fGkSQ//WTPbsXg5hpuvx4vMDSKCztyeSpu04p4xD40/YtEtnn7Ne2qtBBeHuzC1 zlUxhCsf0+O7coIz+rdpl+uEWiQkGer7DjSkPOxCUd+tcxT8poEeRV3H81ECP9xA TzjfwudLcnSHLmxfwfmfdak8dmoPgGGJy79Mf2oBlupUUQyrBRiUpPCpYa0l+k1t jNv1jZTZ8lCnwoP26jotgqSlrv3dAmpbqRpx/A67RFEm1q9P78MYXjhwptcu4TLy WAN6NpiLdV3z04eyEfsK+vUNMX6sON1DIUxr9bDiwDmdgo76uhgdNXI3CBmi1RID XKYp/zRbcKOeBR/2aK6kbfLgNN/8Iv3vgz70f6O+E01+94odx9nNZWm5Ixv3c2Kk bw3NlFr3XNFAG1edK4+9AOIbCkQlEp5IZZCorQdzKmYovD4Q2Ur4hRt6lnneA+jo RqH+GMywu45gZ/0nYltiWcxGRHI1Ut99Bcnv6YqsWX12eVyDAJUXsqvNP1a4n4To mpS57cu2MvykVuIrKCW4NdBx747hM+TYx1bLRICz/61VrywAmxXEKR0m3sh9zE30 hRK+1eThhdrSDk5/6WhXzRLC2GGQeUxy/y5Xro2EEqsLxZXH9m06G0bWUyr+foy7 D/yYKnyuJp8JjEaxzZSd/KSs421H/h5hzPhZDudABm5pKVv1Dcs=
    =1fCo
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Mon Jul 8 17:00:02 2024
    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


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)