:: Re: [DNG] Pardon my ignorance (Daed…
Top Page
Delete this message
Reply to this message
Author: Steven
Date:  
To: dng
Subject: Re: [DNG] Pardon my ignorance (Daedalus desktop in proxmox)
On 2024-04-11 21:50, crichmon wrote:
> This question isn't exactly Devuan related, but.
> In furtherance of my son's education (and my escape from Windows), I'm
> installing a full
> devuan_daedalus_5.0.1_amd64_desktop.iso in a VM in proxmox. Installation
> went OK
> except for a failure when I included Web Server in the Software

Install step
> (took a couple of tries to figure that out).
>
> I've zero familiarity with modern Linux desktops and picked whatever

was at
> the top of the list.
> Not the current problem, but the point is to find out what I can run in
> Wine.
>
> >From the VM config, I picked VirtIO-GPU for display. The VM boots

OK, but
> within the proxmox
> Console view. My question is; how do I boot this so that I get a full KVM
> interface. Meaning; the
> VM controls the KVM bits? To complicate the question, I've got several
> computers hooked to
> a KVM switch, including this proxmox host. When I switch to that port, I
> get the proxmox login,
> in this case, while the VM isn't running.
>
> Up to this point, I've started a VNC server and run a bunch of xterms in
> twm and been happy
> using a VNC client in Windows. Any suggestions are welcome.
>
> Thx, Chris
>
>
>


If I am understanding your intent correctly, you would like to use
Proxmox Virtual Environment (PVE) to host virtual machines (VMs). Using
the VMs as if directly working on (log into and using) each VM. This is
similar to remotely accessing workstations, servers, etc., on a network.

Though it may not be obvious, PVE is a virtual network environment with
the hosted VMs on this virtual network. In which case remotely accessing
the VMs on this virtual network is the same as on a physical network
with physical machines i.e., Some kind of remote desktop Viewer for
graphical user interface (GUI) and SSH for non-GUI access. The PVE
console for each or any VM can be used, however, this requires logging
into  the PVE web-GUI interface and working form there. This requires
giving all users access the PVE, not recommended.

SSH is install by default on Devuan and most GNU-Linux installation. For
MS Windows  Putty can be installed and used.
Windows RDP can be used to remotely access MS Windows machines, however,
Remmina, available on GNU-Linux machines, support multiple remote access
protocol including RDP, SFTP, SSH and VNC.

PVE can host VMs and LXC containers. For remote GUI (remote desktop)
access I recommend using VMs.
Using VMs for remote GUI access requires either passing-through a
physical graphics card from the PVE host, or using a virtualized
graphics card.

Passing-through a physical graphics card to a VM results in only that
one VM being able use that card. Therefore, a physical card is required
for each VM. This gets costly and is likely impractical.

Using virtualized graphics card is less costly and more practical.
However, VirtIO-GPU performs poorly. With PVE  I've found that the best
option is to use Spice/qxl combination. I have successfully used this
combination for sometime now without any noticeable latency.
In PVE set the VM disply to SPICE/qxl and install the qxl
drivers/modules in the VM. On GNU-linux install and use Remote Viewer
(virt-viewer).
See the following Proxmox Spice web page for details:
 https://pve.proxmox.com/wiki/SPICE

Suggest reading the following pages:
https://pve.proxmox.com/wiki/Main_Page
https://pve.proxmox.com/pve-docs/
https://pve.proxmox.com/wiki/Category:HOWTO

Please note that PVE is built on Debian which means dealing with Systemd!



--

Steven
202 281 4272