Customer experience with hypervisors untested by VSI
-
Topic author - Site Admin
- Valued Contributor
- Posts: 96
- Joined: Tue May 21, 2019 6:56 am
- Reputation: 0
- Status: Offline
Customer experience with hypervisors untested by VSI
Dear OpenVMS users,
Please use this thread to report your experience with different hypervisors not listed by VSI as compatible with the latest OpenVMS release. For the list of the hypervisors that were proven to be compatible by VSI staff, refer to this document (Section 1.2. Tested Platforms).
Please use this thread to report your experience with different hypervisors not listed by VSI as compatible with the latest OpenVMS release. For the list of the hypervisors that were proven to be compatible by VSI staff, refer to this document (Section 1.2. Tested Platforms).
Re: Customer experience with hypervisors untested by VSI
Is Galaxy still a thing?smirk wrote: ↑Mon May 01, 2023 9:02 amBeyond installing it I have not done anything but VMS appears responsive, and demonstrates that nested virtualisation works.
Perhaps unsurprisingly, the KSM feature of Proxmox (Linux) seems to happily work with OpenVMS and share it's memory pages between the various VMs.
Re: Customer experience with hypervisors untested by VSI
i zipped my config for UTM on M1, but i assume u can't upload zips?
Re: Customer experience with hypervisors untested by VSI
Consider using something like pastebin to share.
Re: Customer experience with hypervisors untested by VSI
You can perhaps paste the UTM config code here is you use the
Code: Select all
code metatag like this
Re: Customer experience with hypervisors untested by VSI
it's a directory which behaves like a file (like a application on MacOS). i can upload the template somewhere
Re: Customer experience with hypervisors untested by VSI
Why doesn't the "Attachement" tab work?
Why would ZIP's be not allowed?
Why would ZIP's be not allowed?
Re: Customer experience with hypervisors untested by VSI
Inside that file, there is a config file called `config.plist`. That is the most useful thing to share. The rest of that directory contains the disk images etc. and is not necessary to share.
Re: Customer experience with hypervisors untested by VSI
I've managed to get VMS 9.2-1 installed on qemu on Debian (Buster)
I had some 'fun and games' sorting out exactly how to configure qemu from the command line but once that was sorted everything just worked. Very lovely indeed..!
I've done a quick write up here.
Rather amused to discover that my login .com (that I've been using for about 30 years) had a syntax error in an if statement that earlier versions just ignored and that I'd never noticed.
Great job
Mike T.
Code: Select all
$ kvm --version
QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-8+deb10u10)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
$ virsh version
Compiled against library: libvirt 5.0.0
Using library: libvirt 5.0.0
Using API: QEMU 5.0.0
Running hypervisor: QEMU 3.1.0
$
I've done a quick write up here.
Rather amused to discover that my login .com (that I've been using for about 30 years) had a syntax error in an if statement that earlier versions just ignored and that I'd never noticed.
Great job
Mike T.
Last edited by mike632t on Sat May 06, 2023 9:02 pm, edited 1 time in total.
Mike T.
Re: Customer experience with hypervisors untested by VSI
The KVM qemu setup is straight forward, what is needed here is the non-kvm qemu-system-x86_64 simulator config for qemu (where kvm is not possible)
-
- Valued Contributor
- Posts: 73
- Joined: Tue Mar 22, 2022 6:47 pm
- Reputation: 0
- Location: England
- Status: Offline
Re: Customer experience with hypervisors untested by VSI
Host: AlmaLinux release 8.7 (Stone Smilodon)experience with different hypervisors not listed by VSI
MoBo: H81M-PLUS (ASUS)
Memory: 16 GiB
CPU: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
First attempt: Cockpit -> Virtual Machines
Configuration as per release notes was difficult and the installation failed with minimal information.
Second attempt: Virtual Machine Manager
Easy to configure and install. Once installed it was possible to control it through the cockpit application which is Red Hat's preferred method. The start the VM boot it through cockpit, then use cockpit to create a remote viewer graphical console, boot VMS and then use the inbuilt serial console in cockpit.
One happy bunny here! Thanks to VSI for developing the community scheme and bringing us the X86 version.
Martin
- Retired System Manager: VMS/UNIX/UNICOS/Linux.
- Started on a VAX 11/782 in 1984 with VMS 3.6.