On 2012-08-27 at 21:12 Matthias said: > You could try and change the config > on your start system and disable VT-x there, and hope, that on reboot > on that system it does reconfigure itself without the VT-x support > in the guest.
Only a hope? Result unpredicatble, then? Will give it a try - depending on: > But that depends on the specific guest OS... Windows XP SP3 So, given the guest OS, what hope is there the exporting system*will* re-configure the VM so as not to need VT-x support? What also occurs to me is that - presumably - the Import Appliance mechanism could check that the system being imported to does/does not have the VT-x support needed by the imported VM, and simply *report* this to the user as a showstopper. (If it cannot re-configure the imported VM to not need VT-x) Thank you again for your help, Matthias. -- /\/\aurice ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:[email protected]?subject=unsubscribe
