• ProxMox/KVM Serial terminal via ssh/telnet - WAS: OpenVMS x86 and qemu/

    From John H. Reinhardt@21:1/5 to Chris Townley on Tue May 28 15:40:28 2024
    On 4/20/2023 1:33 PM, Chris Townley wrote:
    Have you managed to get he serial console accessible over ssh? So far I have been stuck with the Virtual Machine builder serial console, which is pretty carp.


    I've got a ProxMox V8.2.2 instance running now. It boots the OpenVMS V9.2-2 ISO but for the life of me I can't get ssh/telnet setup to the serial console. The documentation for this is quite obtuse. As with you I have the serial console connected in
    the ProxMox console but I want to be able to telnet or ssh to it from other places than where the web gui is running.


    --
    John H. Reinhardt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Townley@21:1/5 to John H. Reinhardt on Tue May 28 23:58:05 2024
    On 28/05/2024 21:40, John H. Reinhardt wrote:
    On 4/20/2023 1:33 PM, Chris Townley wrote:
    Have you managed to get he serial console accessible over ssh? So far
    I have been stuck with the Virtual Machine builder serial console,
    which is pretty carp.


    I've got a ProxMox V8.2.2 instance running now.  It boots the OpenVMS
    V9.2-2 ISO but for the life of me I can't get ssh/telnet setup to the
    serial console.  The documentation for this is quite obtuse.  As with
    you I have the serial console connected in the ProxMox console but I
    want to be able to telnet or ssh to it from other places than where the
    web gui is running.

    I never managed to get any serial terminal running, but I am on KVM/QEMU
    under Ubuntu - I don't know anything about Proxmox.

    I got a PuTTy instance running on the host, then issued:
    $ virsh console <VM_name>

    That works well as a console.

    When DECNET, TCP and SSH installed - my network is bridged to the host's
    second NIC, I has no problem using ssh from my Windoze workstation


    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John H. Reinhardt@21:1/5 to Chris Townley on Tue May 28 21:32:08 2024
    On 5/28/2024 5:58 PM, Chris Townley wrote:
    On 28/05/2024 21:40, John H. Reinhardt wrote:
    On 4/20/2023 1:33 PM, Chris Townley wrote:
    Have you managed to get he serial console accessible over ssh? So far I have been stuck with the Virtual Machine builder serial console, which is pretty carp.


    I've got a ProxMox V8.2.2 instance running now.  It boots the OpenVMS V9.2-2 ISO but for the life of me I can't get ssh/telnet setup to the serial console.  The documentation for this is quite obtuse.  As with you I have the serial console
    connected in the ProxMox console but I want to be able to telnet or ssh to it from other places than where the web gui is running.

    I never managed to get any serial terminal running, but I am on KVM/QEMU under Ubuntu - I don't know anything about Proxmox.


    ProxMox is based on KVM, but it's got cluster aware parts. There is a distributed, shared file system that it interfaces to called Ceph (as do others). The aim is to have shared virtual disks for VMSClusters with common shared drives. Not sure if that'
    s possible yet, but I think all the parts are there.

    ProxMox - https://www.proxmox.com/en/
    Ceph - https://ceph.io/en/

    I got a PuTTy instance running on the host, then issued:
    $ virsh console <VM_name>

    That works well as a console.

    When DECNET, TCP and SSH installed - my network is bridged to the host's second NIC, I has no problem using ssh from my Windoze workstation



    --
    John H. Reinhardt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael Brown@21:1/5 to John H. Reinhardt on Fri Jun 7 12:42:38 2024
    On 29/5/24 06:40, John H. Reinhardt wrote:

    I've got a ProxMox V8.2.2 instance running now.  It boots the OpenVMS
    V9.2-2 ISO .......
    Is there a secret to getting the network device working under proxmox ?
    I used e1000 as the device model but during bootup it sends the cpu
    usage up to 100% and just freezes. Using other device models some will seemingly fail immediately and the bootup goes ahead but you end up with openvms running but with no network device available.

    Have you seen anything like this happening before.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From John H. Reinhardt@21:1/5 to Michael Brown on Sat Jun 8 23:34:30 2024
    On 6/6/2024 9:42 PM, Michael Brown wrote:
    On 29/5/24 06:40, John H. Reinhardt wrote:

    I've got a ProxMox V8.2.2 instance running now.  It boots the OpenVMS V9.2-2 ISO .......
    Is there a secret to getting the network device working under proxmox ?
    I used e1000 as the device model but during bootup it sends the cpu usage up to 100% and just freezes. Using other device models some will seemingly fail immediately and the bootup goes ahead but you end up with openvms running but with no network
    device available.

    Have you seen anything like this happening before.

    Go back to using the e1000 device. After you create the VM, but before you boot it, edit the VM config file /etc/pve/qemu-server/<vid>.conf

    Add "args: -machine hpet=off" if it's not already there. If it wasn't there, then that should fix the problem.

    This is my current test config file:

    pve011:/etc/pve/qemu-server# cat 100.conf
    args: -machine hpet=off
    balloon: 0
    bios: ovmf
    boot: order=ide2;sata0;sata1;net0
    cores: 2
    cpu: host
    efidisk0: local-lvm:vm-100-disk-0,efitype=4m,size=4M
    ide2: local:iso/X860922OE.ISO,media=cdrom,size=1517408K
    machine: q35
    memory: 8192
    meta: creation-qemu=8.1.5,ctime=1717891692
    name: openvms-test
    net0: e1000=BC:24:11:A5:FB:1A,bridge=vmbr0,firewall=1,tag=16
    net1: e1000=BC:24:11:0D:4F:69,bridge=vmbr0,firewall=1
    net2: e1000=BC:24:11:0C:52:86,bridge=vmbr0,firewall=1,tag=20
    numa: 0
    ostype: other
    sata0: local-lvm:vm-100-disk-2,discard=on,size=16G,ssd=1
    sata1: local-lvm:vm-100-disk-1,discard=on,size=16G,ssd=1
    scsihw: virtio-scsi-pci
    serial0: socket
    smbios1: uuid=1fa8bf23-cff3-4746-91cb-d9fed4ea99c5
    sockets: 1
    vmgenid: ce4c0615-9dc0-46e5-8f5c-5a4eca5b7647


    --
    John H. Reinhardt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael Brown@21:1/5 to John H. Reinhardt on Wed Jun 12 14:20:30 2024
    On 9/6/24 14:34, John H. Reinhardt wrote:
    On 6/6/2024 9:42 PM, Michael Brown wrote:
    On 29/5/24 06:40, John H. Reinhardt wrote:

    I've got a ProxMox V8.2.2 instance running now.  It boots the OpenVMS
    V9.2-2 ISO .......
    Is there a secret to getting the network device working under proxmox ?

    Go back to using the e1000 device.  After you create the VM, but before
    you boot it, edit the VM config file /etc/pve/qemu-server/<vid>.conf

    Add "args: -machine hpet=off" if it's not already there.  If it wasn't there, then that should fix the problem.


    Yes! that was the secret. vms boots up now and is on the net. Thank you
    muchly.

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