ce -tools has a hardcoded dependency on (>= 0.0.20171001).
Thanks,
Hans van Kranenburg
Hi,
On 5/17/19 5:21 PM, Wiebe Cazemier wrote:
> Package: xen-hypervisor-4.8-amd64
> Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11
>
> All Xen Hypervisor packages also need patches against the Intel MDS bug,
> same as https://www.debian.org/security/2019/dsa-.
>
>
jftr: Yesterday I discovered this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29d11cfd8698038b87458ba4d1329b9da81150a5
"xen/grant-table: log the lack of grants"
This is great, this is something we have discussed before, that the domU
kernel should tell
Hi,
On 4/22/19 1:10 AM, Elliott Mitchell wrote:
> Refering to this as "balloon-leak" as it looks sort of like a
> memory-leak, but is instead memory disappearing into the balloon.
I haven't heard about this symptom before your report.
> There are two things which have been happening more
d.
Thanks a lot,
Hans van Kranenburg
diff -Nru python-btrfs-11/debian/changelog python-btrfs-11/debian/changelog
--- python-btrfs-11/debian/changelog2019-02-28 19:42:36.0 +0100
+++ python-btrfs-11/debian/changelog2019-03-22 01:12:12.0 +0100
@@ -1,3 +1,11 @@
+python-btrfs (11-2
Package: python3-btrfs
Version: 11-1
In the upstream issue tracker, an issue was reported about a crash when
using the example program 'btrfs-space-calculator' that is shipped
together with the python-btrfs library:
https://github.com/knorrie/python-btrfs/issues/19
Package: python3-btrfs
Version: 10-1
In the upstream issue tracker, an issue was reported about a crash when
using the python-btrfs library:
https://github.com/knorrie/python-btrfs/issues/17
When trying to decode MetaDataItem objects from a btrfs kernel ioctl
result buffer, the code crashes.
On 3/12/19 8:19 PM, Juergen Gross wrote:
> On 12/03/2019 17:41, Hans van Kranenburg wrote:
>> On 3/12/19 5:04 PM, Juergen Gross wrote:
>>> On 11/03/2019 20:50, Hans van Kranenburg wrote:
>>>> On 3/11/19 7:34 AM, Juergen Gross wrote:
>>>>>
>>&g
On 3/12/19 5:04 PM, Juergen Gross wrote:
> On 11/03/2019 20:50, Hans van Kranenburg wrote:
>> On 3/11/19 7:34 AM, Juergen Gross wrote:
>>>
>>> I'm not sure. Patch 3 of this series is basically already there (see
>>> commit c6d4381220a0087ce19dbf6984d
On 3/11/19 7:34 AM, Juergen Gross wrote:
>
> I'm not sure. Patch 3 of this series is basically already there (see
> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need
> is patch 4, which should really be easy to do?
>
> Hans, could you give it a try? You'd need to use a 4.20
On 3/10/19 11:03 PM, Andrew Cooper wrote:
> On 10/03/2019 21:35, Hans van Kranenburg wrote:
>>
>> [...]
>>
>> Using dom0_mem=2GiB,max:4GiB instead of dom0_mem=2GiB,max:2GiB (which I
>> started with) makes the errors go away, so workaround confirmed.
It's act
found -1 4.19.20-1
thanks
Hi,
Reviving a thing from Jan 2017 here. I don't have this thread in my
mailbox, so no inline quotes.
I just installed some HP z820 workstation and rebooted it into Xen
4.11.1+26-g87f51bf366-3 with linux 4.19.20-1 as dom0 kernel.
During boot I'm greeted by a long list
Hi,
On 2/12/19 2:27 AM, Hans van Kranenburg wrote:
> Hi,
>
> On 2/11/19 2:01 PM, Adi Kriegisch wrote:
>>
>>> Reassigning to Debian Xen team, since I that makes more sense. We
>>> totally missed this on our (release) radar.
>>>
>>> And indeed, w
On 2/27/19 6:08 PM, Ian Jackson wrote:
> Package: xen-utils-common
> Version: 4.11.1+26-g87f51bf366-2
>
> In stretch, /etc/default/xen was a ucf config file. In buster until
> recently it was absent, with some special casing in rules etc. to
> handle its removal. in recent buster it is back, as
Ok, so...
On 2/24/19 3:39 PM, Santiago Vila wrote:
>> All of this seems to be related to the dh-exec usage for putting files
>> in the xen-utils-common package with a different name. This is the first
>> time this package is using dh-exec.
>>
>> [...]
>>
>> Interestingly, 'etc/default/xencommons
, and
then the report that it ftbfs came in, and I was too quick with thinking
"no way, I just built it!". :)
Thanks for your report.
On 2/23/19 7:04 AM, Santiago Vila wrote:
> On Sat, Feb 23, 2019 at 01:15:49AM +0100, Hans van Kranenburg wrote:
>
>> Can you please help me by formu
Hi Gabriel,
On 2/23/19 2:52 PM, Gabriel F. T. Gomes wrote:
> On Tue, Feb 12 2019, Hans van Kranenburg wrote:
>> On 2/12/19 1:35 AM, Gabriel F. T. Gomes wrote:
>>>
>>> That should be easy to do for Debian. On the other hand, I wonder if I
>>> should work first
On 2/23/19 1:15 AM, Hans van Kranenburg wrote:
> Hi,
>
> On 2/23/19 12:59 AM, Santiago Vila wrote:
>>
>>> Hint: Try splitting override_dh_compress into override_dh_compress-arch
>>> and override_dh_compress-indep.
>>
>> Not really sure that thi
Hi,
On 2/23/19 12:59 AM, Santiago Vila wrote:
>
>> Hint: Try splitting override_dh_compress into override_dh_compress-arch
>> and override_dh_compress-indep.
>
> Not really sure that this is a good hint in this case. The first rule showing
> an
> error is certainly this one:
>
> find:
Hi,
Our Buster TODO [1] has a TODO item for me about adding a paragraph in
the "Known Issues" section of the Debian README / NEWS / or wherever it
will go about the grant frames issue.
It would be very nice to have some WARN_ONCE code in the linux kernel
exactly at the place where this issue
Hi Alexander,
On 2/22/19 9:41 PM, Alexander Dahl wrote:
>
> On Fri, Feb 22, 2019 at 07:24:11PM +0100, Hans van Kranenburg wrote:
>> The current state of this bug does not really allow anyone other than
>> yourself to cause it to progress.
>
> FWIW, I also have probl
tags 894013 + upstream
severity 894013 wishlist
thanks
On 1/4/19 12:01 AM, Hans van Kranenburg wrote:
> On 1/3/19 11:46 PM, Hans van Kranenburg wrote:
>> Hi,
>>
>> [...]
I'm moving this one to the wishlist department of the bug list, and
tagging upstream, because this nee
to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
tags 912975 + moreinfo
thanks
Hi,
On 11/7/18 3:43 PM, Roalt Zijlstra | webpower wrote:
>
> Op wo 7 nov. 2018 om 14:30 schreef Hans van Kranenburg <mailto:h...@knorrie.org>>:
> >
> > Well hopefully the 'noreboot' provided server crashes soon for some
>
On 1/22/19 6:55 PM, Hans van Kranenburg wrote:
> [...]
>
> Please note that unless there's a response within a month from now, we
> will close the bug report.
Closing now.
Hans
is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
On 2/17/19 12:27 AM, Marek Marczykowski-Górecki wrote:
> On Sat, Feb 16, 2019 at 10:36:00PM +0100, Hans van Kranenburg wrote:
>> Actually, while looking at this again...
>>
>> In the init script, we already have...
>>
>> capability_check()
>> {
>>
On 2/16/19 1:41 PM, Hans van Kranenburg wrote:
> On 2/16/19 4:26 AM, Marek Marczykowski-Górecki wrote:
>> On Wed, Feb 13, 2019 at 02:27:18AM +0100, Hans van Kranenburg wrote:
>>> Creating new binary packages etc... is not an option anymore during the
>>> Buster freeze.
&
On 2/16/19 4:26 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Feb 13, 2019 at 02:27:18AM +0100, Hans van Kranenburg wrote:
>> Creating new binary packages etc... is not an option anymore during the
>> Buster freeze.
>
> Ok, I can carry myself a startup script calli
On 2/13/19 2:17 AM, Marek Marczykowski-Górecki wrote:
> On Wed, Feb 13, 2019 at 02:07:22AM +0100, Hans van Kranenburg wrote:
>> xen-utils-common 4.11 does not depend on xen-utils 4.11, so it can be
>> missing.
>
> Oh... so maybe search for latest one and error out if none i
Hi,
On 2/13/19 1:53 AM, Marek Marczykowski-Górecki wrote:
> Preliminary test results of something based on debian-xen master branch:
> Xen version detection seems fundamentally wrong when talking about domU
> side. I've installed relevant packages in buster-based domU, then tried
> manually `xl
Hi,
On 2/11/19 2:01 PM, Adi Kriegisch wrote:
>
>> Reassigning to Debian Xen team, since I that makes more sense. We
>> totally missed this on our (release) radar.
>>
>> And indeed, we're shipping the upstream completion file now. Adi, I see
>> how you're improving it, and I like it.
> I'm happy
On 2/12/19 1:35 AM, Gabriel F. T. Gomes wrote:
> On Sun, Feb 10 2019, Hans van Kranenburg wrote:
>>
>> Please remove the 'xm' file from the bash-completion package. This
>> command does not exist in Xen any more (last time it was relevant was in
>> Jessie, wher
On 2/12/19 1:59 AM, Hans van Kranenburg wrote:
> On 2/12/19 1:35 AM, Gabriel F. T. Gomes wrote:
>> On Sun, Feb 10 2019, Hans van Kranenburg wrote:
>>>
>>> Please remove the 'xm' file from the bash-completion package. This
>>> command does not exist in Xen
Hi,
On 2/9/19 6:37 AM, Elliott Mitchell wrote:
> I'm seeing bug #810964 occur in Xen 4.8 as well. Perhaps #810964
> should be reassigned to xen-hypervisor-common or src:xen ?
>
> I don't know whether it effects Xen 4.11 yet...
Since the issue seems to be a lack of functionality to support
Hi,
On 2/11/19 6:35 PM, Marek Marczykowski-Górecki wrote:
> On Mon, Feb 11, 2019 at 04:27:45PM +0100, Hans van Kranenburg wrote:
>> A number of the things above are currently being done.
>
> Thanks for the info.
>
>> If you want to help testing, please subscribe
Hi,
On 2/11/19 2:15 PM, Marek Marczykowski-Górecki wrote:
> Source: xen
> Severity: normal
>
> Dear Maintainer,
>
> Driver domain running Debian buster does not work, because
> xendriverdomain service is missing. Upstream xen have
> /etc/init.d/xendriverdomain (and equivalent
bugs, 768005 , about the xl
command completion. Hope that's fine, we can maintain this in the Xen
packaging and upstream improvements.
Thanks a lot for taking care of it up until now!
Hans van Kranenburg
reassign 768005 src:xen 4.11.1-1
thanks
Hi,
I was browsing the bash-completion package bug list before filing a bug
to remove the obsolete 'xm' file, and then I ran into this one.
Reassigning to Debian Xen team, since I that makes more sense. We
totally missed this on our (release) radar.
And
FYI this...
https://lists.xenproject.org/archives/html/xen-devel/2019-01/msg01696.html
...led me here...
https://salsa.debian.org/qemu-team/qemu/commit/a6a863e912bf03bb321dead3a98c755951665ced
...which resulted in...
https://packages.debian.org/sid/qemu-system-x86
...which still depends on
On 1/24/19 12:08 AM, Hans van Kranenburg wrote:
> [...]
>
> When looking at the upstream source, I can find a
> docs/README.xen-bugtool about it, and this little script trying to
> import it, but nothing else.
>
> So, if anyone feels like sending an upstream PATCH to re
tags 903494 + moreinfo
thanks
Hi Stefan,
On 7/10/18 8:23 PM, Stefan Kadow wrote:
> Package: xen-utils-common
> Version: 4.8.3+xsa267+shim4.10.1+xsa267-1+deb9u9
> Severity: normal
>
> The xendomains script does not work properly on Xen dom0 shutdown and
> reboot.
>
> When restarting or shutting
Actually,
On 2/2/19 9:25 PM, Hans van Kranenburg wrote:
>
> Currently, these are rdepends:
>
> -$ apt-cache rdepends libxenmisc4.11
> libxenmisc4.11
> Reverse Depends:
> libxen-dev
> xen-utils-4.11
> collectd
> qemu-system-x86
> libvirt-d
Hi,
On 2/2/19 11:49 PM, Andy Smith wrote:
>
> On Sat, Feb 02, 2019 at 11:24:36PM +0100, Hans van Kranenburg wrote:
>> When working on actually shipping systemd units we'd really need
>> to have a group of users that want to actively help testing
>> everything. Downgrad
Hi Andy,
Just to set expectations... Ian is not using systemd at all, and for me,
the current whatever init script stuff there is does its thing for my
usecase at work. I don't use xendomains, I use live migrate to drain
physical servers so I can reboot / upgrade / whatever them without any
need
Hi,
We aim to have a working pygrub in Buster, regardless of the fact that
using grub2-based boot images is the prefered upgrade path.
This issue is on our Buster TODO list:
https://salsa.debian.org/xen-team/debian-xen/issues/24
Hans
Hi,
This issue is on our Buster TODO list:
https://salsa.debian.org/xen-team/debian-xen/issues/24
Hans
Hi,
Thanks for your report.
FYI Actually fixing this is on the TODO list for Buster:
https://salsa.debian.org/xen-team/debian-xen/issues/24
It's true that in order to have xendomains restore things after reboot,
the network bridge has to be functional, so it's clear that this has to
be fixed.
Package: src:xen
Version: 4.11.1-1
Currently, these are rdepends:
-$ apt-cache rdepends libxenmisc4.11
libxenmisc4.11
Reverse Depends:
libxen-dev
xen-utils-4.11
collectd
qemu-system-x86
libvirt-daemon
collectd-core
It's on the wishlist to start doing buster-backports for Xen.
If
tags 911045 + pending
thanks
Ok, now this is confusing. For a moment I was thinking that this bug was
cloned because of the "Similar problems in..." and then I couldn't find
the other one.
I just added the Breaks for xenstore-utils jftfoi, so this one is now
both wontfix and pending.
package, instead of a -common one.
--
Hans van Kranenburg
tags 915063 + moreinfo
thanks
Hi Gregory,
I'm tagging this report moreinfo now, since it clearly needs your
cooperation to advance.
Please let us know if you have addition information on what you were
trying to do, and which exact error messages you encoutered etc...
We might close this bug in
tags 911046 + pending
thanks
Hi Andreas,
Yes, you're right. I just added a Suggests: xen-doc to it, I hope that
will alleviate the issue:
https://salsa.debian.org/xen-team/debian-xen/commit/b6909b92f28cd388f390f1c99c2f3f1e06b59cfa
Thanks,
Hans
tags 901602 + moreinfo
thanks
Hi Stefan,
I'm going over open bug reports for the Xen packages in Debian, and I
ran into this one.
I think you might at least want to try out Debian Buster with the Xen
4.11 packages which might provide better support for your hardware.
However, I think you might
will close the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van
. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
tags 866380 + upstream
thanks
Hi,
xen-bugtool seems to be a tool to collect some system information for a
bug report.
I can confirm that in the 4.11 packaging it gives the same result:
-# xen-bugtool
Traceback (most recent call last):
File "/usr/sbin/xen-bugtool", line 9, in
from
tags 863198 + moreinfo
thanks
Hi Hervé,
I'm hunting down old bug reports in the Xen packages, and also ran into
this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863198
Like John Keates already answered in there, when dealing with the source
of a debian package, you're also expected
reassign 862408 src:xen 4.4.1-9+deb8u8
tags 862408 + wishlist
thanks
Hi Sébastien,
I'm hunting down old bug reports in the Xen packages, and also ran into
this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862408
I see why your suggestion would be a nice feature.
Just to set
list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
tags 908453 + pending
thanks
Hi Keith,
I added a change in the packaging that removed the misleading text about
PVH from the README.comet:
https://salsa.debian.org/xen-team/debian-xen/commit/f7f02e1b2ba0dd6464b53f134f9ca13c5a5550e8
Hans
tags 909667 + moreinfo
thanks
Hi Ian,
is this one still relevant, especially after the packaging rewrite?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909667
The text in also doesn't really contain a question or a copy of the
error message, or point out what would need to be done, so I'm
tags 866952 + moreinfo
thanks
Hi Bill, Thomas, Joachim, Maxime and Radoslav,
I'm hunting down old bug reports in the Xen packages, and also ran into
this one:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866952
The bug report is a collection of seemingly similar problems with a
bunch of
tags 491793 + wontfix
thanks
Tagging wontfix since the bug it's blocked by is tagged wontfix.
Hans
ing the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
vel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
ach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
Hi Daniel, Dameon,
On 1/22/19 8:26 AM, Daniel Pocock wrote:
>
>
> On 20/01/2019 19:01, Hans van Kranenburg wrote:
>> reassign 783346 src:xen 4.1.4-3+deb7u4
>> severity 783346 normal
>> thanks
>>
>> Hi Daniel,
>>
>> This is about the bug report
discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
ainer team at that time to
guide you.
Have fun,
Hans van Kranenburg
you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
reassign 851654 src:xen
thanks
Hm!
I think this is the same one that I've been observing during upgrade
tests from 4.8 -> 4.11 and 4.10 -> 4.11.
In my IRC logs I can find myself complaining about xenconsoled that's
suddenly gone multiple times during 2018. I didn't manage to track this
issue
discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van
the bug report. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van
tor etc is needed.
[0] https://packages.debian.org/buster/grub-xen
[1] https://packages.debian.org/buster/grub-xen-host
>8
Thanks,
Hans van Kranenburg
ort. If you discover this message later, and this
case is important to you, then you can try unarchiving the bug and
replying to it, or reach out to the maintainers email list at
pkg-xen-devel at lists.alioth.debian.org (no subscription required) and
post a message.
Thanks,
Hans van Kranenburg
why you
think the problem is caused by a defect in Xen?
If not, can you show more debug logging?
Good luck,
Hans van Kranenburg
also try your luck on the upstream xen-users mailing list [0].
However, this would also require more detailed information instead of
only "It doesn't work"-style information in order to enable others to
help you.
Good luck,
Hans van Kranenburg
[0] https://lists.xenproject.org/mailman/li
Hi Ralph,
On 1/20/19 1:44 PM, Ralph Aichinger wrote:
> [...]
>
> root@xen1:~# xl create /etc/xen/registry.cfg
> Parsing config from /etc/xen/registry.cfg
> libxl: error: libxl_bootloader.c:649:bootloader_finished: Domain 4:bootloader
> failed - consult logfile /var/log/xen/bootloader.4.log
>
Hi Gergely,
On 1/19/19 9:32 AM, root wrote:
> Package: src:xen
> Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11
> Severity: minor
>
> Dear Maintainer,
>
> the GRUB configuration file /etc/defaults/grub.d/xen.cfg contains incorrect
> examples:
>
> 1. Bad syntax for dom0 memory allocation settings:
Hi Sergio,
On 1/16/19 10:31 AM, Sergio Gelato wrote:
> Source: xen Version: 4.8.5+shim4.10.2+xsa282-1+deb9u11
>
> Yesterday I upgraded a test dom0 to this version (from
> 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10; stretch amd64, Xeon E5430),
> then rebooted. Running domU's were saved and restored
Package: wnpp
Severity: wishlist
Owner: Hans van Kranenburg
* Package name: libapache2-mod-authn-yolo
Version : 1.1
Upstream Author : Hans van Kranenburg
* URL : https://github.com/knorrie/mod-authn-yolo/
* License : Apache-2.0
Programming Lang: C
On 1/7/19 10:17 PM, Colin Watson wrote:
> On Mon, Jan 07, 2019 at 09:53:36PM +0100, Hans van Kranenburg wrote:
>> Note that:
>>
>> Installing for x86_64-xen platform.
>> grub-install: warning: no hints available for your platform. Expect
>> reduced performance.
&
On 1/7/19 2:13 PM, Hans van Kranenburg wrote:
> On 1/7/19 12:48 PM, Colin Watson wrote:
>> [...]
>
>> Would you mind trying out the temporary pvh branch of
>> https://salsa.debian.org/grub-team/grub ? I'd like to know whether the
>> resulting grub-xen-host binar
On 1/7/19 12:48 PM, Colin Watson wrote:
> On Mon, Jan 07, 2019 at 08:44:50AM +, Colin Watson wrote:
>> On Mon, Jan 07, 2019 at 01:58:19AM +0100, Hans van Kranenburg wrote:
>>> Ok great. Since I'm not using (and probably not going to use) the
>>> multi-stage multi
On 1/6/19 11:21 AM, Colin Watson wrote:
> On Sat, Jan 05, 2019 at 10:51:13PM +0100, Hans van Kranenburg wrote:
>> On 1/5/19 8:04 PM, Colin Watson wrote:
>>> I think I'm OK with cherry-picking the relevant patch stack. Presumably
>>> this would need to be in new grub
On 1/6/19 11:28 AM, Colin Watson wrote:
> On Sun, Jan 06, 2019 at 01:45:53AM +0100, Hans van Kranenburg wrote:
>> Hm, so I have a PV (or PVH) domU in a test environment here, and I tried
>> to use it in the Debian way of booting it.
>>
>> If I install grub-xen-bin insi
On 1/5/19 10:51 PM, Hans van Kranenburg wrote:
> [...]
>
> I'll try to see if I can get things working when creating a grub image
> using the grub-xen-host_grub.cfg like we have already, and then put
> module stuff and a grub.cfg on the domU filesystem.
Hm, so I have a PV (or PVH)
Hi Colin,
Thanks for the quick reply.
On 1/5/19 8:04 PM, Colin Watson wrote:
> On Thu, Jan 03, 2019 at 01:02:47AM +0100, Hans van Kranenburg wrote:
>> In december, Xen PVH support has been committed in grub master:
>> https://www.mail-archive.com/grub-devel@gnu.org/msg28125.html
On 1/3/19 11:46 PM, Hans van Kranenburg wrote:
> Hi,
>
> On 11/6/18 10:30 PM, Sebastian Piecha wrote:
>> The patch file has a little bug as I commented out the else branch in
>> the last if section. Now it works again...
>>
>> [...]
>
> I think we sh
Hi,
On 11/6/18 10:30 PM, Sebastian Piecha wrote:
> The patch file has a little bug as I commented out the else branch in
> the last if section. Now it works again...
>
> [...]
I think we should move this discussion to (or extend to) upstream Xen
development. If you want, please do so by
101 - 200 of 364 matches
Mail list logo
