similar to: build problems with current xen unstable cpu.h vl.h:75 vl.c:24 cpu-all.h:122: error: syntax error before "float64"

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

After syncing to the latest xen-unstable sources, I am getting following compilation error : make[3]: *** No rule to make target `/data/xen-sources/xen-unstable.hg/stubdom/ioemu/i386-stubdom/qemu.a'', needed by `/data/xen-sources/xen-unstable.hg/stubdom/mini-os-x86_32-ioemu/mini-os_app.o''. Stop. make[3]: Leaving directory

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

This patch adds the ia64-specific code for new Qemu . In addition, some ia64 patches aren''t checked into xen-unstable.hg, so I reversed the related logic temporarily. Once sync with xen-ia64-unstable.hg, the logic will regain automatically. Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list

Hi, guys. I''m trying to use physical disks as virtual disks in HVM domains. But I couldn''t. I''m using cs10508 of xen-unstable.hg. When I use disk = [ ''phy:sda5,ioemu:hda,w'' ] in conf file, creating HVM domain says, I need to use ''file'' modifier if I use ''ioemu''. So, I changed it to disk = [

Hi Keir, Please pull the ia64 trees: http://xenbits.xensource.com/ext/ia64/xen-unstable.hg http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg This includes updates of acpi related files, save/restore update for pv_ops and bug fixes from Akio, and mini-os update from Samuel Thibault. Thanks, -- yamahata _______________________________________________ Xen-devel mailing list

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

Hi, I am unable to build libxl from the tools. I am getting always the following error. Disabling Werror did not solve the problem: === PCI passthrough capability has been enabled === === PCI passthrough capability has been enabled === make[4]: Entering directory `/usr/src/xen-unstable.hg/tools/ioemu-remote/i386-dm'' /usr/src/xen-unstable.hg//tools/cross-install -d -m0755 -p

Hi Ian, There have been a lot of interest on gfx passthru recently. This patch enables ATI VBIOS in passthru mode. The guest VM system BIOS (including Windows boot logo) can now show in passthru screen. We have tested with various Windows and Linux guest VMs. Please help review it. We are also looking forward to comments and suggestions from Xen community users. Signed-off-by: Wei Huang

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

Source: xen Version: 4.1.4-4 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value

This patch supports basic gfx passthrough on QEMU: - disable emulated VGA adpater if there is passthroughed gfx - register/unregister legacy VGA I/O ports and MMIOs for passthroughed gfx Signed-off-by: Ben Lin <ben.y.lin@intel.com> Signed-off-by: Weidong Han <weidong.han@intel.com> _______________________________________________ Xen-devel mailing list

I''m using FC5 with its Xen 3.0.2-2 package and 2.6.16-1.2118_FC5xen0 kernel. I''ve got a Pentium 9xx chip with virtualization enabled in the BIOS; it appears to be VT-enabled, since xm dmesg includes "(XEN) VMXON is done". I base my config file on example.hvm and on previous emails to this list. Unfortunately, I don''t get very far. xm create winxp.conf

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi there, Last night I was trying to start a HVM domU via stubdom-dm device model. Initially I did not receive any error to stdout when I did so with Xen-3.4.2. My Xen-3.4.2 installation works fine with qemu-dm (or regular HVM guests). The stubdom-dm guest I was trying to create did not really operate as I was unable to connect to the VNC console. The output of xm list showed the DomU was there,

Hi List, many People seem to be interested in the Graphic-Card Passthrough Feature (for more or less obvious reasons). Official Support is still under development, and i hope not to interfere with it in any (bad) way ... But i remember my own painfull and timeconsuming research when i wanted this feature to work, so i thought perhaps this spares some time for the unpatient users like me :)

Hi Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and Xen package (NOT unstable or debug). When start, a window pops up for few seconds.. then it dies and another one comes up... and it disappears too. (Xen is trying to restart and giving up because the restart happens in 2 seconds..) It seems DomU is not able to read/understand something from Cirrus VGABIOS.

Hi Trying to get WinXP HVM to install as domU on AMD. Got latest Xen Kernel and Xen package (NOT unstable or debug). When start, a window pops up for few seconds.. then it dies and another one comes up... and it disappears too. (Xen is trying to restart and giving up because the restart happens in 2 seconds..) It seems DomU is not able to read/understand something from Cirrus VGABIOS.

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

I''m having some trouble working out how to make the SDL interface for HVM domUs appear. The documentation simply says "it will appear" when you start the domU, but doesn''t state what packages or libraries are needed in order for this magic to happen, or explain how to debug it if it doesn''t happen. All that I''m getting at the moment is a domU (running