search for: shutdown_reasons

To allow for more flexibility, this notifies domain shutdown through a function rather than a wake queue, to let the application use a wake queue only if it wishes. Signed-off-by: Samuel Thibault <samuel.thibaut@ens-lyon.org> diff -r 090cc3e20d3e extras/mini-os/include/kernel.h --- a/extras/mini-os/include/kernel.h Wed Dec 19 16:04:50 2012 +0000 +++ b/extras/mini-os/include/kernel.h Fri

Add a thread watching the xenbus shutdown control path and notifies a wait queue. Add HYPERVISOR_shutdown convenient inline for minios shutdown. Add proper shutdown to the minios test application. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r fdf241ea6ff4 extras/mini-os/include/kernel.h --- a/extras/mini-os/include/kernel.h Wed Nov 28 21:29:18 2012 +0100 +++

This patch fixes the bug that "xm reboot <domid>" can not reboot vmx domain. In xm reboot process, control panel will wait until DomU notified it. Unlike DomU, vmx domain can not passively do that, since it runs unmodified OS. This patch adds the missing logic in control panel. Any comment? Signed-off-by: Xu Dan <dan.d.xu@intel.com > Yu Ke

On a 8 Core system only dom0 can set cap > 100 and vcpus > 1. On a domU ''xm sched-credit -d <domU> -c 200'' says "Error: cap is out of range". Vcpu cannot be set higher than 1 - regardless of boot/config/command line. Low performance is equivalent to the cap setting. See ''xm list --long'': (domain (domid 0) (uuid

# HG changeset patch # User Zhigang Wang <zhigang.x.wang@oracle.com> # Date 1326227259 18000 # Node ID a78507899bea4824901d209d818b69545f607312 # Parent 03138a08366b895d79e143119d4c9c72833cdbcd libxl: fix typo iff -> if Signed-off-by: Zhigang Wang <zhigang.x.wang@oracle.com> diff -r 03138a08366b -r a78507899bea tools/libxl/libxl_types.idl --- a/tools/libxl/libxl_types.idl Fri Dec

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Hi, I have compiled xen-unstable (using hg clone http://xenbits.xensource.com/xen-unstable.hg). I have successfully booted into the dom0 kernel. output of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 932 1 r----- 591.2 But whenever I xm create, I get: # xm create /etc/xen/domu1 Using config file

Hello, yesterday a coworker had to reboot one VM, the Vm did shutdown but never came back up. We are USing CentOS 5.1 and XEN xen-3.0-x86_64. What can be the reason of this behavior? Here ist the part of the logfile: [2008-07-02 15:04:18 xend.XendDomainInfo 31150] INFO (XendDomainInfo:947) Domain has shutdown: name=auto-input-vm1 id=26 reason=reboot. [2008-07-02 15:04:18 xend.XendDomainInfo

Hi, I''m trying to use a Gentoo whit Xem 4.0, but I try: xm create windows2008r2.hvm I get the error: Error: coercing to Unicode: need string or buffer, NoneType found. Does anybody knows how to solve that? windows2008r2.hvm: kernel = "hvmloader" builder=''hvm'' memory = 512 name = "Windows2008R2" vcpus=2 acpi=1 apic=1 disk = [

I have been playing with Xen 3.0.1 for some days now, using debian sarge for dom0 and domU''s, and it works like a charm. But, I have a problem with rebooting domU''s. Here is the output from /var/log/xend.log [2006-03-30 13:44:58 xend.XendDomainInfo] INFO (XendDomainInfo:823) Domain has shutdown: name=vmintraweb1 id=5 reason=reboot . [2006-03-30 13:44:58 xend.XendDomainInfo]

Package: xen-utils-4.0 Version: 4.0.1~rc6-1 Severity: important Tags: patch The patch is not necessary for HVM DomU guests. The Error: 'NoneType' object has no attribute 'rfind' was fixed by installing xen-qemu-dm-4.0. [1] [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588888 -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I have 2 Dell 1955 blade servers, running RHEL5-Xen. I''m testing the migrate functionality from one blade to another. I can start the domain, move it to one blade (minor delay/packet loss) and everything is fine. When I try to move it back to the original blade the migration fails and the DomU crashes c1b1 = Blade 1 (192.168.131.201) c1b2 = Blade 2

Hi, I try to start a DomU with xm create endian -c and got the following error message Xend has probably crashed! Invalid or missing HTTP status code. I''ve tested the DomU with nearly the same system at VMWare (Windows) and it works normaly, but on my server I get this error message. I useing gentoo as Dom0. I tried also a gentoo DomU with the same result. Thanks.

Hi all, I''m having some problem migrating a simple domU between two hosts. Short question: xm migrate (live or not) fails even though either host is capable of running the VM. Error seems to be: "not a valid guest state file: pfn count read" Long question: I have two boxes (devvmdevvmhost1 and devvmhost2) running xen 3.0.3 (RHEL 5), they are attached to a Dell MD3000 unit

Hi folks I deploy a two Dell PowerEdge T300 to test Virtualization with kvm+drbd+heartbaet. The KVM drbd and heartbeat work properly. However, I have doubt!! When the primary node has down, the secondary node start the VM that has original running on primary node... So, this required a full stop of hole system... This is not we wish here... Is there something way to live migrate VM from

I''m running Xen 3.0.2 on a system that''s based on Slackware 10.2 as Dom0. DomU is also slackware 10.2. Am using the kernel that came with 3.0.2 - no custom config, just a "make world", etc.. Did have to add grub of course. When I start up xend, I get the following on /var/adm/messages: Apr 23 21:04:11 rc25 kernel: Bridge firewalling registered Apr 23 21:04:11 rc25

This is patch 2of2 of an eighth cut of the patch of the proposed XENMEM_claim_pages hypercall/subop, taking into account feedback from Jan and Keir and IanC and Matthew Daley. As requested by Jan, this is a separate post of the tools part of the patch. NOTE: This patch must be applied after the hypervisor part of the patchset or otherwise may break the build! v5->v8: - no change in this

I''ve installed a Fedora Core 5 2054 and Xen 3.0.4.1 on a Intel 945 mainboard with xen3.0 user manual, everything seemed fine then. After I rebooted and chosed to enter into xen kernel , I find xend doesn''t run . when I try to run manually by input: /etc/init.d/xend start there some dot(indicating time maybe) appeared, and then nothing happened, the xend jun didn''t get