About
You arrived at the weblog of Geert Baeke. I am the technology manager for a company called Xylos (Belgium). I mostly work with Microsoft technologies such as Windows, Active Directory, Exchange, Sharepoint, MSCS, and more. I am also actively busy with VMware's products, focussing on VMware ESX.

Sections
Search






XBOX 360

RSS Newsfeeds
baeke.info Main RSS Feed Main Page RSS
Virtual Machines RSS Feed Virtual Machines RSS
View Article  Backup software esXpress evolving further

A while ago, I had a post about esXpress 3.0. The development is progressing nicely (rc 2) as a GUI helper has been added to the feature set for those that do not want to use the console.

The GUI helper can be started from the console but you can also instruct esXpress to start the helper from VI Client. What you get is a new virtual machine and to get to the GUI, you just have to open the virtual machine console from VI Client.

Some examples of what you get in the screenshots below.

The main menu:

The configuration screen:

The live log file:

 

The GUI is not yet complete. Later releases will add virtual machine restore options and scheduling options as well. We are using the tool in our test environment at Xylos and it is working reliably.

View Article  Virtual machines slow after using Virtual Machine Importer?

Just a quick tip here. During some tests for an ESX 3.0 project, we imported some GSX 3.2 virtual machines in ESX 3.0.1 with VMware's Virtual Machine Importer 2.0. That process went fine and Virtual Machine Importer works really well.

The imported virtual machine was configured with 256 MB of RAM. When we changed the virtual machine's memory (on ESX) to more than 512 MB of RAM, the virtual machine became very slow. So slow that it was not usable. Inside the virtual machine, the CPU was maxed out (system process). From the outside however (esxtop), the machine did not seem busy at all.

The problem was that, during the import, the sched.mem.max setting was set to 256 MB of RAM, thus limiting the virtual machine's memory. Changing that setting to unlimited (or to a more realistic value) fixed the slowness.

Bottom line: after importing with Virtual Machine Importer, adjust the sched.mem.max setting if you plan on increasing the virtual machine's memory. This can be done with the GUI in the virtual machine's settings in the Resources tab.

 

Login
User name:
Password:
Remember me 
This Month
November 2006
Sun Mon Tue Wed Thu Fri Sat
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30
Networking
View Geert Baeke's profile on LinkedIn

Services

Powered by BlogHarbor
Powered by BlogHarbor
StatCounter