WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xend start error

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] xend start error
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 18 Feb 2009 01:04:58 -0800 (PST)
Cc: jonr@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 18 Feb 2009 01:05:31 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1234947898; bh=7GtYWkWsRGg4T8YTFuqGnQoTiiw4zNWcUX7Qmb5uXfE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Z5i6abnUpKawA8bSEIjHJhT9P8AEPsIO/D1lQHlm7hr4J0MbsOXdUBnk3dGKQ1KLPRr+gohmCipVxSxjwH+amke0B2kp4H/TRLYmipba9GKuIs504nfIr+DLdE7L7uR7ztyNhIPbo5/EAR5kXSCncMf/Hk2aGd5V0Aq2J1fsBPs=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=G2Bz/ajy4jQ5iCRz/uPPFcpPC2xzQstPegdZPL7Qwy+tktbMI3LwzPkIbionkPGrTVhpYDAcj+VEPAVVCRpf1PbjyHbk9qN7vq0MAruo7oPgwLJdTVT5H7NXoXX5G7J0w52W1NkodijFHEfBTbPTvoG9MlEUrqTZAA1NA0CN9p0=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499BC722.2030608@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bderzhavets@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I setup VNC on the box and major part of time work remotely via Gnome
Desktop Env.

Following PV DomUs have been installed successfully and ran pretty stable (2.6.29-rc3 kernel)  :-

1. Fedora 10
2. Ubuntu 8.10 Server (via debootstrap)
3. OpenSuse 11.1
4. Solaris Nevada b106 been also installed yesterday with 2.6.29-rc5

 VNC has been setup on (1),(2),(4) .  (3) was installed via vfb and went
directly KDE 4.1 desktop. Numerous "aptitude installs" have been run on
(2) with no problems.
 I am experiencing only one issue. At the end of work time frame (4-6hr)
 i notice  {DRDY} - messages on text console. Pressing "enter" returns
 to root prompt "#" and nothing else. 
    It's Intel box assembled on ASUS P5K Premium/WIFI (South Bridge ICH9R), CPU C2D E8400, 8 GB RAM,2x250 SATA Seagate Barracuda
drives (no RAID). Actually, 1-1.5 years old hardware.
I did have problems assembling boxes with ASUS P5Q Deluxe (P45) .
It was not Xen related issues.


--- On Wed, 2/18/09, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] xend start error
To: bderzhavets@xxxxxxxxx
Cc: jonr@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Wednesday, February 18, 2009, 3:30 AM

Boris Derzhavets wrote:
> [ 0.706848] ahci 0000:00:1f.2: version 3.0
> [ 0.706866] xen: registering gsi 22 triggering 0 polarity 1
> [ 0.706878] xen: --> irq=22
> [ 0.706881] xen_set_ioapic_routing: irq 22 gsi 22 vector 176 ioapic 0
pin 22 triggering 0 polarity 1
> [ 0.706943] ahci 0000:00:1f.2: PCI INT B -> GSI 22 (level, low)
-> IRQ 22
> [ 0.707070] ahci: SSS flag set, parallel bus scan disabled
> [ 0.707143] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps
0x3f impl SATA mode
> [ 0.707199] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo
pmp pio slum part ems
> [ 0.707259] ahci 0000:00:1f.2: setting latency timer to 64
> [ 0.707796] scsi0 : ahci
> [ 0.708037] scsi1 : ahci
> [ 0.708243] scsi2 : ahci
> [ 0.708450] scsi3 : ahci
> [ 0.708651] scsi4 : ahci
> [ 0.708855] scsi5 : ahci
> [ 0.709221] ata1: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffe900 irq 22
> [ 0.709277] ata2: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffe980 irq 22
> [ 0.709332] ata3: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffea00 irq 22
> [ 0.709387] ata4: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffea80 irq 22
> [ 0.709442] ata5: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffeb00 irq 22
> [ 0.709497] ata6: SATA max UDMA/133 abar m2048@0xf9ffe800 port
0xf9ffeb80 irq 22
> [ 1.230023] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 1.230663] ata1.00: ATA-7: ST3250410AS, 3.AAC, max UDMA/133
> [ 1.230718] ata1.00: 488397168 sectors, multi 0: LBA48 NCQ (depth
31/32)
> [ 1.231469] ata1.00: configured for UDMA/133
> [ 1.250137] scsi 0:0:0:0: Direct-Access ATA ST3250410AS
3.AA PQ: 0 ANSI: 5
> [ 1.780022] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [ 1.780605] ata2.00: ATA-7: ST3250410AS, 3.AAC, max UDMA/133
> [ 1.780656] ata2.00: 488397168 sectors, multi 0: LBA48 NCQ (depth
31/32)
> [ 1.781394] ata2.00: configured for UDMA/133
> [ 1.800124] scsi 1:0:0:0: Direct-Access ATA ST3250410AS
3.AA PQ: 0 ANSI: 5
> [ 2.150024] ata3: SATA link down (SStatus 0 SControl 300)
> [ 2.520024] ata4: SATA link down (SStatus 0 SControl 300)
> [ 2.890023] ata5: SATA link down (SStatus 0 SControl 300)
> [ 3.260024] ata6: SATA link down (SStatus 0 SControl 300)
>

How reliable is your machine with AHCI? Last time I tried it I got nowhere.
Others have reported that its quite unstable (fails a couple of minutes after
boot, at best).

Thanks,
J

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