With Citrix PVS the content of a disk is streamed over the network to an endpoint. This requires sufficient bandwidth and an optimized configuration. If both criteria. Download the latest drivers for your Network & Wireless Cards to keep your Computer up-to-date.

All Operating System Compatibility CAESAR II CAESAR II ® is compatible with Windows desktop operating systems listed below. Note: The operating system compatibility details that follow refer to the latest released version of this software. Previous versions of the software may not work with newer operating systems.

Additional details on the life-cycle of Microsoft operating systems can be obtained from Microsoft’s web site at: Desktop Operating System Compatibility Information Windows 7/8/8.1/10* Professional (32- and 64-bit) Windows 7 Ultimate (32- and 6 4-bit) Windows 7/8 /8.1/10* Enterprise (32- and 64-bit) These operating systems are tested by CADWorx & Analysis Solutions. CAESAR II does not support Windows 7/ 8 /8.1 Starter, Home Basic, and Home Pr emium. The software does not support Windows XP, Windows Vista Starter, and Home ersions of Windows 7/8/8.1 (i.e., Starter, Home Basic, Home Premium). * Windows 8 /8.1 - Enable.NET 4.5.2 from your Control Panel prior to installing CAESAR II. Windows Server (all versions) Only tested by CADWorx & Analysis Solutions for the installation of network licensing systems (NetHASP License Manager). Recommended System Requirements for CAESAR II: • Processor: 3.0 GHz Intel Pentium IV or higher AMD Athlon dual-core processor or higher • Memory: 4 GB RAM or higher (Windows 7/8 /8.1) • Display: 1280x1024 or higher, with True Color • Video Card: 256 MB or greater video RAM, OpenGL 1.1 or later, DirectX 9.0 or later, drivers updated with the latest manufacturer's drivers (Motherboard-integrated video cards not recommended for desktop systems.) • Remote Technologies: Citrix XenApp 6.0 required on Windows Server 2008 R2 Enterprise • Software: Adobe Reader 8.0 or later.

CADWorx Plant Professional Minimum system requirements to run CADWorx Plant Design Suite are those recommended for the version of AutoCAD (or Autodesk vertical product) or BricsCAD that you have chosen to use as your design platform. For product specific installation requirements refer to the product installation guide. CADWorx P&ID Professional Minimum system requirements to run CADWorx Plant Design Suite are those recommended for the version of AutoCAD (or Autodesk vertical product) or BricsCAD that you have chosen to use as your design platform. Refer to the applicable Autodesk Product System Requirements on the Autodesk website. For product specific installation requirements refer to the product installation guide. Bosch Wfb 3200 Manual on this page. OrthoGen for CADWorx Standard Edition: • 3.0 GHz Intel Pentium IV or greater • Windows XP Professional or later • 2 GB RAM • 1600x1200 with true color • 128 MB or greater OpenGL-capable graphics card CADWorx Structure Minimum system requirements to run CADWorx Plant Design Suite are those recommended for the version of AutoCAD (or Autodesk vertical product) or BricsCAD that you have chosen to use as your design.

Contents • • • • • • • • • • • • • • • • • • • • • • • Software architecture [ ] Xen Project runs in a more privileged CPU state than any other software on the machine. Responsibilities of the hypervisor include memory management and CPU scheduling of all virtual machines ('domains'), and for launching the most privileged domain ('dom0') - the only virtual machine which by default has direct access to hardware. From the dom0 the hypervisor can be managed and unprivileged domains ('domU') can be launched. The dom0 domain is typically a version of. User domains may either be traditional operating systems, such as under which privileged instructions are provided by hardware virtualization instructions (if the host processor supports, e.g., and ), or para-virtualized operating systems whereby the operating system is aware that it is running inside a virtual machine, and so makes hypercalls directly, rather than issuing privileged instructions.

Xen Project boots from a such as, and then usually loads a host operating system into the host domain (dom0). History [ ] Xen originated as a research project at the led by, a in the, and his PhD student Keir Fraser.

The first public release of Xen was made in 2003, with v1.0 following in 2004. Soon after, Ian and Keir along with other Cambridge alumni including founded XenSource Inc. To turn Xen into a competitive enterprise product. The Open Source Xen Project continued to be supported by XenSource, then by Citrix following XenSource's acquisition in October 2007.

This organization supports the development of the project and also sells enterprise versions of the software. On October 22, 2007, completed its acquisition of XenSource, and the Xen Project moved to the xen.org domain. This move had started some time previously, and made public the existence of the Xen Project Advisory Board (Xen AB), which had members from,,,,,, and. The Xen Advisory Board advises the Xen Project leader and is responsible for the Xen trademark, which Citrix has freely licensed to all vendors and projects that implement the Xen. Citrix has also used the Xen brand itself for some proprietary products unrelated to Xen, including at least 'XenApp' and 'XenDesktop'. On April 15, 2013, it was announced that the Xen Project was moved under the auspices of the as a Collaborative Project. The Linux Foundation launched a new trademark for 'Xen Project' to differentiate the project from any commercial use of the older 'Xen' trademark.

A new community website was launched at xenproject.org as part of the transfer. Project members at the time of the announcement included: Amazon, AMD, Bromium, CA Technologies, Calxeda, Cisco, Citrix, Google, Intel, Oracle, Samsung, and Verizon. The Xen project itself is self-governing.

Release history for Xen Project (upstream project) [ ] Version Release date Notes 1.0 03- October 2, 2003 2.0 04- November 5, 2004 3.0 05- December 5, 2005 • Supports the for HVM guests. • Support for the Intel architecture. The releases up to 3.0.4 also added: • Support for the extensions. • Support for the architecture. • Graphical framebuffer support for paravirtualized guests. 3.1 07- May 18, 2007 for HVM guests, XenAPI 3.2 08- January 17, 2008 PCI passthrough and ACPI S3 standby mode for the host system.

3.3 08- August 24, 2008 Improvements for the PCI passthrough and the power management. Xen ARM hypervisor source code released for ARM CPU support 3.4 09- May 18, 2009 Contains a first version of the 'Xen Client Initiative', shortly XCI.

4.0 10- April 7, 2010 Makes it possible to use a dom0 Linux kernel, which has been implemented by using PVOps. A Linux kernel of version 2.6.31 has been modified for this purpose, because the official Linux kernel actually does not support the usage as dom0 kernel (date July 2010). 4.1 11- March 25, 2011 Some of the improvements: Support for more than 255 processors, better stability. Linux kernel v2.6.37 and onward support usage as dom0 kernel.

4.2 12- September 8, 2012 XL became the default toolstack. Support for up to 4095 host processors and up to 512 guest processors. 4.3 13- July 9, 2013 Experimental ARM support. NUMA-aware scheduling.

4.4 14- March 10, 2014 Solid libvirt support for libxl, new scalable event channel interface, hypervisor ABI for ARM declared stable, Nested Virtualization on Intel hardware. 4.5 15- January 17, 2015 With 43 major new features, 4.5 includes the most updates in the project’s history. 4.6 15- October 13, 2015 Focused on improving code quality, security hardening, enablement of security appliances, and release cycle predictability. 4.7 16- June 24, 2016 Improved: security, live migrations, performances and workload. Hardware support (ARM and Intel Xeon). Xen in Linux distributions and Linux upstream [ ] Since version 3.0 of the, Xen support for dom0 and domU exists in the mainline kernel.

This article needs to be updated. Please update this article to reflect recent events or newly available information. (May 2016) companies use hypervisors to provide. (since August 2006), IBM,,,, and use Xen as the primary VM hypervisor for their product offerings. Virtual machine monitors (also known as hypervisors) also often operate on and large servers running IBM, HP, and other systems. [ ] Server virtualization can provide benefits such as: • consolidation leading to increased utilization • rapid provisioning • dynamic against software failures (through rapid bootstrapping or rebooting) • hardware fault tolerance (through migration of a virtual machine to different hardware) • the ability to securely separate virtual operating systems • the ability to support legacy software as well as new OS instances on the same computer Xen's support for virtual machine live migration from one host to another allows and the avoidance of downtime.

Virtualization also has benefits when working on development (including the development of operating systems): running the new system as a guest avoids the need to reboot the physical computer whenever a bug occurs. Guest systems can also help in computer-security research, allowing study of the effects of some or without the possibility of compromising the host system. Finally, hardware appliance vendors may decide to ship their appliance running several guest systems, so as to be able to execute various pieces of software that require different operating systems.

Technology [ ] Types of virtualization [ ] Xen supports five different approaches to running the guest operating system: HVM (hardware virtual machine), HVM with PV drivers, PVHVM (HVM with PVHVM drivers), PVH (PV in an HVM container) and PV (paravirtualization). Paravirtualization – modified guests [ ] Xen supports a form of virtualization known as paravirtualization, in which guests run a modified operating system. The guests are modified to use a special hypercall, instead of certain architectural features. Through paravirtualization, Xen can achieve high performance even on its host architecture (x86) which has a reputation for non-cooperation with traditional virtualization techniques. Xen can run paravirtualized guests ('PV guests' in Xen terminology) even on CPUs without any explicit support for virtualization. Paravirtualization avoids the need to emulate a full set of hardware and firmware services, which makes a PV system simpler to manage and reduces the attack surface exposed to potentially malicious guests.

On 32-bit x86, the Xen host kernel code runs in, while the hosted domains run in Ring 1 (kernel) and Ring 3 (applications). Hardware-assisted virtualization, allowing for unmodified guests [ ] CPUs that support virtualization make it possible to support unmodified guests, including proprietary operating systems (such as Microsoft Windows). This is known as, however in Xen this is known as hardware virtual machine (HVM). HVM extensions provide additional execution modes, with an explicit distinction between the most-privileged modes used by the hypervisor with access to the real hardware (called 'root mode' in x86) and the less-privileged modes used by guest kernels and applications with 'hardware' accesses under complete control of the hypervisor (in x86, known as 'non-root mode'; both root and non-root mode have Rings 0–3).

Both Intel and have contributed modifications to Xen to support their respective Intel VT-x and AMD-V architecture extensions. Support for v7A and v8A virtualization extensions came with Xen 4.3. HVM extensions also often offer new instructions to support direct calls by a paravirtualized guest/driver into the hypervisor, typically used for I/O or other operations needing high performance. These allow HVM guests with suitable minor modifications to gain many of the performance benefits of paravirtualized I/O. In current versions of Xen (up to 4.2) only fully virtualized HVM guests can make use of hardware support for multiple independent levels of memory protection and paging. As a result, for some workloads, HVM guests with PV drivers (also known as PV-on-HVM, or PVH) provide better performance than pure PV guests. Xen HVM has device emulation based on the project to provide I/O virtualization to the virtual machines.

The system emulates hardware via a patched QEMU 'device manager' (qemu-dm) daemon running as a backend in dom0. This means that the virtualized machines see an emulated version of a fairly basic PC. In a performance-critical environment, PV-on-HVM disk and network drivers are used during normal guest operation, so that the emulated PC hardware is mostly used for booting.

Virtual machine migration [ ] Administrators can 'live migrate' Xen virtual machines between physical hosts across a LAN without loss of availability. During this procedure, the LAN iteratively copies the memory of the virtual machine to the destination without stopping its execution.

The process requires a stoppage of around 60–300 ms to perform final synchronization before the virtual machine begins executing at its final destination, providing an illusion of seamless migration. Similar technology can serve to suspend running virtual machines to disk, 'freezing' their running state for resumption at a later date. Target processors [ ] The Xen hypervisor has been ported to a number of processor families. • Intel: IA-32, IA-64 (before version 4.2 ), x86-64 • PowerPC: previously supported under the XenPPC project, no longer active after Xen 3.2 • ARM: previously supported under the XenARM project for older versions of ARM without virtualization extensions, such as the Cortex-A9. Currently [ ] supported since Xen 4.3 for newer versions of the ARM with virtualization extensions, such as the.

•: XLP832 experimental port Scalability [ ] Xen can scale to 4095 physical CPUs, 256 VCPUs per HVM guest, 512 VCPUs per PV guest, 16 TB of RAM per host, and up to 1 TB of RAM per HVM guest or 512 GB of RAM per PV guest. Hosts [ ] Xen can be shipped in a dedicated virtualization platform, such as Citrix XenServer Enterprise Edition (formerly XenSource's XenEnterprise). Alternatively, Xen is distributed as an optional configuration of many standard operating systems.

Xen is available for and distributed with: • offers a minimal dom0 system (, ) that can be run from removable media, like USB sticks. • GNU/Linux (since version 4.0 'etch') and many of its derivatives • 11 includes experimental host support. • and both have packages available to support Xen. • (since version 4) • can function as domU and dom0 • -based distributions can function as dom0 and domU from Nevada build 75 onwards. • 10.x to 12.x; only 64-bit hosts are supported since 12.1 • for secure desktop usage • (since version 10) • (since 2013 with, before with ) • (since; also 8.04, but no dom0-capable kernel in 8.10 until 12.04 ) Guests [ ] Unix-like systems as guests [ ] Guest systems can run fully virtualized (which requires hardware support) or paravirtualized (which requires a modified guest operating system).

Most operating systems which can run on PC can run as a Xen HVM guest. Commercial versions [ ] • Citrix XenServer • FusionSphere • • Thinsy Corporation • (discontinued by Oracle) • by Star Lab Corp.

The Xen hypervisor is covered by the GNU General Public Licence, so all of these versions contain a core of free software with source code. However, many of them contain proprietary additions. April 12, 2017. Retrieved June 1, 2017. May 22, 2017.

Retrieved June 1, 2017. Retrieved April 5, 2015. Free Download Style Dangdut Keyboard Yamaha Psr S710.

February 8, 2007. Retrieved June 8, 2013.

Citrix Systems. July 12, 2007. Retrieved June 8, 2012. • (PDF) (PDF). June 1, 2008.

Retrieved June 8, 2013. Retrieved May 3, 2013.

Retrieved May 3, 2013. Retrieved May 3, 2013. Retrieved May 3, 2013. October 2, 2003. Retrieved October 18, 2012. • Jonathan Corbet (October 2, 2003).. Retrieved October 18, 2012.

• Jonathan Corbet (November 5, 2004).. Retrieved October 18, 2012. • Jonathan Corbet (December 6, 2005).. Retrieved October 18, 2012. XenSource, Inc. December 10, 2005. Archived from on December 10, 2005.

Retrieved October 18, 2012. December 14, 2005. Retrieved June 8, 2013. October 17, 2006. Retrieved June 8, 2013. December 20, 2006.

Retrieved June 8, 2013. May 18, 2007. Retrieved June 8, 2013. Retrieved October 18, 2012. August 25, 2008.

Archived from on March 14, 2012. Retrieved October 18, 2012.

May 18, 2009. Retrieved October 18, 2012. April 9, 2010. Archived from on March 14, 2012. Retrieved October 18, 2012. • (PDF) (PDF).

Retrieved October 18, 2012. March 25, 2011. Retrieved October 18, 2012. Retrieved June 8, 2013. October 13, 2015.

Retrieved October 13, 2015. July 9, 2013.

Retrieved July 16, 2013. March 10, 2014. Retrieved March 10, 2014. Retrieved March 10, 2014. Retrieved March 10, 2014. January 15, 2015. Retrieved January 17, 2015.

May 30, 2011. Retrieved October 18, 2012.

• • (PDF) (PDF). Retrieved April 5, 2015. • Suzanne Tindal (February 28, 2011).. ZDNet Australia. April 1, 2012. Retrieved June 27, 2014. September 13, 2011.

Retrieved October 18, 2012. • Roger Pau Monne. Retrieved April 6, 2015. • Robin and Irvine,, 9th Usenix Security Symposium, 2000 • Gil Neiger, Amy Santoni, Felix Leung, Dion Rodgers, Rich Uhlig., Intel Technology Journal, Volume 10 Issue 03, August 2006. •, intel.com •. Retrieved April 6, 2015.

December 17, 2012. Retrieved January 22, 2014. August 15, 2010. Retrieved January 22, 2014. • Mashable (September 4, 2012)..

Retrieved January 22, 2014. Retrieved October 18, 2012. Retrieved September 28, 2015. Retrieved July 14, 2014. Retrieved June 8, 2013.

November 8, 2011. Retrieved June 8, 2013. Retrieved January 22, 2014. September 5, 2012. Retrieved October 18, 2012.

June 25, 2012. Retrieved October 18, 2012.

The FreeBSD Documentation Project. September 22, 2016. Retrieved October 23, 2016. Retrieved June 12, 2016. • (PDF) (PDF). University of Cambridge SOSP'03 paper.

Retrieved October 18, 2012. • The information on the XenSource wiki seems to be outdated, but newer information is here:. Jolokia Networks. Retrieved October 18, 2012.

Retrieved 2016-12-06. Citrix Blogs. Retrieved 2016-12-06. Retrieved 2016-12-06. Retrieved 2016-12-06. Citrix Blogs.

Retrieved 2016-12-06. • Citrix XenServer 7.0 Release Notes •.

Retrieved 2016-12-06. Further reading [ ] • Paul Venezia (April 13, 2011), External links [ ] Wikimedia Commons has media related to.