Xen users - Dec 2006 - Xen3 on Etch - Rebooting when 2nd DomU started

Hi All,

Fairly new to Debian and Xen but I have a box running with lots of DomUs 
under Xen2 and it is fine.

I have setup a new IBM eServer P4 and loaded Etch and loaded Xen3.

It runs up my first DomU beautifully but when I start my second DomU it 
crashes the PC and reboots.

If I comment out the line in /etc/xen/xend-config.sxp

(network-script network-bridge)

It will run 2 DomUs

Have I run into a common problem or can someone suggest what I might 
have messed up?

TIA

Simon



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On 12/4/06, Simon Faulkner <simon@titanic.co.uk>
wrote:
> I have setup a new IBM eServer P4 and loaded Etch and loaded Xen3.
Debian Packages of Xen?
> It runs up my first DomU beautifully but when I start my second DomU it
> crashes the PC and reboots.
Anything in the logs?
> If I comment out the line in /etc/xen/xend-config.sxp
>
> (network-script network-bridge)
>
> It will run 2 DomUs
But you have no nice network connection then :)

Only 2 but also 3 and more than? This sounds strange.

I''d try to see what the Xen demo cd does, to see if it''s your
hardware, or your configuration, or the version,  and if another
version of Xen does better (if you have the debian packages, try
xensource binary or sozurce packages, or vice versa).

If it''s only in the debian packages, a bug report would be a good idea.
Henning

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> Debian Packages of Xen?
Yes
>> It runs up my first DomU beautifully but when I start my second DomU it
>> crashes the PC and reboots.
> 
> Anything in the logs?
Mmmm, not that I understand :-)
Last message on the screen is:
kernel panic - not syncing: fatal exception in interrupt
>> If I comment out the line in /etc/xen/xend-config.sxp
>>
>> (network-script network-bridge)
>>
>> It will run 2 DomUs
> 
> But you have no nice network connection then :)
No :-(
> Only 2 but also 3 and more than? This sounds strange.
> 
> I''d try to see what the Xen demo cd does, to see if it''s
your
> hardware, or your configuration, or the version,  and if another
> version of Xen does better (if you have the debian packages, try
> xensource binary or sozurce packages, or vice versa).
Xen CD won''t boot - some problem with SATA and the CD ROM not being 
recognised
> If it''s only in the debian packages, a bug report would be a good
idea.
Given my lack of knowledge it is far more likely to be me than Debian!
I was kinda hoping you were all going to say - "yeah, we hear this all 
the time" but perhaps not.

I will go and learn more about interrupts...

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

I have the same problem with Debian/Etch
xen-linux-system-2.6.17-2-xen-686 package.

I have a domU with two net-if and works well, when I start a second domU
 I receive a kernel panic.   If I start simple domU (one net-if e.o.), I
can boot two domUs, but the third produces a kernel panic.

I have a second server with a similar problem.

But I have a third server that boot up to 4 domUs without problems.

The first two servers are Celeron, and the third is PII.  (Today I will
test with a third celeron and a fresh installation).

Simon Faulkner wrote:
>> Debian Packages of Xen?
> 
> Yes
> 
>>> It runs up my first DomU beautifully but when I start my second
DomU it
>>> crashes the PC and reboots.
>>
>> Anything in the logs?
> 
> Mmmm, not that I understand :-)
> Last message on the screen is:
> kernel panic - not syncing: fatal exception in interrupt
> 
>>> If I comment out the line in /etc/xen/xend-config.sxp
>>>
>>> (network-script network-bridge)
>>>
>>> It will run 2 DomUs
>>
>> But you have no nice network connection then :)
> 
> No :-(
> 
>> Only 2 but also 3 and more than? This sounds strange.
>>
>> I''d try to see what the Xen demo cd does, to see if
it''s your
>> hardware, or your configuration, or the version,  and if another
>> version of Xen does better (if you have the debian packages, try
>> xensource binary or sozurce packages, or vice versa).
> 
> Xen CD won''t boot - some problem with SATA and the CD ROM not
being
> recognised
> 
>> If it''s only in the debian packages, a bug report would be a
good idea.
> 
> Given my lack of knowledge it is far more likely to be me than Debian!
> I was kinda hoping you were all going to say - "yeah, we hear this all
> the time" but perhaps not.
> 
> I will go and learn more about interrupts...
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Simon Faulkner wrote:
> Hi All,
>
> Fairly new to Debian and Xen but I have a box running with lots of 
> DomUs under Xen2 and it is fine.
>
> I have setup a new IBM eServer P4 and loaded Etch and loaded Xen3.
>
> It runs up my first DomU beautifully but when I start my second DomU 
> it crashes the PC and reboots.
>
If I disable hyperthreading in the BIOS I can I boot a 2nd DomU without 
crashing the box .. but not a 3rd
> If I comment out the line in /etc/xen/xend-config.sxp
>
> (network-script network-bridge)
>
Haven''t tried this - thanks!
> It will run 2 DomUs
>
> Have I run into a common problem or can someone suggest what I might 
> have messed up?
>
> TIA
>
> Simon
>


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Dec 04, 2006 at 04:47:24PM +0000, Simon Faulkner
wrote:
> Fairly new to Debian and Xen but I have a box running with lots of DomUs 
> under Xen2 and it is fine.
> 
> I have setup a new IBM eServer P4 and loaded Etch and loaded Xen3.
> 
> It runs up my first DomU beautifully but when I start my second DomU it 
> crashes the PC and reboots.
> 
> If I comment out the line in /etc/xen/xend-config.sxp
> 
> (network-script network-bridge)
> 
> It will run 2 DomUs
> 
> Have I run into a common problem or can someone suggest what I might 
> have messed up?
I came across this with 2.6.17, as did other people. It goes away if you
use 2.6.16 or 2.6.18.
It shouldnt be too hard to install 2.6.18-2 from sid in etch.

-- 
Pete

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Rodolfo Pilas wrote:
> I have the same problem with Debian/Etch
> xen-linux-system-2.6.17-2-xen-686 package.
> 
> I have a domU with two net-if and works well, when I start a second domU
>  I receive a kernel panic.   If I start simple domU (one net-if e.o.), I
> can boot two domUs, but the third produces a kernel panic.
> 
> I have a second server with a similar problem.
> 
> But I have a third server that boot up to 4 domUs without problems.
> 
> The first two servers are Celeron, and the third is PII.  (Today I will
> test with a third celeron and a fresh installation).
Mmmm.  I made a duo-core 2 PC on a Gigabyte Mobo and had this problem so 
made that into a workstation and bought an IBM eServer P4 which has 
exactly the same problem.  My friend, who helped me get Xen setup, has 
it running on older hardware and has no problem at all.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Pete McEvoy wrote:
> I came across this with 2.6.17, as did other people. It goes away if you
> use 2.6.16 or 2.6.18.
> It shouldnt be too hard to install 2.6.18-2 from sid in etch.
Yes, I have just seen that Debian/Etch has
	xen-linux-system-2.6.17-2-xen-686
and Debian/Sid has
	xen-linux-system-2.6.18-3-xen-686

Cool, today I will backport to 2.6.18.

Rodolfo

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

The problem is solved upgrading to kernel 2.6.18

On 12/4/06, Rodolfo Pilas <rodolfo@pilas.net>
wrote:
> Pete McEvoy wrote:
>
> > I came across this with 2.6.17, as did other people. It goes away if
you
> > use 2.6.16 or 2.6.18.
> > It shouldnt be too hard to install 2.6.18-2 from sid in etch.
>
> Yes, I have just seen that Debian/Etch has
>         xen-linux-system-2.6.17-2-xen-686
> and Debian/Sid has
>         xen-linux-system-2.6.18-3-xen-686
>
> Cool, today I will backport to 2.6.18.
>
> Rodolfo
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Alejandro Leyva wrote:
> The problem is solved upgrading to kernel 2.6.18
Yes!

1) apt-get install xen-linux-system-2.6.18-3-xen-686
   (from unstable)

2) modify config files:
	kernel  = ''/boot/vmlinuz-2.6.18-3-xen-686''
	ramdisk = ''/boot/initrd.img-2.6.18-3-xen-686''

3) cp  /lib/modules/2.6.18-3-xen-686  into domU

and all work!

# xm list
Name                                      ID Mem(MiB) VCPUs State
Domain-0                                   0      365     1 r-----
check                                      7      128     1 -b----
mono                                       3      128     1 -b----
vm03                                       5      128     1 -b----
vm04                                       6      128     1 -b----

Rodolfo



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users