On 24/01/2013 06:35, Ian McLaughlin wrote:
On 2013-01-23, at 9:28 PM, Cory Smelosky <b4 at gewt.net> wrote:
Eeeeeep! Was it an important tape?
AQ-JP22D-BE VMS V5.2 BIN TK50 1/2
I think I have another copy somewhere. I'm suspecting that the TK50 drive in this external SCSI chassis might be bad...
Ian
Ian,
This is usually down to the tape rather than the drive.
It is recommended that you 'bake' old tapes before reading them - over time they become 'sticky'. IIRC a couple of hours at around 50 degC.
I have a load of tapes that I need to read off but I've currently got no way of baking. I suspect that a standard oven, even on it's lowest setting, will be too hot - you need something like an incubating oven. I know someone who used to do this on a regular occasion and had very few failures using this method.
Regards, Mark.
On 1/23/2013 8:57 PM, Johnny Billquist wrote:
On 2013-01-24 02:44, Brian Hechinger wrote:
On 1/22/2013 9:15 PM, Cory Smelosky wrote:
Is that a proper Xeon or a P4 Xeon?
If it's a quad core it's a core2 arch xeon. P4 (Pentium-D) only came in
dual core.
Gents... Fun as all the small talk is, this is getting a little much outside of hecnet stuff, isn't it?
Johnny
It's iffy... Since we're discussing a host where a SIMH-11 VAX might run with a HECnet connection.
Besides, Sampa started it. (Sorry about throwing you under the bus)
John H. Reinhardt
On 2013-01-23, at 9:28 PM, Cory Smelosky <b4 at gewt.net> wrote:
Eeeeeep! Was it an important tape?
AQ-JP22D-BE VMS V5.2 BIN TK50 1/2
I think I have another copy somewhere. I'm suspecting that the TK50 drive in this external SCSI chassis might be bad...
Ian
On 23 Jan 2013, at 21:09, Dave McGuire <mcguire at neurotica.com> wrote:
On 01/23/2013 08:38 PM, Brian Hechinger wrote:
but it's nice to be able to just
create a VM with a few measly clicks. The downside is that I have to
run the VMWare vSphere Client on a Windows platform. In this case it's
Windows 7 running on my Mac Pro inside a VMWare Fusion VM.
You can do a lot of stuff from the BB shell within ESXi, though the
command structure is somewhat obtuse. It's handy in emergencies. If
you're just bringing up or shutting down VMs, etc, it's very easy to
deal with, and you don't need to sully yourself with Winblows and end up
with that "not so fresh" feeling.
With the move to ESXi from "full blown" ESX VMware has been moving more
and more out of the ESXi host.
Are they reducing the functionality that's available there? I don't
*want* full-blown ESX.
I wish I could tell. The product descriptions on the website are a bit too full of buzzwords for me to figure out what's actually being said.
The things you can do in BB are *very* limited.
Nah. Here's my quick cheat sheet, which is only the stuff I've used:
vim-cmd vmsvc/getallvms # lists VMs
vim-cmd vmsvc/power.getstat <vmid> # get power state
vim-cmd vmsvc/power.on <vmid> # power on VM
vim-cmd vmsvc/power.off <vmid> # power off VM
vim-cmd vmsvc/power.shutdown <vmid> # shutdown
vim-cmd vmsvc/power.restart <vmid> # restart
vim-cmd hostsvc/maintenance_mode_enter # enter maintenance mode
vim-cmd hostsvc/maintenance_mode_exit # exit maintenance mode
vim-cmd vmsvc/unregister <vmid> # remove VM from inv.
vim-cmd solo/registervm /path/to/<filename>.vmx # add VM to inv.
vim-cmd vmsvc/message <msg_num> # get messages
So, basically anything except creating a new one or re-provisioning
disks or other resources...and I've done THOSE from the BB shell as
well, though not often enough that I've put it in my cheat-sheet.
Useful cheat sheet.
However, you can download the API tools (perl or PowerShell versions
available) or install the VMA (Virtual Management Appliance, just a
linux box with the tools already installed) you can do everything you
need to do from the CLI of your favorite OS.
Got a link for that? And will it work with 4.1?
A quick google seems to only mention it for 5.0 :(
If you can use vCenter, the web based GUI in 5.1 is FANTASTIC and only
required flash. Works fine in Chrome.
If you need keys for 5 I might *cough* know *cough* where *cough* to get
some. *cough cough*. :)
Hmm! Please to be sending! Can I do an in-place upgrade from 4.1 to 5?
I could use a key I think .I'm not sure which product I want through due to the number of buzzwords on the website.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
On 01/23/2013 08:38 PM, Brian Hechinger wrote:
but it's nice to be able to just
create a VM with a few measly clicks. The downside is that I have to
run the VMWare vSphere Client on a Windows platform. In this case it's
Windows 7 running on my Mac Pro inside a VMWare Fusion VM.
You can do a lot of stuff from the BB shell within ESXi, though the
command structure is somewhat obtuse. It's handy in emergencies. If
you're just bringing up or shutting down VMs, etc, it's very easy to
deal with, and you don't need to sully yourself with Winblows and end up
with that "not so fresh" feeling.
With the move to ESXi from "full blown" ESX VMware has been moving more
and more out of the ESXi host.
Are they reducing the functionality that's available there? I don't
*want* full-blown ESX.
The things you can do in BB are *very* limited.
Nah. Here's my quick cheat sheet, which is only the stuff I've used:
vim-cmd vmsvc/getallvms # lists VMs
vim-cmd vmsvc/power.getstat <vmid> # get power state
vim-cmd vmsvc/power.on <vmid> # power on VM
vim-cmd vmsvc/power.off <vmid> # power off VM
vim-cmd vmsvc/power.shutdown <vmid> # shutdown
vim-cmd vmsvc/power.restart <vmid> # restart
vim-cmd hostsvc/maintenance_mode_enter # enter maintenance mode
vim-cmd hostsvc/maintenance_mode_exit # exit maintenance mode
vim-cmd vmsvc/unregister <vmid> # remove VM from inv.
vim-cmd solo/registervm /path/to/<filename>.vmx # add VM to inv.
vim-cmd vmsvc/message <msg_num> # get messages
So, basically anything except creating a new one or re-provisioning
disks or other resources...and I've done THOSE from the BB shell as
well, though not often enough that I've put it in my cheat-sheet.
However, you can download the API tools (perl or PowerShell versions
available) or install the VMA (Virtual Management Appliance, just a
linux box with the tools already installed) you can do everything you
need to do from the CLI of your favorite OS.
Got a link for that? And will it work with 4.1?
If you can use vCenter, the web based GUI in 5.1 is FANTASTIC and only
required flash. Works fine in Chrome.
If you need keys for 5 I might *cough* know *cough* where *cough* to get
some. *cough cough*. :)
Hmm! Please to be sending! Can I do an in-place upgrade from 4.1 to 5?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2013-01-24 02:44, Brian Hechinger wrote:
On 1/22/2013 9:15 PM, Cory Smelosky wrote:
Is that a proper Xeon or a P4 Xeon?
If it's a quad core it's a core2 arch xeon. P4 (Pentium-D) only came in
dual core.
Gents... Fun as all the small talk is, this is getting a little much outside of hecnet stuff, isn't it?
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 23 Jan 2013, at 20:43, Brian Hechinger <wonko at 4amlunch.net> wrote:
On 1/23/2013 8:40 PM, Cory Smelosky wrote:
If you can use vCenter, the web based GUI in 5.1 is FANTASTIC and only required flash. Works fine in Chrome.
Better than the Windows client! Eeeek. Visual J#!
The one that shipped with 5.0 wasn't. :)
Yay
>
> If you need keys for 5 I might *cough* know *cough* where *cough* to get some. *cough cough*. :)
What I need is a box to run 5 on. ;)
It'll run on just about anything. Look at Dell 1950s or HP DL/ML G5s.
That'd cost a bit of money though. ;)
I can grab some RAM and shoehorn it on to my desktop I never use though
-brian
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.