similar to: [PATCH] Add monitor arg in configure_hvm() of create.py.

This issue only happened on creating VTI domain in IPF platform. Creating IA32 or IA32E VMX domain is okay. Best Regards, Yongkang (Kangkang) 永康 >-----Original Message----- >From: xen-ia64-devel-bounces@lists.xensource.com >[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Zhang, >Jingke >Sent: 2006年10月11日 16:35 >To: xen-ia64-devel@lists.xensource.com

================== 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 All, I sent the patch to allow blktap to be able to booted as system bolume for PV-on-HVM. However, there was a problem that hdN and xvdN were not able to be specified at the same time. I made the patch to correct it as follows. - Whether hdN is defined first is checked. - If hdN is defined, xvdN is not replaced with hdN. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com>

Image.py should send 2 new arguments to qemu-dm for setting QEMU window Title. 1 is const string "-domain-name", the other is the string of domain name. At present imagy.py combines these two strings to 1. So Qemu will fail to recognize it and fail to start. Signed-off-by: Yongkang You <yongkang.you@intel.com> --- a/tools/python/xen/xend/image.py 2005-12-04 14:32:04.956602836

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

>-----Original Message----- >From: Jan Beulich [mailto:jbeulich@novell.com] >Sent: 2006年9月12日 17:06 >To: You, Yongkang >Cc: xen-devel >Subject: Re: [Xen-devel] 32E (64bit) VMX keyboard is out of control, ifgiven an >addition ''hde'' > >>After creating VMX, its keyboard can not be used properly. For example, if >pressing

>-----Original Message----- >From: Jan Beulich [mailto:jbeulich@novell.com] >Sent: 2006年9月12日 18:05 >To: You, Yongkang >Cc: xen-devel >Subject: RE: [Xen-devel] 32E (64bit) VMX keyboard is out of control,ifgiven an >addition ''hde'' > > >Not sure what RC3 is, but the other two are Linux-es: Can you try rebuilding >the guest kernels with attached

Hi, Here''s the first step toward dealing with the small memory issue. The 15_create_smallmem_pos.py test was hanging because it created a 16 MB domain and never got to the point where it could set a console limit. The OOM messages flooded the console on creation and the select in Console.py always had something to read. Since there was no limit and it never timed out, the test would

Cycling around many CPUs in XenMon''s curses mode can get cumbersome. This trivial patch adds bindings to move to the previous CPU. The next/previous binding seems more natural to me than the earlier cycle binding, but we can keep them all for now. # HG changeset patch # Node ID 146b5c76086c07fad61bea7ccf60f2f4fd66abbd # Parent 7dd31dbf16e75f0f70e0f9c44b2bb2b5fc6eecf1 Add next/previous

>5. LTP testing might run very slow in SMP VTI Domain with credit scheduler. If binding VTI >and Xen0 vcpu, this bug won''t be there. Hi keir, In credit scheduler, two vcpus in the same domain may be scheduled on the same CPU. For instance, vcpu0 and vcpu1 are running on the same CPU, vcpu0 is doing spin_lock in guest, then time slice is due, vcpu0 is scheduled out before doing

>-----Original Message----- >From: Ian Pratt [mailto:m+Ian.Pratt@cl.cam.ac.uk] >Sent: 2006年9月12日 18:02 >To: You, Yongkang; Jan Beulich >Cc: xen-devel; ian.pratt@cl.cam.ac.uk >Subject: RE: [Xen-devel] 32E (64bit) VMX keyboard is out of control,ifgiven an >addition ''hde'' > >Do you mean that with a plain 32b or 32b PAE hypervisor the problem

Hi all, I found this problem in the latest xen-unstable 6117. I reported a bug #154 to track it. The log====> <...> gcc -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Wall -Werror -Wno-pointer-arith -pipe - I/home/nightly/builds_xen_unstable/xen-3.0-hg-xen-unstable-6096- 20050812/xen/include -I/home/nightly/builds_xen_unstable/xen-3.0-hg-xen-

''vncdisplay=N'' in hvm config file is ignored when building qemu-dm arguments. xm create or xm new -> xm start with hvm config file containing vnc=1 vncdisplay=5 results in ''-vncunused'' being passed to qemu-dm. There are several approaches for a fix - this patch defaults vncdisplay to None in xm options. It currently defaults to 1 and is always included in

Hi, This issue only happens on my IA32E VMX domain. IA32 VMX domain is okay. I am trying VBD disk in IA32E VMX domain. I used following disk configuration to create an IA32E VMX domain. disk = [ ''file:/mnt/disk1.img,hda,w'', ''file:/mnt/disk2.img,hde,w'' ] After creating VMX, its keyboard can not be used properly. For example, if pressing

>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月12日 8:57 >To: xen-users@lists.xensource.com >Subject: [Xen-users] Help: Xen HVM Domain can ONLY support four hard >drivesat most??? > >Hi, > >I have 5 SATA hard drives and I want to expose all these five

When making the "unstable" version I got an in "tools". There was a complaint about "cc.has_function" in the following code area in tools/pygrub/setup.py if cc.has_function("ext2fs_open"): ext2defines.append( ("HAVE_EXT2FS_OPEN2", None) ) else : sys.stderr.write ("Warning: older veriosn of e2fsprogs installed ...")

Hi Kashyap, Thanks for the reply. >> >> Now for some reason, I need to add “ -qmp tcp:127.0.0.1:1235” when >> creating a KVM VM using libvirt. > > You might need to elaborate how exactly you're doing this. I wanted to add “-qmp tcp:127.0.0.1:1235” when creating VM because I was using a multi-level debugger which needs this option to get more information of the VM

Hi Raj, I also meet the same python problem when create VMX in FC3-x86_64 xen0. But python error doesn''t happen in RHEL4U1-x86_64 xen0. Are your two computers all SLES9? Thanks, Yongkang You(Kangkang) > >All. > >I am running Xen on an ES7000 system with 4 procs and 4 GB memory. >I am running Suse Sles-9 (32-bit) on the machine. > >I have compiled Xen (the tip on

This patch fixes error(help) messages in main.py and shutdown.py. 1.change the maximun number of argument for xm_reboot 2.unify error message for xm_shutdown Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r 1e1107e3d894 tools/python/xen/xm/main.py --- a/tools/python/xen/xm/main.py Wed Jan 11 19:14:27 2006 +++

Hi, any link[1] that I can find for "xva.py" did not seem to be working. where it has been moved? regards Andreas [1] http://www.xen.org/products/cloud_projects.html http://www.xen.org/files/xva/README -- Andreas Rieck Fraunhofer-Gesellschaft e.V. / Zentrale Abteilung C7 Kommunikationsmanagement Schloss Birlinghoven, 53754 Sankt Augustin Phone: (+49 2241) 14-2641 Fax: (+49 2241)