similar to: [PATCH] Fix typo in waitForBackend() for phantom VBDs

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

Hi, xstransact and xswatch are well designed python interface that can be used by third party utils rather than only in xend. But the logging approach here binds xswatch to xend and prevent it from being used by other utils. This patch removes the dependency on XendLogging from xswatch. Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com> regards, zhigang

delete xend entry when destroying pv usb host controller of a guest os which has no pv-frontend driver loaded. -James (Song Wei) Signed-off-by: James (Song Wei) <jsong@novell.com> diff -r f42ff98a2cdc tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py Thu Mar 25 09:32:21 2010 +0000 +++ b/tools/python/xen/xend/XendDomainInfo.py Fri Mar 26 13:27:25

Hey everyone, I''m trying to write a simple python program in dom0 that registers a watch on the xenstore to determine when a domU has shutdown. Is there a particular token I should use? Looking through the tools/python/xen/*.py code, I''ve come across the ''control/shutdown'' token... seems promising? My code is attached below. As is, if fails to call the

Hi I tried building xen on my IA64 machine. It builds and installs smoothly. But I have not been able to start xend. I get the error in /var/log/xen/xend.log as below: [2007-06-14 05:02:01 xend 26504] WARNING (XendAuthSessions:27) python-pam is required for XenAPI support. [2007-06-14 05:02:01 xend 26520] INFO (SrvDaemon:322) Xend Daemon started [2007-06-14 05:02:01 xend 26520] INFO

I''ve compiled xen-3.0.2-2 from sources. I''ve went to the end without errors. The ./install.sh script have been created the /etc/grub.conf file as it : # initrd /boot/initrd-version.img #boot=/dev/hdc default=0 timeout=5 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.15-1.2054_FC5) root (hd0,0) kernel

Hi,I want to watch a xenstore node,when the value of the node is changed I will be noticed. So I use the xswatch function. I use the python template of the http://wiki.xensource.com/xenwiki/XenStoreReference. However, it is weird that when the xenstore node changed, the call back function is never called. Thanks! _______________________________________________ Xen-users mailing list

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

Hi, on ia64, the do_* functions for hypercalls are called in C. However, they are not declared in any .h file. I think it is cleaner to declare them in an header file rather than locally. The question is in which header file. Thank you for any suggestion. The do_* functions are at least: extern long do_ni_hypercall(void); extern long do_dom0_op(dom0_op_t *u_dom0_op); extern long

Hi, This patch fixes the Bug:835 issue. # xm create /home/kanno/smp-domU.conf cpu_weight=512 cpu_cap=150 Using config file "/home/kanno/smp-domU.conf". Started domain vm1-smp # xm sched-credit -d vm1-smp {''cap'': 150, ''weight'': 512} Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan

Not sure if this is a Fedora Core 6 issue. I already post a message on their list but didn''t get an answer. So I am going to try here.. Does anyone has Windows Guest OS running successfully with the Dom0 has all the physical memory allocated? If I don''t lower the memory assign to Dom0 through grub, I will not be able to run a Windows Guest OS. This what I got Using

Hi, When I tried xm trigger command to a inactive managed domain, I saw the following error message. # xm list vm1 Name ID Mem VCPUs State Time(s) vm1 256 2 0.0 # xm trigger vm1 init Error: an integer is required Usage: xm trigger <Domain> <nmi|reset|init> [<VCPU>]

Hi, I found minor bugs in xm restore command. 1) When I gave a wrong check point file, a return code of command was 0. # touch /tmp/dummy # xm restore /tmp/dummy Error: not a valid guest state file: signature read # echo $? 0 2) When Xend had been stopping, I saw the following traceback message. # xend stop # xm restore /xen/save.vm1 Unexpected error: exceptions.AttributeError Please

Hi, As for xm create and xm new, an error may not occur even if wrong vscsi configuration is given. e.g. vscsi = [ ''0:0:0:0,0:0:0:0'', ''0:0:0:0,1:0:0:0'' ] # xm create vm1 Using config file "/etc/xen/vm1". Started domain vm1 (id=8) # xm scsi-list vm1 Idx BE state host phy-hctl phy vir-hctl devstate 0 0 1 0 0:0:0:0

Hi, We can give multiple domains to the following commands. But, the help messages of the commands are explained to be able to give a single domain. # xm vcpu-list vm1 vm2 Name ID VCPU CPU State Time(s) CPU Affinity vm1 1 0 0 r-- 1409.3 any cpu vm2 2 0 0 r-- 1255.8

Hi, When I tested the xentop with a wrong option, the xentop returned the return code 0. # xentop --abc xentop: unrecognized option `--abc'' Usage: xentop [OPTION] Displays ongoing information about xen vm resources <snip> # echo $? 0 If the wrong option was specified, I think that the xentop had better return the return code 1 (or not 0). This patch fixes the return code of

Hi, The xm vcpu-set command is able to set zero to the number of VCPU of a domain. Therefore I think that it is a natural result that the xm start command fails. But I think that a xm vcpu-set command must fail usually. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 942 2 r----- 75.2 vm1

Hi, We cannot get correct records of VDI by VDI.get_record. The correct records of VDI are gotten by this patch. Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com> Best regards, Kan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Hi, I found the following problems. xm pci-attach command and xm pci-detach command fail on inactive managed domains. An attaching patch solves the problems. # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r----- 51.5 vm1 512 2