Hi, how can i passthroughs HDD with sda instead of xvda ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Is this on XCP/XenServer? If so, it''s not possible. On 21 July 2010 21:35, Tegger <xen@tegger.de> wrote:> Hi, > > how can i passthroughs HDD with sda instead of xvda ? > > _______________________________________________ > 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
normal xen 4.0.0 installation on debian lenny. with xvda there seems to be problems with mdadm on debian domain. Am 21.07.2010 23:40, schrieb David Markey:> Is this on XCP/XenServer? If so, it''s not possible. > > On 21 July 2010 21:35, Tegger <xen@tegger.de <mailto:xen@tegger.de>> > wrote: > > Hi, > > how can i passthroughs HDD with sda instead of xvda ? > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto: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_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html -- Major Hayden major@mhtx.net On Jul 21, 2010, at 15:35, Tegger wrote:> Hi, > > how can i passthroughs HDD with sda instead of xvda ? > > _______________________________________________ > 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
I cant imagine mdadm would have any problems using xvda, can you give specific examples? On 22 July 2010 21:22, Major Hayden <major+xen@mhtx.net<major%2Bxen@mhtx.net>> wrote:> If you don''t mind using a custom kernel, you can patch it [1] to ensure > that your disks appear as sdX rather than xvdX. > > [1] > http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html > > -- > Major Hayden > major@mhtx.net > > On Jul 21, 2010, at 15:35, Tegger wrote: > > > Hi, > > > > how can i passthroughs HDD with sda instead of xvda ? > > > > _______________________________________________ > > 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 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
SAMBA:~# fdisk -l
Disk /dev/xvda2: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/xvda2 doesn''t contain a valid partition table
Disk /dev/xvda1: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/xvda1 doesn''t contain a valid partition table
Disk /dev/xvdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6492aa07
Device Boot Start End Blocks Id System
/dev/xvdb1 1 30401 244196001 fd Linux raid
autodetect
Disk /dev/xvdc: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd0551df2
Device Boot Start End Blocks Id System
/dev/xvdc1 1 30401 244196001 fd Linux raid
autodetect
Disk /dev/xvdd: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2edf965e
Device Boot Start End Blocks Id System
/dev/xvdd1 1 30401 244196001 fd Linux raid
autodetect
SAMBA:~# mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/xvdb1
/dev/xvdc1 /dev/xvdd1
mdadm: /dev/xvdb1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Wed Jul 21 22:28:54 2010
mdadm: /dev/xvdc1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Wed Jul 21 22:04:04 2010
mdadm: /dev/xvdd1 appears to be part of a raid array:
level=raid5 devices=3 ctime=Wed Jul 21 22:28:54 2010
Continue creating array? yes
mdadm: RUN_ARRAY failed: Invalid argument
mdadm: stopped /dev/md0
SAMBA:~# cat /proc/mdstat
Personalities :
unused devices: <none>
SAMBA:~#
I didn''t find any other error, so i think xvd* ist the invalid
argument.......
Am 23.07.2010 00:38, schrieb David Markey:> I cant imagine mdadm would have any problems using xvda, can you give
> specific examples?
>
> On 22 July 2010 21:22, Major Hayden <major+xen@mhtx.net
> <mailto:major%2Bxen@mhtx.net>> wrote:
>
> If you don''t mind using a custom kernel, you can patch it [1]
to
> ensure that your disks appear as sdX rather than xvdX.
>
> [1]
>
http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html
>
> --
> Major Hayden
> major@mhtx.net <mailto:major@mhtx.net>
>
> On Jul 21, 2010, at 15:35, Tegger wrote:
>
> > Hi,
> >
> > how can i passthroughs HDD with sda instead of xvda ?
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
> > http://lists.xensource.com/xen-users
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
<mailto: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
how should i patch the diff ? i haven''t a/ and b/ directory.... Am 22.07.2010 22:22, schrieb Major Hayden:> If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. > > [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html > > -- > Major Hayden > major@mhtx.net > > On Jul 21, 2010, at 15:35, Tegger wrote: > > >> Hi, >> >> how can i passthroughs HDD with sda instead of xvda ? >> >> _______________________________________________ >> 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
You can download a tarball of the kernel source from kernel.org, or you can check out a copy via git. Here are the basic steps: wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 tar xzf linux-2.6.34.2.tar.bz2 cd linux-2.6.34.2 git apply pvops.diff From there, you can proceed with building the kernel as you normally would. The "pvops.diff" referenced above is the diff attached to the original xen-devel e-mail I sent: http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html There are two parts to the diff: one part allows you to configure the block device names arbitrarily and the other part adjusts the hvc console in the same way. You might want to remove the portion of the diff related to the console as it''s probably not necessary for your system. -- Major Hayden major@mhtx.net On Aug 2, 2010, at 11:51, Tegger wrote:> how should i patch the diff ? > i haven''t a/ and b/ directory.... > > Am 22.07.2010 22:22, schrieb Major Hayden: >> If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. >> >> [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >> >> -- >> Major Hayden >> major@mhtx.net >> >> On Jul 21, 2010, at 15:35, Tegger wrote: >> >> >>> Hi, >>> >>> how can i passthroughs HDD with sda instead of xvda ? >>> >>> _______________________________________________ >>> 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
hmm, i got an error DOM0:~/linux-2.6.34.2# git apply pvops.diff fatal: corrupt patch at line 90 DOM0:~/linux-2.6.34.2# Am 02.08.2010 20:50, schrieb Major Hayden:> You can download a tarball of the kernel source from kernel.org, or you can check out a copy via git. Here are the basic steps: > > wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 > tar xzf linux-2.6.34.2.tar.bz2 > cd linux-2.6.34.2 > git apply pvops.diff > > From there, you can proceed with building the kernel as you normally would. The "pvops.diff" referenced above is the diff attached to the original xen-devel e-mail I sent: > > http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html > > There are two parts to the diff: one part allows you to configure the block device names arbitrarily and the other part adjusts the hvc console in the same way. You might want to remove the portion of the diff related to the console as it''s probably not necessary for your system. > > -- > Major Hayden > major@mhtx.net > > On Aug 2, 2010, at 11:51, Tegger wrote: > > >> how should i patch the diff ? >> i haven''t a/ and b/ directory.... >> >> Am 22.07.2010 22:22, schrieb Major Hayden: >> >>> If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. >>> >>> [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>> >>> -- >>> Major Hayden >>> major@mhtx.net >>> >>> On Jul 21, 2010, at 15:35, Tegger wrote: >>> >>> >>> >>>> Hi, >>>> >>>> how can i passthroughs HDD with sda instead of xvda ? >>>> >>>> _______________________________________________ >>>> 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
I just download the source for 2.6.34.2 and it applied cleanly for me. The diff may have been garbled in the original e-mail. You can download it directly from: http://kernel.slicehost.com/2.6.34.1-rscloud/patches/2.6.34.1-rscloud.diff Let me know if you''re still having trouble with it. -- Major Hayden major@mhtx.net On Aug 2, 2010, at 14:28, Tegger wrote:> hmm, i got an error > > DOM0:~/linux-2.6.34.2# git apply pvops.diff > fatal: corrupt patch at line 90 > DOM0:~/linux-2.6.34.2# > > > > Am 02.08.2010 20:50, schrieb Major Hayden: >> You can download a tarball of the kernel source from kernel.org, or you can check out a copy via git. Here are the basic steps: >> >> wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 >> tar xzf linux-2.6.34.2.tar.bz2 >> cd linux-2.6.34.2 >> git apply pvops.diff >> >> From there, you can proceed with building the kernel as you normally would. The "pvops.diff" referenced above is the diff attached to the original xen-devel e-mail I sent: >> >> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >> >> There are two parts to the diff: one part allows you to configure the block device names arbitrarily and the other part adjusts the hvc console in the same way. You might want to remove the portion of the diff related to the console as it''s probably not necessary for your system. >> >> -- >> Major Hayden >> major@mhtx.net >> >> On Aug 2, 2010, at 11:51, Tegger wrote: >> >> >>> how should i patch the diff ? >>> i haven''t a/ and b/ directory.... >>> >>> Am 22.07.2010 22:22, schrieb Major Hayden: >>> >>>> If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. >>>> >>>> [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>> >>>> -- >>>> Major Hayden >>>> major@mhtx.net >>>> >>>> On Jul 21, 2010, at 15:35, Tegger wrote: >>>> >>>> >>>> >>>>> Hi, >>>>> >>>>> how can i passthroughs HDD with sda instead of xvda ? >>>>> >>>>> _______________________________________________ >>>>> 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
you need to add an new line after line 90, then it works... i have now trouble with the kernel as xen domain, xen-create-image --size=4Gb --swap=1Gb --hostname=SAMBA2 --ip=192.168.123.215 --netmask=255.255.255.0 --gateway=192.168.123.253 --dist=lenny --fs=ext3 --kernel=/boot/vmlinuz-2.6.34.2 --memory=356Mb --passwd --role=udev --dir=/home/user/ but i was unable to build a runnable xen domain i copy manually DOM0:~# mount -o loop /home/userle/domains/SAMBA2/disk.img /mnt/ DOM0:/mnt# cp -r /lib/modules/2.6.34.2/ lib/modules/2.6.34.2/ but: . . . . [ 0.206158] mice: PS/2 mouse device common for all mice [ 0.206331] rtc_cmos: probe of rtc_cmos failed with error -16 [ 0.206698] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com [ 0.206780] cpuidle: using governor ladder [ 0.206785] cpuidle: using governor menu [ 0.207925] usbcore: registered new interface driver hiddev [ 0.207966] usbcore: registered new interface driver usbhid [ 0.207971] usbhid: USB HID core driver modprobe: FATAL: Could not load /lib/modules/2.6.34.2/modules.dep: No such file or directory [ 0.210269] ALSA device list: [ 0.210274] No soundcards found. [ 0.210295] Netfilter messages via NETLINK v0.30. [ 0.210308] nf_conntrack version 0.5.0 (2683 buckets, 10732 max) [ 0.210408] ctnetlink v0.93: registering with nfnetlink. [ 0.210677] ip_tables: (C) 2000-2006 Netfilter Core Team [ 0.210704] TCP cubic registered [ 0.210707] Initializing XFRM netlink socket [ 0.210987] NET: Registered protocol family 10 [ 0.211512] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 0.211546] IPv6 over IPv4 tunneling driver [ 0.211911] NET: Registered protocol family 17 [ 0.212153] registered taskstats version 1 [ 0.217779] blkfront: xvda2: barriers enabled [ 0.218541] blkfront: xvda1: barriers enabled [ 0.312052] XENBUS: Device with no driver: device/console/0 [ 0.312087] Magic number: 1:252:3141 [ 0.312341] Freeing unused kernel memory: 552k freed [ 0.312535] Write protecting the kernel read-only data: 10240k Am 02.08.2010 21:57, schrieb Major Hayden:> I just download the source for 2.6.34.2 and it applied cleanly for me. The diff may have been garbled in the original e-mail. You can download it directly from: > > http://kernel.slicehost.com/2.6.34.1-rscloud/patches/2.6.34.1-rscloud.diff > > Let me know if you''re still having trouble with it. > > -- > Major Hayden > major@mhtx.net > > On Aug 2, 2010, at 14:28, Tegger wrote: > > >> hmm, i got an error >> >> DOM0:~/linux-2.6.34.2# git apply pvops.diff >> fatal: corrupt patch at line 90 >> DOM0:~/linux-2.6.34.2# >> >> >> >> Am 02.08.2010 20:50, schrieb Major Hayden: >> >>> You can download a tarball of the kernel source from kernel.org, or you can check out a copy via git. Here are the basic steps: >>> >>> wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 >>> tar xzf linux-2.6.34.2.tar.bz2 >>> cd linux-2.6.34.2 >>> git apply pvops.diff >>> >>> From there, you can proceed with building the kernel as you normally would. The "pvops.diff" referenced above is the diff attached to the original xen-devel e-mail I sent: >>> >>> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>> >>> There are two parts to the diff: one part allows you to configure the block device names arbitrarily and the other part adjusts the hvc console in the same way. You might want to remove the portion of the diff related to the console as it''s probably not necessary for your system. >>> >>> -- >>> Major Hayden >>> major@mhtx.net >>> >>> On Aug 2, 2010, at 11:51, Tegger wrote: >>> >>> >>> >>>> how should i patch the diff ? >>>> i haven''t a/ and b/ directory.... >>>> >>>> Am 22.07.2010 22:22, schrieb Major Hayden: >>>> >>>> >>>>> If you don''t mind using a custom kernel, you can patch it [1] to ensure that your disks appear as sdX rather than xvdX. >>>>> >>>>> [1] http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>>> >>>>> -- >>>>> Major Hayden >>>>> major@mhtx.net >>>>> >>>>> On Jul 21, 2010, at 15:35, Tegger wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> how can i passthroughs HDD with sda instead of xvda ? >>>>>> >>>>>> _______________________________________________ >>>>>> 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
I have any problems creating a Raid-1 array with xvdb/xvdc. root@host:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/xvdb /dev/xvdc mdadm: array /dev/md0 started. root@host:~# mkfs.ext3 /dev/md0 mke2fs 1.41.11 (14-Mar-2010) Filesystem labelOS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks 65536 inodes, 262128 blocks 13106 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=268435456 8 block groups 32768 blocks per group, 32768 fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376 Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 29 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. root@host:~# mount /dev/md0 /mnt On 2 August 2010 22:15, Tegger <xen@tegger.de> wrote:> you need to add an new line after line 90, then it works... > > i have now trouble with the kernel as xen domain, > > xen-create-image --size=4Gb --swap=1Gb --hostname=SAMBA2 > --ip=192.168.123.215 --netmask=255.255.255.0 --gateway=192.168.123.253 > --dist=lenny --fs=ext3 --kernel=/boot/vmlinuz-2.6.34.2 --memory=356Mb > --passwd --role=udev --dir=/home/user/ > > but i was unable to build a runnable xen domain > > i copy manually > > DOM0:~# mount -o loop /home/userle/domains/SAMBA2/disk.img /mnt/ > DOM0:/mnt# cp -r /lib/modules/2.6.34.2/ lib/modules/2.6.34.2/ > > but: > > . > . > . > . > [ 0.206158] mice: PS/2 mouse device common for all mice > [ 0.206331] rtc_cmos: probe of rtc_cmos failed with error -16 > [ 0.206698] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: > dm-devel@redhat.com > [ 0.206780] cpuidle: using governor ladder > [ 0.206785] cpuidle: using governor menu > [ 0.207925] usbcore: registered new interface driver hiddev > [ 0.207966] usbcore: registered new interface driver usbhid > [ 0.207971] usbhid: USB HID core driver > modprobe: FATAL: Could not load /lib/modules/2.6.34.2/modules.dep: No such > file or directory > > [ 0.210269] ALSA device list: > [ 0.210274] No soundcards found. > [ 0.210295] Netfilter messages via NETLINK v0.30. > [ 0.210308] nf_conntrack version 0.5.0 (2683 buckets, 10732 max) > [ 0.210408] ctnetlink v0.93: registering with nfnetlink. > [ 0.210677] ip_tables: (C) 2000-2006 Netfilter Core Team > [ 0.210704] TCP cubic registered > [ 0.210707] Initializing XFRM netlink socket > [ 0.210987] NET: Registered protocol family 10 > [ 0.211512] ip6_tables: (C) 2000-2006 Netfilter Core Team > [ 0.211546] IPv6 over IPv4 tunneling driver > [ 0.211911] NET: Registered protocol family 17 > [ 0.212153] registered taskstats version 1 > [ 0.217779] blkfront: xvda2: barriers enabled > [ 0.218541] blkfront: xvda1: barriers enabled > [ 0.312052] XENBUS: Device with no driver: device/console/0 > [ 0.312087] Magic number: 1:252:3141 > [ 0.312341] Freeing unused kernel memory: 552k freed > [ 0.312535] Write protecting the kernel read-only data: 10240k > > > > > Am 02.08.2010 21:57, schrieb Major Hayden: > >> I just download the source for 2.6.34.2 and it applied cleanly for me. >> The diff may have been garbled in the original e-mail. You can download it >> directly from: >> >> >> http://kernel.slicehost.com/2.6.34.1-rscloud/patches/2.6.34.1-rscloud.diff >> >> Let me know if you''re still having trouble with it. >> >> >> -- >> Major Hayden >> major@mhtx.net >> >> On Aug 2, 2010, at 14:28, Tegger wrote: >> >> >> >>> hmm, i got an error >>> >>> DOM0:~/linux-2.6.34.2# git apply pvops.diff >>> fatal: corrupt patch at line 90 >>> DOM0:~/linux-2.6.34.2# >>> >>> >>> >>> Am 02.08.2010 20:50, schrieb Major Hayden: >>> >>> >>>> You can download a tarball of the kernel source from kernel.org, or you >>>> can check out a copy via git. Here are the basic steps: >>>> >>>> wget >>>> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 >>>> tar xzf linux-2.6.34.2.tar.bz2 >>>> cd linux-2.6.34.2 >>>> git apply pvops.diff >>>> >>>> From there, you can proceed with building the kernel as you normally >>>> would. The "pvops.diff" referenced above is the diff attached to the >>>> original xen-devel e-mail I sent: >>>> >>>> >>>> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>> >>>> There are two parts to the diff: one part allows you to configure the >>>> block device names arbitrarily and the other part adjusts the hvc console in >>>> the same way. You might want to remove the portion of the diff related to >>>> the console as it''s probably not necessary for your system. >>>> >>>> -- >>>> Major Hayden >>>> major@mhtx.net >>>> >>>> On Aug 2, 2010, at 11:51, Tegger wrote: >>>> >>>> >>>> >>>> >>>>> how should i patch the diff ? >>>>> i haven''t a/ and b/ directory.... >>>>> >>>>> Am 22.07.2010 22:22, schrieb Major Hayden: >>>>> >>>>> >>>>> >>>>>> If you don''t mind using a custom kernel, you can patch it [1] to >>>>>> ensure that your disks appear as sdX rather than xvdX. >>>>>> >>>>>> [1] >>>>>> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>>>> >>>>>> -- >>>>>> Major Hayden >>>>>> major@mhtx.net >>>>>> >>>>>> On Jul 21, 2010, at 15:35, Tegger wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> how can i passthroughs HDD with sda instead of xvda ? >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Dont have any problems* On 3 August 2010 16:48, David Markey <admin@dmarkey.com> wrote:> I have any problems creating a Raid-1 array with xvdb/xvdc. > > root@host:~# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/xvdb > /dev/xvdc > mdadm: array /dev/md0 started. > root@host:~# mkfs.ext3 /dev/md0 > mke2fs 1.41.11 (14-Mar-2010) > Filesystem label> OS type: Linux > Block size=4096 (log=2) > Fragment size=4096 (log=2) > Stride=0 blocks, Stripe width=0 blocks > 65536 inodes, 262128 blocks > 13106 blocks (5.00%) reserved for the super user > First data block=0 > Maximum filesystem blocks=268435456 > 8 block groups > 32768 blocks per group, 32768 fragments per group > 8192 inodes per group > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376 > > Writing inode tables: done > Creating journal (4096 blocks): done > Writing superblocks and filesystem accounting information: done > > This filesystem will be automatically checked every 29 mounts or > 180 days, whichever comes first. Use tune2fs -c or -i to override. > root@host:~# mount /dev/md0 /mnt > > > > On 2 August 2010 22:15, Tegger <xen@tegger.de> wrote: > >> you need to add an new line after line 90, then it works... >> >> i have now trouble with the kernel as xen domain, >> >> xen-create-image --size=4Gb --swap=1Gb --hostname=SAMBA2 >> --ip=192.168.123.215 --netmask=255.255.255.0 --gateway=192.168.123.253 >> --dist=lenny --fs=ext3 --kernel=/boot/vmlinuz-2.6.34.2 --memory=356Mb >> --passwd --role=udev --dir=/home/user/ >> >> but i was unable to build a runnable xen domain >> >> i copy manually >> >> DOM0:~# mount -o loop /home/userle/domains/SAMBA2/disk.img /mnt/ >> DOM0:/mnt# cp -r /lib/modules/2.6.34.2/ lib/modules/2.6.34.2/ >> >> but: >> >> . >> . >> . >> . >> [ 0.206158] mice: PS/2 mouse device common for all mice >> [ 0.206331] rtc_cmos: probe of rtc_cmos failed with error -16 >> [ 0.206698] device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) >> initialised: dm-devel@redhat.com >> [ 0.206780] cpuidle: using governor ladder >> [ 0.206785] cpuidle: using governor menu >> [ 0.207925] usbcore: registered new interface driver hiddev >> [ 0.207966] usbcore: registered new interface driver usbhid >> [ 0.207971] usbhid: USB HID core driver >> modprobe: FATAL: Could not load /lib/modules/2.6.34.2/modules.dep: No >> such file or directory >> >> [ 0.210269] ALSA device list: >> [ 0.210274] No soundcards found. >> [ 0.210295] Netfilter messages via NETLINK v0.30. >> [ 0.210308] nf_conntrack version 0.5.0 (2683 buckets, 10732 max) >> [ 0.210408] ctnetlink v0.93: registering with nfnetlink. >> [ 0.210677] ip_tables: (C) 2000-2006 Netfilter Core Team >> [ 0.210704] TCP cubic registered >> [ 0.210707] Initializing XFRM netlink socket >> [ 0.210987] NET: Registered protocol family 10 >> [ 0.211512] ip6_tables: (C) 2000-2006 Netfilter Core Team >> [ 0.211546] IPv6 over IPv4 tunneling driver >> [ 0.211911] NET: Registered protocol family 17 >> [ 0.212153] registered taskstats version 1 >> [ 0.217779] blkfront: xvda2: barriers enabled >> [ 0.218541] blkfront: xvda1: barriers enabled >> [ 0.312052] XENBUS: Device with no driver: device/console/0 >> [ 0.312087] Magic number: 1:252:3141 >> [ 0.312341] Freeing unused kernel memory: 552k freed >> [ 0.312535] Write protecting the kernel read-only data: 10240k >> >> >> >> >> Am 02.08.2010 21:57, schrieb Major Hayden: >> >>> I just download the source for 2.6.34.2 and it applied cleanly for me. >>> The diff may have been garbled in the original e-mail. You can download it >>> directly from: >>> >>> >>> http://kernel.slicehost.com/2.6.34.1-rscloud/patches/2.6.34.1-rscloud.diff >>> >>> Let me know if you''re still having trouble with it. >>> >>> >>> -- >>> Major Hayden >>> major@mhtx.net >>> >>> On Aug 2, 2010, at 14:28, Tegger wrote: >>> >>> >>> >>>> hmm, i got an error >>>> >>>> DOM0:~/linux-2.6.34.2# git apply pvops.diff >>>> fatal: corrupt patch at line 90 >>>> DOM0:~/linux-2.6.34.2# >>>> >>>> >>>> >>>> Am 02.08.2010 20:50, schrieb Major Hayden: >>>> >>>> >>>>> You can download a tarball of the kernel source from kernel.org, or >>>>> you can check out a copy via git. Here are the basic steps: >>>>> >>>>> wget >>>>> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.34.2.tar.bz2 >>>>> tar xzf linux-2.6.34.2.tar.bz2 >>>>> cd linux-2.6.34.2 >>>>> git apply pvops.diff >>>>> >>>>> From there, you can proceed with building the kernel as you normally >>>>> would. The "pvops.diff" referenced above is the diff attached to the >>>>> original xen-devel e-mail I sent: >>>>> >>>>> >>>>> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>>> >>>>> There are two parts to the diff: one part allows you to configure the >>>>> block device names arbitrarily and the other part adjusts the hvc console in >>>>> the same way. You might want to remove the portion of the diff related to >>>>> the console as it''s probably not necessary for your system. >>>>> >>>>> -- >>>>> Major Hayden >>>>> major@mhtx.net >>>>> >>>>> On Aug 2, 2010, at 11:51, Tegger wrote: >>>>> >>>>> >>>>> >>>>> >>>>>> how should i patch the diff ? >>>>>> i haven''t a/ and b/ directory.... >>>>>> >>>>>> Am 22.07.2010 22:22, schrieb Major Hayden: >>>>>> >>>>>> >>>>>> >>>>>>> If you don''t mind using a custom kernel, you can patch it [1] to >>>>>>> ensure that your disks appear as sdX rather than xvdX. >>>>>>> >>>>>>> [1] >>>>>>> http://lists.xensource.com/archives/html/xen-devel/2010-05/msg00712.html >>>>>>> >>>>>>> -- >>>>>>> Major Hayden >>>>>>> major@mhtx.net >>>>>>> >>>>>>> On Jul 21, 2010, at 15:35, Tegger wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> how can i passthroughs HDD with sda instead of xvda ? >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
i got the error, the raid support wasn''t active in Kernel-config. I don''t know why, i was sure it was activated, but now the raid seems to be running.... Am 01.08.2010 13:51, schrieb Tegger:> > SAMBA:~# mdadm --create /dev/md0 --level=5 --raid-devices=3 /dev/xvdb1 > /dev/xvdc1 /dev/xvdd1 > mdadm: /dev/xvdb1 appears to be part of a raid array: > level=raid5 devices=3 ctime=Wed Jul 21 22:28:54 2010 > mdadm: /dev/xvdc1 appears to be part of a raid array: > level=raid5 devices=3 ctime=Wed Jul 21 22:04:04 2010 > mdadm: /dev/xvdd1 appears to be part of a raid array: > level=raid5 devices=3 ctime=Wed Jul 21 22:28:54 2010 > Continue creating array? yes > mdadm: RUN_ARRAY failed: Invalid argument > mdadm: stopped /dev/md0 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users