linux-kernel - Re: [Xen-devel] [PATCH 0/3] [v4] kexec and kdump for Xen PVonHVM guests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110809190215.GA19789@dumpdata.com>
Date:	Tue, 9 Aug 2011 15:02:16 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	Olaf Hering <olaf@...fle.de>
Cc:	linux-kernel@...r.kernel.org,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	xen-devel@...ts.xensource.com
Subject: Re: [Xen-devel] [PATCH 0/3] [v4] kexec and kdump for Xen PVonHVM
 guests

On Thu, Aug 04, 2011 at 06:20:53PM +0200, Olaf Hering wrote:
> 
> 
> The following series implements kexec and kdump in a Xen PVonHVM guest.
> 
> It is (should be) available via git:
> 
>  git://github.com/olafhering/linux.git xen-kexec-3.0
> 
> The kexec or kdump kernel has to take care of already allocated virqs,
> PV devices in Closed or Connected state, and of registered watches in
> the old kernel. With the three patches these conditions are checked
> during boot of the new kernel rather than in the reboot/crash path.
> 
> A fixed kexec-tools-2.0.2 package is required:
> http://lists.infradead.org/pipermail/kexec/2011-May/005026.html
> http://lists.infradead.org/pipermail/kexec/2011-August/005339.html
> 
> Another fix is for xenstored, it has to accept the XS_INTRODUCE from a guest:
> http://lists.xensource.com/archives/html/xen-devel/2011-08/msg00007.html
> 
> One open issue is the balloon driver. It removes pages from the guest
> and gives them back to the hypervisor. The kexec kernel is not aware of
> the fact that some pages are unavailable, and hangs or crashes.
> The workaround for the time being is:
> 
> if test -f /sys/devices/system/xen_memory/xen_memory0/target -a \
>         -f /sys/devices/system/xen_memory/xen_memory0/target_kb
> then
>     cat /sys/devices/system/xen_memory/xen_memory0/target > \
>         /sys/devices/system/xen_memory/xen_memory0/target_kb
> fi
> kexec -e
> 
> This has to be resolved with another series of changes.

You are just plowing through these bugs and fixing. Thanks for doing it!

I think one more revision and they will be ready?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/