similar to: Re: [Xen-ia64-devel] [PATCH] Fix unaligned reference of QEMU

Tags: patch fixed-upstream Patch below allows this package to be built on ia64. Xen has supported ia64 since ~3.0.1. Thanks, Alex diff -urN a/xen-3.0-3.0.4-1/debian/arch/defines b/xen-3.0-3.0.4-1/debian/arch/defines --- a/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:40:58.000000000 -0600 +++ b/xen-3.0-3.0.4-1/debian/arch/defines 2007-07-17 12:41:17.000000000 -0600 @@ -5,3 +5,4 @@

xenapi.out needs to be ignored and removed on clean; tools/ioemu/i386-dm/Makefile is a soft link and should be ignored. Signed-off-by: Alex Williamson <alex.williamson@hp.com> -- diff -r dba5f548b894 .hgignore --- a/.hgignore Mon Mar 24 14:25:52 2008 -0600 +++ b/.hgignore Mon Mar 24 16:27:21 2008 -0600 @@ -58,6 +58,7 @@ ^docs/user/user\.html$ ^docs/xen-api/vm_lifecycle.eps$

Hi Keir, The CS# 17131 which I write for bind guest to NUMA node via cpu affinity missed one condition existing in some machines, where there aren''t any cpus but only memories. Under this condition it will fail to set cpu_affinity because of none parameter. I cope with this condition in the new patch and make a little change of the methods to find suitable node to bind guest. When

https://bugzilla.mindrot.org/show_bug.cgi?id=1462 Summary: Unaligned access warnings on IA64 when using umac-64 Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Itanium2 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

refactoring balback Signed-off-by: Ronghui Duan <ronghui.duan@intel.com<mailto:ronghui.duan@intel.com>> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c index 73f196c..b4767f5 100644 --- a/drivers/block/xen-blkback/blkback.c +++ b/drivers/block/xen-blkback/blkback.c @@ -64,6 +64,11 @@ MODULE_PARM_DESC(reqs, "Number of blkback requests to

I assume this commit message was supposed to be "Enable VGA acceleration for VTI" right? We''re not actually accelerating CGA right? Regards, Anthony Liguori Xen patchbot-unstable wrote: > # HG changeset patch > # User kaf24@firebug.cl.cam.ac.uk > # Node ID e67432187b88ee60433779ad0f004b532ed378c8 > # Parent 639ad22eb7c80ac21c3958747b879892680bdaba >

Hi, Has anyone come across this problem please? Couldn''t see it in the list archives: This is the error message generated by make tools (run twice, so the successful object creation has been removed.) Thanks Install prefix /usr BIOS directory /usr/share/qemu binary directory /usr/bin Manual directory /usr/share/man ELF interp prefix /usr/gnemul/qemu-%M Source path

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

Akio, Thank you for pointing out this issue. Maybe I sent out the older one incorrectly.:( Thanks again. -Xiantao OTC,Intel Corporation > -----Original Message----- > From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com] > Sent: 2006年7月26日 19:24 > To: Zhang, Xiantao; xen-devel@lists.xensource.com > Cc: xen-ia64-devel@lists.xensource.com > Subject: Re: [Xen-ia64-devel]

Looks like cset 8863 included a header in xenbus.h that makes the ia64 build unhappy. domid_t isn''t define so we blow up including grant_table.h. Fix below. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3ed537add538 linux-2.6-xen-sparse/include/xen/xenbus.h --- a/linux-2.6-xen-sparse/include/xen/xenbus.h Fri Feb 17 21:26:49 2006 +0100 +++

Hi, I''ve been trying to boot from a RHEL4 install iso without much luck (the xen way). The Host is: RHEL 5.1 xen-3.0.3-41.el5 Here is my guest config: # -*- mode: python; -*- #============================================================================ # Python configuration setup for ''xm create''. # This script sets the parameters used when a domain is created using

================== STATUS ================== I do the heavy load test of create/destroy. CREDIT scheduler(cshed_schedule) checks BUG_ON(!vcpu_running) at the end of code. It makes error. The reason is that atomic_inc(&v->pausecnt)@vcpu_pause() is called without lock. (spin_lock(&schedule_data[cpu].schedule_lock)) This lock-less "pausecnt" makes vcpu_running state changing

Hi Keir, With the recent per cpu changes, scheduler_init() now starts poking at per cpu space before we''ve configured it on ia64. This re-orders the setup calls to avoid this problem. Please apply. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 1f05ac8abda6 xen/arch/ia64/xen/xensetup.c --- a/xen/arch/ia64/xen/xensetup.c Tue Aug 08

introduce CONFIG_PARAVIRT_GUEST, CONFIG_PARAVIRT for paravirtualized guest. introduce CONFIG_XEN, CONFIG_IA64_XEN_GUEST for xen. Signed-off-by: Alex Williamson <alex.williamson at hp.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at intel.com> --- arch/ia64/Kconfig | 32 ++++++++++++++++++++++++++++++++

introduce CONFIG_PARAVIRT_GUEST, CONFIG_PARAVIRT for paravirtualized guest. introduce CONFIG_XEN, CONFIG_IA64_XEN_GUEST for xen. Signed-off-by: Alex Williamson <alex.williamson at hp.com> Signed-off-by: Isaku Yamahata <yamahata at valinux.co.jp> Cc: "Luck, Tony" <tony.luck at intel.com> --- arch/ia64/Kconfig | 32 ++++++++++++++++++++++++++++++++

Hi Alex: I was looking at an ia64 bug report and noticed that we don''t actually free IRQs in the free_irq_vector hypercall. This would eventually lead to alloc_irq_vector failing. Unless I''m mistaken something like calling pci_disable_device and pci_enable_device can lead to this situation. So I''m wondering what the original problem was and how could we resolve it

Keir, The patch below is necessary to get ia64 building on current xen-unstable.hg. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 3983e4f1b054 xen/arch/ia64/Rules.mk --- a/xen/arch/ia64/Rules.mk Sun Mar 12 10:03:33 2006 +0100 +++ b/xen/arch/ia64/Rules.mk Mon Mar 13 09:36:01 2006 -0700 @@ -12,7 +12,7 @@ CPPFLAGS += -I$(BASEDIR)/include -I$(BA

add segring support in blkback Signed-off-by: Ronghui Duan <ronghui.duan@intel.com> diff --git a/drivers/block/xen-blkback/blkback.c b/drivers/block/xen-blkback/blkback.c index 45eda98..0bbc226 100644 --- a/drivers/block/xen-blkback/blkback.c +++ b/drivers/block/xen-blkback/blkback.c @@ -60,6 +60,10 @@ static int xen_blkif_reqs = 64; module_param_named(reqs, xen_blkif_reqs, int, 0);

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