On Thu, Oct 30, 2008 at 06:50:10PM +0100, Raphael Hertzog wrote:
Why are we trying to guess the future here ? We want something working for
lenny now and we'll fix that for squeeze when it has been merged upstream.
[...]
I propose to not use Thomas patch but to remove the code that tries
On Fri, 31 Oct 2008, Ian Campbell wrote:
Please find the patch attached. It works here at least.
I'm happy with it too since it works in domU (no change).
Several days passed and I saw no reaction from the maintainers.
Robert, can you apply the patch and upload a fixed package to get rid of
On Thu, Nov 06, 2008 at 07:45:09PM +0100, Raphael Hertzog wrote:
On Fri, 31 Oct 2008, Ian Campbell wrote:
Please find the patch attached. It works here at least.
I'm happy with it too since it works in domU (no change).
Several days passed and I saw no reaction from the maintainers.
On Thu, 2008-10-30 at 18:50 +0100, Raphael Hertzog wrote:
tag 500336 + patch
thanks
On Thu, 30 Oct 2008, Ian Campbell wrote:
What's the reasoning behind this loop ? All the suitable kernels are
already selected
by the first loot that matches CONFIG_XEN + CONFIG_XEN_PRIVILEGED_GUEST.
On Wed, 29 Oct 2008, Ian Campbell wrote:
So the problem would bite people upgrading grub but not the kernel.
Someone who installs 2.6.26-1-xen-amd64 in a Lenny domU with the Lenny
version of grub would end up with a menu.lst which did not contain this
kernel, which would be
On Thu, 2008-10-30 at 10:57 +0100, Raphael Hertzog wrote:
On Wed, 29 Oct 2008, Ian Campbell wrote:
So the problem would bite people upgrading grub but not the kernel.
Someone who installs 2.6.26-1-xen-amd64 in a Lenny domU with the Lenny
version of grub would end up with a
On Thu, 30 Oct 2008, Ian Campbell wrote:
This means that if I am running a pv ops kernel and I install a
non-pvops kernel for whatever reason then my menu.lst will omit it.
Sure.
Let's come back to the root of this bug report, the problem is that
2.6.26-1-686-bigmem has CONFIG_XEN and
On Thu, 2008-10-30 at 16:45 +0100, Raphael Hertzog wrote:
On Thu, 30 Oct 2008, Ian Campbell wrote:
This means that if I am running a pv ops kernel and I install a
non-pvops kernel for whatever reason then my menu.lst will omit it.
Sure.
Let's come back to the root of this bug report,
Processing commands for [EMAIL PROTECTED]:
tag 500336 + patch
Bug#500336: grub - Misguides Xen images
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
tag 500336 + patch
thanks
On Thu, 30 Oct 2008, Ian Campbell wrote:
What's the reasoning behind this loop ? All the suitable kernels are
already selected
by the first loot that matches CONFIG_XEN + CONFIG_XEN_PRIVILEGED_GUEST.
Can't we simply drop this loop and be done with it ? What
Hi,
we need to decide on a fix for this RC bug and get a new grub uploaded.
So lets restart the discussion.
On Tue, 21 Oct 2008, Ian Campbell wrote:
On Mon, 2008-10-20 at 21:18 +0200, Thomas Viehmann wrote:
Hi,
Ian Campbell wrote:
My only concern would be the behaviour when running in
On Wed, 2008-10-29 at 17:56 +0100, Raphael Hertzog wrote:
Hi,
we need to decide on a fix for this RC bug and get a new grub uploaded.
So lets restart the discussion.
On Tue, 21 Oct 2008, Ian Campbell wrote:
On Mon, 2008-10-20 at 21:18 +0200, Thomas Viehmann wrote:
Hi,
Ian
Processing commands for [EMAIL PROTECTED]:
tags 500336 - patch
Bug#500336: grub - Misguides Xen images
Tags were: patch
Tags removed: patch
# still being discussed
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 500336 - patch
# still being discussed
thanks
On Wed, Oct 29, 2008 at 05:56:01PM +0100, Raphael Hertzog wrote:
I wonder if we have a reliable way to know that the target system
is a domU when we install it with d-i. After all, from what I understand
that's the main problem to solve to
On Mon, 2008-10-20 at 21:18 +0200, Thomas Viehmann wrote:
Hi,
Ian Campbell wrote:
My only concern would be the behaviour when running in a domU. I haven't
looked very closely at the patch yet but a comment says
+# CONFIG_XEN + NO CONFIG_PARAVIRT
+# -- domU capable, but must not
On Fri, Oct 17, 2008 at 11:40:07PM +0200, Thomas Viehmann wrote:
Hi,
based on Bastian's comments here and a clarification on IRC (thanks!), I
would like to propose the attached patch.
I understand that Bastian knows what he's doing, but nevertheless I'd like
this to be okayed by Ian (CCed)
On Mon, 2008-10-20 at 08:52 +0200, Robert Millan wrote:
On Fri, Oct 17, 2008 at 11:40:07PM +0200, Thomas Viehmann wrote:
Hi,
based on Bastian's comments here and a clarification on IRC (thanks!), I
would like to propose the attached patch.
I understand that Bastian knows what he's
Hi,
Ian Campbell wrote:
My only concern would be the behaviour when running in a domU. I haven't
looked very closely at the patch yet but a comment says
+# CONFIG_XEN + NO CONFIG_PARAVIRT
+# -- domU capable, but must not show up in grub
which sounds like menu.lst in a guest domain
On Fri, Oct 17, 2008 at 11:40:07PM +0200, Thomas Viehmann wrote:
based on Bastian's comments here and a clarification on IRC (thanks!), I
would like to propose the attached patch.
Looks okay.
Bastian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
based on Bastian's comments here and a clarification on IRC (thanks!), I
would like to propose the attached patch.
It implements the following behaviour
CONFIG_XEN + CONFIG_XEN_PRIVILEGED_GUEST
-- added to xen0Kernels
CONFIG_XEN + CONFIG_PARAVIRT
-- kept in kernel list
CONFIG_XEN + no
20 matches
Mail list logo
