[masand]

Originariamente inviato da unnilennium

Mi son ricordato un'altra distro molto leggera debian-based,anche se magari masand nn ne ha più bisogno... Mepis antix..una meraviglia davvero..

Grazie molte invece!!! Gli darò un'occhiata sicuramente!!!!

Invece, forse sarà old, ma...

VIRTUALBOX CON LA NUOVA VERSIONE 2.1 SUPPORTA IL 3D (in via sperimentale)

Questo è il Changelog:

VirtualBox 2.1.0 (released 2008-12-17)

This version is a major update. The following major new features were added:

* Support for hardware virtualization (VT-x and AMD-V) on Mac OS X hosts
* Support for 64-bit guests on 32-bit host operating systems (experimental; see user manual, chapter 1.6, 64-bit guests, page 16)
* Added support for Intel Nehalem virtualization enhancements (EPT and VPID; see user manual, chapter 1.2, Software vs. hardware virtualization (VT-x and AMD-V), page 10))
* Experimental 3D acceleration via OpenGL (see user manual, chapter 4.8, Hardware 3D acceleration (OpenGL), page 66)
* Experimental LsiLogic and BusLogic SCSI controllers (see user manual, chapter 5.1, Hard disk controllers: IDE, SATA (AHCI), SCSI, page 70)
* Full VMDK/VHD support including snapshots (see user manual, chapter 5.2, Disk image files (VDI, VMDK, VHD), page 72)
* New NAT engine with significantly better performance, reliability and ICMP echo (ping) support (bugs #1046, #2438, #2223, #1247)
* New Host Interface Networking implementations for Windows and Linux hosts with easier setup (replaces TUN/TAP on Linux and manual bridging on Windows)

In addition, the following items were fixed and/or added:

* VMM: significant performance improvements for VT-x (real mode execution)
* VMM: support for hardware breakpoints (VT-x and AMD-V only; bug #477)
* VMM: VGA performance improvements for VT-x and AMD-V
* VMM: Solaris and OpenSolaris guest performance improvements for AMD-V (Barcelona family CPUs only)
* VMM: fixed guru meditation while running the Dr. Web virus scanner (software virtualization only; bug #1439)
* VMM: deactivate VT-x and AMD-V when the host machine goes into suspend mode; reactivate when the host machine resumes (Windows, Mac OS X & Linux hosts; bug #1660)
* VMM: fixed guest hangs when restoring VT-x or AMD-V saved states/snapshots
* VMM: fixed guru meditation when executing a one byte debug instruction (VT-x only; bug #2617)
* VMM: fixed guru meditation for PAE guests on non-PAE hosts (VT-x)
* VMM: disallow mixing of software and hardware virtualization execution in general (bug #2404)
* VMM: fixed black screen when booting OS/2 1.x (AMD-V only)
* GUI: pause running VMs when the host machine goes into suspend mode (Windows & Mac OS X hosts)
* GUI: resume previously paused VMs when the host machine resumes after suspend (Windows & Mac OS X hosts)
* GUI: save the state of running or paused VMs when the host machine’s battery reaches critical level (Windows hosts)
* GUI: properly restore the position of the selector window when running on the compiz window manager
* GUI: properly restore the VM in seamless mode (2.0 regression)
* GUI: warn user about non optimal memory settings
* GUI: structure operating system list according to family and version for improved usability
* GUI: predefined settings for QNX guests
* IDE: improved ATAPI passthrough support
* Networking: added support for up to 8 Ethernet adapters per VM
* Networking: fixed issue where a VM could lose connectivity after a reboot
* iSCSI: allow snapshot/diff creation using local VDI file
* iSCSI: improved interoperability with iSCSI targets
* Graphics: fixed handling of a guest video memory which is not a power of two (bug #2724)
* VBoxManage: fixed bug which prevented setting up the serial port for direct device access.
* VBoxManage: added support for VMDK and VHD image creation
* VBoxManage: added support for image conversion (VDI/VMDK/VHD/RAW)
* Solaris hosts: added IPv6 support between host and guest when using host interface networking
* Mac OS X hosts: added ACPI host power status reporting
* API: redesigned storage model with better generalization
* API: allow attaching a hard disk to more than one VM at a time
* API: added methods to return network configuration information of the host system
* Shared Folders: performance and stability fixes for Windows guests (Microsoft Office Applications)

Ho messo in grassetto la parte relativa al 3D.

Di seguito invece, quello che c'è scritto sul manuale nel capitolo 4.8:

4.8 Hardware 3D acceleration (OpenGL)

Starting with version 2.1, the VirtualBox Guest Additions for Windows contain experimental
hardware 3D support.
With this new feature, if an application inside your Windows guest uses 3D features
through the OpenGL programming interfaces, these will not be emulated in software
(which is slow), but instead VirtualBox will attempt to use your host’s 3D hardware.
This works for all supported host platforms (Windows, Mac, Linux, Solaris), provided
that your host operating system can make use of your accelerated 3D hardware in the
first place.
1The X server version differs from the version of the entire X.org suite. You can type X -version in a
terminal to find out about the X.org server version level that is currently installed.
66
4 The VirtualBox Guest Additions
The 3D acceleration currently has the following limitations:
1. It is only available in Windows XP and 32-bit Vista guests with the Windows
Guest Additions installed.
2. Only OpenGL acceleration is presently available in those guests; Direct3D is not
yet supported and will be added in a future release.
3. Because the feature is experimental at this time, it is disabled by default and
must be manually enabled in the VM settings (see chapter 3.7.1.2, “Advanced”
tab, page 46).
Please see chapter 13, Known issues, page 182 also.
Technically, VirtualBox implements this by installing an additional hardware 3D
driver inside your Windows guest when the Guest Additions are installed. This driver
acts as an OpenGL hardware driver and reports toWindows that the (virtual) hardware
is capable of 3D hardware acceleration. When an application in the Windows guest requests
hardware acceleration through the OpenGL programming interfaces, these are
sent to the host through a special communication tunnel implemented by VirtualBox,
and then the host performs the requested 3D operation via the host’s OpenGL programming
interfaces.

Si capisce che per il momento si avrà il 3D solo per i guest WindowsXP e Vista (per il momento) e addirittura supporteranno anche il Direct3D...

Spettacolo!!!!

Un saluto a tutti...
masand