[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Virtual SCSI


  • To: Paolo Rivetti <natecult@xxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Sun, 14 Mar 2010 14:39:34 -0700 (PDT)
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Sun, 14 Mar 2010 14:41:19 -0700
  • 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:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=x2TB9H7nYxI3IiHyGh3ytNwUfCc2KQk2AhXyNvJ7FZatNzh6dWX0d7vvIZVS0YMe0+z1IFUn9UdUejR97EEsI3Sd3hW8Z4/uHedzEIy8UKfFIA0tWHfHnRFx1gD8Gsl1EMenMqXNuU0u3+ex86Jufuq9VZjzn7MwGo6aWYGTcvk=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

> Well now your Xen hypervisor and xen tools have PVSCSI support,
> but your dom0 and domU kernels still lack support (drivers)!

1. Port to clean CentOS 5.X Xen 3.3.1 from xensource 2.6.18 kernel been built via   xensource,  per Pasi previous statement should have have required drivers.
Work without Libvirt is hard, but quite possible.

2. Xen 3.4.3-rc3 ( 2.6.32.9 pvops)  on top F12 - hard for newcomer but Libvirt is there.

Boris.


--- On Sun, 3/14/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] Virtual SCSI
To: "Paolo Rivetti" <natecult@xxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Sunday, March 14, 2010, 2:46 PM

On Sun, Mar 14, 2010 at 04:58:06PM +0100, Paolo Rivetti wrote:
>    I just updated my Xen host to version 3.4.2 through gitco.de /repo
>    Starting a virtual machine I have the following error, anyone know what
>    this is?

Well now your Xen hypervisor and xen tools have PVSCSI support,
but your dom0 and domU kernels still lack support (drivers)!

-- Pasi

>    xm create -c / etc/xen/tb0
>    Using config file "/etc/xen/tb0.
>    Error: Boot loader did not return any data!
>    My configuration uses this parameter: bootloader = "/usr/bin/pygrub"
>    On Mar 14, 2010, at 3:24 PM, Boris Derzhavets wrote:
>
>      Xen Hypervisor on CentOS 5.X  may be upgraded to 3.4.2 via
>      [1]http://gitco.com/repo
>      Xenified kernel will stay matching current status in repos
>      2.6.18-128el5xen or something
>      like that.
>
>      Boris.
>
>      --- On Sun, 3/14/10, Pasi Kärkkäinen <[2]pasik@xxxxxx> wrote:
>
>        From: Pasi Kärkkäinen <[3]pasik@xxxxxx>
>        Subject: Re: [Xen-users] Virtual SCSI
>        To: "Paolo Rivetti" <[4]natecult@xxxxxx>
>        Cc: "James Harper" <[5]james.harper@xxxxxxxxxxxxxxxx>,
>        [6]xen-users@xxxxxxxxxxxxxxxxxxx
>        Date: Sunday, March 14, 2010, 10:10 AM
>
>        On Sun, Mar 14, 2010 at 02:30:58PM +0100, Paolo Rivetti wrote:
>        >        I'm trying to assign 2 SATA devices to a PV guest.
>        >
>        >        Command lsscsi:
>        >
>        >        [0:0:0:0] disk ATA WDC WD3200AAJS-0 12.0 / dev / sda
>        >
>        >        [2:0:0:0] disk ATA WDC WD10EADS-00L 01.0 / dev / sdb
>        >
>        >        [3:0:0:0] disk ATA WDC WD10EADS-00L 01.0 / dev / sdc
>        >
>        >        Therefore my configuration:
>        >
>        >        vscsi = [ '/ dev / sdb, 2:0:0:0', '/ dev / sdc, 3:0:0:0']
>        >
>        >        The PV guest starts correctly but there are no disks sdb and
>        sdc.
>        >
>        >        Where am I wrong? Thanks
>        >
>        >      There shouldn't be spaces between the '/'s. Are they just an
>        artefact of
>        >      the cut & paste to email?
>        >
>        >    It was only a mistake of copy pasting. This is my configuration:
>        >    name = "of0"
>        >    memory = "512"
>        >    disk = [ 'phy:/dev/vg1/of0,xvda,w' ]
>        >    #, 'phy:/dev/sdb,xvdb,w', 'phy:/dev/sdc,xvdc,w' ]
>        >    vif = [ 'mac=00:01:4F:FC:00:00,bridge=xenbr0' ]
>        >    bootloader="/usr/bin/pygrub"
>        >    vcpus=2
>        >   
>        >   
>        >    kernel="/boot/vmlinuz-2.6.18-164.el5xen"
>        >    root ="/dev/xvda ro"
>        >    vscsi = [ '/dev/sdb, 2:0:0:0', '/dev/sdc, 3:0:0:0' ]
>        >
>        >      Other things to consider:
>        >      1. is the pvscsi module loaded? Is it definitely supported by
>        your
>        >      version of xen? The fact that it silently doesn't do anything
>        is
>        >      suspicious
>        >
>        >    What is the module to load? With the command "dmesg | grep
>        pvscsi" prompt
>        >    returns nothing. How can I check if the version of Xen supports
>        this
>        >    module? My version is this:
>        >    xen-3.0.3-94.el5
>        >    xen-libs-3.0.3-94.el5
>        >    kernel-xen-2.6.18-164.el5
>        >
>
>        I don't think RHEL5 version of Xen has PVSCSI support.
>
>        You need to have the pvscsi backend driver (scsiback) in dom0 kernel,
>        and the pvscsi frontend driver (scsifront) in the domU kernel.
>
>        Also Xen tools in dom0 need to have the support for handling PVSCSI.
>        iirc PVSCSI first appeared on Xen 3.3.0.
>
>        -- Pasi
>
>        _______________________________________________
>        Xen-users mailing list
>        [7]Xen-users@xxxxxxxxxxxxxxxxxxx
>        [8]http://lists.xensource.com/xen-users
>
> References
>
>    Visible links
>    1. http://gitco.com/repo
>    2. mailto:pasik@xxxxxx
>    3. mailto:pasik@xxxxxx
>    4. mailto:natecult@xxxxxx
>    5. mailto:james.harper@xxxxxxxxxxxxxxxx
>    6. mailto:xen-users@xxxxxxxxxxxxxxxxxxx
>    7. file:///mc/compose?to=Xen-users@xxxxxxxxxxxxxxxxxxx
>    8. http://lists.xensource.com/xen-users

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

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

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.