. . . . . . . . . . . . . . . . . . . . . . . . 194 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 195 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 194 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 195 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 182 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 183 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. 46 3 Configuring virtual machines (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 195 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 196 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . . 182 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 183 12.2.3 Poor performance caused by host power management . . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. 46 3 Configuring virtual machines (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 203 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 204 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 193 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 194 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 180 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 181 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 203 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 204 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the

. . . . . . . . . . . . . . . . . . . . . . . . 203 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 204 12.2.3 Poor performance caused by host power management . . Controllers (PICs) in recent years. With an I/O APIC, operating systems can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. Note: Enabling the I/O APIC is (virtual) hardware is capable of 3D hardware acceleration. When an application in the guest then requests hardware acceleration through the OpenGL or Direct3D programming interfaces, these are sent to the