similar to: [PATCH] xend: fix LinuxImageHandler debugging output

On ia64 we have a desire to know the guest OS the user plans to run in an HVM domain. With this information we can make certain optimizations, for instance knowing if a guest identity maps a memory region can change how we handle page faults. In the past we''ve tried to do this via the guest firmware detecting the guest type, but this is error prone and doesn''t allow the user to

Hello, I''m trying to get a freebsd virtual machine running following : http://www.yuanjue.net/xen/howto.html But I get : # xm create freebsd_xen_INSTALL -c Using config file "./freebsd_xen_INSTALL". Error: (14, ''Bad address'') Am I missing something? I am using xen 3.0.4. Thanks and regards, Sergi .... log output from xend.log: [2007-02-27 12:46:59

Hi Ewan, I''m almost ready to integrate some PPC-specific stuff into xend, and I was wondering if you had a plan for how that should work. First example: the device tree data structure we talked about a few weeks ago. We will need to pass the config data to PPC code, probably in XendDomainInfo.initDomain(), and then pass the resulting data structure into libxc''s xc_linux_load()

Hello there, I might have found some bug in xen-utils-unstable (amd64). When starting some Linux in domU, the ?ramdisk? parameter of my .cfg file is overridden and has the same value as the ?image? parameter. That ends in an unbootable VM (vmlinuz is not a ramdisk ?) ?No filesystem could mount root, tried: cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(x,y)?

Thanks, Alex. See my comments below. On Wed, Aug 23, 2017 at 12:59 AM, Alex Bradbury <asb at asbradbury.org> wrote: > On 22 August 2017 at 23:39, Y Song via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> Hi, > > Hi Yonghong. > >> I found some different discrepancy on how Subtarget is created >> between some arch specific TargetMachine constructor.

stubdom: int32_t is provided by stdint.h, not sys/types.h diff -r c2472ded5c7c extras/mini-os/include/posix/dirent.h --- a/extras/mini-os/include/posix/dirent.h Tue Aug 26 15:16:57 2008 +0100 +++ b/extras/mini-os/include/posix/dirent.h Tue Aug 26 16:43:27 2008 +0100 @@ -1,7 +1,7 @@ #ifndef _POSIX_DIRENT_H #define _POSIX_DIRENT_H -#include <sys/types.h> +#include <stdint.h>

.. avoiding the need to update them with atomic (locked) ops. Conversion here isn''t complete in the sense that many places still use the old per-CPU accessors (which are now redundant). Since the patch is already rather big, I''d prefer replacing those in a subsequent patch. While doing this, I also converted x86''s multicall macros to no longer require inclusion of

Thanks Bradley. I see that the features set in /ARM.td/ get written to the generated file /<build>/llvm/lib/Target/ARM/ARMGenSubtargetInfo.inc./ Here the ProcA9 features appear in /ARMFeatureKV/ table: /{ "a9", "Cortex-A9 ARM processors", { ARM::ProcA9 }, { *ARM::FeatureFP16* } }, /With your change, the features for ProcA9 in the above entry are empty.//This

The QEMU code in Xen has a custom patch which stops QEMU sending its log messages to stderr as vanilla QEMU would. Instead it dup()s FD 2 on to /var/log/xen/qemu-dm-{DOMID}.log This is fine in principle, but it assumes that XenD is the only thing that will ever want to run qemu-dm. With the use of Xenner, qemu-dm processes may be run by the ''xenner'' program directly. Xenner in

Hi all I''ve taken the plunge and decided to set up Xen on my AMD64 machine. I want to use amd64 debian as the domain 0 O/S, then install a full amd64 debian dev kit and a couple of 32-bit linuxes on top. I''ve got an install of debian amd64 running as domain0, which boots up just fine. I boot it with dom0_mem=131072 (the machine has 1Gb of RAM). I then created some disk

[HVM] enable sound card support for qemu Signed-off-by: Edwin Zhai <edwin.zhai@intel.com> diff -r 2abb1c801ab7 tools/examples/xmexample.hvm --- a/tools/examples/xmexample.hvm Wed Jul 19 16:09:59 2006 +0800 +++ b/tools/examples/xmexample.hvm Thu Jul 20 21:19:07 2006 +0800 @@ -153,8 +153,8 @@ serial=''pty''

Zhang, Xiantao wrote: >>From 6b731c15afa8cec84f16408c421c286f1dd1b7d3 Mon Sep 17 00:00:00 2001 > From: Xiantao Zhang <xiantao.zhang at intel.com> > Date: Wed, 12 Mar 2008 13:45:40 +0800 > Subject: [PATCH] KVM:IA64 : Add TLB virtulization support. > > vtlb.c includes tlb/VHPT virtulization. > Signed-off-by: Anthony Xu <anthony.xu at intel.com> >

Zhang, Xiantao wrote: >>From 6b731c15afa8cec84f16408c421c286f1dd1b7d3 Mon Sep 17 00:00:00 2001 > From: Xiantao Zhang <xiantao.zhang at intel.com> > Date: Wed, 12 Mar 2008 13:45:40 +0800 > Subject: [PATCH] KVM:IA64 : Add TLB virtulization support. > > vtlb.c includes tlb/VHPT virtulization. > Signed-off-by: Anthony Xu <anthony.xu at intel.com> >

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG

Hi guys, I cannot get my domU''s to boot. My current setup is as follows: Xen: 4.0.1 Dom0: Debian with custom linux 2.6.32.27 Xen kernel DomU: Same kernel as Dom0 When I try to start the VM, I just get: Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'') And /var/log/xend.log says: [2011-01-23 15:36:01 3201] DEBUG

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Hey guys, I'm using the dolphin emulator from time and the stable version works reasonable well with current nvidia cards and nouveau.The git version got an overhaul however and now uses opengl3 and ubos (without ubo it uses a glUniform fallback). The ubo support works with the blobs. There are probably a few bugs with ubo one might be because of ubo access+offset (glBindBufferRange) as this

On Fri, Apr 10, 2020 at 02:51:52PM +0100, Richard W.M. Jones wrote: > Similar to C, OCaml and Rust, this is not a plugin per se. Instead > it's more of a method and set of tests around writing plugins in > golang. They are standalone programs that compile into shared objects > that nbdkit can then load (so there is no "go plugin" between nbdkit > and the user plugin,

Here are two patches that let xm create, save and restore extract and preserve elfnotes read by the domain builder. This is handy for a few things. In particular, I''d like it so that xm can decide whether or not guest domains support fast resume (if save fails, or for checkpointing). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

The stub domain device model needs to trap the termination signal so as to actually destroy the stub domain. SIGKILL can''t be trapped, SIGTERM is caught by SDL and so may be unnoticed. SIGHUP can be trapped and is not caught by SDL (and by default causes a process termination without core). Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 2407a61c0d30