similar to: Re: event-test.py cannot detects domain shutdown

On 02/18/2014 05:12 AM, Kim Larry wrote: > 2014년 2월 11일 오후 10:00에 Eric Blake <eblake@redhat.com> 작성: > >> On 02/11/2014 12:20 AM, Kim Larry wrote: >> >>>>> libvirtd version is 1.1.4 and using Xen for hypervisor. >>>> I'm not as familiar with the xen hypervisor as with qemu; it may just be >>>> the case that no one has coded the

Cole Robinson wrote: > On 02/18/2014 05:12 AM, Kim Larry wrote: > >> The thing I found today is that if libvirt uses xend driver, shutdown events >> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >> seems there are bugs on shutdown event, so I did dig into the libvirt source >> briefly, but I couldn't find where libxl driver

Cole Robinson wrote: > On 02/18/2014 10:45 PM, Jim Fehlig wrote: > >> Cole Robinson wrote: >> >>> On 02/18/2014 05:12 AM, Kim Larry wrote: >>> >>> >>>> The thing I found today is that if libvirt uses xend driver, shutdown events >>>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything.

Assume an architecture that has multiple condition code registers, e.g., powerpc. Now assume that there are predicate instructions like thumb2, but can specify which condition code register they refer to. Now also assume that these predicate instructions themselves are predicatible, if executed they change the current predication state. Can LLVM handle multiple levels of predication? When is

On 02/18/2014 10:45 PM, Jim Fehlig wrote: > Cole Robinson wrote: >> On 02/18/2014 05:12 AM, Kim Larry wrote: >> >>> The thing I found today is that if libvirt uses xend driver, shutdown events >>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >>> seems there are bugs on shutdown event, so I did dig into the libvirt

Hi,  I''m currently stuck with creating VM which cannot boot with disk using blktap2 driver. I''ve been searching nearly a whole week and I couldn''t get a answer. When creating vm with blktap2, it keep shows a error:   libxl: debug: libxl_device.c:200:disk_try_backend: Disk vdev=xvda, backend tap unsuitable because blktap not available.  VM configuration (XML):

I want to know all the optimization applied by the passes. I found two options in clang 1. -fsave-optimization-record 2. -Rpass-analysis=... However, they have nothing to do with the interaction btw IR files(.ll) Is there any tool that records all optimizations on IR file? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I have a problem shutting down a domU with xen-4.1.2, which doesn''t terminate the corresponding blktap2 process, since one (other) VM uses a image file, which contains spaces in its file name. /var/log/xen/xend-debug.log has the following information: Unhandled exception in thread started by Traceback (most recent call last): File

Hi All, I have got one domination error after running LoopVectorizer with VPlanNatviePath. Let's see simple IR snippet after loop vectorization with VPlanNatviePath. vector.body: ... br label %for.body10.preheader67 for.body10.preheader67: ; preds = %for.cond.cleanup972, %vector.body %vec.phi = phi <4 x i64> [ zeroinitializer, %for.cond.cleanup972 ], [ %8,

Hi there, I have a Dell T3400 Workstation with CentOS5.1 as dom0. I have hidden a network interface in dom0 to pass it to domU. The domU can come up with the NIC when it''s OS is CentOS5.1 or RHEL5. But when it comes to RedHat4.5 , the NIC can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci

Package: xen-utils-common Version: 4.4.1-6 Severity: normal Dear Maintainer, (There appear to be several reports on the BTS with concerns relating to this report. Some unarchiving/merging may be necessary. Reassignment may be needed as well since I'm not sure which package this problem would fall under. Ultimately decided to file with xen-utils-common with 'xl' being the frontend

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

Add tmem-* commands, did some simple tests. [PATCH 1/6]xl: Add ''xl tmem-list'' command [PATCH 2/6]xl: Add ''xl tmem-freeze'' command [PATCH 3/6]xl: Add ''xl tmem-destroy'' command [PATCH 4/6]xl: Add ''xl tmem-thaw'' command [PATCH 5/6]xl: Add ''xl tmem-set'' command [PATCH 6/6]xl: Add ''xl

Hello Xen Users, Been experimenting with upstream-qemu and wanted to try out the OVMF bios option, but I seem to be missing something. Are there additional steps to installing OVMF beyond compiling Xen? I saw notes on patching back in february, but I thought the package was included with Xen 4.2 on release. When I attempt to set it as my bios option, the machine boots then immediately closes.

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

a, libxl_event.h is included in libxl.h. So, the former one also need to be installed. b, define __XEN_TOOLS__ in libxl.h: the head file "xen/sysctl.h" need check this macro. It is the same way used by the xen libxc public headers(tools/libxc/xenctrl.h and tools/libxc/xenctrlosdep.h). Signed-off-by: Bamvor Jian Zhang <bjzhang@suse.com> diff -r 87218bd367be

commit cad172d7b88bd443c81d865051297875ce2551bc Author: Christoph Egger <chegger@amazon.de> Date: Thu Feb 7 14:42:29 2013 +0000 tools/libxl: fix compilation and link errors on NetBSD - Fix testidl link error that libyajl is not found - Make linking of xl and testidl consistent - fix error: array subscript has type ''char'' Signed-off-by:

Hi, George sent a patch on this problem before, but it was not completed. This patch makes libxl use xenbus to communicate with xenstored if libxl cannot open a socket. There''s a place that does not close fd in the case of failure, which is also fixed in this patch. -----------------------------------------Patch------------------------------------------------------ diff -r eff592364826

I have built on clean system with xen-unstable 25374 and stops with this error: gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -D__XEN_TOOLS__ -MMD -MF .libxl.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -fno-optimize-sibling-calls -Werror -Wno-format-zero-length

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> -- 1.7.10.4