2009/6/7 Bruno Damour :
> Well there are a couple of things to take into consideration.
> First, I _did_ get some dom0 crashes so that in deed the opensolaris xvm
> code could be responsible for this
Ok.
> Second, xen version on opensolaris is still 3.1.4, which may also explain
> the differenc
Adrian Chadd wrote:
I can't trigger this here with my Centos 5.3 domU. I have a feeling
this may be related to the hypervisor/dom0 environment.
Not to say it isn't a bug, it is just going to take me more time to
try and figure out.
I'll commit some more Xen tidyups to -current and build a new i
I can't trigger this here with my Centos 5.3 domU. I have a feeling
this may be related to the hypervisor/dom0 environment.
Not to say it isn't a bug, it is just going to take me more time to
try and figure out.
I'll commit some more Xen tidyups to -current and build a new image
for you. It'll st
Adrian Chadd wrote:
What, so fetching data from ftpd running on the xen domU to another
LAN connected host?
so the problem seems to come more from upload traffic than download ?
See, thats the sort of information I need to reproduce the problem. :)
I enable a ftp on a local LAN ho
Adrian Chadd wrote:
2009/6/7 Bruno Damour :
Adrian Chadd wrote:
That seems to be dereferencing a mbuf pointer. I'll look into it.
What are you doing to trigger this condition again?
Adrian
Hello,
Well it is consistently reproductible : each time I issue a cvsup command.
2009/6/7 Bruno Damour :
> Adrian Chadd wrote:
>>
>> That seems to be dereferencing a mbuf pointer. I'll look into it.
>>
>> What are you doing to trigger this condition again?
>>
>>
>> Adrian
>>
>
> Hello,
> Well it is consistently reproductible : each time I issue a cvsup command.
Ok, so cvsup'in
Adrian Chadd wrote:
That seems to be dereferencing a mbuf pointer. I'll look into it.
What are you doing to trigger this condition again?
Adrian
Hello,
Well it is consistently reproductible : each time I issue a cvsup command.
The interesting point is that I can _download_ without any prob
2009/6/7 Bruno Damour :
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x2
> fault code = supervisor read, page not present
> instruction pointer = 0x21:0xc02f719b
> stack pointer = 0x29:0xc3527bc8
> frame
Hello Adrian,
Well, same pb w/ the new img :
Cannot open "surrent-supfile": No such file or directory
# csup current-supfile
Connected to 130.94.149.166
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex xennetif_tx (network transmit lock) r = 0
G'day,
I've just uploaded another -current image.
http://wiki.freebsd.org/AdrianChadd/XenImages will have a link to it.
Pygrub will give you a boot menu list (just like normal GRUB) if you
create the domain with "xm create -c". That attaches the console at
startup, giving pygrub time to display t
I'd like whatever information you can provide about the domU panic. It
should dump you into the kernel debugger. Please type "bt" at the
(ddb) prompt and then provide me with a copy of the domU console
output. Don't kill the domain either; I may ask for further ddb
commands.
Here is a full log
Adrian Chadd wrote:
2009/6/5 Bruno Damour :
Hello,
I have tried for some time to get to install freeBSD on an up-to-date (SXCE
b114) opensolaris xvm box (xen 3.1.4) which already has had success in
running in a quite stable xay NetBSD and Gentoo Linux as PV domUs and
different Windows flavou
2009/6/5 Bruno Damour :
> Hello,
> I have tried for some time to get to install freeBSD on an up-to-date (SXCE
> b114) opensolaris xvm box (xen 3.1.4) which already has had success in
> running in a quite stable xay NetBSD and Gentoo Linux as PV domUs and
> different Windows flavours (Server 2008,
Hello,
I have tried for some time to get to install freeBSD on an up-to-date
(SXCE b114) opensolaris xvm box (xen 3.1.4) which already has had
success in running in a quite stable xay NetBSD and Gentoo Linux as PV
domUs and different Windows flavours (Server 2008, Win7 RC, Xp, Server
2003) as
14 matches
Mail list logo
