Skip to content

Xen 3.4 Feature Request from Customers

To Xen customers:

If  you are using Xen, either as a direct download from the site or from a partner who is leveraging Xen as their virtualization engine (e.g. Oracle, RedHat, Novell, Sun, etc) they I am looking for you. The Xen development community is actively looking for feedback on the existing solution as the new Xen 3.4 release plan is built. All feature ideas can be submitted to this blog posting as a comment, direct mail to myself, or via an email to xen-devel.

Be Sociable and Share!

Posted in Community.

Tagged with , .

3 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. styro says

    Thanks for asking :)

    This thread about consistent LVM snapshots from Dom0 is something I’d like to see:

    I don’t recall this happening as part of 3.3 (I could be wrong – we haven’t installed 3.3 yet).

  2. Rob says

    A great feature would be the ability to lock a specific hardware to a specific process.


    You have two video cards and two network cards, you want to run WinXP and Linux with WinXP using one video card and one network card with Linux using the other ones.

    You do NOT want to Virtualize the hardware, you want to assign it, permanantly (both for performance issues and because it would be foolish to be able to Virtualize when you have two of something (like Video monitors or network cards)).

    We desire direct hardware access to allow WinXP OpenGL Accelerated drivers (from the Manufacturer, and only available for Windows) to run unfettered on the WinXP side and we want to be able to run Wireshark (or other program requiring direct access to the network card) on the Linux side.

    Let us assign hardware (and lock it) to a process.

    You would want to Virtualize the processor and may desire to Virtualize the USB ports, Firewire, etc.

    Lets (at least) have a (short / long?) list of devices that can be put into a “Request Pool” and allocated.


    Monitor 1 would be assigned in Xen’s boot script to be called “Windows_Video_Monitor” and the name “Windows_Video_Monitor” could be ‘mapped’ to “VGA” so when Windows boots it sees that there is a “VGA” monitor (only one, it can’t see the other) available and ‘grabs’ it.

    Monitor 2 would be assigned in Xen’s boot script to be called “Linux_Video_Monitor” and the name “Linux_Video_Monitor” could be ‘mapped’ to “VGA” so when Linux boots it sees that there is a “VGA” monitor (only one, it can’t see the other) available and ‘grabs’ it.

    There could be a “Helper Executable” that could be ran when WinXP or Linux starts to tell the OS the name of the “Video Device Driver” so that WinXP could choose to use “Windows_Video_Monitor” and set the ‘screen resolution and bits’ to a prechosen vaule and when Linux starts it’s “Helper Executable” would choose “Linux_Video_Monitor” as it’s video device and set it up to use ‘screen resolution and bits’ that may (or may not) differ from the WinXP setup.

    Another example is just ONE video card and 16 ethernet ports with WinXP and half a dozen flavors of Linux running. All would _share_ the same monitor (and it would be virtualized and ‘swapable’ _BUT_ each process would be locked to ONE (or Bridged to a few) ethernet ports to: Improve performance, ensure _absolute_ security and do away with _unneccesary_ Virtualization where it is not desired.

    Sometimes a great thing (Virtualization) can go too far (Full Virtualization, and no ability to ‘assign / lock’) so I ask for the ability to have a little less Virtualization (and a little more control).


  3. alex says

    Hello, Rob

    I am interested in this kinds of applications too.
    Can we communicate via email?
    my email address is


You must be logged in to post a comment.