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@xxxxxxxxx> 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@xxxxxxxxxx
[ 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.
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@xxxxxxxx
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@xxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
Home