The anxiously awaited RHEL5 was released recently. The following is from RHEL5 release notes. Looks like virtualization support (with Xen 3) is only half- or perhaps only quarter-baked.
“Fully virtualized guests cannot be saved, restored or migrated.”
So, does that mean no suspend/resume and no VMotion?
“Hardware-virtualized guests cannot have more than 2GB of virtual memory.”
One really shouldn’t try putting Enterprise or even SMB workloads with only 2GB upper limit.
“When you install a fully virtualized guest configured with vcpus=2, the fully virtualized guest may take an unreasonably long time to boot up. To work around this, destroy the slow-booting guest using the command xm destroy and then use xm create to start the same guest afterwards.”
Welcome to my ramblings. An introduction is in order. Irfan is the name. Software Engineering is the profession. Performance analysis and optimization is the specialty. VMware, Inc. is the employer. Islam is the way of life. Peace is the motto (Love for All; Hatred for None).
I’ve been at VMware over 4 years. Most recently, I have worked for Transmeta, Autodesk Canada, Toronto Stock Exchange and Canada Trust (now TD) in various capacities including (in no particular order) software engineer, software performance engineer, programmer, intern, research analyst, etc. I graduated from the University of Waterloo in Ontario with a degree in Mathematics/Computer Science.
For the last few months, I’ve been reading blogs of friends and others in the area of virtualization. For what it’s worth, I’m overall impressed with the coverage of interesting virtualization topics in the blogosphere. However, I’ve felt a distinct need for more coverage of real and present issues in the day to day operations of virtual machine software. So, I hope to bring to readers an interesting mix of tips & tricks, commentary & opinion, future directions and hopefully some fun fact alongs the way. One virtual scoop at a time.