On Wednesday 02 December 2009 17:37:47 Frank Joosten wrote: > Hi > > Had a quick play with this new option and must say it is very cool and > is > going to save me lots of time in my test lab > > > VirtualBox Host1 Linux Ubuntu 9.10 64bit > VirtualBox Host2 Windows 7 64bit > > Client Windows 2008 server 64bit > Hard disk on a Cifs server (a readynas) > > Seems to work like well, would be nice to be able to clone the > Configuration > file across the two Hosts > > Now if Sun could give us auto telepotation. > > Michael > > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > > > Hi, > > Teleportation Works ok from Intel T8100 (Core2Duo) host Vista to Intel > PIII 1000 host Fedora 11 > > Teleportation back from PIII to T8100 works but after half a minute the > guest WinXP reboots with a system arror. > > According to "This Computer" - "Properties" XP sees a Xeon processor on > the T8100 and a PIII on the PIII. > I think XP can have a problem with this.... > > Thanks for this nice feature, > > Frank > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users >
Don't know if this info is useful in this particular case but here it goes: ------------------------------------------------------------------- "Under certain circumstances with a Windows XP / 2003 operating system - intelppm.sys and processr.sys can cause a virtual machine running under Virtual PC / Virtual Server to crash (by default this will cause the Windows guest operating system to reboot automatically - but if you have changed this setting you will see a blue screen). The reason for this crash is because these drivers are attempting to perform an unsupported operation inside of the virtual machine (like upgrading the physical processors microcode, changing power state on the physical processor). Today this problem only occurs on Centrino and AMD K8 processors. Most people see this problem when they move a virtual machine that was created on another type of processor to a computer running one of these types of processors (and then they usually see the problem when they attempt to shutdown their virtual machine for the first time). Now you may be wondering why you have not heard about this problem more often - and the reason for that is that if these drivers fail once - they are smart enough to not attempt to perform the operation that failed again. If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by running the following at the safe mode command prompt: sc config processor start= disabled sc config intelppm start= disabled" ------------------------------------------------------------------- This is in the guest OS, of course. I used this info when my XP vm refused to boot because of processor issues. Hope it helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% winfoes FREE) _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
