Re: NetBSD host rebooting automatically.

[Adiel de Lima Ribeiro <adiel.netadmin%gmail.com@localhost>]

On Tue, 2013-09-03 at 17:47 +0200, Roger Pau Monné wrote:
> On 03/09/13 17:48, Adiel de Lima Ribeiro wrote:
> > Hi everyone again.
> > I have NetBSD host 6.1 Stable amd64 with xenkernel42-4.2.2 and
> > xentools42-4.2.2nb3, I'm working with the Xen xl toolstack. 
> > The relevant parts in my xend-config.sxp are these:
> > 
> > (dom0-min-mem 196)
> > (enable-dom0-ballooning no)
> > (dom0-cpus 1)
> > (enable-dump no)
> > (xend-domains-path /xen/config)
> > (device-create-timeout 30)
> > (device-destroy-timeout 30)
> > #(pci-passthrough-strict-check yes)
> 
> This is only relevant if you are using the xm toolstack, xl completely
> ignores this file, take a look at xl.conf instead
> (http://xenbits.xen.org/docs/unstable/man/xl.conf.5.html)

That's all right, so here is my xl.conf:

## Global XL config file ##

# automatically balloon down dom0 when xen doesn't have enough free
# memory to create a domain
#autoballoon=1

# full path of the lockfile used by xl during domain creation
#lockfile="/var/lock/xl"

# default vif script 
#vifscript="vif-bridge"

# default output format used by "xl list -l"
#output_format="json"

# first block device to be used for temporary VM disk mounts
#blkdev_start="xvda"

# default option to run hotplug scripts from xl
# if disabled the old behaviour will be used, and hotplug scripts will
be
# launched by udev.
#run_hotplug_scripts=1

> 
> > 
> > I have FreeBSD 9.2 Prerelease i386 guests, the config file is bellow:
> > 
> > builder='hvm'
> > name="source"
> > memory=200
> > on_poweroff="destroy"
> > disk = [ '/xen/domains/source/source.img,file:hda,w' ]
> > vif = [ 'bridge=bridge0, type=vif' ]
> > vnc=0
> > boot='c'
> > usb=0
> > nographic=1
> > 
> > Everything works fine, except because that my NetBSD host reboots from
> > about 5 and 5 days automatically. 
> > The relevant part of qemu-dm-source.log is bellow:
> > 
> > xen be core: xen be core: can't open gnttab device
> > can't open gnttab device
> > Log-dirty: no command yet.
> > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
> > vcpu-set: watch node error.
> > xs_read(/local/domain/6/log-throttling): read error
> > qemu: ignoring not-understood drive `/local/domain/6/log-throttling'
> > medium change watch on `/local/domain/6/log-throttling' - unknown
> > device, ignored
> 
> You should attach a serial console to the host, so you can capture the
> messages when the system reboots, without that it is impossible to know
> what's going on.
> 

I redirected my Host log files from console to a file, there isn't
nothing different from this:

Sep  2 09:21:33 xen /netbsd: xbd backend: detach device vnd0d for domain
1
Sep  2 09:21:33 xen /netbsd: xbd backend: detach device vnd1d for domain
1
Sep  2 09:21:33 xen /netbsd: xvif1i0: disconnecting
Sep  2 09:21:54 xen /netbsd: xbd backend: attach device vnd0d (size
314572800) for domain 4
Sep  2 09:21:54 xen /netbsd: xbd backend: attach device vnd1d (size
14680064) for domain 4
Sep  2 09:21:55 xen /netbsd: xvif4i0: Ethernet address 00:16:3e:41:92:e2
Sep  2 09:22:14 xen /netbsd: xbd backend domain 4 handle 0x300 (768)
using event channel 33, protocol x86_32-abi
Sep  2 09:22:14 xen /netbsd: xbd backend domain 4 handle 0x340 (832)
using event channel 34, protocol x86_32-abi
Sep  2 09:23:12 xen /netbsd: xbd backend: detach device vnd1d for domain
4
Sep  2 09:23:12 xen /netbsd: xbd backend: detach device vnd0d for domain
4
Sep  2 09:23:12 xen /netbsd: xvif4i0: disconnecting
Sep  2 09:24:47 xen /netbsd: xbd backend: attach device vnd0d (size
14680064) for domain 5
Sep  2 09:24:47 xen /netbsd: xbd backend: attach device vnd1d (size
314572800) for domain 5
Sep  2 09:24:47 xen /netbsd: xvif5i0: Ethernet address 00:16:3e:1c:80:af
Sep  2 09:25:07 xen /netbsd: xbd backend domain 5 handle 0x300 (768)
using event channel 36, protocol x86_32-abi
Sep  2 09:25:07 xen /netbsd: xbd backend domain 5 handle 0x340 (832)
using event channel 37, protocol x86_32-abi
Sep  2 09:26:24 xen /netbsd: xbd backend: detach device vnd0d for domain
5
Sep  2 09:26:24 xen /netbsd: xbd backend: detach device vnd1d for domain
5
Sep  2 09:26:24 xen /netbsd: xvif5i0: disconnecting
Sep  2 09:26:29 xen /netbsd: xbd backend: attach device vnd1d (size
314572800) for domain 6
Sep  2 09:26:29 xen /netbsd: xbd backend: attach device vnd0d (size
14680064) for domain 6
Sep  2 09:26:29 xen /netbsd: xvif6i0: Ethernet address 00:16:3e:17:2f:53
Sep  2 09:26:47 xen /netbsd: xbd backend domain 6 handle 0x300 (768)
using event channel 39, protocol x86_32-abi
Sep  2 09:26:47 xen /netbsd: xbd backend domain 6 handle 0x340 (832)
using event channel 40, protocol x86_32-abi

-- 
att,
Adiel de Lima Ribeiro