similar to: xm dump-core and analyzing

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

Hi, Sometimes when I mount a disk image, unmount it, and then try to create a domU using the disk image I get the following error: Error: Device 2049 (vbd) could not be connected. Backend device not found. Im using a FC4 image. Here is the config file: kernel = "/boot/vmlinuz-2.6.16-rc3-xenU" memory=256 name=Domain1 vif = [''bridge=xenbr0''] disk = [

Hi Keir, This patch updates the ia64 buildconfigs, enabling pcifront for all kernels and pciback for -xen and -xen0. Thanks, Alex Signed-off-by: Alex Williamson <alex.williamson@hp.com> --- diff -r 4833dc75ce4d buildconfigs/linux-defconfig_xen0_ia64 --- a/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28 17:52:57 2006 +0100 +++ b/buildconfigs/linux-defconfig_xen0_ia64 Fri Jul 28

> Hi, Simon > > >Two things: > > > >1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this > >(and if you want > > a dump, do ''xm dump'' followed by ''xm destroy'') > > > What do you mean? > I think we cannot dump with "xm destroy" now. >

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).

This cset: changeset: 11473:0008fca70351 date: Thu Sep 14 08:19:38 2006 +0100 description: xm dump command add on xm dump-core [-L|--live][-C| --crash] <domID> [output path] Didn''t actually implement anything. Worse, it looks like we don''t even pause the domain, so it''s always live (not good). What''s going on? regards john

Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be

Hi, I got the following compilation error. This patch fix the error, I think it is needed for xen-testing tree. /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c: In function ''get_src_version'': /root/unstable/linux-2.6.18-xen.hg/scripts/mod/sumversion.c:384: error: ''PATH_MAX'' undeclared (first use in this function)

Hi, This patch is enabling write access during rom_scan. Signed-off-by: Akio Takebe <takebe_akio@jp.fujitsu.com> Best Regards, Akio Takebe _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I hope I''m right here. If not then please point me in the right direction. My problem in short: I have problems using (pinning, mmu_update) physical pages from 0x900000 to 0xB1000 usualy. I''m writing my own little amd64 64bit toy kernel (based on Mini-OS as starting point) for xen and I run into problems with the way the start of day sets up the physical pages. My kernel

I am seeing random reboots after installing Xen 3.2.1 (running with linux-2.6.18-8 pulled from a few days ago). So far, the reboots only happen if I have enabled cpufreq=dom0-kernel and actually run frequency scaling (such as with the ondemand governor). The reboots only happen after a few hours. The machines seem to be stable if I pass the cpufreq option to Xen but disable frequency scaling. I

Hallo *! I have a board SE7501HG2. - On 2.6.18 ipmitool works succefull. On Xen-3.1 (2.6.18) ipmitool say: # ipmitool sensor WARNING: Unknown SDR repository version 0x00 SDR record id 0x0000: invalid length 0 (see thread [ipmitool-devel] Unknown SDR version) - On page [4] as written: ipmitool -> BMC ---> i2c/smbus ''-> SDR - On Thread [9] was written:

This patch unifys error messag of migrate and sysrq. Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r bfcdf4099d23 tools/python/xen/xm/migrate.py --- a/tools/python/xen/xm/migrate.py Thu Jan 12 13:27:55 2006 +++ b/tools/python/xen/xm/migrate.py Fri Jan 13 15:26:14 2006 @@ -56,8 +56,8 @@ if opts.vals.help: opts.usage()

CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 drivers/built-in.o: In function `vmcoreinfo_show'': /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `vmcoreinfo_size_xen'' /usr/src/linux-2.6.18-xen.hg/drivers/xen/core/xen_sysfs.c:340: undefined reference to `paddr_vmcoreinfo_xen'' make[4]: ** [.tmp_vmlinux1]

I ran some iperf tests today and it looks like the etherbridge is the limiting factor on throughput. In the beforetime, I saw great throughput to the VMs; over 800 Mbps. With the bridge, the numbers are in the 400s somewhere. Is this the speed I can expect from the bridge? Is there some tuning I should try, or another way to get more bandwidth into the VMs? This is with xen-2.0, 2.4.27-xen0

Hello. Up to version 3.0.4, I did the following to get two xen kernels (dom0 and domU) with my own config: wget http://www.cl.cam.ac.uk/Research/SRG/netos/xen/downloads/... make xen make tools make docs make linux-2.6-xen0-config CONFIGMODE=menuconfig make linux-2.6-xen0-build make linux-2.6-xen0-install make linux-2.6-xen0-dist make linux-2.6-xenU-config CONFIGMODE=menuconfig make

i just ran install.sh from the xen 3.0.2 pre-built distribution. in /boot it put vmlinuz-2.6.16-xen vmlinuz-2.6-xen -> vmlinuz-2.6.16-xen what happened to the xen0 and xenU kernels? also in /boot from xen 3.0.1 is vmlinuz-2.6-xen0 -> vmlinuz-2.6.12.6-xen0 vmlinuz-2.6-xenU -> vmlinuz-2.6.12.6-xenU which is what i expected from xen 3.0.2. don

Hi, i''m a little bit stuck here with creating a HVM-Windows (w2k3) Guest under Xen 3.1. I''m using ubuntu 7,10 with a 2.6.22.16-xen-patched kernel which seems to be stable for single cpu-linux guests. Cpu is a Q6600 and XD,VT and VT-d is enabled in the bios. When i create the windows guest with ''xm create w2k3 -c" (conf below) I get: "Started domain

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, I can''t get rid of an annoying domU machines hanging issue with Hyperthreading enabled in my BIOS. Hardware config: IBM x325 series 2 * CPUs Intel Xeon 3.06 Ghz Xen version: 3.0.0 Kernel version: 2.6.12.6 Linux distrib: Debian Sarge 3.1 r1 I run 1 domU machine on my dom0, here is my Xen config: . xen0: /etc/xen/xend-config.sxp : (dom0-num-cpus 0) .