similar to: is kexec on Xen domU possible?

The following series improves kexec in a Xen PVonHVM guest. It is available via git: git://github.com/olafhering/linux.git xen-kexec-XS_RESET_WATCHES-3.0 A new xenstored command XS_RESET_WATCHES has been added in xen-unstable.hg changeset 23839:42a45baf037d. The command removes all watches and transactions for the guest. The following patches make use of the new command to wipe all existing

Add xs_reset_watches function to shutdown watches from old kernel after kexec boot. The old kernel does not unregister all watches in the shutdown path. They are still active, the double registration can not be detected by the new kernel. When the watches fire, unexpected events will arrive and the xenwatch thread will crash (jumps to NULL). An orderly reboot of a hvm guest will destroy the

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

Hi all, Here I am sending as attachments patches enabling kexec/kdump support in Xen PV domU. Only x84_64 architecture is supported. There is no support for i386 but some code could be easily reused. Here is a description of patches: - kexec-tools-2.0.3_20120522.patch: patch for kexec-tools which cleanly applies to version 2.0.3, - kexec-kernel-only_20120522.patch: main kexec/kdump kernel

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 We''re nearly to the completion of the code freeze, scheduled for tomorrow. After the code freeze, only bug fixes and features marked as "blockers" will be considered. At the moment, the only feature considered a blocker is experimental PVH dom0 support. In early RCs,

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

> Daniel Kiper <daniel.kiper at oracle.com> writes: > > > Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default > > Linux infrastructure and require some support from firmware and/or hypervisor. > > To cope with that problem kexec firmware infrastructure was introduced. > > It allows a developer to use all kexec/kdump features of given firmware

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

I''ve searched in a couple of places, but have yet to find a conclusive answer for this question: is kexec supported for domU kernels, yet? I saw a couple of developer threads about possible implementation, but I tried it in SLES 11 (2.6.32.13-0.5-xen) and I get an error: Invalid memory segment 0x2000 - 0x595fff I was wondering if there''s something that needs to be done for

All, I''m posting to the Xen-devel list and the OSDL fastboot list. There are a number of Xen folks who''ll want to look at the code. For the fastboot folks, this is mostly intended as an announcement of the port. Please limit your replies to the list(s) that they applies to, thanks :-) A number of people have expressed interest in kexec support for Xen guests. In

The XenPVHVM extensions have not been tested much on very old hypervisors. At least Xen 3.4 gets some testing with the pvops kernel. Require at least Xen 3.4 for the PVonHVM extensions. If an older hypervisor is detected the extensions will be disabled and the guest will only see emulated hardware. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- arch/x86/xen/enlighten.c | 27

Hello, trying to update to the latest kexec version I'm blocked by the lack of basename() and vfscanf() in klibc. I've noticed it only recently because I'm building almost exclusively for arm. This commit intruduced the issue: http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/kexec/arch/i386/x86-linux-setup.c?id=3bf0213789d56054f601c5a06372f78567aacdd9 Has

Is it possible to kexec to the syslinux interface, thus bypassing the hw initialization? What would be the kexec command? kexec -l ??? --append=??? --initrd=??? TIA Jorge Almeida

From: David Vrabel <david.vrabel@citrix.com> elf_rel_set_symbol() fails if the symbol is in the .bss section. Signed-off-by: David Vrabel <david.vrabel@citrix.com> --- purgatory/arch/i386/console-x86.c | 6 +++--- purgatory/arch/i386/crashdump_backup.c | 8 +++++--- purgatory/arch/x86_64/purgatory-x86_64.c | 6 +++--- purgatory/include/purgatory.h | 4

While trying to port kexec cleanly to klibc, came across this syscall usage for reboot(2). Calling reboot directly simplifies the code. Signed-off-by: maximilian attems <max at stro.at> --- kexec/kexec-syscall.h | 18 ------------------ kexec/kexec.c | 3 ++- 2 files changed, 2 insertions(+), 19 deletions(-) v2: keep LINUX_REBOOT_CMD_KEXEC defines, thus no need of

https://bugs.freedesktop.org/show_bug.cgi?id=62848 Priority: medium Bug ID: 62848 Assignee: nouveau at lists.freedesktop.org Summary: xorg not start after kexec when use nouveau QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: SuloevDmitry at gmail.com

Hi all, I try to use kernel 2.6.36.1 in HVM but building the drivers xen-blkfront, xenfs, platform-pci. I used Xen 4.0.2-rc1-pre and a DomU is a ubuntu 10.04 and I try with ubuntu 10.10. In boot I receive error "Cannot find a root partition /dev/xvda2" and a prompt (initramfs) appear. In dmesg (initramfs) appear: blkfront: xvda: barriers enabled (tag) xvda: xvda1 vbd vbd-51712: 16