Dom0 shutdown hangs

Hi,

I have a netbsd dom0 running 2 * netbsd domU and 1 * debian
domU.
Ok so far, but when I execute shutdown -r on *dom0* (or just
reboot)
it just hangs.

On console things look quite normal, I get
syncing disks... done
unmounting file systems...
unmounting /kern
unmounting /opt
unmounting /... done
rebooting....

and then it just hangs. I have to power-cycle the machine.

Any ideas I could try to fix this ? I plan to administer
this server mostly remotely so this is a little bit
annoying...

	Ari S.

On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari Suutari wrote:
> Hi,
> 
> I have a netbsd dom0 running 2 * netbsd domU and 1 *
debian domU.
> Ok so far, but when I execute shutdown -r on *dom0* (or
just reboot)
> it just hangs.
> 
> On console things look quite normal, I get
> syncing disks... done
> unmounting file systems...
> unmounting /kern
> unmounting /opt
> unmounting /... done
> rebooting....
> 
> and then it just hangs. I have to power-cycle the
machine.
> 
> Any ideas I could try to fix this ? I plan to
administer
> this server mostly remotely so this is a little bit
annoying...

Is it Xen2 or Xen3 ? Also do you have serial console ? If
so,
try '^A^A^A' (tree ^A in a row) and then 'q', and look at
the result.
You can reboot with 'R'.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari Suutari wrote:
> Hi,
> 
> I have a netbsd dom0 running 2 * netbsd domU and 1 *
debian domU.
> Ok so far, but when I execute shutdown -r on *dom0* (or
just reboot)
> it just hangs.
> 
> On console things look quite normal, I get
> syncing disks... done
> unmounting file systems...
> unmounting /kern
> unmounting /opt
> unmounting /... done
> rebooting....
> 
> and then it just hangs. I have to power-cycle the
machine.
> 
> Any ideas I could try to fix this ? I plan to
administer
> this server mostly remotely so this is a little bit
annoying...

Is it Xen2 or Xen3 ? Also do you have serial console ? If
so,
try '^A^A^A' (tree ^A in a row) and then 'q', and look
at the result.
You can reboot with 'R'.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

Hi,

Manuel Bouyer wrote:
> On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari Suutari
wrote:
>> Hi,
>>
>> I have a netbsd dom0 running 2 * netbsd domU and 1
* debian domU.
>> Ok so far, but when I execute shutdown -r on *dom0*
(or just reboot)
>> it just hangs.
> 
> Is it Xen2 or Xen3 ? Also do you have serial console ?
If so,
> try '^A^A^A' (tree ^A in a row) and then 'q', and
look at the result.
> You can reboot with 'R'.

	It is Xen3. I don't have serial console attached, but I
can
	sure attach one.


	Ari S.

Hi,

> Manuel Bouyer wrote:
>> On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari
Suutari wrote:
>>> Hi,
>>>
>>> I have a netbsd dom0 running 2 * netbsd domU
and 1 * debian domU.
>>> Ok so far, but when I execute shutdown -r on
*dom0* (or just reboot)
>>> it just hangs.
>>
>> Is it Xen2 or Xen3 ? Also do you have serial
console ? If so,
>> try '^A^A^A' (tree ^A in a row) and then 'q',
and look at the result.
>> You can reboot with 'R'.
> 
	The serial console says:
(XEN) Domain0 shutdown: rebooting machine.

but nothing happens.... It doesn't respond to ctrl-a at
this time neither.

When the system is running using ctrl-a to get back to xen
works and 'q' followed by 'R' gives following output:
NetBSD/i386 (netxen.syncrontech.com) (console)

login: (XEN) *** Serial input -> Xen (type 'CTRL-a'
three times to switch input to DOM0).
(XEN) 'q' pressed -> dumping domain info
(now=0xA:691CEE43)
(XEN) General information for domain 0:
(XEN)     flags=1 refcnt=3 nr_pages=32000 xenheap_pages=5
dirty_cpus=
(XEN)     handle=00000000-0000-0000-0000-000000000000
(XEN) Rangesets belonging to domain 0:
(XEN)     Interrupts 
(XEN)     I/O Memory 
(XEN)     I/O Ports  { 0-1f, 22-3f, 44-60, 62-9f, a2-3f7,
400-ffff }
(XEN) Memory pages belonging to domain 0:
(XEN)     DomPage list too long to display
(XEN)     XenPage 001bc000: mfn=000001bc, caf=80000002,
taf=f0000002
(XEN)     XenPage 001bd000: mfn=000001bd, caf=80000002,
taf=f0000002
(XEN)     XenPage 001be000: mfn=000001be, caf=80000002,
taf=f0000002
(XEN)     XenPage 001bf000: mfn=000001bf, caf=80000002,
taf=f0000002
(XEN)     XenPage 001bb000: mfn=000001bb, caf=80000002,
taf=f0000002
(XEN) VCPU information and callbacks for domain 0:
(XEN)     VCPU0: CPU0 [has=F] flags=17 upcall_pend = 00,
upcall_mask = 00 dirty_cpus= cpu_affinity=
(XEN)     Notifying guest (virq 1, port 1, stat 0/0/0)
debug event
ci_ilevel 0x0 ci_ipending 0x0 ci_idepth 0
evtchn_upcall_pending 0 evtchn_upcall_mask 1
evtchn_pending_sel 0x0
evtchn_mask ffffc403 ffffffff ffffffff ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff 
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff
ffffffff ffffffff ffffffff ffffffff ffffffff
evtchn_pending 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0
(XEN) 'R' pressed -> rebooting machine


I tried also putting "noapic" and
"noacpi" to menu.lst but it didn't help.

	Ari S.

On Mon, Sep 25, 2006 at 10:49:20AM +0300, Ari Suutari wrote:
> Hi,
> 
> >Manuel Bouyer wrote:
> >>On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari
Suutari wrote:
> >>>Hi,
> >>>
> >>>I have a netbsd dom0 running 2 * netbsd
domU and 1 * debian domU.
> >>>Ok so far, but when I execute shutdown -r
on *dom0* (or just reboot)
> >>>it just hangs.
> >>
> >>Is it Xen2 or Xen3 ? Also do you have serial
console ? If so,
> >>try '^A^A^A' (tree ^A in a row) and then
'q', and look at the result.
> >>You can reboot with 'R'.
> >
> 	The serial console says:
> (XEN) Domain0 shutdown: rebooting machine.
> 
> but nothing happens.... It doesn't respond to ctrl-a
at
> this time neither.

Hum so Xen should have dome the reset, and has given up (or
is actually
looping waiting for the CPU to reset). Maybe the dom0 kernel
is doing
something to the hardware which prevents it from resetting
but it's more
likely that the hypervisor it's doing the right thing to
reset this
particular CPU/motherboard. You could try a newer hypervisor
from
the 3.0-testing serie, from
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/download
s/

> [...]
> evtchn_pending 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 
> 0 0
> (XEN) 'R' pressed -> rebooting machine

And does it really reboot at this point ?

-- 
Manuel Bouyer, LIP6, Universite Paris VI.          
Manuel.Bouyerlip6.fr
     NetBSD: 26 ans d'experience feront toujours la
difference
--

Hi,

Manuel Bouyer wrote:
> Hum so Xen should have dome the reset, and has given up
(or is actually
> looping waiting for the CPU to reset). Maybe the dom0
kernel is doing
> something to the hardware which prevents it from
resetting but it's more
> likely that the hypervisor it's doing the right thing
to reset this
> particular CPU/motherboard. You could try a newer
hypervisor from
> the 3.0-testing serie, from
> http://www.cl.cam.ac.uk/Research/SRG/netos/xen/download
s/

	Tried the one from 25-Sep-2006, no change. Maybe it's my
	hardware, it's an oldish 800 Mhz intel board I'm using
for testing.
	(works otherwise OK, however)
> 
>> [...]
>> evtchn_pending 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 
>> 0 0
>> (XEN) 'R' pressed -> rebooting machine
> 
> And does it really reboot at this point ?

	No, it does not.

	Ari S.

On Mon, Sep 25, 2006 at 02:05:41PM +0300, Ari Suutari wrote:
> Hi,
> 
> Manuel Bouyer wrote:
> >Hum so Xen should have dome the reset, and has
given up (or is actually
> >looping waiting for the CPU to reset). Maybe the
dom0 kernel is doing
> >something to the hardware which prevents it from
resetting but it's more
> >likely that the hypervisor it's doing the right
thing to reset this
> >particular CPU/motherboard. You could try a newer
hypervisor from
> >the 3.0-testing serie, from
> >http://www.cl.cam.ac.uk/Research/SRG/netos/xen/download
s/
> 
> 	Tried the one from 25-Sep-2006, no change. Maybe it's
my
> 	hardware, it's an oldish 800 Mhz intel board I'm
using for testing.
> 	(works otherwise OK, however)

Can a NetBSD/i386 kernel reboot OK ?

> >And does it really reboot at this point ?
> 
> 	No, it does not.

It really looks like an hypervisor issue ...

-- 
Manuel Bouyer, LIP6, Universite Paris VI.          
Manuel.Bouyerlip6.fr
     NetBSD: 26 ans d'experience feront toujours la
difference
--

Hi,

Manuel Bouyer wrote:
> 
> Can a NetBSD/i386 kernel reboot OK ?

	Yes (at least I don't recall having any problems)
> 
> It really looks like an hypervisor issue ...
> 
	Well, I can live with this currently, just have to
	remember not to reboot remotely.

	Ari S.

Hi,

Manuel Bouyer wrote:
> On Fri, Sep 22, 2006 at 01:43:04PM +0300, Ari Suutari
wrote:
>> Hi,
>>
>> I have a netbsd dom0 running 2 * netbsd domU and 1
* debian domU.
>> Ok so far, but when I execute shutdown -r on *dom0*
(or just reboot)
>> it just hangs.
> 
> Is it Xen2 or Xen3 ? Also do you have serial console ?
If so,
> try '^A^A^A' (tree ^A in a row) and then 'q', and look
at the result.
> You can reboot with 'R'.

	It is Xen3. I don't have serial console attached, but I can
	sure attach one.


	Ari S.