I used xp before, now i Virtualize it, But in Microsoft Virtual Pc & VirtualBox im getting perfomance issues Vmware Player & Workstacion Works well but its hard to operate, so give me tips to get petter perfomance
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Theres a way to Get Better Perfomance in a Virtual Machime
- Thread starter GreenStar_ON_Emachimes
- Start date
I could not get decent performance with Virtual PC and VirtualBox. Both are dogs, not fixable (unless some coding miracle has taken place recently).
VMWare is the only one I get good performance from.
I currently have 3 Linux VMs- Rockbox's dev version, and 2 Linux Mints, a Win 7 VM (multiple audio-video performance issues, native Win7 is no better) and 3 well performing XP VMs, all using VMWare Player (some began life on VMWare Server 1). I found VMWare Player to have the best interface (easiest). What are you finding is hard?
Keep in mind, any VM requires you to know how to google for answers. Most of the VMWare Workstation vmx file mods work in VMWare Player. Some of these mods are undocumented, only found in blogs and forums.
The best thing I like about VMWare is the control you have of the date time. Got a legacy program that refuses to run past a certain date? No problem on VMWare.
some values I use:
time.synchronize.continue = "FALSE"
time.synchronize.restore = "FALSE"
time.synchronize.resume.disk = "FALSE"
time.synchronize.shrink = "FALSE"
time.synchronize.tools.startup = "FALSE"
time.synchronize.tools.enable = "FALSE"
time.synchronize.resume.host = "FALSE"
rtc.startTime = "1256500505"
Set the last one to the UTC (date-time) you want (that value above is in 2009). When reverting your VM from a backup, delete the rtc.startTime line after the first VM shutdown. Then the clock moves forward, but from that UTC date. Google UTC Caclulator if you want to know how to create the values.
Performance mods:
Run each vmdk in your VM on a separate SSD. Note a RAMDisk will blow a SSD away. I have this planned for the new XP32 box I'm building next year (going to have 64 to 128GB RAM, most of it for one or more RAMDisks).
Have only one pagefile on your host OS and put it on the fastest dedicated drive you have. For most folks, this a is dedicated SSD, 128 to 512GB in size (more space=longer life). If you can make it work, put your pagefile on a RAMDisk (Superspeed's works, there are others I have yet to try).
It sounds like your host machine is not XP. I haven't done the ramdisk on a pagefile mod on Win7, but it may be possible. Keep in mind Win7, and 8.1, 10 are in page fault hell from the moment you boot- look at the Commit Charge. Any XP or newer box is in page fault hell above 1.5GB Commit (thus why Win7, and 8.1, 10 only run decently from a SSD).
There are several performance enhancements you can implement in the vmx file:
Here are some from my Linux Mint box (used to safely browse the web from XP) run on XP 32bit:
memsize = "1280"
mem.hotadd = "TRUE"
MemTrimRate = "0"
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100"
logging = "FALSE"
workingDir = "G:\VMSwap"
Running that VM puts the host XP Commit Charge at 1.5 to 2GB, which is in the page fault hell territory. Thus, I've run the pagefile on Superspeed ramdisk mod since 2011 without any issues (8GB RAM, 5GB RAMDisk, 5GB pagefile). Benefits are zero page fault delays even if I'm editing 20 videos with 20 VideoRedo instances (Commit at 4.5GB) and copying 500GB across the network.
memsize = "1280" and prefvmx.useRecommendedLockedMemSize = "TRUE" allocate all the RAM upfront (not the default VMWare behavior), but Linux Mint runs faster that way. XP is much more tolerant of RAM allocation by VMWare. You don't need any of those vmx memory mods on XP (might even slow it down).
VMWare is the only one I get good performance from.
I currently have 3 Linux VMs- Rockbox's dev version, and 2 Linux Mints, a Win 7 VM (multiple audio-video performance issues, native Win7 is no better) and 3 well performing XP VMs, all using VMWare Player (some began life on VMWare Server 1). I found VMWare Player to have the best interface (easiest). What are you finding is hard?
Keep in mind, any VM requires you to know how to google for answers. Most of the VMWare Workstation vmx file mods work in VMWare Player. Some of these mods are undocumented, only found in blogs and forums.
The best thing I like about VMWare is the control you have of the date time. Got a legacy program that refuses to run past a certain date? No problem on VMWare.
some values I use:
time.synchronize.continue = "FALSE"
time.synchronize.restore = "FALSE"
time.synchronize.resume.disk = "FALSE"
time.synchronize.shrink = "FALSE"
time.synchronize.tools.startup = "FALSE"
time.synchronize.tools.enable = "FALSE"
time.synchronize.resume.host = "FALSE"
rtc.startTime = "1256500505"
Set the last one to the UTC (date-time) you want (that value above is in 2009). When reverting your VM from a backup, delete the rtc.startTime line after the first VM shutdown. Then the clock moves forward, but from that UTC date. Google UTC Caclulator if you want to know how to create the values.
Performance mods:
Run each vmdk in your VM on a separate SSD. Note a RAMDisk will blow a SSD away. I have this planned for the new XP32 box I'm building next year (going to have 64 to 128GB RAM, most of it for one or more RAMDisks).
Have only one pagefile on your host OS and put it on the fastest dedicated drive you have. For most folks, this a is dedicated SSD, 128 to 512GB in size (more space=longer life). If you can make it work, put your pagefile on a RAMDisk (Superspeed's works, there are others I have yet to try).
It sounds like your host machine is not XP. I haven't done the ramdisk on a pagefile mod on Win7, but it may be possible. Keep in mind Win7, and 8.1, 10 are in page fault hell from the moment you boot- look at the Commit Charge. Any XP or newer box is in page fault hell above 1.5GB Commit (thus why Win7, and 8.1, 10 only run decently from a SSD).
There are several performance enhancements you can implement in the vmx file:
Here are some from my Linux Mint box (used to safely browse the web from XP) run on XP 32bit:
memsize = "1280"
mem.hotadd = "TRUE"
MemTrimRate = "0"
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "TRUE"
prefvmx.minVmMemPct = "100"
logging = "FALSE"
workingDir = "G:\VMSwap"
Running that VM puts the host XP Commit Charge at 1.5 to 2GB, which is in the page fault hell territory. Thus, I've run the pagefile on Superspeed ramdisk mod since 2011 without any issues (8GB RAM, 5GB RAMDisk, 5GB pagefile). Benefits are zero page fault delays even if I'm editing 20 videos with 20 VideoRedo instances (Commit at 4.5GB) and copying 500GB across the network.
memsize = "1280" and prefvmx.useRecommendedLockedMemSize = "TRUE" allocate all the RAM upfront (not the default VMWare behavior), but Linux Mint runs faster that way. XP is much more tolerant of RAM allocation by VMWare. You don't need any of those vmx memory mods on XP (might even slow it down).