Skip to main content

My other blog...

I decided to blog about my experience with Red Hat Enterprise Virtualization and Satellite.

http://rhevdup.blogspot.com

I think creating online docs motivate you to complete something, as though you are being held accountable.  Even though I am probably the only person who ever reads this crap anyhow.


 It will be populated with (hopefully) useful bits regarding RHEV (specifically RHEV 3), conjecture and opinion on the product and comparisons with VMware ESX/ESXi.  I found the vcritical.com blog offensive, childish - mostly because the individual actually works for VMware (EMC) and identifies this on his blog.  As a result, I have decided that RHEV deserves an audience as well ;-)  Although, I will not go on tirades trying to trash VMware.

So - for the record: I like VMware, a lot.  I realize that I have barely scratched the surface of the capabilities that VMware offers.  For the most part, the experience I have with VMware has been practically flawless and generally does not disappoint.  However, like anything IT related, I like the idea of competition.  It potentially makes both products better, accelerates the development cycle to keep up with each other.  Sun's implementation of Zones and/or containers does not seem to be a relevant contender, and I am not interested in comparing desktop technologies, or "workstation" virtualization products, yet...

More to follow...

Expect to see plenty of my footnotes and such to indicate that I am not done with that topic.  I plan to start a lot of topics and populate those topics as I become more educated on the subject.

Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.