But what if you prefer to run ESX on ESX instead of Workstation?
Full article at:http://www.vcritical.com/2009/05/vmware-esx-4-can-even-virtualize-itself/
I believe the Next Generation Computing is Software Defined Infrastructure on top of the robust physical infrastructure. You can ask me anything about enterprise infrastructure (virtualization, compute, storage, network) and we can discuss it deeply on this blog. Don't hesitate to contact me.
But what if you prefer to run ESX on ESX instead of Workstation?
Full article at:A BTU is a British thermal unit, which is the measure of energy to raise one CC of water one degree Celsius.
But you probably want to know about airflow in CFM (not water), and the amount of cooling (or heating) available in 1 cfm or airflow.
In Houston, we tend to cool things more than heat. We also try to drive moisture out of the air (dehumidify), but I won't discuss that now. The general equation to answer your question is like this: Qsens = cfm * 1.08 * (Tin - Tout) <-- "delta T"
You need to determine what your "delta T" is. For cooling a space to 75degF (23.89 degC), your dT is usually 20degF (-6.67 degC) with your supply air temperature (SA=55degF 12.78degC) and your return air temperature (RA=75degF 23.89 degC). This has been idealized and simplified. For cooling, 1cfm will do about 21.6btu/h of cooling. For heating, (SA=90/32.2, RA=68, 1cfm => 23.76btu/h)So sometimes RAID 5 or 6 makes sense.
1. Edit /etc/inittab. Any text editors will do- I like nano but vi works just as well.
2. Search for "CTRL-ALT-DELETE" or "ctrlaltdel"
3. Comment out the line "ca::ctrlaltdel:/sbin/shutdown -t3 -r now" with a # symbol.It should look like:# Trap CTRL-ALT-DELETE
# ca::ctrlaltdel:/sbin/shutdown -t3 -r now
4. Save and exit the file.
5. To make this take effect without a reboot, run the command:
init q
Question: How to add multiple gateways to a FreeBSD?
Answer: No you can not do this (at least directly) on FreeBSD. FreeBSD don't support multiple gateways.
Workaround solution: If you have a server with 2 set of IPs and each set have there own gateway.
#Firewall & NAT & DummyNetadd the following rule to your ipfw rules set.
options IPFIREWALL
options IPDIVERT
options IPFIREWALL_DEFAULT_TO_ACCEPT
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options DUMMYNET
options IPFW2
ipfw add rule_no fwd second_gateyway_ip ip from ip_of_this_gateway to not meFor example, I have 2 ip set (10.0.0.100,10.0.0.101,10.0.0.102 for gateway 10.0.0.254) and (192.168.0.77,192.168.0.78 for gateways 192.168.0.254). I chose 10.0.0.254 as the default gateway. So, my ipfw rules are
ipfw add 100 fwd 192.168.0.254 ip from 192.168.0.77 to not me
ipfw add 110 fwd 192.168.0.254 ip from 192.168.0.78 to not me
vnc1024 5901/tcp # VNC & GDMnow create service description for xinetd. Go to directory /etc/xinetd.d
cd /etc/xinetd.dand create file vnc1024
service vnc1024Move to runlevel 3
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -geometry 1024x800 -depth 16 -once -fp unix/:7100 -securitytypes=none
}
init 3Restart xinetd
/etc/init.d/xinetdMove back to runlevel 5
init 5And that's it. Now try connect via VNCviewer to port 6901
Once you are at the command prompt, use Diskpart.exe to create an aligned partition. To do so, type in the following:
diskpart
select disk 0
create partition primary align=64
You can now exit diskpart by typing 'exit'.
Default IP | 192.168.1.20 |
---|---|
Default name | ubnt |
Default password | ubnt |
Install vncserver (as root): apt-get install vncserver
Choose your desired window size and color depth, then, as an ordinary user, open a terminal and type:vncserver -geometry 1024x768 -depth 24
orvncserver -geometry 1024x768 -depth 24 -pixelformat rgb565
This will prompt you to create a password:
You will require a password to access your desktops.
Password:
Verify
The server will start and tell you where to access it:
New 'X' desktop is foobar:1
Starting applications specified in /etc/X11/Xsession
Log file is /home/jorey/.vnc/foobar:1.log
Open the VNC viewer on your remote machine, enter the hostname:screen and password (use a hostname or IP that your client machine understands), and your Linux desktop will open in a window! Network speed and processor power will affect performance, but it's amazing how many apps will run fine under VNC. You might not be able to play Frozen Bubble, but you can use productivity applications without any trouble.
To kill the server enter a command similar to this, using the appropriate settings:vncserver -kill :1
The reason for killing the session is that you may need to edit the default configuration file that vncserver
creates for you, for example to get the vncserver to run the K desktop environment instead of twm
, you may want to edit the $HOME/.vnc/xstartup
file to replace the line:
twm &
with this line is you use KDE:
startkde &
and with this line if you use GNOME:
gnome-session &
before launching the vncserver again using:
vncserver :1 -geometry 1024x768 -depth 16 -pixelformat rgb565
ssh
session on the machine where you will be running the vncviewer, to request that ssh
listen on a particular port on your local machine, and forward communication on that port down the secure connection to a port on the machine running the vncserver.
For example:
ssh -L x:localhost:y vncserver_machine
means "Start an SSH connection to the vncserver_machine
, and also listen on port x
on my machine, and forward any connections there to port y
on the vncserver_machine
."
Now, the VNC protocol normally uses port 59xx
, where xx
is the display number of the server. So a VNC server on a Windows machine, which normally uses display number 0
, will listen on port 5900
. The first VNC server on linux will probably use display number 1
, and subsequent servers would use 2
, 3
, etc. and so the vncservers on linux will be listening on ports 5901
, 5902
and so forth. By forwarding these ports to a remote machine running vncserver
, you can make the remote VNC server appear to be a server running on your local machine. So, imagine you had a VNC server running as display :1
on vncserver_machine
, and you wanted a secure connection to it from your local machine. You could start the ssh
session using:
ssh -CL 5902:localhost:5901 vncserver_machine
After that, starting up the vncviewer
as follows on your local machine: vncviewer -encodings "copyrect hextile" localhost:2 would actually connect to display :1
on the vncserver_machine
.
Note that the above OpenSSH command-line is deliberately meant to accept incoming connections only from the local machine. This means that to use the ssh
connection that we have just set up, we must connect to it from the same machine, using the special name localhost
, rather than using the local machine's own unique name.
Paolo Conti wrote how to hack VMware tools to work on linux kernels 2.6.18
[CITATION FROM http://www.atlink.it/~conti/2007/12/19/vmware-uts_release/]The error is something like this: The directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.18.2-34-default). Even if the module were to compile successfully, it would not load into the running kernel.
With this bug you cannot sync the time with your hosting server, automate shutdown tasks, etc… This problem exist because the kernel source code structure is changed in recent kernels (I guess > 2.6.18). The VMWare tools installation script is looking for the string “#define UTS_RELEASE $kernel_number” into /usr/src/kernels/$(uname -r)*/include/linux/version.h but the UTS_RELEASE variable is now into the file utsrelease.h.
To fix this, you can patch the VMWare tools installation script or just add the content of utsrelease.h to version.h. I suppose the second solution is the fastest one
To do this:
cd /usr/src/kernels/$(uname -r)*/include/linux
cat utsrelease.h >> version.h
Happy virtualization folks!
cd C:\Program Files\Qemu
C:\Program Files\Qemu>qemu-img.exe create -f vmdk WindowsXPPro.vmdk 2G
Formating 'WindowsXPPro.vmdk', fmt=vmdk, size=2097152 kB
Note: I have made several empty VMware virtual disk files of various sizes available as a single 21 KB download.
config.version = "8"
virtualHW.version = "3"
ide0:0.present = "TRUE"
ide0:0.filename = "WindowsXPPro.vmdk"
memsize = "64"
MemAllowAutoScaleDown = "FALSE"
ide1:0.present = "TRUE"
ide1:0.fileName = "auto detect"
ide1:0.deviceType = "cdrom-raw"
ide1:0.autodetect = "TRUE"
floppy0.present = "FALSE"
ethernet0.present = "TRUE"
usb.present = "TRUE"
sound.present = "TRUE"
sound.virtualDev = "es1371"
displayName = "Windows XP Pro"
guestOS = "winXPPro"
nvram = "WindowsXPPro.nvram"
MemTrimRate = "-1"
ide0:0.redo = ""
ethernet0.addressType = "generated"
uuid.location = "56 4d 5c cc 3d 4a 43 29-55 89 5c 28 1e 7e 06 58"
uuid.bios = "56 4d 5c cc 3d 4a 43 29-55 89 5c 28 1e 7e 06 58"
ethernet0.generatedAddress = "00:0c:29:7e:06:58"
ethernet0.generatedAddressOffset = "0"
tools.syncTime = "TRUE"
ide1:0.startConnected = "TRUE"
uuid.action = "create"
checkpoint.vmState = ""