virtualbox.org

Hi..

I have had a good stable version of windows xp guest which ran really well.

I have then created another Linux Mint 64 bit guest so I can run a certain program. ( I have only installed linux mint and haven't really run anything in it).

However, now the Win XP guest is running really slowly with windows now almost freezing.. ( the XP guest has up to 8mb of memory available)

Have tried things like turning off VT-x acceleration and nested paging.. But that crashed the xp completely, so now back on.

Even upgraded to 4.3.8 (was 4.2.13 -I think)

I think something has happened as regards having both 64 and 32 bit guest running simultaneously..

Anybody had similar issues, or know a way of getting the XP speed back..

Much thanks in advance

Will

Update:

Removed the Linux 64 bit guest .. Was still getting issues seems that it was trying to boot 64-bit xp..or so it said in log file.

Re-assigned the virtual hard drive to a new 32 bit xp virtual machine and all seems fine.

Guess I won't be able to install a 64 bit VM then.. Unless anyone has a suggestion..

One guest can't affect another unless you try to run both at the same time, and your host lacks resources for it.

Frankly, I think you jumped to conclusions, after seeing a pattern that wasn't there. The only thing you know for sure is that your XP guest seems slower than before, and my guess is that you've encountered the XP Windows Update problem. If so then the solution was discussed here.

That's just a guess based on the fact that lots of XP users had that problem. However if you want to be sure then pop up the guests task list and see who's taking all the CPU or I/O time.

Hi thanks for reply..

Definitely not the update issue, as the XP guest has been working like a dream fully updated for two years now..

I thought I had copied the log when it said it was trying to boot xp in 64 bit mode (under the fHM forced true -DARWIN bit) but I didn't. So you will just have to believe me.

I might try uploading another 64 bit guest another time, but not when xp is mission critical, as is now..

Cheers Will

What I said, about one VM not being able to affect another, applies even if my guess re the CPU hog was incorrect.

The log wouldn't be very useful in this case - it won't tell me anything about the guest task list. It essentually tells me your config, and if you've been using the VM successfully for a couple of years then I presume the config is correct (*). As I said, you need to pop up and examine the task list yourself, this should eliminate the need for guesswork.

(*) That said, a log should be provided if you ever want to continue this discussion.