NetBSD Problem Report #48125
From gson@gson.org Thu Aug 15 12:52:15 2013
Return-Path: <gson@gson.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "Postmaster NetBSD.org" (verified OK))
by mollari.NetBSD.org (Postfix) with ESMTPS id C7F43714BA
for <gnats-bugs@gnats.NetBSD.org>; Thu, 15 Aug 2013 12:52:15 +0000 (UTC)
Message-Id: <20130815125209.E1A6C75E34@guava.gson.org>
Date: Thu, 15 Aug 2013 15:52:09 +0300 (EEST)
From: gson@gson.org (Andreas Gustafsson)
Reply-To: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@gnats.NetBSD.org
Subject: dom0 panic during domU creation attempt
X-Send-Pr-Version: 3.95
>Number: 48125
>Category: port-xen
>Synopsis: dom0 panic during domU creation attempt
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: jdolecek
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 15 12:55:00 +0000 2013
>Closed-Date: Sun Jul 15 11:32:00 +0000 2018
>Last-Modified: Sun Jul 15 11:32:00 +0000 2018
>Originator: Andreas Gustafsson
>Release: NetBSD 6.0.1
>Organization:
>Environment:
System: NetBSD gusto.araneus.fi 6.0.1 NetBSD 6.0.1 (XEN3_DOM0) amd64
Architecture: x86_64
Machine: amd64
>Description:
I have an amd64 machine running Xen 4.1.4 with a NetBSD 6.0.1 dom0.
It is successfully hosting one NetBSD 5.2 i386PAE domU residing
on a physical disk (as in disk = [ 'phy:/dev/wd1d,0x1,w' ]).
I have been trying to create a second domU "bloute" which unlike the
existing domU would reside in a disk image file in the dom0 file
system.
So far, all my attempts have failed; when I run "xl create -c
/usr/pkg/etc/xen/bloute" I get the error message "xenconsole: Could
not read tty from store: No such file or directory". However, the
subject of this bug report is not the failure to create the domU, but
the more serious problem that one of my attempts triggered a panic
in the dom0.
The contents of the configuration file /usr/pkg/etc/xen/bloute were:
kernel = "/root/netbsd-XEN3PAE_DOMU-5.2"
memory = 512
name = "bloute"
vcpus = 1
nics = 1
vif = [ 'mac=00:0c:29:90:62:eb, bridge=bridge0' ]
disk= [ 'file:/root/bloute.img,xvda,w' ]
root = "xbd0a"
The following output appeared on the console:
Aug 15 10:19:29 gusto xenbackendd[438]: Failed to read /local/domain/0/backend/qdisk/19/51712/script (No such file or directory)
Aug 15 10:19:29 gusto xenbackendd[438]: Failed to read /local/domain/0/backend/console/19/0/script (No such file or directory)
uvm_fault(0xffffa000057b8a60, 0x0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff806d0b68 cs e030 rflags 10246 cr2 8 cpl 0 rsp ffffa0005bb3da20
panic: trap
cpu0: Begin traceback...
printf_nolog() at netbsd:printf_nolog
startlwp() at netbsd:startlwp
alltraps() at netbsd:alltraps+0x9f
kernfs_try_fileop() at netbsd:kernfs_try_fileop+0x64
VOP_WRITE() at netbsd:VOP_WRITE+0x3c
vn_write() at netbsd:vn_write+0xf9
dofilewrite() at netbsd:dofilewrite+0x7d
sys_write() at netbsd:sys_write+0x62
syscall() at netbsd:syscall+0xc4
cpu0: End traceback...
dump to dev 0,1 not possible
rebooting...
(XEN) Domain 0 shutdown: rebooting machine.
>How-To-Repeat:
Don't know. I made several attempts at creating the domU, and
although they all failed, only the last one caused a dom0 panic.
Since the machine is also hosting a production domU and a successful
reproduction of the bug would cause downtime for that domU, I am
reluctant to try.
>Fix:
>Release-Note:
>Audit-Trail:
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@NetBSD.org, gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 16:16:21 +0200
On Thu, Aug 15, 2013 at 12:55:01PM +0000, Andreas Gustafsson wrote:
> I have an amd64 machine running Xen 4.1.4 with a NetBSD 6.0.1 dom0.
> It is successfully hosting one NetBSD 5.2 i386PAE domU residing
> on a physical disk (as in disk = [ 'phy:/dev/wd1d,0x1,w' ]).
>
> I have been trying to create a second domU "bloute" which unlike the
> existing domU would reside in a disk image file in the dom0 file
> system.
>
> So far, all my attempts have failed; when I run "xl create -c
> /usr/pkg/etc/xen/bloute" I get the error message "xenconsole: Could
> not read tty from store: No such file or directory".
should not be a problem.
> However, the
> subject of this bug report is not the failure to create the domU, but
> the more serious problem that one of my attempts triggered a panic
> in the dom0.
>
> The contents of the configuration file /usr/pkg/etc/xen/bloute were:
>
> kernel = "/root/netbsd-XEN3PAE_DOMU-5.2"
> memory = 512
> name = "bloute"
> vcpus = 1
> nics = 1
> vif = [ 'mac=00:0c:29:90:62:eb, bridge=bridge0' ]
> disk= [ 'file:/root/bloute.img,xvda,w' ]
> root = "xbd0a"
>
> The following output appeared on the console:
>
> Aug 15 10:19:29 gusto xenbackendd[438]: Failed to read /local/domain/0/backend/qdisk/19/51712/script (No such file or directory)
> Aug 15 10:19:29 gusto xenbackendd[438]: Failed to read /local/domain/0/backend/console/19/0/script (No such file or directory)
> uvm_fault(0xffffa000057b8a60, 0x0, 1) -> e
> fatal page fault in supervisor mode
> trap type 6 code 0 rip ffffffff806d0b68 cs e030 rflags 10246 cr2 8 cpl 0 rsp ffffa0005bb3da20
> panic: trap
> cpu0: Begin traceback...
> printf_nolog() at netbsd:printf_nolog
> startlwp() at netbsd:startlwp
> alltraps() at netbsd:alltraps+0x9f
> kernfs_try_fileop() at netbsd:kernfs_try_fileop+0x64
> VOP_WRITE() at netbsd:VOP_WRITE+0x3c
> vn_write() at netbsd:vn_write+0xf9
> dofilewrite() at netbsd:dofilewrite+0x7d
> sys_write() at netbsd:sys_write+0x62
> syscall() at netbsd:syscall+0xc4
> cpu0: End traceback...
Is the file sparse ? What mount options for this filesystem do you have ?
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: Andreas Gustafsson <gson@gson.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@netbsd.org,
gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org,
gson@gson.org (Andreas Gustafsson)
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 17:47:08 +0300
Manuel Bouyer wrote:
> Is the file sparse
I don't think so - at least it's taking up more than its size's worth of
blocks:
gusto# BLOCKSIZE=512 ls -als bloute.img
4195392 -rw-r--r-- 1 root wheel 2147483648 Aug 15 09:31 bloute.img
gusto# bc
4195392*512
2148040704
Is there a better way of checking?
> What mount options for this filesystem do you have ?
gusto# mount | grep wd0a
/dev/wd0a on / type ffs (log, local)
--
Andreas Gustafsson, gson@gson.org
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Andreas Gustafsson <gson@gson.org>
Cc: gnats-bugs@NetBSD.org, port-xen-maintainer@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 17:11:18 +0200
On Mon, Aug 26, 2013 at 05:47:08PM +0300, Andreas Gustafsson wrote:
> Manuel Bouyer wrote:
> > Is the file sparse
>
> I don't think so - at least it's taking up more than its size's worth of
> blocks:
>
> gusto# BLOCKSIZE=512 ls -als bloute.img
> 4195392 -rw-r--r-- 1 root wheel 2147483648 Aug 15 09:31 bloute.img
> gusto# bc
> 4195392*512
> 2148040704
>
> Is there a better way of checking?
I would check with du
>
> > What mount options for this filesystem do you have ?
>
> gusto# mount | grep wd0a
> /dev/wd0a on / type ffs (log, local)
Maybe log can be an issue here. Can you check without -o log ?
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: Andreas Gustafsson <gson@gson.org>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: Andreas Gustafsson <gson@gson.org>,
gnats-bugs@NetBSD.org,
port-xen-maintainer@NetBSD.org,
gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 19:14:46 +0300
Manuel Bouyer wrote:
> I would check with du
Same result as "ls -s":
gusto# BLOCKSIZE=512 du bloute.img
4195392 bloute.img
> Maybe log can be an issue here. Can you check without -o log ?
Not until I move the production domU running on the same machine
somewhere else. What would the purpose of this experiment be?
--
Andreas Gustafsson, gson@gson.org
From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Andreas Gustafsson <gson@gson.org>
Cc: gnats-bugs@NetBSD.org, port-xen-maintainer@NetBSD.org,
gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 18:25:43 +0200
On Mon, Aug 26, 2013 at 07:14:46PM +0300, Andreas Gustafsson wrote:
> Manuel Bouyer wrote:
> > I would check with du
>
> Same result as "ls -s":
>
> gusto# BLOCKSIZE=512 du bloute.img
> 4195392 bloute.img
>
> > Maybe log can be an issue here. Can you check without -o log ?
>
> Not until I move the production domU running on the same machine
> somewhere else. What would the purpose of this experiment be?
See what causes the panic exactly, as I've never seen it. One difference
is that I don't use -o log on partitions where I have domU disk images.
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
From: Andreas Gustafsson <gson@gson.org>
To: Manuel Bouyer <bouyer@antioche.eu.org>
Cc: Andreas Gustafsson <gson@gson.org>,
gnats-bugs@NetBSD.org,
port-xen-maintainer@NetBSD.org,
gnats-admin@NetBSD.org,
netbsd-bugs@NetBSD.org
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 26 Aug 2013 19:37:32 +0300
Manuel Bouyer wrote:
> See what causes the panic exactly, as I've never seen it.
Fair enough.
> One difference is that I don't use -o log on partitions where I have
> domU disk images.
-o log is the default setting in NetBSD 6, so it really ought to work,
or if it does not, it needs to be prominently warned against in the
documentation.
--
Andreas Gustafsson, gson@gson.org
From: Andreas Gustafsson <gson@gson.org>
To: gnats-bugs@NetBSD.org
Cc: port-xen-maintainer@netbsd.org,
Manuel Bouyer <bouyer@antioche.eu.org>
Subject: Re: port-xen/48125: dom0 panic during domU creation attempt
Date: Mon, 9 Sep 2013 23:51:08 +0300
Manuel Bouyer wrote:
> Maybe log can be an issue here. Can you check without -o log ?
I have now done a virtual-to-physical migration of the production domU
that was running on the same server, turned off the log option in the
dom0 /etc/fstab, and rebooted, and I can reliably reproduce the panic
by running "xl create" and "xl destroy" a few times in a loop.
Unedited console output follows.
gusto# mount
/dev/wd0a on / type ffs (local)
kernfs on /kern type kernfs (local)
ptyfs on /dev/pts type ptyfs (local)
procfs on /proc type procfs (local)
tmpfs on /tmp type tmpfs (local)
gusto# set -x
gusto# while true; do xl create -c /usr/pkg/etc/xen/bloute; xl destroy bloute; sleep 5; done
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:49:58 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/1/0/script (No such file or directory)
Sep 9 20:50:03 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/1/script (No such file or directory)
Daemon running with PID 97
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:50:09 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/2/51712/script (No such file or directory)
Sep 9 20:50:09 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/2/0/script (No such file or directory)
Sep 9 20:50:14 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/2/script (No such file or directory)
Daemon running with PID 600
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:50:20 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/3/51712/script (No such file or directory)
Sep 9 20:50:20 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/3/0/script (No such file or directory)
Sep 9 20:50:25 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/3/script (No such file or directory)
Daemon running with PID 299
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:50:32 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/4/51712/script (No such file or directory)
Sep 9 20:50:32 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/4/0/script (No such file or directory)
Sep 9 20:50:37 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/4/script (No such file or directory)
Daemon running with PID 233
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:50:43 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/5/51712/script (No such file or directory)
Sep 9 20:50:43 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/5/0/script (No such file or directory)
Sep 9 20:50:48 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/5/script (No such file or directory)
Daemon running with PID 848
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:50:54 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/6/51712/script (No such file or directory)
Sep 9 20:50:54 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/6/0/script (No such file or directory)
Sep 9 20:50:59 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/6/script (No such file or directory)
Daemon running with PID 258
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:51:05 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/7/51712/script (No such file or directory)
Sep 9 20:51:05 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/7/0/script (No such file or directory)
Sep 9 20:51:10 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/7/script (No such file or directory)
Daemon running with PID 730
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:51:17 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/8/51712/script (No such file or directory)
Sep 9 20:51:17 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/8/0/script (No such file or directory)
Sep 9 20:51:22 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/8/script (No such file or directory)
Daemon running with PID 1541
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:51:28 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/9/51712/script (No such file or directory)
Sep 9 20:51:28 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/9/0/script (No such file or directory)
Sep 9 20:51:33 gusto xenbackendd[220]: Failed to read /local/domain/0/device-model/9/script (No such file or directory)
Daemon running with PID 572
xenconsole: Could not read tty from store: No such file or directory
+ xl destroy bloute
+ sleep 5
+ true
+ xl create -c /usr/pkg/etc/xen/bloute
Parsing config file /usr/pkg/etc/xen/bloute
Sep 9 20:51:39 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/qdisk/10/51712/script (No such file or directory)
Sep 9 20:51:39 gusto xenbackendd[220]: Failed to read /local/domain/0/backend/console/10/0/script (No such file or directory)
uvm_fault(0xffffa00005469768, 0x0, 1) -> e
fatal page fault in supervisor mode
trap type 6 code 0 rip ffffffff806d0b68 cs e030 rflags 10246 cr2 8 cpl 0 rsp ffffa0005c178a20
panic: trap
cpu0: Begin traceback...
printf_nolog() at netbsd:printf_nolog
startlwp() at netbsd:startlwp
alltraps() at netbsd:alltraps+0x9f
kernfs_try_fileop() at netbsd:kernfs_try_fileop+0x64
VOP_WRITE() at netbsd:VOP_WRITE+0x3c
vn_write() at netbsd:vn_write+0xf9
dofilewrite() at netbsd:dofilewrite+0x7d
sys_write() at netbsd:sys_write+0x62
syscall() at netbsd:syscall+0xc4
cpu0: End traceback...
dump to dev 0,1 not possible
rebooting...
(XEN) Domain 0 shutdown: rebooting machine.
From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek@gmail.com>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-xen/48125 dom0 panic during domU creation attempt
Date: Sat, 23 Jun 2018 17:25:38 +0200
I experienced similar symtoms for xl destroy on 4.2.6, repeatable.
1. xl create a DOMU with kernel which would crash during boot and drop into ddb
2. detach from DOMU console using Ctrl-]
3. xl destroy the DOMU
Makes the DOM0 crash:
[ 4759.4069454] xbd backend: detach device vnd0d for domain 4
[ 4759.4569453] uvm_fault(0xffffffff80feb900, 0x0, 1) -> e
[ 4759.4569453] fatal page fault in supervisor mode
[ 4759.4569453] trap type 6 code 0 rip 0xffffffff8021bfae cs 0xe030
rflags 0x10247 cr2 0 ilevel 0 rsp 0xffffa001765f8e38
[ 4759.4569453] curlwp 0xffffa0001012b5a0 pid 0.39 lowest kstack 0xffffa001765f4
2c0
[ 4759.4569453] panic: trap
[ 4759.4569453] cpu0: Begin traceback...
[ 4759.4569453] ?() at ffffffff80882c18
[ 4759.4569453] ?() at ffffffff80882cb8
[ 4759.4569453] ?() at ffffffff8020b617
[ 4759.4569453] ?() at ffffffff80204f0b
[ 4759.4569453] ?() at ffffffff80229fb3
[ 4759.4569453] ?() at ffffffff8022a441
[ 4759.4569453] cpu0: End traceback...
[ 4759.4569453] dumping to dev 4,1 (offset=0, size=0): not possible
[ 4759.4569453] rebooting...
From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek@gmail.com>
To: "gnats-bugs@NetBSD.org" <gnats-bugs@netbsd.org>
Cc:
Subject: Re: port-xen/48125 dom0 panic during domU creation attempt
Date: Sun, 24 Jun 2018 23:08:43 +0200
Hey,
My problem actually turned out to be bad xennetback_xenbus cleanup and
panic in intr_disestablish(). I've fixed it, but it's likely
completely unrelated to your problem.
With my fix, I've tried to run a loop creating and destroying a DOMU
which would not boot, run some 60 iterations and still no panic. I
also tried experiment that I unmounted /dev/pts so that creation fails
with similar error (Failed to create tty), that still did not panic
after ~20 iterations. This was with Xen 4.2.6.
Are you still in position to test this with -current and confirm
whether it still happens?
Jaromir
From: Andreas Gustafsson <gson@gson.org>
To: =?iso-8859-2?Q?Jarom=EDr_Dole=E8ek?= <jaromir.dolecek@gmail.com>
Cc: gnats-bugs@NetBSD.org
Subject: Re: port-xen/48125 dom0 panic during domU creation attempt
Date: Mon, 25 Jun 2018 22:54:51 +0300
Jarom=EDr Dole=E8ek wrote:
> Are you still in position to test this with -current and confirm
> whether it still happens=3F
I no longer have the setup from the PR, but I will try to reproduce
the problem and verify your fix on a different system.
--=20
Andreas Gustafsson, gson@gson.org
From: Andreas Gustafsson <gson@gson.org>
To: jaromir.dolecek@gmail.com, gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-xen/48125 dom0 panic during domU creation attempt
Date: Wed, 27 Jun 2018 11:38:54 +0300
Jaromir,
I was able to reproduce the dom0 crash reported in this PR using the
same domU image as in the original report, Xen 4.5, and a dom0 built
from HEAD sources as of CVS source date 2018.03.28.07.51.09.
I was *not* able to reprodude the crash with an otherwise identical
setup but using a dom0 built from HEAD sources as of CVS source date
2018.06.24.20.28.58.
Therefore, I conclude that your recent change do in fact fix the
problem, and this PR can be closed. Thank you!
--
Andreas Gustafsson, gson@gson.org
State-Changed-From-To: open->needs-pullups
State-Changed-By: gson@NetBSD.org
State-Changed-When: Wed, 27 Jun 2018 08:43:51 +0000
State-Changed-Why:
On further thought, this should be pulled up.
From: coypu@sdf.org
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: port-xen/48125 dom0 panic during domU creation attempt
Date: Wed, 27 Jun 2018 09:00:49 +0000
For future reference purposes (in case nobody files a pullup right
away), this was the commit:
https://mail-index.netbsd.org/source-changes/2018/06/24/msg096302.html
Responsible-Changed-From-To: port-xen-maintainer->jdolecek
Responsible-Changed-By: jdolecek@NetBSD.org
Responsible-Changed-When: Wed, 27 Jun 2018 18:38:53 +0000
Responsible-Changed-Why:
I'll take care about the pullup.
State-Changed-From-To: needs-pullups->pending-pullups
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Thu, 28 Jun 2018 08:46:48 +0000
State-Changed-Why:
Requested pullup to netbsd-8 - #909
State-Changed-From-To: pending-pullups->closed
State-Changed-By: jdolecek@NetBSD.org
State-Changed-When: Sun, 15 Jul 2018 11:32:00 +0000
State-Changed-Why:
Pullup to netbsd-8 done so fix will be part of final 8.0.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.