Hi, at the list I read the that some guys have this setup working: Access though iSCSI in dom0 to the target, starting domU directly form iSCSI-LUN as vbd. Accessing the iSCSI-LUN via dom0 works like a charme but my hole box crashes, when domU starts and tries to mount the filesystems. I''m testing with xen-3.0.2, open-iscsi 1.0-485 and a NetApp-Filer as target. The config looks like: disk = [ ''phy:sdb1,sda1,w'' ] where sdb1 is the iSCSI-LUN in dom0. Are there any clues how to setup this or why it crashes? Thanks, Peter -- Leibniz Computing Centre Peter Simon High Performance Systems http://www.lrz.de Boltzmannstrasse 1 phone: +49 89 35831 8723 D-85748 Garching/Munich fax: +49 89 35831 9700 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, at the list I read the that some guys have this setup working: Access though iSCSI in dom0 to the target, starting domU directly form iSCSI-LUN as vbd. Accessing the iSCSI-LUN via dom0 works like a charme but my hole box crashes, when domU starts and tries to mount the filesystems. I''m testing with xen-3.0.2, open-iscsi 1.0-485 and a NetApp-Filer as target. The config looks like: disk = [ ''phy:sdb1,sda1,w'' ] where sdb1 is the iSCSI-LUN in dom0. Are there any clues how to setup this or why it crashes? Thanks, Peter -- Leibniz Computing Centre Peter Simon High Performance Systems http://www.lrz.de Boltzmannstrasse 1 phone: +49 89 35831 8723 D-85748 Garching/Munich fax: +49 89 35831 9700 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Peter Simon wrote:> at the list I read the that some guys have this setup working: > Access though iSCSI in dom0 to the target, starting domU directly form > iSCSI-LUN as vbd.We got xen-2.0.7 with Debian Sarge 2.6.11 and core-iscsi 1.6.2.5 as initator and iscsi-tools 3.3.> Accessing the iSCSI-LUN via dom0 works like a charme but my hole box > crashes, when domU starts and tries to mount the filesystems. > > I''m testing with xen-3.0.2, open-iscsi 1.0-485 and a NetApp-Filer as > target.Our DomU also crashed while using open-iscsi 1.0-485 with an segmentation fault.> Are there any clues how to setup this or why it crashes?We didn''t have any idea why open-iscsi crashed but core-iscsi works pretty fine. Kind regards Martin -- Forschungsgemeinschaft elektronische Medien e.V. Max-Planck-Ring 6d 98693 Ilmenau http://www.fem.tu-ilmenau.de martin.heller@fem.tu-ilmenau.de 0176 / 211 69 132 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Monday 22 May 2006 14:32, Peter Simon wrote:> Hi, > > at the list I read the that some guys have this setup working: > Access though iSCSI in dom0 to the target, starting domU directly form > iSCSI-LUN as vbd. >I have iSCSI vbd based domUs working in SuSE10.1, xen-3.0.2 and open-iscsi-0.5.545-9 against an IET server.> Accessing the iSCSI-LUN via dom0 works like a charme but my hole box > crashes, when domU starts and tries to mount the filesystems. > > I''m testing with xen-3.0.2, open-iscsi 1.0-485 and a NetApp-Filer as > target. > > The config looks like: > > disk = [ ''phy:sdb1,sda1,w'' ] > > where sdb1 is the iSCSI-LUN in dom0. >Is sdb partitioned? iSCSI attaches each LUN as a single block device that the dom0 needs to partition or to use whole. I would have thought you''d want disk = [ ''phy:sdb,sda1,w'' ] unless you had partitioned the disk /dev/sdb on the dom0. I have the config like this disk = [ ''phy:disk/by_id/scsi-0049003c...,hda1,w'' , ''phy:disk/by-id/scsi-0049005a...,hda2,w'' ] where /dev/disk/by-id/scsi-0049003c... would represent /dev/sdc for the domU root space and /dev/disk/by-id/scsi-0049005a... would represent /dev/sdd for the domU swap space and are individual disks as seen by the dom0. I''m using the /dev/disk/by-id names for each disk as these are unique names as seen by all iSCSI initiators and allow me to migrate live domUs between physical dom0s. Regards Matthew -- Matthew Wild Tel.: +44 (0)1235 445173 M.Wild@rl.ac.uk URL http://www.ukssdc.ac.uk/ UK Solar System Data Centre and World Data Centre - Solar-Terrestrial Physics, Chilton Rutherford Appleton Laboratory, Chilton, Didcot, Oxon, OX11 0QX _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 5/23/06, Matthew Wild <M.Wild@rl.ac.uk> wrote:> > I have iSCSI vbd based domUs working in SuSE10.1, xen-3.0.2 and > open-iscsi-0.5.545-9 against an IET server.What system do you have ? I used the standard suse 10.1 pkgs on a x86_64 system but open-iscsi-0.5.545 caused a crash on the iscsi modules. iSCSI didn''t work until I manually compiled and installed the lastest open-iscsi sources. where /dev/disk/by-id/scsi-0049003c... would represent /dev/sdc for the domU> root space and /dev/disk/by-id/scsi-0049005a... would represent /dev/sdd > for > the domU swap space and are individual disks as seen by the dom0. I''m > using > the /dev/disk/by-id names for each disk as these are unique names as seen > by > all iSCSI initiators and allow me to migrate live domUs between physical > dom0s.To perform live migration, do you have a separate iscsi target server or can one use one of the dom0''s? I want to test live migration with 2 dom0''s, one has a large disk attached to it which I want to use for the iSCSI target. But if I try to connect to the iSCSI shares on both dom0''s at the same time... the dom0 with the large disk hangs. Am I doing something wrong here? My impression is/was that both xen''s mount the same iscsi drive at the same time when transferring (hence the need for GFS/OCFS2 I''ve read about in this list), or does one dom0 safely unmount and the other one mounts? Greetings Tijl Van den Broeck _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday 23 May 2006 13:02, Tijl Van den Broeck wrote:> On 5/23/06, Matthew Wild <M.Wild@rl.ac.uk> wrote: > > I have iSCSI vbd based domUs working in SuSE10.1, xen-3.0.2 and > > open-iscsi-0.5.545-9 against an IET server. > > What system do you have ? I used the standard suse 10.1 pkgs on a x86_64 > system but open-iscsi-0.5.545 caused a crash on the iscsi modules. iSCSI > didn''t work until I manually compiled and installed the lastest open-iscsi > sources. >I have a dual dual-core Opteron box.> where /dev/disk/by-id/scsi-0049003c... would represent /dev/sdc for the > domU > > > root space and /dev/disk/by-id/scsi-0049005a... would represent /dev/sdd > > for > > the domU swap space and are individual disks as seen by the dom0. I''m > > using > > the /dev/disk/by-id names for each disk as these are unique names as seen > > by > > all iSCSI initiators and allow me to migrate live domUs between physical > > dom0s. > > To perform live migration, do you have a separate iscsi target server or > can one use one of the dom0''s? I want to test live migration with 2 dom0''s, > one has a large disk attached to it which I want to use for the iSCSI > target. But if I try to connect to the iSCSI shares on both dom0''s at the > same time... the dom0 with the large disk hangs. >I am using a separate target server - as in a large ~6T storage server using IET to provide a pile of LUNs. I have seen some comments on the open-iscsi list about problems with accessing targets on the same machine in certain circumstances, I''m afraid I can''t remember the details as they didn''t apply in my situation.> Am I doing something wrong here? My impression is/was that both xen''s mount > the same iscsi drive at the same time when transferring (hence the need for > GFS/OCFS2 I''ve read about in this list), or does one dom0 safely unmount > and the other one mounts? >I don''t know about this. I''m only using reiserfs on the connected LUNs and haven''t hit any problems yet. Matthew -- Matthew Wild Tel.: +44 (0)1235 445173 M.Wild@rl.ac.uk URL http://www.ukssdc.ac.uk/ UK Solar System Data Centre and World Data Centre - Solar-Terrestrial Physics, Chilton Rutherford Appleton Laboratory, Chilton, Didcot, Oxon, OX11 0QX _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Heller wrote:> Peter Simon wrote: > > at the list I read the that some guys have this setup working: > > Access though iSCSI in dom0 to the target, starting domU directly form > > iSCSI-LUN as vbd. > > We got xen-2.0.7 with Debian Sarge 2.6.11 and core-iscsi 1.6.2.5 as > initator and iscsi-tools 3.3. >Thanks for this hint. I''ve tested core-iscsi and it works pretty well with xen-3.0.2, SLES9, Kernel 2.6.16 and our NetApp-Box :-) Now I''m asking me, if their is something in core-iscsi to do persistent LUN mapping, like this /dev/disk/by-id/...-thing in open-iscsi? Schöne Grüße aus München ;-) Peter -- Leibniz Computing Centre Peter Simon High Performance Systems http://www.lrz.de Boltzmannstrasse 1 phone: +49 89 35831 8723 D-85748 Garching/Munich fax: +49 89 35831 9700 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
feel curious, have u ever tried live migration with an iscsi vbd? thx. ming On Tue, 2006-05-23 at 13:19 +0100, Matthew Wild wrote:> On Tuesday 23 May 2006 13:02, Tijl Van den Broeck wrote: > > On 5/23/06, Matthew Wild <M.Wild@rl.ac.uk> wrote: > > > I have iSCSI vbd based domUs working in SuSE10.1, xen-3.0.2 and > > > open-iscsi-0.5.545-9 against an IET server. > > > > What system do you have ? I used the standard suse 10.1 pkgs on a x86_64 > > system but open-iscsi-0.5.545 caused a crash on the iscsi modules. iSCSI > > didn''t work until I manually compiled and installed the lastest open-iscsi > > sources. > > > I have a dual dual-core Opteron box. > > > where /dev/disk/by-id/scsi-0049003c... would represent /dev/sdc for the > > domU > > > > > root space and /dev/disk/by-id/scsi-0049005a... would represent /dev/sdd > > > for > > > the domU swap space and are individual disks as seen by the dom0. I''m > > > using > > > the /dev/disk/by-id names for each disk as these are unique names as seen > > > by > > > all iSCSI initiators and allow me to migrate live domUs between physical > > > dom0s. > > > > To perform live migration, do you have a separate iscsi target server or > > can one use one of the dom0''s? I want to test live migration with 2 dom0''s, > > one has a large disk attached to it which I want to use for the iSCSI > > target. But if I try to connect to the iSCSI shares on both dom0''s at the > > same time... the dom0 with the large disk hangs. > > > I am using a separate target server - as in a large ~6T storage server using > IET to provide a pile of LUNs. I have seen some comments on the open-iscsi > list about problems with accessing targets on the same machine in certain > circumstances, I''m afraid I can''t remember the details as they didn''t apply > in my situation. > > > Am I doing something wrong here? My impression is/was that both xen''s mount > > the same iscsi drive at the same time when transferring (hence the need for > > GFS/OCFS2 I''ve read about in this list), or does one dom0 safely unmount > > and the other one mounts? > > > I don''t know about this. I''m only using reiserfs on the connected LUNs and > haven''t hit any problems yet. > > Matthew_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Peter Simon wrote:> I''ve tested core-iscsi and it works pretty well with xen-3.0.2, SLES9, > Kernel 2.6.16 and our NetApp-Box :-) > > Now I''m asking me, if their is something in core-iscsi to do persistent > LUN mapping, like this /dev/disk/by-id/...-thing in open-iscsi?No core-iscsi maps the LUNs by using /dev/sd[LUN-ID in alphabetics] eg LUN0 is /dev/sda LUN1 is /dev/sdb LUN2 doesn''t exist LUN3 is /dev/sdc The mappings are shifted if devices exist. Gruesse aus dem Thueringer Wald Martin Heller -- Forschungsgemeinschaft elektronische Medien e.V. Max-Planck-Ring 6d 98693 Ilmenau http://www.fem.tu-ilmenau.de martin.heller@fem.tu-ilmenau.de _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users