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


[Xen-users] RE: The death of XEN by Novell

To: "'Lynn Bendixsen'" <lbendixs@xxxxxxxxxx>, "'Mark Williamson'" <mark.williamson@xxxxxxxxxxxx>, "'Antoine Benkemoun'" <antoine.benkemoun@xxxxxxxxx>, "'Ky Srinivasan'" <KSrinivasan.PRV-5.PROVO@xxxxxxxxxx>
Subject: [Xen-users] RE: The death of XEN by Novell
From: "Venefax" <venefax@xxxxxxxxx>
Date: Mon, 21 Jul 2008 20:06:00 -0400
Cc: stephen.spector@xxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Jul 2008 17:06:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=XB42rFzoc9XtQrHFbULYgjDQlNTHdSLBHaJP7pc7fb0=; b=OT8+ielgHWpXABVMXbDjPIQDWNvSaUTpR66bIbxmt0OmCmTwkNgTEl3dTqKQfB4K7P oG1ZY/s+aPEfod2rS+8DKtxJa8ul17usuR5ai9RXvAUjAvyGMNYMHB5zPQg3f/lbQnJZ kF1YiNu+0Nnqs6cE3aJYCHVCKk3toPRuRxI7o=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; b=W+Q7q6Wzi0Lru79qmMO5OHX9nFv4NPYzVw11CR+CDwca2k5d3m8l8mfMnexDR3quec F3vO6AeSsGdFJ/7lJPtfF90or3kJA8KR3eSAMQcxb9c4JNGFB77tpi7AXMbQe0+wyw0D +cYQPCsQWJ53h39LHfqIPnEKWmVvZPMxImOEQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4884C589.30F0.00FC.0@xxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <fc1cbedb0807170903s1f539b8aj32017e643bbd2853@xxxxxxxxxxxxxx> <200807172153.44456.mark.williamson@xxxxxxxxxxxx> <fc1cbedb0807180010v29527992p7f8b727b64f3f4cb@xxxxxxxxxxxxxx> <200807191738.51169.mark.williamson@xxxxxxxxxxxx> <039901c8e9c2$e5dd4530$b197cf90$@com> <4884C589.30F0.00FC.0@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjriH1HccuT+nd+SuO1f9H9Dwp2igABOQkg
Dear Lynn
Why don't you take ownership of the case since obviously the engineer is not
up to date?
If you log into the box you may notice that I am pinning the dom0 to VCPU 0,
and excluding the domu's  from using it. I also restricted dom0 to 4 GB out
of 127.
Is this setup what causes the issue?
When that happened, a while earlier, I was doing a backup of a large
database over the network. The curious thing is the largest database backup
finished fine. It blew-up when I was backing up the other smaller database,
or maybe the first large database blew some buffer and the second got
affected. I cannot know, but that was the only operation that was unusual
that night. The Windows boxes have a note with a minidump, which probably
can be used to trace what driver is the culprit. I can do the same operation
tonight of somebody wants to set up some traces.

I can be reached at 954 444 7408, 24x7.

-----Original Message-----
From: Lynn Bendixsen [mailto:lbendixs@xxxxxxxxxx] 
Sent: Monday, July 21, 2008 7:21 PM
To: 'Mark Williamson'; 'Antoine Benkemoun'; Venefax; Ky Srinivasan
Cc: stephen.spector@xxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: The death of XEN by Novell

>>> On Sat, Jul 19, 2008 at 11:14 AM, in message
<039901c8e9c2$e5dd4530$b197cf90$@com>, "Venefax" <venefax@xxxxxxxxx>
> Subject: The death of XEN by Novell (case number 10406546031)
> According to Novell, Xen has a flaw that in fact means it is useless.
I have 
> a single supported system with SLES SP2, where I have 3 Windows VM's
and 5 
> Linux VM's. In each of the Windows VM's I have 8 Virtual CPU's,
because I 
> have a vital SQL Server installed where my company runs all its
business. The 
> data comes precisely from the Linux virtual machines, and having the
> "right there" has proven extremely efficient. But all my three
Windows VM's 
> crashed simultaneously yesterday and I lost two hours of business. I
am using 
> of course the right Novell drivers, etc., every piece of the puzzle
in place. 
> Novell already checked that. The engineers showed me a technical note
> says that having more than one Virtual CPU in a Windows VM leads to

The technical note you refer to here is outdated.  It is for SLES 10
SP1 and earlier. Here is a link to our current Support Document for Xen
in SLES 10 SP2.
To summarize breifly: we support multiple vcpus for Windows guests in
our SLES10 SP2 and later hosts.  Any issues encountered with multiple
VCPUs in windows should be reported and its certainly a high priority
for us to help you get it working.  All of the testing we do has 2 or 4
vcpus by default in each Windows VM.

> But then we cannot have any windows VM at all, hello!!! This means
that the 
> $35.000 box that I bought is the wrong box, because now I need to
remove my 
> windows VM and create a separate windows installation, and order more

> hardware, spend more money. It means that XEN is useless, because if
it only 
> can virtualize Linux, actually Virtuozzo (Open VZ) has a lot less
> far less. The beauty of Xen is that it is supposed to virtualize
Windows and 
> Linux together. Now, that dream is gone. In case somebody wants to
look at my 
> Novell case number, it is 10406546031

Lynn Bendixsen
Software Engineer

Novell, Inc. 
SUSE* Linux Enterprise 10 SP2
Your Linux is more than ready 

Xen-users mailing list