similar to: [PATCH 2/4][RFC] Paravirtual Framebuffer/Keyboard

_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

This is the patch from Amos Waterland for the xenconsole to use /dev/xvc0 instead of taking over ttys. I''ve fixed a few places which needed to check for XVC mode in addition to serial mode. Also, until LANANA responds with an official minor, I''ve adjusted it to use char 250/187 (in the experimental range) as opposed to 204/187 Signed-off-by: Jeremy Katz

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

I''m breaking the tidying up into parts. The first is renaming libxc => libxenctl. I''d like to rename tools/libxc to tools/libxenctl but I thought it might be worth waiting until "flag day" so that we can avoid losing revision history. Does that seem reasonable? Rename libxc to libxenctl, xc.h to xenctl.h, and install xenctl.h to /usr/include/xen/xenctl.h

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

Hello Xen-Users, I am currently provisioning old Linux guests as HVM on a server, and giving clients access through VNC. The current setup uses the default Xen framebuffer as a VNC server (all configuration files have vnc=1 and a few other settings), and my clients are using vinagre (a.k.a. Remote Desktop Viewer) on Arch as their VNC client. Problem: Keyboard input is not consistently handled

Hi, This issue only happens on my IA32E VMX domain. IA32 VMX domain is okay. I am trying VBD disk in IA32E VMX domain. I used following disk configuration to create an IA32E VMX domain. disk = [ ''file:/mnt/disk1.img,hda,w'', ''file:/mnt/disk2.img,hde,w'' ] After creating VMX, its keyboard can not be used properly. For example, if pressing

Hi, I just added 32GB memory in my system and wanted Xen to see that memory, so enabled PAE in xen0 and XenU. I did a make menuconfig in xen0 and xenU, then did a make in xen-unstable and a make install. Whilebooting this kernel, I get the above error PAE mode mismatch. I looked under xen/include/asm-x86/processor.h has #define X86_CR4_PAE defined and so does cpufeature.h have this defined.

The attached patch: 1. Converts the shutdown driver and xend to use the store instead of control messages, 2. Includes Anthony''s xenstore notification code, and 3. Changes xend so that sysrq''s are no longer sent as "special case" shutdown messages. Store keys are cheap, so making the sysrq delivery less obscure is good. I think I have made all of the

This fixes a number of problems introduces in the recent XML-RPC check-in. The higher level errors are a great idea and I''ve also extended it a bit to have a slightly nicer interface. Please apply. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Obviously not a very fair comparison [1]. I can''t see how this was done well at all. VMWare are a bit silly to release stuff like this, just lowers the whole game. [1] http://www.vmware.com/vmtn/resources/711 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Xen patchbot -unstable wrote: > # HG changeset patch > # User emellor@leeni.uk.xensource.com > # Node ID da24df1ea484cf72dc9d367d52e828777e0e20cd > # Parent c1bb4eb565296bdb00aed84fcc877befbcebd8e9 > Improve error handling, in particular fixing the ProtocolError that is thrown > when a domain is specified by the user that does not exist. Added a few > error codes -- many

Anthony Liguori <aliguori at us.ibm.com> writes: > 4) Do virtio-pcie, make it PCI-e friendly (drop the IO BAR completely), give > it a new device/vendor ID. Continue to use virtio-pci for existing > devices potentially adding virtio-{net,blk,...}-pcie variants for > people that care to use them. Now you have a different compatibility problem; how do you know the guest

Anthony Liguori <aliguori at us.ibm.com> writes: > 4) Do virtio-pcie, make it PCI-e friendly (drop the IO BAR completely), give > it a new device/vendor ID. Continue to use virtio-pci for existing > devices potentially adding virtio-{net,blk,...}-pcie variants for > people that care to use them. Now you have a different compatibility problem; how do you know the guest

Attached patch fixes a problem in marshaling large integers. It seems to only occur on systems with very large memory. However, on those systems, it''s a show-stopper. I see this as a temporary solution until we can sanitize the XML-RPC functions and get rid of all the S-Expression stuff. I''ll run xm-test tomorrow against it. Right now I''ve only done basic