Page 4 of 5
Virtualbox and VMDK
Posted: Tue Apr 02, 2024 6:48 pm
by aussiesusan
Environment: Windows 11 (fully patched) on an IntelNUC PC.
Installed VirtualBox 7.0.14r161095.
From the email I have downloaded the VMDK zip file and expanded ot to get the 2 VMDK files ('community' at 637 bytes, and 'community_flat' at 5.37GB).
Using the link in the email (
https://d2h1r304.na1.hubspotlinks.com/C ... jf9fL1Z204) and following the 'Windows GUI' section, I get to the guide in step 2 (
https://docs.vmssoftware.com/vsi-openvm ... eateVboxVM) but there my problem starts.
Step b) says to set the ISO image to the OpenVMS ISO file - is that the VMDK? If so which one?
If I try to use the VMDK image (either one) I get
Failed to open the disk image file C:\Users\Susan\Downloads\community.vmdk.
The medium 'C:\Users\Susan\Downloads\community.vmdk' can't be used as the requested device type (DVD, detected HDD).
Result Code:E_FAIL (0X80004005)
Component:MediumWrap
Interface:IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee:IVirtualBox {7682d5eb-f00e-44f1-8ca2-99d08b1cd607}
Callee RC:VBOX_E_OBJECT_NOT_FOUND (0X80BB0001)
What am I doing worng?
Susan
Re: Virtualbox and VMDK
Posted: Mon Apr 22, 2024 5:03 pm
by sms
Code: Select all
> [...] Putty [...]
> [...] PUTTY [...]
I use xterm, not PuTTY, for my console terminal emulators, so I know
nothing, but if PuTTY settings were causing the problem, I'd expect the
original password entry to suffer similarly:
> [...] after putting first pwd as : alphabits000000(supplied by VSI)
>
> Your password has expired; you must set a new password to log in
But it apparently worked.
If the original password entry works, but SET PASSWORD fails, then
I'd tend to classify that behavior as a defect.
Re: Virtualbox and VMDK
Posted: Mon Apr 22, 2024 11:43 pm
by gdwnldsksc
jonesd wrote: ↑Mon Apr 22, 2024 8:01 am
The claim in
https://wiki.vmssoftware.com/Windows_ho ... ox%20host. is that running with hyper-V enabled is slower than if disabled. This is echoed in
section 2.33 of the Virtualbox documention. Has anyone tried to measure this effect with a VMS guest (e.g. compare the CPU and elapsed time from the sysinit accounting shown on the console)?
Does your CPU icon have a green turtle?
Yes to the green turtle.
Some things are "noticeably" slower but not in an impactful way, as I require (both for testing and for policy reasons) all these security functionalities to be enabled, so I can't give a same-machine comparison with Hyper-V disabled.
I have a vCenter instance, a VMS instance, and two OS/2 instances running right now in such a manner that they're perfectly usable, as well as multiple vBOX VMs at the same time.
I'd say the slowdown is mostly in I/O (and it's not really bad at all), because Hyper-V is only being used as the CPU execution engine, and vbox/vmware are providing their own hardware emulation still. (Which is awesome, because I can run my NT3.1/3.51 VMs in vbox that i can't run anywhere else using some hand tuned CPU compatibility settings).
The vast majority of my local virtual machines, however, are all in Hyper-V. I only fall back to VBOX/VMware for compatibility reasons if needed.
Re: Virtualbox and VMDK
Posted: Tue Apr 23, 2024 12:06 am
by vmsxpert
thanks for replies .
Able to login and change pwd . But its difficult to put cmds as I am not able to view whats being written till the time it gets executed .Also i want to configure decnet and tcpip (so that remote login could be enabled) , but that could be done only if i am able to open com files correctly .
Its not working smooth on this telnet console . can u pl suggest any ways to come out of it .
Re: Virtualbox and VMDK
Posted: Tue Apr 23, 2024 1:19 am
by sms
Code: Select all
> Able to login and change pwd . [...]
That's nice. And you achieved this result _how_, exactly?
> [...] But its difficult to put cmds as I am not able to view whats
> being written [...]
"Not able" is not a useful problem description. It does not say
what you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, ...) can be more helpful than vague descriptions or
interpretations.
Are you trying to say that characters are not echoed in your PuTTY
window when you hit normal (alpha-numeric) keys?
> [...] till the time it gets executed . [...]
By "the time it gets executed", do you mean when you hit the <return>
key? General advice: Describe actual actions and actual observed
results, not what you think it all means.
My PuTTY expertise is still minimal, but a Forum search should find
much discussion of PuTTY settings, not to mention TFM (as in, "RTFM"):
https://docs.vmssoftware.com/docs/vsi-openvms-x86-64-boot-manager-user-guide-922.pdf
> [...] that could be done only if i am able to open com files correctly
> . [...]
Are you simply elaborating here on your complaint about PuTTY
behavior, or is there something else wrong?
Re: Virtualbox and VMDK
Posted: Tue Apr 23, 2024 7:17 am
by alexwong
See attached PDF for putty settings which works for console login to x86 OpenVMS. The port 2023 must match virtualbox's Serial Port COM1 Path/Address setting. I also add the following in SYLOGIN.COM
$ set term/insert/dev=vt102
$ edt:==edit/edt
Re: Virtualbox and VMDK
Posted: Tue Apr 23, 2024 10:10 am
by imiller
I have a raw putty session for the console and a standard telnet or ssh one for normal use.
I usually set windows translation to DEC-MCS too IIRC that helps with running MONITOR.
Also usually set width to 132 instead of 80 as there are some displays that work better with 132 columns.
Re: Virtualbox and VMDK
Posted: Tue Apr 23, 2024 11:36 am
by arne_v
alexwong wrote: ↑Tue Apr 23, 2024 7:17 am
See attached PDF for putty settings which works for console login to x86 OpenVMS. The port 2023 must match virtualbox's Serial Port COM1 Path/Address setting. I also add the following in SYLOGIN.COM
$ set term/insert/dev=vt102
$ edt:==edit/edt
I always recommend people to try to get to VT200 or higher (probably no reason not to go for VT400) and 8 bit.
Some VMS stuff may expect that.
And VT200 did "replace" VT100 more than 40 years ago.
Re: Virtualbox and VMDK
Posted: Wed Apr 24, 2024 6:36 am
by alexwong
Yes VT102 is a bit dated, VT200 is good esp if you have Reflections which is a better emulator. Attached new putty settings that works with EDT and line drawings in MON SYS.
Re: Virtualbox and VMDK
Posted: Thu Apr 25, 2024 12:30 am
by vmsxpert
I have setup the m/c now (through vmdk disks)and trying for tcpipconfig and decnet config .I am trying through these cmd procedures : @sys$manager:TCPIP$CONFIG.COM (for tcpip) and @sys$manager:net$config.com (for decnet).
But i am not able to start decnet though tcpip services i could start .
can anyone give me correct procedure to config both services . I have attached my logs .
$ tcpip ifconfig -a
IE0: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>
*inet 192.168.1.23 netmask ffffff00 broadcast 192.168.1.255 ipmtu 1500
LO0: flags=100c89<UP,LOOPBACK,NOARP,MULTICAST,SIMPLEX,NOCHECKSUM>
inet 127.0.0.1 netmask ff000000 ipmtu 4096
TN0: flags=80<NOARP>
TN1: flags=80<NOARP>
Re: Virtualbox and VMDK
Posted: Thu Apr 25, 2024 1:29 am
by sms
Code: Select all
> @sys$manager:net$config.com (for decnet).
SYS$MANAGER:NET$CONFIGURE.COM?
> [...] i am not able to start decnet [...]
> "Not able" is not a useful problem description. [...]
Still true. See above.
> [...] I have attached my logs .
I see TCPIP-CONFIG-LOG.txt; nothing about DECnet.
> Enter Internet domain [x]: skc.com
That's a real-world domain. Is it yours?
> [...] tcpip services i could start .
Does that mean that you're happy with TCPIP operation?
> can anyone give me correct procedure to config both services .
I wouldn't day that there is one universal "correct procedure" for
either one. (For example, I've never configured a VMS system as a DHCP
client.)
Do you have other VMS systems? Have you an actual use for DECnet?
It could be handy, but it wouldn't be a top priority for me if this was
my only VMS system. Also, I'd say that configuring DECnet-Plus is more
complicated than configuring TCPIP, especially for a DECnet novice.