I'm afraid we are both in the situation that the standaard log files are not enough for the developers to track down the issue. We need to get a console log by attaching a console cable to an other system, starting a terminal program op the other system and booting with the correct boot options so xen will log its events to the console on the other side... see here for more info see comment #5 in https://bugzilla.novell.com/show_bug.cgi?id=389944 If you add your comments to the bug the devs will try to guide you through the process to get things fixed... Hope that helps you a bit further! Cheers, Wj On Tue, 2008-06-24 at 22:14 +0800, 李瑞江 wrote:

Hi Willem Meens:

Thank you for your reply.

I am not using tg3 driver but I am using bnx2. I think we got the same problem: the kernel got something wrong with the broadcom network device.

It seems that xen works well with the old 2.6.22 kernel now and all my virtual machine is running well.

An other problem I encountered now is that Yast->Virtualization->Virtual Machine Manager gives me no reply just like it does in early 10.3 x86_64(but in 10.3, after some upgrade the Yast xen program works!)

The system hangs when using 2.6.25 kernel and I don't know how to get the boot log. Can you tell me how to save the hanged system's boot log?

Thanks!

RuijiangLi

On Tuesday 24 June 2008 16:15:12 Willem Meens wrote:

...

Hi RuijiangLi,

These bugs could be related although you are using the tg3 driver I would think:

https://bugzilla.novell.com/show_bug.cgi?id=396236

https://bugzilla.novell.com/show_bug.cgi?id=389944

Downgrading the kernel does not seem like a good plan and could really mess up the Xen working state. Best of course if this gets fixed with the current kernel in 11.0, but if you are out of time a workaround could be to install openSUSE 10.3 which should work fine.

Hope that helps & this gets sorted!

Wj

-----Oorspronkelijk bericht----- Van: ??? [mailto:lithium7456@gmail.com] Verzonden: dinsdag 24 juni 2008 6:53 Aan: opensuse-virtual@opensuse.org Onderwerp: [opensuse-virtual] opensuse11 x86_64 kernel_xen and Dell 2950

I installed opensuse11 x86_64 on a Dell 2950 server, at first, everything goes well.

But after I installed Xen via Yast and choose "Xen" from boot menu, the system hangs, and the small LCD on the server shows "CPU 1 IERR" or "CPU 2 IERR"

The last line of screen is like this:

Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.5.11 (June 4, 2007) ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16

I have to download kernel-xen 2.6.22 from opensuse 10.3's repo and with the old kernel system can boot.

Anyone has the same problem? And any other solution?

Thanks!

RuijiangLi

-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org

I'm afraid we are both in the situation that the standaard log files are not enough for the developers to track down the issue. We need to get a console log by attaching a console cable to an other system, starting a terminal program op the other system and booting with the correct boot options so xen will log its events to the console on the other side... see here for more info see comment #5 in https://bugzilla.novell.com/show_bug.cgi?id=389944 If you add your comments to the bug the devs will try to guide you through the process to get things fixed... Hope that helps you a bit further! Cheers, Wj On Tue, 2008-06-24 at 22:14 +0800, 李瑞江 wrote:

Hi Willem Meens:

Thank you for your reply.

I am not using tg3 driver but I am using bnx2. I think we got the same problem: the kernel got something wrong with the broadcom network device.

It seems that xen works well with the old 2.6.22 kernel now and all my virtual machine is running well.

An other problem I encountered now is that Yast->Virtualization->Virtual Machine Manager gives me no reply just like it does in early 10.3 x86_64(but in 10.3, after some upgrade the Yast xen program works!)

The system hangs when using 2.6.25 kernel and I don't know how to get the boot log. Can you tell me how to save the hanged system's boot log?

Thanks!

RuijiangLi

On Tuesday 24 June 2008 16:15:12 Willem Meens wrote:

...

Hi RuijiangLi,

These bugs could be related although you are using the tg3 driver I would think:

https://bugzilla.novell.com/show_bug.cgi?id=396236

https://bugzilla.novell.com/show_bug.cgi?id=389944

Downgrading the kernel does not seem like a good plan and could really mess up the Xen working state. Best of course if this gets fixed with the current kernel in 11.0, but if you are out of time a workaround could be to install openSUSE 10.3 which should work fine.

Hope that helps & this gets sorted!

Wj

-----Oorspronkelijk bericht----- Van: ??? [mailto:lithium7456@gmail.com] Verzonden: dinsdag 24 juni 2008 6:53 Aan: opensuse-virtual@opensuse.org Onderwerp: [opensuse-virtual] opensuse11 x86_64 kernel_xen and Dell 2950

I installed opensuse11 x86_64 on a Dell 2950 server, at first, everything goes well.

But after I installed Xen via Yast and choose "Xen" from boot menu, the system hangs, and the small LCD on the server shows "CPU 1 IERR" or "CPU 2 IERR"

The last line of screen is like this:

Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v1.5.11 (June 4, 2007) ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 16 (level, low) -> IRQ 16

I have to download kernel-xen 2.6.22 from opensuse 10.3's repo and with the old kernel system can boot.

Anyone has the same problem? And any other solution?

Thanks!

RuijiangLi

-- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-virtual+help@opensuse.org