Hi, There's a problem with my Win98 VM in the sense that the only way I seem to be able to boot Win98 succesfully is by DISABLING ACPI DISABLING IO APIC DISABLING AMD-V DISABLING PAE-NX
I really wouldn't mind disabling the first three, but disabling AMD-V means that I can no longer run any other guest concurrently with AMD-V support (like for instance is needed to run Win XP64 under 32-bit Linux) because I get a dialog informing me that: "An active VM already uses AMD-V hardware acceleration. It is not allowed to simultaneously use software virtualization. (VERR_ACCESS_DENIED). Unknown error creating VM (VERR_ACCESS_DENIED)". So, any idea on why Win98 SE crashes at boot with AMD-V enabled? What sort of special trickery does the Win98SE kernel do when initializing itself that crashes and burns with AMD-V enabled?. I am surprised that NT4 works fine, Win2k works fine, XP64 runs even better, and Win7 beta (32-bit and 64-bit) work well. Win98SE seems to be the one which runs slower and has the most problems with all those "advanced" settings, perhaps confirming what sort of ugly kludge Win9X really was... Thoughts? Ideas? I remember there were a few active users in here which used Win9x under VirtualBox.... Frank, do you think I could do a memory dump or log of the VM so you could see where Win98 is hanging when AMD-V is enabled? Thanks FC -- Dream of the Daily Mail It is the Holy Grail And then the BBC Your life would be complete -Manic Street Preachers, "Royal Correspondent" _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
