similar to: Qemu-0.8.1 based ioemu preview available

resend to larger group: which one is the right one? I''m going thru some merge hell and a need some newer PPC code from kernel.org. is it: http://xenbits.xensource.com/linux-2.6-xen.hg (worked on) --or-- http://xenbits.xensource.com/ext/linux-2.6-merge.hg (six weeks of nothing) there is also linux-2.6.rc-xen.hg, linux-2.6.tip-xen.hg, linux-2.6- patchqueue.hg the PPC team

Hello, September 7th I pulled a copy of Xen 4 with: hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg I installed development tools and packages from the Xen 4 wiki: bcc bin86 gawk bridge-utils iproute libcurl3 libcurl4-openssl-dev bzip2 module-init-tools transfig tgif texinfo texlive-latex-base texlive-latex-recommended texlive-fonts-extra texlive-fonts-recommended

Build infomation: build of xen-unstable(cs:19963 and 19974) failed for i386/x86_64,details as below: .... make[1]: Entering directory `/builddir/build/BUILD/xen-unstable/tools'' set -ex; \ if test -d git://xenbits.xensource.com/qemu-xen-unstable.git; then \ rm -f ioemu-dir; \ ln -sf git://xenbits.xensource.com/qemu-xen-unstable.git ioemu-dir; \ else \ if [ ! -d ioemu-remote ];

There was some discussion about the lack of visibility of the Xen4CentOS development process. The Xen spec files and supporting patches are kept in a git tree. I've pushed copies of these trees here: https://github.com/gwd/sig-virt-xen xen-44 is the branch for Xen 4.4 development, and xen-46 is the branch for Xen 4.6 development. As is normal, these repos do not contain many of the binary

Il 27/04/2011 14:37, Ian Campbell ha scritto: > Which specific revision of qemu-xen-4.1 are you using? I'm using a tarball from http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz It seems Thomas used the tools/ioemu-qemu-xen subdirectory as source for xen-qemu-dm. At a first glance I didn't notice debian/mypatches/add-rules.patch: it adds Rules.mk from the tools

Hi all, this is the tenth version of the patch series to introduce upstream qemu and seabios in the xen-unstable build system. Changes to v9: - rename QEMU_UPSTREAM_TAG to QEMU_UPSTREAM_REVISION: we are going to use it with a branch name by default; - set QEMU_UPSTREAM_REVISION to "master" by default; - set SEABIOS_UPSTREAM_URL to git://xenbits.xen.org/seabios.git by default; - add

Hi, when I try to build xen-unstable/staging (cs 24143) tools via make tools I get: ... got 1b6bfb99c2b55ff2e35ab61caf307dad3aebc82a got efd594c960330cc3eee44e65f5fee258c798e610 got ccc9677505c0dd2c6c5054e73a42cef2d25687b4 got 86a2a2a59a8b76117b221c712ba0a156d21441c9 error: File efd594c960330cc3eee44e65f5fee258c798e610

Hi. I can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis

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

OK, I've got a basic initial port of the xen package up to 4.4.0. But before I post that, I wanted to get comments on a new method of managing the Xen part of the patchqueue. You can find the RFC branch here: repo: http://github.com/gwd/sig-virt-xen branch: out/git-am-patchqueue-RFC-v1 The basic idea is to put as much as possible into a 'git am' file. This file can easily be

This patch adds lost logic for vga initialization. It was lost after changing to new Qemu. Signed-off-by : Kevin Tian <kevin.tian@intel.com> Signed-off-by : Zhang Xiantao <xiantao.zhang@intel.com> Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

# 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

I''ve been doing some merge work between tools/ioemu and qemu upstream. I came across this commit: changeset: 11209:9bb6c1c1890a07885265bbc59f4dbb660312974e date: Sun Aug 20 23:59:34 2006 +0100 files: [...] description: [qemu] hdparm tunable IDE write cache for HVM qemu 0.8.2 has a flush callback to the storage backends, so now it is possible to implement

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.

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag on disks with qemu-xen" has been applied to Xen4CentOS. I assume this was on purpose? If not, I can have someone try adding the original patch from http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b

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

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 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

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