-utils 2.7.0-3 Filesystem in USErspace (utilities)
ii libfuse2 2.7.0-3 Filesystem in USErspace library
Hans van Kranenburg
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.18
dann frazier wrote:
On Mon, Oct 29, 2007 at 06:15:42PM +0100, Hans van Kranenburg wrote:
Confirmation of this bug.
Upgrading fuse-utils while sshfs-mounts are active screws up the whole
fuse-system. Kernel log attached.
I'm using kernel 2.6.18-5-xen-amd64 on a Xen domU Lenny host.
Can you
Correction on a confusing sentence:
Hans van Kranenburg wrote:
By the way... On the box where fuse crashed yesterday, I reinstalled the
fuse-utils package.
That is, I reinstalled it *after* having to use xm destroy on the domU
to stop it, and re-creating it again.
Unfortunately, I don't
how things went yesterday.
Have fun,
Hans van Kranenburg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
is only using one vcpu now.
Hans van Kranenburg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Using the Xen clocksource seems to be somewhat buggy yes, I also
experienced lots of related problems until I decoupled the domU clock
from dom0.
Some time ago I edited the Xen page on wiki.debian.org about this, so I
think it could be helpful to provide a link for others who are searching
words at the console and
in /var/log/syslog [1].
The dom0 system is based on Etch, running
xen-linux-system-2.6.18-xen-3.1-2-amd64
version 2.6.18.dfsg.1-22etch2+xen.1 with xen-hypervisor-3.2-1-amd64 and
xen-utils-3.2-1 3.2.1-2 from unstable, which I backported to Etch [2].
Greetings,
Hans van
This xen domU keeps eeeking and crashing, approx once a day. Attached
related errors which were logged today after the last Eeek
Another domU running the same kernel/xen setup, but serving DNS instead
of mail filtering just runs fine for days now.
I just restarted this domU with the 'old'
.
Hans van Kranenburg
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/252977
[2] http://launchpadlibrarian.net/17573131/syslog-2009-09-12.txt
[3] http://ubuntuforums.org/showthread.php?t=964133
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
no more warnings occur, even when messing
around at the dom0 command line.
Greetings,
Hans van Kranenburg
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hans van Kranenburg wrote:
Furthermore, when starting a domU (also using 2.6.26-12), SSH-ing into
the domU, whether it's over IPv4 of IPv6, it does not trigger the
warnings again in the domU or dom0 console.
After shutting down the domU no more warnings occur, even when messing
around
to the eth0 NIC. It 'works', but it
feels like being a dirty workaround...
Hope this helps...
Greetings,
Hans van Kranenburg
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
Thanks,
Hans van Kranenburg
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e554d3a.8060...@knorrie.org
On 09/08/2011 07:12 PM, Hans van Kranenburg wrote:
When putting disk/network load on one of our office servers, Xen/dom0
crashes. Triple ctrl-a does not react any more on serial console.
We did not encounter this earlier on this particular piece of hardware,
having tortured it some more
Hi Ian,
On 09/11/2011 05:37 PM, Ian Campbell wrote:
On Sun, 2011-09-11 at 01:18 +0200, Hans van Kranenburg wrote:
On 09/08/2011 07:12 PM, Hans van Kranenburg wrote:
When putting disk/network load on one of our office servers, Xen/dom0
crashes. Triple ctrl-a does not react any more on serial
On 11/09/2016 12:34 AM, Hans van Kranenburg wrote:
>
> Problem description: After using live migration with Xen, there's a
> chance a block device in a virtual machine ends up displaying 100% usage
> all the time. This also causes 1.00 to be added to the system load average.
This
mation in the fix commit and patchwork link,
I'm however quite confident that this is the exact same issue/fix.
Thanks,
--
Hans van Kranenburg
=
-# iostat -y -x 2
Linux 3.16.0-4
On 11/16/2017 02:19 PM, Hans van Kranenburg wrote:
>
> Latest work on this:
>
> https://patchwork.kernel.org/patch/10035835/
>
> "Applied to for-linus-4.15."
Ok, I just built a 4.9.65 kernel with this patch on top and the config
from debian (config-4.9.0-4-amd64). I
not an expert in the cpu time accounting area, but I can help
testing etc...
Thanks,
--
Hans van Kranenburg
or changes.
Please advice what else I could do to help resolving this issue.
Thanks,
Regards,
Hans van Kranenburg
[0] https://bugs.debian.org/899044
May 4 08:23:03 altair kernel: [83978.662075] BUG: unable to handle kernel
paging request at 0003001f
May 4 08:23:03 altair kernel: [839
is, except for just waiting until
it happens again.
Please advice what else I could use to help resolving this issue.
Thanks,
Regards,
--
Hans van Kranenburg
May 4 08:23:03 altair kernel: [83978.662075] BUG: unable to handle kernel
paging request at 0003001f
May 4 08:23:03 alt
To: Debian xen and kernel team list, Ian Jackson
Cc: Stefan Bader, maintainer of xen packages in Ubuntu
Hi all,
Short version: Hi! I'd like to help with the Xen packaging in Debian.
Long version:
Q: Who are you? How are you related to Debian an the Xen project?
A: Hi, I'm Hans van Kranenburg
On 01/07/2018 06:42 PM, Michael Stone wrote:
> retitle 886491 linux-image-4.9.0-5-amd64: Does not boot as Xen guest in
> PVH mode
> thanks
>
> HVM and PVH are two different modes. The fix suggested in this bug
> report (commenting out pvh=1 in the conf file) points to the problem
> being the
Hi,
On 12/22/2017 02:01 AM, Hans van Kranenburg wrote:
> To: Debian xen and kernel team list, Ian Jackson
I'm replying to my own email, since there has not been a reply on the
lists to it yet.
For Ian Jackson: There's a question for you below (section "Moving
packaging repository&qu
# ok, let's try again...
severity 886591 important
reassign 886591 src:linux 4.9.65-3+deb9u2
merge 886591 886491
thanks
Thanks for your report. This does not render the complete package
unusable for any user.
Hans
tags 886491 + wontfix
tags 886591 + wontfix
thanks
On 01/07/2018 11:28 PM, Hans van Kranenburg wrote:
>
> Thanks for your report. This does not render the complete package
> unusable for any user.
The answer from upstream Xen to this is:
https://lists.xenproject.org/archives/html/
On 01/10/2018 08:54 AM, Wolodja Wentland wrote:
> Hans van Kranenburg <h...@knorrie.org> writes:
>
>> == Security update for Stretch ==
>>
>> On IRC I got some questions about the already earlier released XSA
>> patches, which still aren't in Stretch.
>
Hi,
Please reply-all and not only to me.
On 01/07/2018 12:07 AM, frm wrote:
>> The first step here is to collect more information. Things that are or are
>> not
>> working with Xen setups can be difficult to track down, since it can be
>> related
>> to any combination of anything like
image-4.9.0-4-amd64.
Anything you could do yourself to narrow down the issue would help.
With enough information, someone else might be able to reproduce the
same situation and confirm the issue.
Hans van Kranenburg
Control: forcemerge 886591 -1
Hi,
On 01/19/2018 01:30 AM, Michael J. Redd wrote:
> Package: linux-image-amd64
> Version: 4.9+80+deb9u
>
> [...]
>
> Latest Stretch kernel (4.9.0-5-amd64), released per DSA-4082-1, breaks
> Xen PVH domU support.
If you are using Xen 4.8, then it's the obsolete
Hi Ryan,
On 01/26/2018 12:20 AM, Ryan Thoryk wrote:
> Package: linux-image-4.9.0-5-amd64
> Version: 4.9.65-3+deb9u2
> Severity: normal
>
> I'm having an issue with CPU usage reporting, tested on kernels 4.9.0-3
> and 4.9.0-5. The machines are running on Amazon EC2, which could be
> related.
Reportedly, adding pti=off to the kernel boot parameters will work
around the issue for now.
Turning off pti in the guest kernel is done in any case for PV. The
issue between 4.9.107 and 4.9.111 affects the detection and turning off
of pti, that's why forcing it off helps.
In 4.9.112 it's fixed
Hi,
On 07/15/2018 12:16 PM, Benoît Tonnerre wrote:
> [...]
>
> After updating 3 Xen servers from stretch (9.4) to stretch (9.5), I
> notice a kernel panic on these 3 servers.
Thanks for the report.
This is probably all related:
This went into 4.9.102:
On 07/17/2018 12:39 AM, Benoît Tonnerre wrote:
> Hi,
>
> I tested this workaround : I confirm that it works on Xen host, but not
> on Xen guest.
> If you try to start a vm with latest kernel i.e. theses parameters in
> cfg file :
>
> #
> # Kernel + memory size
> #
> kernel =
Hi,
On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> Hi Michael,
>
> On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
>>
>> After this, there was a file that was errored on the filesystem (as
>> reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to
>> resolve
On 11/30/18 10:46 PM, Hans van Kranenburg wrote:
> On 11/29/18 2:38 AM, Hans van Kranenburg wrote:
>> On 11/29/18 1:20 AM, Hans van Kranenburg wrote:
>>> Package: src:linux
>>> Version: 4.19.5-1~exp1
>>> Severity: normal
>>>
>>> Hi,
>>&g
On 11/29/18 2:38 AM, Hans van Kranenburg wrote:
> On 11/29/18 1:20 AM, Hans van Kranenburg wrote:
>> Package: src:linux
>> Version: 4.19.5-1~exp1
>> Severity: normal
>>
>> Hi,
>>
>> Latest 4.19 upload fails to boot as Xen dom0.
>
> Copy at
>
On 11/29/18 1:20 AM, Hans van Kranenburg wrote:
> Package: src:linux
> Version: 4.19.5-1~exp1
> Severity: normal
>
> Hi,
>
> Latest 4.19 upload fails to boot as Xen dom0.
Copy at
https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03313.html
But at least if so
Hi,
On 11/24/18 12:42 AM, Cesare Leonardi wrote:
> Bug still present with the new 4.18.0-3-amd64 (4.18.20-1).
>
> This morning I've tryed to boot this new kernel version, removing the
> workaround given by the following kernel parameters:
> scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0
>
> The
Hi,
On 11/24/18 2:19 AM, Cesare Leonardi wrote:
>
> On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg
> wrote:
>> You didn't share any part of your logging. Can you share a part of dmesg
>> logging that shows Oops in it?
>
> Here it is, attached to this mes
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
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
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/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/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
that case, try triggering the problem by
generate the same workload that's now coming from the domUs.
Curious to hear what happens,
Thanks,
Hans van Kranenburg
Hi,
On Wed, 15 Jul 2020 20:52:40 -0700 Sarah Newman wrote:
> On 7/7/20 8:13 PM, Ben Hutchings wrote:
> > Control: reassign -1 src:linux
> > Control: tag -1 moreinfo
> >
> > On Tue, 2020-07-07 at 17:30 -0700, Sarah Newman wrote:
> >> Package: linux-signed-amd64
> >> Version: 4.19.0-9-amd64
> >>
Oh,
On 4/16/21 11:44 AM, Hans van Kranenburg wrote:
> [...]
>
> I have the same issue here, it started at the moment I moved from the
> 4.19 kernel to 5.9, and now 5.10. For totally non-obvious reasons fans
> start blowing like crazy regularly for a few seconds. When observin
Hi,
On 4/15/21 10:51 PM, klak wrote:
> Package: linux-image-5.10.0-6-amd64
> Version: 5.10.28-1
>
> Hello Maintainer,
>
> every few minutes the fans turn to maximum for a few seconds. The CPU
> load is less than 1 %, but the fans are turning maximum. The problen
> starts with version
Hi spi, Salvatore,
On 8/5/21 1:58 PM, s...@gmxpro.de wrote:
>
> In preparation for the bug report for upstream I did some more
> investigation.
>
> The kernel panic also occurs without bonding interfaces but needs much
> more time to happen. With a bonding interface it happens within some
>
Hi Elliot and others,
Also including #994899 for once, since that's the bug number for the Xen
issue now.
On 9/26/21 5:27 AM, Elliott Mitchell wrote:
> On Tue, Sep 21, 2021 at 06:33:20AM -0400, Chuck Zmudzinski wrote:
>> I presume you are suggesting I try booting 4.19.181-1 on the
>> current
Hi!
On 10/19/21 5:44 AM, Chuck Zmudzinski wrote:
> On 5/10/2021 1:33 PM, Chuck Zmudzinski wrote:
>> [...] with buster and bullseye running as the Dom0, I can only get the
>> VGA/Passthrough feature to work with Windows Xen HVMs. I would expect both
>> Windows and Linux HVMs to work comparably
Hi Eric,
I think I can help answering this one. It's a good question.
On 8/5/23 10:43, Eric Valette wrote:
> Hi Debian kernel maintainers,
>
> I have a question regarding the way kernel versions are selected for the
> stable tree. [...]
> [...]
>
> So I have reverted to 6.1.x release for many
53 matches
Mail list logo
