[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: disappointing upgrade to NetBSD 5.0
On Tue, 26 May 2009 05:40:04 -0700, Jean-Yves Migeon
Dan Engholm wrote:
I can't be sure what I am doing to get the problem to occur, but it
to be network related. Looking around Google, I found one thread in
port-xen with a similar description but it dead ended with no
It is network related, but the error is due to the hypervisor returning
an error for the decrease memory operation. As the domU does not expect
it to fail, it ends in panic().
Advice would be the same as in the link above: any error reported by the
hypervisor on its console?
The console doesn't show anything when the panic occurs. I don't have a
terminal on the serial port but my xconsole shows XEN related messages so
I'm assuming that is where I would see something related to this problem,
too. Here is what I see while the user domain is starting up:
xvif2.0: Ethernet address aa:00:00:51:02:f0
May 26 18:39:11 xxxxxx routed: Send bcast sendto(xvif2.0,
172.16.3.7.520): Network is down
xbd backend: attach device wd1b (size 2097152) for domain 2
xbd backend: attach device raid2f (size 209715200) for domain 2
xbd backend: attach device raid1f (size 4194304) for domain 2
xvif2.0 using event channel 17
xbd backend 0 for domain 2 using event channel 18
Building databases:panic: buf mem pool index 7
uvm_fault(0xc9d58b98, 0, 1) -> 0xe
fatal page fault in supervisor mode
trap type 6 code 0 eip c0396531 cs 9 eflags 10246 cr2 0 ilevel 0
Faulted in mid-traceback; aborting...
dumping to dev 142,16 offset 1582223
dump device bad
What it should have said after "Building databases:" is:
Building databases: dev, utmp, utmpx done
Setting date via ntp.
Checking for core dump...
Any chance we could get a backtrace?
For that, edit the /etc/sysctl.conf of domU, set the ddb.onpanic to 1.
Then "bt" from ddb prompt.
panic: Unable to reduce memory reservation
fatal breakpoint trap in supervisor mode
trap type 1 code 0 eip c039504c cs 9 eflags 246 cr2 0 ilevel 4
Stopped in pid 579.1 (Xvnc) at netbsd:breakpoint+0x4: popl %ebp
No such command: BT
Since the upgrade, my user domain no longer boots without
does not figure out on its own where the root partition is so I have to
manually enter "xbd0a" from the Xen console. The configuration file has
'root = "/dev/xbd0a"' in it as it has since I started using Xen. This
true regardless of which version of Xen I use.
And with root = "xbd0" ?
Specifying 'root = "xbd0a"' seemed to fix this problem. Thanks.
Also, I got burned by Xen telling me that the "nics" configuration
is obsolete. The man page says that it's still valid and that its
value is 1. If I don't have a "nics = 1" line in my configuration
NICs are created and the creation fails because it can't configure the
network. What gives?
vif = ['mac=00:16:3e:00:00:11, bridge=bridge0'] # for example
I don't get this one. I could not create the user domain until I put
'nics = 1' in but now I have it commented out and it works just fine.
The saga continues. See my follow-up to the other reply.
Main Index |
Thread Index |