On Mon, 24 Oct 2011 12:07:40 +0200, Alexander Eichner wrote: > https://www.virtualbox.org/manual/ch09.html#cpuhotplug [3]
This is exacly what I'm doing. This works perfectly on my Debian GNU/Linux Squeeze machine which is truly 64bit (and have the /usr/sbin/VBoxService service running). But on my custom Debian GNU/Linux Lenny boxes (which have 64bit kernel and 32bit userland), it doesn't work (due to the fact that VBoxService won't start). > Ejecting a CPU is bit more difficult because the path in the sysfs > tree differs based on the kernel version. > You have to search for the eject file in one of the directories and > write a 1 to it to disable the CPU. > Search for ACPI0004, LNX_CPU or ACPI_CPU directories. > You can remove the CPU from the guest after ejecting it. That's not the biggest problem :). From what I can tell, the host isn't even getting the ... 'request' to detach a cpu. I've run acpid with full logging and debuging, but it doesn't see it. ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
