similar to: [PATCH] ioemu: enable Cirrus VGA emulation

This is a slightly modified version of the original VGA patch that removes changes to the configure script to check for SSE2 capabilities. SSE2 is now only checked at run time. Signed-off-by: Don Dugger <donald.d.dugger@intel.com> -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Donald.D.Dugger@intel.com Ph: (303)440-1368 diff -r c445d4a0dd76

QEMU fixes - VMX domain owns 0xcxxxx. - guard the fprintf with a log level check Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- 1.1/tools/ioemu/hw/pc.c 2005-05-19 15:04:52 -07:00 +++ edited/tools/ioemu/hw/pc.c 2005-05-23 16:37:18 -07:00 @@ -419,11 +419,11 @@ ret = load_image(buf, phys_ram_base + vga_bios_offset); #endif +#ifndef NOBIOS /* setup basic memory access

Import "DisplayState interface change" from qemu mainstream: the patch has been adapted to qemu-xen and merged with several following fixes. The original qemu svn commit is the following: git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6336 c046a42c-6fe2-441c-8c8c-71466251a162 Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- diff --git a/console.c

The system is Mandrake-9.1 Linux wih gcc-3.2.2. I am trying to compile xenolinux-2.4.24 (with vanilla sources from ftp.kernel.org for linux-2.4.24). The steps of mkbuildtree ARCH=xeno make menuconfig ARCH=xeno make dep produce no errors, but ARCH=xeno make bzImage results in following error messages. Any pointers will be appreciated. -ishwar --- gcc -D__KERNEL__

Hi, I've got a system with a 3com 590 NIC (Boomerang / Vortex), and instructed it to boot using PXE. System load the initrd and the kernel image from the FTP server, boots the image and starts the install routine. So far so good. The strange part is that after the PXE boot completes the kernel doesn't detec the NIC. It's not a driver issue, the same kernel on a floppy does

I''ve just finished Xeno-HOWTO which contains a detailed list of instructions on how to setting up Xen and XenoLinux, from downloading Bitkeeper, compilation of Xen, XenoLinux, tools to configuration, start and stop of new domains. A complete version has just been pushed in xeno.bk and xeno-1.1.bk in our Laboratory. A partital version is already available in

Hello folks, I have this really strange routing problem that no amount of googling and experimenting has been able to solve. Then again, I''m new to Xen and "advanced" networking, so I could be missing something very basic. Summary: an unprivileged domU with PCI frontend for a NIC is used as a router; icmp gets routed, but tcp/ip only partially. I''m using a

Hello folks, I have a really strange routing problem that no amount of googling and experimenting has been able to solve. Then again, I''m new to Xen and "advanced" networking, so I could be missing something very basic. Summary: an unprivileged domU with PCI frontend for a NIC is used as a router; icmp gets routed, but tcp/ip only partially. I''m using a xen-unstable

Hello, I''m trying to write a module to play with hypercall. So I wrote the following module: -------------------------xvifgetinfo.c---------------- /* * xvifgetinfo.c * * The routines in this file are used to get information about virtual * network interface provide by Xen. * */ #include <linux/module.h> #include <linux/init.h> #include <linux/kernel.h>

BTW, the xenlinux-2.6.11.bk''s version is: ChangeSet@1.2085, 2005-05-12 11:10:24-06:00, djm@kirby.fc.hp.com More work on hyperprivops Signed-off-by: Dan Magenheimer <dan.magenheimer@hp.com> Thanks, Kevin >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com >[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Tian, Kevin >Sent: Friday,

From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:07:16 +0200 Subject: [PATCH] [PATCH 1/3] virtio infrastructure This patch implements the basic infrastructure for virtio devices. These devices are exposed to the guest as real PCI devices. The PCI vendor/device IDs have been donated by Qumranet and the

From 80b234220ea85d6fb291b0509ce2b3322e5ecc1f Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:07:16 +0200 Subject: [PATCH] [PATCH 1/3] virtio infrastructure This patch implements the basic infrastructure for virtio devices. These devices are exposed to the guest as real PCI devices. The PCI vendor/device IDs have been donated by Qumranet and the

Yes, like real Linux/ia64, it is not possible to run the same Xenlinux bits both on ski and on real hardware. A different configuration and build is required. The config difference is the same as it was with the privified xenlinux... I think you did that successfully before (with privified xenlinux) so give that config file a try and if it doesn''t work, let me know. BTW, I think I know

Hey everyone, Thanks for the quick help resonses once again, We got some mail saying that RAM disks were not the way to go. So we re-installed, made several partitions to use, and rebuilt xen. However, we''re still having trouble mounting partitions when xeno-linux boots. We give a physical grant of one of our newly made paritions (/dev/hda14 in particular) to the domain. But when

The mount /dev/hdc /mnt problem still exists for me. Regards Robin. Here''s the dmesg of Xen: __ __ _ ____ \ \/ /___ _ __ / | |___ \ \ // _ \ ''_ \ | | __) | / \ __/ | | | | |_ / __/ /_/\_\___|_| |_| |_(_)_____| http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 1.2

To accomodate Intel''s ACPI support, VMX assist now lives at 0xD0000. Leendert Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com> --- xeno-unstable.orig/xen/include/public/vmx_assist.h 2005-04-22 02:26:10.000000000 -0400 +++ xeno-unstable.mine/xen/include/public/vmx_assist.h 2005-05-31 13:22:39.000000000 -0400 @@ -21,7 +21,7 @@ #ifndef _VMX_ASSIST_H_ #define

From 4780a4792ca7776268107e200ae77003c36d55c9 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:52:43 +0200 Subject: [PATCH] virtio block device This patch implements the backend support for the virtio block device. It's designed to support in-order queueing of a virtually unlimited size so it will be able to perform better than SCSI. Besides

From 4780a4792ca7776268107e200ae77003c36d55c9 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:52:43 +0200 Subject: [PATCH] virtio block device This patch implements the backend support for the virtio block device. It's designed to support in-order queueing of a virtually unlimited size so it will be able to perform better than SCSI. Besides

From 83e942e0c7634121243478fa2f4e3459b33d4a67 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:43:24 +0200 Subject: [PATCH] virtio network device This patch implements the backend support for the virtio network device. The device is optimized for virtualized environments by limiting the number of guest=>host transitions per-packet. In the best

From 83e942e0c7634121243478fa2f4e3459b33d4a67 Mon Sep 17 00:00:00 2001 From: Dor Laor <dor.laor@qumranet.com> Date: Wed, 19 Dec 2007 23:43:24 +0200 Subject: [PATCH] virtio network device This patch implements the backend support for the virtio network device. The device is optimized for virtualized environments by limiting the number of guest=>host transitions per-packet. In the best