This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Identical Win3K3 domU's. One panics dom0, other runs fin

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Identical Win3K3 domU's. One panics dom0, other runs fine
From: Don Faulkner <dfaulkner@xxxxxxxxxxx>
Date: Wed, 02 Apr 2008 13:26:11 -0500
Delivery-date: Wed, 02 Apr 2008 11:27:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200804021801.14968.mark.williamson@xxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: The Engineering Institute
References: <47F3A697.5020303@xxxxxxxxxxx> <200804021801.14968.mark.williamson@xxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080213 Thunderbird/ Mnenhy/
Your assumptions are correct. Order doesn't matter; perseus always causes the panic regardless of whether cepheus is already running or not. The vif's are commented out for debug purposes only.

I'll report this to both xen-devel and the Ubuntu Kernel Team (since they apparently maintain the xen kernel too). Thanks.

Mark Williamson wrote:
I suppose it doesn't matter what order the domUs are started in?

And assume that perseus's vif lines (currently being commented out) don't make a difference?

You might want to report this to xen-devel as it's clearly a bug of some sort. It's not *necessarily* an upstream Xen bug (as opposed to a bug with Ubuntu's XenLinux, for instance) so you might want to consider upstream bug reporting too.


On Wednesday 02 April 2008, Don Faulkner wrote:
Hi there.

I'm new to Xen, but a Linux veteran. I've been trying to install Win2K3
in a domU, with some success but I've run into an odd problem. The first
Win2K3 domU boots, installs, and runs perfectly (as far as I can tell).
The second boots and starts the install, but can't finish it. the dom0
kernel panics. This happens whether the first domU is running or not.
The message in syslog is:

BUG: unable to handle kernel NULL pointer dereference at virtual address

A bit about my system. Xubuntu 7.10 (feisty) running on an IBM HS21
blade, with iSCSI SAN. I'm booting from SAN and using separate SAN
volumes for each domU.

I'm attaching the relevant portion of my syslog along with the two domU
config files. The domU name Cepheus is the one that is working fine. The
domU named Perseus is the one that causes the panic. Any ideas would be
greatly appreciated. Like I said, I'm new here, and I'm not sure I've
got everything properly set up, so I won't get insulted if you ask
rudimentary questions. :)

Xen-users mailing list