I''m using xm block attach and xm block detach to dynamically add and remove lvm vbd''s. But after to use xm attach, I don''t see the new device inside the domU. It''s necessary to do something more? Thanks in advance. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
How are you attaching the devices ? For file baked partition are shoud use xm block-attach 20 file:/home/disk /dev/hdb2 w and for physical partition u have to use xm block-attach 20 phy:/dev/sdb4 /dev/hda2 w Are you using the same method ? On 4/3/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> > I''m using xm block attach and xm block detach to dynamically add and > remove lvm vbd''s. But after to use xm attach, I don''t see the new device > inside the domU. It''s necessary to do something more? > > Thanks in advance. > > Regards, > Daniel > -- > Daniel Bareiro - System Administrator > Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 > Powered by Debian GNU/Linux Etch - Linux user #188.598 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGEasSZpa/GxTmHTcRAreZAJ4n+1Mxq3RhE7OOXMfiaDTJaZawIgCeJzJk > F7sXdYCsQ17KbH4Z5o2mtOI> =t/M9 > -----END PGP SIGNATURE----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday, 03 April 2007 13:48:14 +0530, trilok nuwal wrote: Hi trilok.> How are you attaching the devices ? > For file baked partition are shoud use> xm block-attach 20 file:/home/disk /dev/hdb2 w> and for physical partition u have to use > xm block-attach 20 phy:/dev/sdb4 /dev/hda2 w> Are you using the same method ?Yes. In dom0: sirius:~# xm block-list 5 Vdev BE handle state evt-ch ring-ref BE-path 771 0 0 4 6 8 /local/domain/0/backend/vbd/5/771 770 0 0 4 7 9 /local/domain/0/backend/vbd/5/770 769 0 0 4 8 10 /local/domain/0/backend/vbd/5/769 sirius:~# xm block-attach 5 phy:/dev/vm/ws1.space /dev/hda4 w sirius:~# xm block-list 5 Vdev BE handle state evt-ch ring-ref BE-path 771 0 0 4 6 8 /local/domain/0/backend/vbd/5/771 770 0 0 4 7 9 /local/domain/0/backend/vbd/5/770 769 0 0 4 8 10 /local/domain/0/backend/vbd/5/769 772 0 0 4 10 643 /local/domain/0/backend/vbd/5/772 Inside domU: ws1:/dev# mkfs.reiserfs /dev/hda [tab][tab] hda1 hda2 hda3 The domU is Debian GNU/Linux Sarge. It''s necessary to do something more inside domU? Thanks for you answer. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 4/3/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> The domU is Debian GNU/Linux Sarge. It''s necessary to do something more > inside domU?Probably. With real hw, you''d power on after a disk install, right? ** Quoting recent post from Mats ** Subject: [Xen-users] lvm backed domU doesn''t see bigger disk Did you restart the guest or not? You may find that if you "xm block-detach" and "xm block-attach" the device, it will work, but if that''s not working, then you''ll need to restart the guest. Whilst an LVM is resizable, as your DomU isn''t using LVM to manage the volume, it''s not seeing the size-change inside DomU (because it''s thinking that it''s a standard SCSI/IDE disk, which aren''t known to change size once they have been installed in the system). -- Mats ** end quote** jerry -- "Oh joy! Rapture! I''ve got a brain" -Scarecrow _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, The domU is Debian GNU/Linux Sarge. It''s necessary to do something more> inside domU?you need to rescan the vg and lv devices. I have a script doing that: --- vgchange -ay for i in $(lvdisplay | awk ''/LV Name/{print $NF}''); do lvchange --refresh $i; done echo "Done." --- regards Martin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday, 03 April 2007 22:06:18 +0200, Martin Hierling wrote:> Hi,Hi Martin.> > The domU is Debian GNU/Linux Sarge. It''s necessary to do something > > more inside domU?> you need to rescan the vg and lv devices. > I have a script doing that: > --- > vgchange -ay > for i in $(lvdisplay | awk ''/LV Name/{print $NF}''); do lvchange --refresh > $i; done > echo "Done." > ---Thanks for your answer and the script. I try it, but I can''t see the new device yet inside the domU :-( Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Are u using para or HVM domain ? I think, In case of HVM u cant attach a disk partition. U have to attach the full disk. But in case of para it should work fine. What your #cat /proc/partition is showing. On 4/4/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> > On Tuesday, 03 April 2007 13:48:14 +0530, > trilok nuwal wrote: > > Hi trilok. > > > How are you attaching the devices ? > > For file baked partition are shoud use > > > xm block-attach 20 file:/home/disk /dev/hdb2 w > > > and for physical partition u have to use > > xm block-attach 20 phy:/dev/sdb4 /dev/hda2 w > > > Are you using the same method ? > > Yes. In dom0: > > sirius:~# xm block-list 5 > Vdev BE handle state evt-ch ring-ref BE-path > 771 0 0 4 6 8 /local/domain/0/backend/vbd/5/771 > 770 0 0 4 7 9 /local/domain/0/backend/vbd/5/770 > 769 0 0 4 8 10 /local/domain/0/backend/vbd/5/769 > > sirius:~# xm block-attach 5 phy:/dev/vm/ws1.space /dev/hda4 w > sirius:~# xm block-list 5 > Vdev BE handle state evt-ch ring-ref BE-path > 771 0 0 4 6 8 /local/domain/0/backend/vbd/5/771 > 770 0 0 4 7 9 /local/domain/0/backend/vbd/5/770 > 769 0 0 4 8 10 /local/domain/0/backend/vbd/5/769 > 772 0 0 4 10 643 /local/domain/0/backend/vbd/5/772 > > Inside domU: > > ws1:/dev# mkfs.reiserfs /dev/hda [tab][tab] > hda1 hda2 hda3 > > The domU is Debian GNU/Linux Sarge. It''s necessary to do something more > inside domU? > > Thanks for you answer. > > Regards, > Daniel > -- > Daniel Bareiro - System Administrator > Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 > Powered by Debian GNU/Linux Etch - Linux user #188.598 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGEqfpZpa/GxTmHTcRAiSVAJ9dkhuAgDas56R2vJ4ZpVdut4miXgCggYkL > cR6TtR+63D4bq6RjP9X5roo> =PbaW > -----END PGP SIGNATURE----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Liang Yang
2007-Apr-04 16:07 UTC
[Xen-users] Section mismatch warning when building Xen-unstable.
Hi, When I try to do make install to build Xen with the latest xen-unstable on a fresh RHEL 4U4, I got the following warnings (make world is fine). Does anyone know how to solve these problems? BTW, I enabled the OProfile setting for linux-2.6.18-xen. I''m not sure if this is related to the following warnings: WRNING: drivers/atm/fore_200e.o - Section mismatch: reference to .init.text: from .text between ''fore200e_i nitialize'' (at offset 0x29df) and ''fore200e_monitor_putc'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0x50c) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0x8b8) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0x8bf) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0x901) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0xa3c) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0xa43) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0xa59) and ''he_stop'' WARNING: drivers/atm/he.o - Section mismatch: reference to .init.text: from text between ''he_start'' (at off set 0xaa2) and ''he_stop'' WARNING: drivers/atm/horizon.o - Section mismatch: reference to .init.text: from .text between ''hrz_probe'' ( at offset 0x19dd) and ''hrz_remove_one'' WARNING: drivers/atm/lanai.o - Section mismatch: reference to .init.text: from .text between ''sram_test_pass '' (at offset 0x207) and ''sram_test_and_clear'' WARNING: drivers/atm/zatm.o - Section mismatch: reference to .init.text: from .text after ''zatm_init_one'' (a t offset 0x2854) WARNING: drivers/atm/zatm.o - Section mismatch: reference to .init.text: from .text after ''zatm_init_one'' (a t offset 0x2861) WARNING: drivers/net/rrunner.o - Section mismatch: reference to init.text:rr_init from .text between ''rr_in it_one'' (at offset 0x22b) and ''rr_remove_one'' WARNING: drivers/net/sis900.o - Section mismatch: reference to init.text:sis900_mii_probe from .text betwee n ''sis900_probe'' (at offset 0x539) and ''sis900_default_phy'' WARNING: drivers/net/sunhme.o - Section mismatch: reference to .init.text: from .text between ''happy_meal_pc i_probe'' (at offset 0x3816) and ''happy_meal_pci_remove'' WARNING: drivers/net/tokenring/3c359.o - Section mismatch: reference to init.text:xl_init from .text betwee n ''xl_probe'' (at offset 0x228) and ''xl_hw_reset'' Thanks, Liang _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2007-Apr-04 16:22 UTC
RE: [Xen-users] Section mismatch warning when building Xen-unstable.
You should sent things like this to Xen-devel, not Xen-users. -- Mats> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang > Sent: 04 April 2007 17:07 > To: Xen-users@lists.xensource.com > Subject: [Xen-users] Section mismatch warning when building > Xen-unstable. > > Hi, > > When I try to do make install to build Xen with the latest > xen-unstable on a > fresh RHEL 4U4, I got the following warnings (make world is > fine). Does > anyone know how to solve these problems? BTW, I enabled the > OProfile setting > for linux-2.6.18-xen. I''m not sure if this is related to the > following > warnings: > > WRNING: drivers/atm/fore_200e.o - Section mismatch: reference > to .init.text: > from .text between ''fore200e_i nitialize'' (at offset 0x29df) and > ''fore200e_monitor_putc'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0x50c) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0x8b8) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0x8bf) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0x901) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0xa3c) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0xa43) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0xa59) and ''he_stop'' > WARNING: drivers/atm/he.o - Section mismatch: reference to > .init.text: from > text between ''he_start'' (at off set 0xaa2) and ''he_stop'' > WARNING: drivers/atm/horizon.o - Section mismatch: reference > to .init.text: > from .text between ''hrz_probe'' ( at offset 0x19dd) and > ''hrz_remove_one'' > WARNING: drivers/atm/lanai.o - Section mismatch: reference to > .init.text: > from .text between ''sram_test_pass '' (at offset 0x207) and > ''sram_test_and_clear'' > WARNING: drivers/atm/zatm.o - Section mismatch: reference to > .init.text: > from .text after ''zatm_init_one'' (a t offset 0x2854) > WARNING: drivers/atm/zatm.o - Section mismatch: reference to > .init.text: > from .text after ''zatm_init_one'' (a t offset 0x2861) > WARNING: drivers/net/rrunner.o - Section mismatch: reference to > init.text:rr_init from .text between ''rr_in it_one'' (at > offset 0x22b) and > ''rr_remove_one'' > WARNING: drivers/net/sis900.o - Section mismatch: reference to > init.text:sis900_mii_probe from .text betwee n ''sis900_probe'' > (at offset > 0x539) and ''sis900_default_phy'' > WARNING: drivers/net/sunhme.o - Section mismatch: reference > to .init.text: > from .text between ''happy_meal_pc i_probe'' (at offset 0x3816) and > ''happy_meal_pci_remove'' > WARNING: drivers/net/tokenring/3c359.o - Section mismatch: > reference to > init.text:xl_init from .text betwee n ''xl_probe'' (at offset > 0x228) and > ''xl_hw_reset'' > > Thanks, > > Liang > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wednesday, 04 April 2007 10:43:10 +0530, trilok nuwal wrote:> Are u using para or HVM domain ?I''m using para.> I think, In case of HVM u cant attach a disk partition. U have to > attach the full disk.> But in case of para it should work fine. What your #cat > /proc/partition is showing.In dom0: sirius:~# lvs|grep ws1 ws1.mirror vm -wi-ao 30,00G ws1.raiz vm -wi-ao 5,00G ws1.space vm -wi-ao 5,00G ws1.swap vm -wi-ao 256,00M sirius:/etc/xen# cat ws1|grep phy disk = [ ''phy:vm/ws1.mirror,hda3,w'', ''phy:vm/ws1.raiz,hda2,w'',''phy:vm/ws1.swap,hda1,w'' ] In domU: ws1:~# cat /proc/partitions major minor #blocks name 3 3 31457280 hda3 3 2 5242880 hda2 3 1 262144 hda1 3 4 5242880 hda4 It appears to recognize the new lvm-backed vbd, but I can''t access to it: ------------------------------------------------------------------------ ws1:~# mkfs.reiserfs /dev/hda4 mkfs.reiserfs 3.6.19 (2003 www.namesys.com) A pair of credits: Jeremy Fitzhardinge wrote the teahash.c code for V3. Colin Plumb also contributed to that. Yury Umanets (aka Umka) developed libreiser4, userspace plugins, and all userspace tools (reiser4progs) except of fsck. Stat of the device ''/dev/hda4'' failed. ------------------------------------------------------------------------ ws1:~# fdisk /dev/hda [TAB][TAB] hda1 hda2 hda3 ws1:~# fdisk /dev/hda Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
so that partition is exported to domU. then u can create FS and mount this. What is the problem ? On 4/5/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> > On Wednesday, 04 April 2007 10:43:10 +0530, > trilok nuwal wrote: > > > Are u using para or HVM domain ? > > I''m using para. > > > I think, In case of HVM u cant attach a disk partition. U have to > > attach the full disk. > > > But in case of para it should work fine. What your #cat > > /proc/partition is showing. > > In dom0: > > sirius:~# lvs|grep ws1 > ws1.mirror vm -wi-ao 30,00G > ws1.raiz vm -wi-ao 5,00G > ws1.space vm -wi-ao 5,00G > ws1.swap vm -wi-ao 256,00M > > sirius:/etc/xen# cat ws1|grep phy > disk = [ ''phy:vm/ws1.mirror,hda3,w'', > ''phy:vm/ws1.raiz,hda2,w'',''phy:vm/ws1.swap,hda1,w'' ] > > In domU: > > ws1:~# cat /proc/partitions > major minor #blocks name > > 3 3 31457280 hda3 > 3 2 5242880 hda2 > 3 1 262144 hda1 > 3 4 5242880 hda4 > > It appears to recognize the new lvm-backed vbd, but I can''t access to > it: > > ------------------------------------------------------------------------ > ws1:~# mkfs.reiserfs /dev/hda4 > mkfs.reiserfs 3.6.19 (2003 www.namesys.com) > > A pair of credits: > Jeremy Fitzhardinge wrote the teahash.c code for V3. Colin Plumb > also contributed to that. > > Yury Umanets (aka Umka) developed libreiser4, userspace plugins, > and all userspace tools (reiser4progs) except of fsck. > > > Stat of the device ''/dev/hda4'' failed. > ------------------------------------------------------------------------ > ws1:~# fdisk /dev/hda [TAB][TAB] > hda1 hda2 hda3 > ws1:~# fdisk /dev/hda > > > Regards, > Daniel > -- > Daniel Bareiro - System Administrator > Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 > Powered by Debian GNU/Linux Etch - Linux user #188.598 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGE+7PZpa/GxTmHTcRAq//AJoDtE/0EvR3WpKNeLW9Fo7wAm4fhQCeOd2N > 30LreIPAZda1oy2TM0MTrnU> =lt/j > -----END PGP SIGNATURE----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday, 05 April 2007 10:15:44 +0530, trilok nuwal wrote:> so that partition is exported to domU. then u can create FS and mount > this. What is the problem ?How I said, hda4 is in the list of /proc/partitions but mkfs.reiserfs reports a fail at the moment of format it, and fdisk don''t show hda4. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Could you able to make fs on this LV BD in dom0. If then you can try to make the file system on this dom0 then attact to domU and mount in domU. If u are unsuccessfull then could be something wrong in LV itself. On 4/5/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> > On Thursday, 05 April 2007 10:15:44 +0530, > trilok nuwal wrote: > > > so that partition is exported to domU. then u can create FS and mount > > this. What is the problem ? > > How I said, hda4 is in the list of /proc/partitions but mkfs.reiserfs > reports a fail at the moment of format it, and fdisk don''t show hda4. > > Regards, > Daniel > -- > Daniel Bareiro - System Administrator > Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 > Powered by Debian GNU/Linux Etch - Linux user #188.598 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGFPrcZpa/GxTmHTcRArWLAKCIY+11bwck9d5jIcWDtlVy9CYzpwCbB8P8 > O+BaDJEb2xWD8RM9wdaqBuE> =KRxF > -----END PGP SIGNATURE----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Bareiro wrote:> On Thursday, 05 April 2007 10:15:44 +0530, > trilok nuwal wrote: > > >> so that partition is exported to domU. then u can create FS and mount >> this. What is the problem ? >> > > How I said, hda4 is in the list of /proc/partitions but mkfs.reiserfs > reports a fail at the moment of format it, and fdisk don''t show hda4. > > Regards, > Daniel >Do you have any reason to use ReiserFS? With ext3 showing so much improvement over ext2, and with Reiser himself facing murder charges for his missing wife, I suspect it''s development will be much slowed. Given my experience with ReiserFS, I''m not surprised he managed to lose something so important and claim complete innocence despite compelling evidence that he or his filesystem had it last. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thursday, 05 April 2007 19:17:21 +0530, trilok nuwal wrote:> Could you able to make fs on this LV BD in dom0. If then you can try > to make the file system on this dom0 then attact to domU and mount in > domU. If u are unsuccessfull then could be something wrong in LV > itself.I''ve successfully formatted the LVM backed-vbd on dom0. Then I attach it to domU. Both cat /proc/partitions and hwinfo reports the new exported LV backed-vbd, but I can''t operate on it: ws1:/proc# cat /proc/partitions major minor #blocks name 3 3 31457280 hda3 3 2 5242880 hda2 3 1 262144 hda1 3 4 5242880 hda4 ws1:/proc# mount /dev/hda4 /mnt/ mount: you must specify the filesystem type ws1:/proc# mount -t reiserfs /dev/hda4 /mnt/ mount: special device /dev/hda4 does not exist Thanks for your answer. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Bareiro
2007-Apr-06 01:39 UTC
Re: [Xen-users] [Solved] Using xm block-{attach,detach}
On Thursday, 05 April 2007 14:35:35 -0300, Daniel Bareiro wrote:> I''ve successfully formatted the LVM backed-vbd on dom0. Then I attach > it to domU. Both cat /proc/partitions and hwinfo reports the new > exported LV backed-vbd, but I can''t operate on it:> ws1:/proc# cat /proc/partitions > major minor #blocks name> 3 3 31457280 hda3 > 3 2 5242880 hda2 > 3 1 262144 hda1 > 3 4 5242880 hda4> ws1:/proc# mount /dev/hda4 /mnt/ > mount: you must specify the filesystem type > ws1:/proc# mount -t reiserfs /dev/hda4 /mnt/ > mount: special device /dev/hda4 does not existI made the block special file and then I can access to the exported lvm-backed vbd inside the domU: ws1:~# mknod -m 660 /dev/hda4 b 3 4 ws1:~# mount /dev/hda4 /mnt/ ws1:~# df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/hda2 5,0G 358M 4,7G 7% / /dev/hda3 30G 22G 8,8G 71% /home/mirror /dev/hda4 5,0G 33M 5,0G 1% /mnt Thanks for all your replys. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
trilok nuwal
2007-Apr-06 05:08 UTC
Re: [Xen-users] [Solved] Using xm block-{attach,detach}
Ok, Actually i am using the RHEL distribution. Where i dont need to create the node explictly as yours case it is requird. Thanks, Trilok On 4/6/07, Daniel Bareiro <daniel-listas@gmx.net> wrote:> > On Thursday, 05 April 2007 14:35:35 -0300, > Daniel Bareiro wrote: > > > I''ve successfully formatted the LVM backed-vbd on dom0. Then I attach > > it to domU. Both cat /proc/partitions and hwinfo reports the new > > exported LV backed-vbd, but I can''t operate on it: > > > ws1:/proc# cat /proc/partitions > > major minor #blocks name > > > 3 3 31457280 hda3 > > 3 2 5242880 hda2 > > 3 1 262144 hda1 > > 3 4 5242880 hda4 > > > ws1:/proc# mount /dev/hda4 /mnt/ > > mount: you must specify the filesystem type > > ws1:/proc# mount -t reiserfs /dev/hda4 /mnt/ > > mount: special device /dev/hda4 does not exist > > I made the block special file and then I can access to the exported > lvm-backed vbd inside the domU: > > ws1:~# mknod -m 660 /dev/hda4 b 3 4 > ws1:~# mount /dev/hda4 /mnt/ > ws1:~# df -h > S.ficheros Tamaño Usado Disp Uso% Montado en > /dev/hda2 5,0G 358M 4,7G 7% / > /dev/hda3 30G 22G 8,8G 71% /home/mirror > /dev/hda4 5,0G 33M 5,0G 1% /mnt > > Thanks for all your replys. > > Regards, > Daniel > -- > Daniel Bareiro - System Administrator > Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 > Powered by Debian GNU/Linux Etch - Linux user #188.598 > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGFaS3Zpa/GxTmHTcRAscjAKCDAUu3vp/+LLWq8lsrRBsprFDFRwCdFqnm > MBdaLXMhD0hm3mKzoP3z2Cc> =i1QD > -----END PGP SIGNATURE----- > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Martin Hierling
2007-Apr-06 13:32 UTC
Re: [Xen-users] [Solved] Using xm block-{attach,detach}
Hi,>> I made the block special file and then I can access to the exported >>lvm-backed vbd inside the domU:perhaps an udevtrigger would do the job? regards Martin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Bareiro
2007-Apr-07 15:22 UTC
Re: [Xen-users] [Solved] Using xm block-{attach,detach}
On Friday, 06 April 2007 15:32:45 +0200, Martin Hierling wrote:> Hi,Hi Martin.> >> I made the block special file and then I can access to the exported > >> lvm-backed vbd inside the domU:> perhaps an udevtrigger would do the job?Yes. I''ve created /dev/pts and then I''ve installed udev package. It made the work. But I''m surprised some directories and special devices doesn''t exist. This behaviour seems to be normal since xen-tools use "MAKEDEV generic" and "MAKEDEV sd" without to install udev package. Thanks for your reply. Regards, Daniel -- Daniel Bareiro - System Administrator Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Etch - Linux user #188.598 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users