HI
We have been asked by our IT department to move from our current physical solution to a VM environment. I am not that clued up on VM.
I looked from some benchmark tests to run so i can see a comparison between our live and new VM we have been presented. Please see below for results.
To me the VM looks slower. Can someone advice please and offer advice on any other tests we can run please.
We are running Redhat Enterprise 6.4.
Thanks in Advanced
Treds
Moderator's Comments:
Please use code tags next time for your code and data not HTML Thanks
i recently purchased a dual ross sparc processor kit from someone.
the person listed these items as 133mhz processors, however, looking at bridgepoint's site, they do not make 133mhz processors.
so i was wondering, how can i check the processor speeds? (4 Replies)
Hello all,
We have a group of Solaris 8 machines that are having some real network performance issues, they all go through a switch which *should* be set at 100 mb full duplex on every port which goes back to a master switch. I have checked the machines and the NIC cards are all set at 100 full.... (9 Replies)
Hello,
I have a SUN T5240 running Solaris 10 with Logical Domain Manager (v 1.0.3). You can use the "ldm" command to display current resources on the box. Is there away to display all the "physical resources" on the box(i.e.,used and unused). For example, "ldm ls" will tell me what the... (5 Replies)
We have some AIX Unix Servers with 4 or 6 CPU and when type this command “c” in nmon always displays each cpu % with Averages on buttom. However we have several Servers with 18 CPU's and it only shows 16 17 on main page. Does nmon have some command that would show remaining with totals for Physical... (3 Replies)
Hello All,
Can anybody please tell me what is the maximum limit of Physical IBM Power Machine which can be handled by single HMC at a single point of time?
Thanks,
Jenish (1 Reply)
Hi all
I have connected new server to LAN but when I use rlogin command by server name it dose not work but by IP adderss it works.
can any one tell the reason? (4 Replies)
Hi All,
How can I know whether the server I am connecting to is a virtual or physical one? The server might be having any Unix OS (Linux/Solaris/HP-UX etc.).
Is there any system files / commands which can show these concrete information?
Thanks in advance for the replies.
sanzee (1 Reply)
Hi,
i am trying to find whether any particular solaris server is physical or virtual....are there any commands or set of commands which only runs (or provide specific pattern ) on physical machines and provides different pattern or error on virtual one...
Is this the correct approach to... (7 Replies)
Need inputs when physical server is coming down (ex- init 0) .
We have a physical server in that there are couple of LDOM's and in LDOM's there are couple of Zones . In zones there are applications running .
Physical Server (T4 Server) -> LDOM -> ZONES -> applications
There are scripts... (1 Reply)
Discussion started by: ajayram_arya
1 Replies
LEARN ABOUT REDHAT
amdd
AMDD(8) System Manager's Manual AMDD(8)NAME
amdd - Amanda version of dd
SYNOPSIS
amdd [ -d ] [ if=input ] [ of=output ] [ bs=blocksize ] [ skip=count ] [ count=count ]
DESCRIPTION
Amdd provides just enough of the standard dd command for the needs of Amanda. This is handy when doing a full restore and the standard dd
program has not yet been found.
Amdd also provides access to the Amanda output drivers that support various tape simulations. This may be used for debugging or to convert
from one format to another.
See the amanda(8) man page for more details about Amanda. See the OUTPUT DRIVERS section of amanda(8) for more information on the Amanda
output drivers.
OPTIONS -d Turn on debugging output.
-llength
Set the output length. If the output driver limits the output size, this controls when end of tape will be simulated.
Length may have a multiplier suffix:
k 1024 (Kilobytes)
b 512 (Blocks)
M 1024*1024 (Megabytes)
The default is no multipler (bytes).
if=input
Input to dd. Default is stdin.
of=output
Where to send the output of dd. Default is stdout.
bs=blocksize
Size of each record. Input records smaller than this will not be padded. Output records will be the same size as the corresponding
input record. Default is 512 bytes.
Blocksize may have a multiplier suffix:
k 1024 (Kilobytes)
b 512 (Blocks)
M 1024*1024 (Megabytes)
The default is no multipler (bytes).
count=count
Number of records to copy. Default is all records until end of file.
skip=count
Number of records to skip before copying input to output. Default is zero.
AUTHOR
Marc Mengel <mengel@fnal.gov>
John R. Jackson <jrj@purdue.edu>
SEE ALSO amanda(8)AMDD(8)