similar to: [PATCH v10 0/7] build upstream qemu and seabios by default

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

Hello, I''ve tested Xen 4.2 on CentOS 6.3(x86_x64) My goal is to connect to Windows VM on Xen 4.2 using SPICE client. Installation of Xen 4.2 was successful. Also creating Windows VM using qemu-dm and connecting to it using VNC are OK. But qemu-dm can''t support SPICE, so I installed upstream qemu. ( http://wiki.xen.org/wiki/QEMU_Upstream) I also installed spice-server and

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1331924173 -3600 # Node ID bf1d5778ffd10858b402068b9473e410791ebd07 # Parent 72e6530b29463f0913af365f5d085d94ff75627c tools: specify datadir for qemu-xen build to fix firmware loading qemu-xen does currently not find the firmware files, such as vgabios-cirrus.bin. The reason is that qemu-xen uses the default prefix /usr/local.

This patch set mainly allows the user to build a seabios or rombios only version of hvmloader. In addition, when building a seabios only hvmloader, Option ROMs like vgabios and etherboot are no longer required, and therefore can be disabled from the build. Dependency on the bcc compiler can also be avoided the same way. v2: Separate patches for separate issues Introduced config option to

Hi, I am trying to install xen and provide libvrit support to it but while installing at some point of time it tries to connect to GIT repository and creates a clone but I am behind firewall and it is getting timed out.... :( I am pasting a screenshot below. Can anyone of you please help me out with this one. // Varun

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

tools/libxl: Disable useless empty floppy drive with qemu-xen Signed-off-by: Fabio Fantoni <fabio.fantoni@heliman.it> --- tools/libxl/libxl_dm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c index 51f9914..c265618 100644 --- a/tools/libxl/libxl_dm.c +++ b/tools/libxl/libxl_dm.c @@ -406,6 +406,9 @@ static char **

Did something had chaqnged with spice code or settings. I just compiled latest git of 4.4 unstable and I get is a black screen all I see is the green boot image from server 2012 but I dont get blue windows logo and window does not resize it stays black. I reverted back to older git revision of 4.4 and everything is working fine with. _______________________________________________ Xen-users

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).

This small series reintroduces OVMF support in Xen You can fetch working OVMF tree on: git://xenbits.xen.org/people/liuw/ovmf.git master Working changeset that can be sticked in Config.mk is: 8833370303d3bf3153760ee42760ef1b9b5c562 Note that VNC doesn''t work properly when using OVMF, but that''s not OVMF''s problem. This issue should be addressed in Xen and I''m

2011/7/19 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: > CC''ing Tim and xen-devel > > On Mon, 18 Jul 2011, Jiageng Yu wrote: >> 2011/7/16 Stefano Stabellini <stefano.stabellini@eu.citrix.com>: >> > On Fri, 15 Jul 2011, Jiageng Yu wrote: >> >> 2011/7/15 Jiageng Yu <yujiageng734@gmail.com>: >> >> > 2011/7/15

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

I am updating this patch to use the tools/ioemu-dir symlink as qemu source directory in case CONFIG_QEMU != ioemu. Before we were trying to figure out where is the actual qemu source dir again. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- diff -r f5e72cbfbb17 stubdom/Makefile --- a/stubdom/Makefile Wed Sep 10 11:26:16 2008 +0100 +++ b/stubdom/Makefile Thu Sep

Hi,all I have tried to passthrough GPU card(Nvidia quadro 4000) on the latest Xen unstable version (QEMU is using Qemu-upsteam-unstable, not traditional Qemu). This issue as below: Windows7 64-bit guest will blue screen when GPU passthrough configure 4g memory,blue screen code is 50, and SUSE 11 64-bit guest will always stay at the grub screen. I noticed that it will relocate RAM that

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

I''m happy to announce that we have moved the xen-unstable.hg Solaris dom0 development out to the OpenSolaris community. For hard core developers, you can download, build, and run Solaris dom0 and xen-unstable bits following the instructions at the end of this post. We are currently sync''d up to changeset #17644 (~May 15th). Hopefully we will sync up with xen-unstable.hg every