similar to: Ioemu (aka qemu) pci internals documentation

Hello, A preview of the qemu 0.8.1 based ioemu is now available at: http://xenbits.xensource.com/chris/add-ioemu-new and http://xenbits.xensource.com/chris/enable-ioemu-new In addition to these two patches, you need a copy of qemu-0.8.1 and place it into tools/ioemu-new -- one option is the tarball available at http://xenbits.xensource.com/chris/ioemu-cvs-qemu-0.8.1.tar.bz2 which extracts to

ioemu-remote: Enable pci pass-through by default. -- Jean Guyader _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi folks There are two components, which are currently not included in the main utils package: ioemu, xenfb. ioemu is currently shipped in its own package, xenfb is not shipped at all. Should we fold them into the main utils package for simplicity? ioemu adds 300k to the package and 4300k in one dependency (libsdl1.2debian). xenfb adds another 200k to the package and 200k in one dependency

# HG changeset patch # User john.levon@sun.com # Date 1196969481 28800 # Node ID 2c28ac4db1f7542220b1472821e8631b79b6a23a # Parent 4a98d4b6e4daccd610175e3c0f8cab49b056c649 Fix ioemu compile serial.c was including another Linux-specific header. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/ioemu/hw/serial.c b/tools/ioemu/hw/serial.c --- a/tools/ioemu/hw/serial.c +++

ioemu: fix xenfb slow case update Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 067d8f19e78a tools/ioemu/hw/xenfb.c --- a/tools/ioemu/hw/xenfb.c Thu Feb 28 13:55:37 2008 +0000 +++ b/tools/ioemu/hw/xenfb.c Fri Feb 29 15:25:17 2008 +0000 @@ -1072,7 +1072,7 @@ /* A convenient function for munging pixels between different depths */ #define

Hello. I''m trying to set up hvm for linux or windows. I start with a very simple configuration without disks at all. but the virtual machine does boot or even "power up". If i remove the ioemu from the network device and specify type=brige or type=route everything goes fine, the boot process is starting but then I cant get network working in the guest.

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal When trying to create an HVM domain with vif settings enabled (as default) qemu-dm fails to start the virtual machine claiming that the tap device cannot be found. This is because qemu-dm tries to execute /etc/xen/qemu-ifup which is instead located in /etc/xen/scripts/qemu-ifup. As a side note qemu-dm seems to be

Package: xen-ioemu-3.0-unstable Version: 3.0-unstable+hg11561-1 Severity: normal Hi, in #393609 /etc/xen/scripts/qemu-ifup is wrongly placed/referred. This script is missing from the amd64 package, making network enabled HVM domain not startable. Regards, L -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture:

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: normal Under this Xen setup, (Linux) HVM guests fail to have network active when running with *routed* networking, as some hosting providers require (in my case, OVH). In this scenario: * the host is a described below * the guest runs as HVM. * the guest runs exclusively with ioemu; virtual network drivers are not available (vanilla lenny

The existing stdvga driver from xen-unstable tools/ioemu/hw/vga* does not save the emulated VGA memory contents. The symptoms include video malfunction after restore, including black screen (which can often be fixed by asking the guest to redraw) but also missing font setup etc. The attached patch fixes this by saving the entire VGA memory buffer, just like the Xen ioemu Cirrus emulator does. I

tag 554805 + patch thanks The problem to solve is that qemu-ifup assumes the world is always bridged, and vif-routed does not know of the concept of TAP devices, and even if it did, it has at this point no way to get at qemu's TAP device anyway. The following set of patches help run in the ioemu-HVM situation: * xend-image.py.diff : modifies the HVM loader so that when running in

Hello, ioemu-qemu-xen directory under xen-unstable.hg/tools/ is missing in Xen Unstable version. Anybody has any idea how to get the ioemu-qemu-xen directory in Xen Unstable version. Thank you, Regards, Prashanth _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools

Hello, ioemu-qemu-xen directory under xen-unstable.hg/tools/ is missing in Xen Unstable version. Anybody has any idea how to get the ioemu-qemu-xen directory in Xen Unstable version. Thank you, Regards, Prashanth _______________________________________________ Xen-tools mailing list Xen-tools@lists.xensource.com http://lists.xensource.com/xen-tools

Hello every body. Well, my question is very simple . I Have a HVM working fine ( I hope so ... ) on a CentOS 5.1 , xen 3.1. I created config file by hand .. I''m not using virtmanager from CentOS .. I '' m using LVM dev w/o file system formated. My HDA is configured like this: disk = [ ''phy:/dev/vms_1/win01,hda,w'' ] My question , what is the diference if I

Hi, From cset 10921, ioemu: prefix is removed from disk config in /etc/xen/xmexample.hvm. Now HVM VBD driver is available, this thus raises a question: how would HVM domain know if one disk is a qemu-dm disk or a VBD disk? From current implementation, qemu-dm will recognize disk had, hdb, hdc, hdd, and VBD drive can recognize all disk (had~hdd, hde, hdf ...) . So the result is: qemu-dm will

Hi! Attached patch makes git-ioemu compile on NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> P.S.: I''m about sending the pieces to qemu-devel. The changes in vl.c already went upstream in qemu''s svn c/s 5646. -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz

In config file, ''*type=ioemu*'' is added with vif . Does it make the difference if we don''t add. Because i did not notice any difference in para as well as full virtulization. Same as in case of exporting the disk to Guest dom. Is it just a placeholder or else ? Second thing, I am running RHEL3 as a HVM DomU on xen-3.0.4. Every thing works fine, but i had a problem to

in xen.hg/tools/ioemu/tools/vl.c, function net_tap_init() if (need_setphysaddr) { if ((r = dlpi_set_physaddr(dh, DL_CURR_PHYS_ADDR, s->mac_addr, ETHERADDRL)) != DLPI_SUCCESS) { fprintf(logfile, "net_tap_init: cannot set physaddr (%d)\n", r);

Hi all: I installed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront

Hi all: I installed Fedora 6 on xen 3.0.4(which is intalled in fedoa 7) as domainU, I find the following information int the cfg file: # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ ''type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci'' ] # type=ioemu specify the NIC is an ioemu device not netfront