These behave almost identically to Windows Vista Beta builds and are relatively easy to virtualize. Dealing with the Time Bomb
If you are using or standardizing on KVM with libvirt, creating a .qcow2 image via qemu-img is still recommended for performance, but you might need to use the virtio-win ISO to load drivers during the Windows "Load Driver" screen. windows longhorn qcow2 work
-cpu pentium3 : Emulating an older CPU limits advanced instruction sets that the unoptimized Longhorn kernel doesn't know how to handle. If you experience crashes on launch, switching to pentium3 or core2duo usually fixes it. These behave almost identically to Windows Vista Beta
The beauty of QCOW2 is that it separates the "base image" from the "user data." A pristine Longhorn build might only take up 2GB. As you play with the sidebar, load the WinFS data stores, or install Longhorn-specific Win32 apps, the file grows. But you can always roll back to the pristine base. It preserves the digital artifact in amber while allowing you to play with it. If you experience crashes on launch, switching to