--- Todd Deshane <deshantm@xxxxxxxxx> wrote:
> Try a more manual procedure.
>
> Something like:
>
> sudo mkdir -p /xen/images
> sudo dd if=/dev/zero of=/xen/images/para.partition bs=1M seek=10240
> count=1
> ls -lh /xen/images/
> sudo mkfs.ext3 -F /xen/images/para.partition
> sudo mkdir /mnt/para
$ sudo mkdir -p /xen/images
Password:
$ sudo dd if=/dev/zero of=/xen/images/para.partition bs=1M seek=10240
count=1
1+0 records in
1+0 records out
1048576 bytes (1.0 MB) copied, 0.003378 seconds, 310 MB/s
$ ls -lh /xen/images/
total 1.1M
-rw-r--r-- 1 root root 11G 2008-09-15 09:06 para.partition
$ sudo mkfs.ext3 -F /xen/images/para.partition
mke2fs 1.40-WIP (14-Nov-2006)
warning: 256 blocks unused.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1313280 inodes, 2621440 blocks
131084 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2684354560
80 block groups
32768 blocks per group, 32768 fragments per group
16416 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 33 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
* end *
Up to here there is no problem.
> sudo mount -o loop /xen/images/para.partition /mnt/para
> http://archive.ubuntu.com/ubuntu
If putting above in ONE line it complains;
$ sudo mount -o loop /xen/images/para.partition /mnt/para
http://archive.ubuntu.com/ubuntu
Usage: mount -V : print version
mount -h : print this help
mount : list mounted filesystems
mount -l : idem, including volume labels
So far the informational part. Next the mounting.
The command is `mount [-t fstype] something somewhere'.
Details found in /etc/fstab may be omitted.
mount -a [-t|-O] ... : mount all stuff from /etc/fstab
mount device : mount device at the known place
mount directory : mount known device here
mount -t type dev dir : ordinary mount command
Note that one does not really mount a device, one mounts
a filesystem (of the given type) found on the device.
One can also mount an already visible directory tree elsewhere:
mount --bind olddir newdir
or move a subtree:
mount --move olddir newdir
A device can be given by name, say /dev/hda1 or /dev/cdrom,
or by label, using -L label or by uuid, using -U uuid .
Other options: [-nfFrsvw] [-o options] [-p passwdfd].
For many more details, say man 8 mount .
* end *
If running them in 2 lines;
$ sudo mount -o loop /xen/images/para.partition /mnt/para
No complaint
However;
$ http://archive.ubuntu.com/ubuntu
Can't run on console. Please advise. TIA
B.R.
satimis
> sudo debootstrap hardy /mnt/para
>
> You should then have a file system at /mnt/para.
>
> You can then customize things like hostname,etc.
>
> When you are done customizing, umount it and make a domU config file.
>
> something like:
>
> kernel="/boot/<Xen kernel>"
> ramdisk="/boot/Xen initrd"
> disk=['tap:aio:/xen/images/para.partition,xvda1,w']
> memory=512
> vif=['']
> root="/dev/xvda1"
> extra='xencons=tty'
>
> and then
>
> xm create -c <the config file>
>
>
> On Mon, Sep 15, 2008 at 7:40 AM, Stephen Liu <satimis@xxxxxxxxx>
> wrote:
> >
> > --- Tim Post <echo@xxxxxxxxxxxx> wrote:
> >
> >> On Mon, 2008-09-15 at 15:11 +0800, Stephen Liu wrote:
> >> [ snip ]
> >>
> >> > WARNING
> >> > -------
> >> > Loopback module not loaded and you're using loopback images
> >> > Run the following to load the module:
> >> >
> >> > modprobe loop loop_max=255
> >>
> >> Did you ensure that loop was loaded? If not, its going to be
> >> impossible
> >> to mount a file backed block device and copy over the newly
> strapped
> >> file system, much less boot it.
> >
> >
> > Hi Tim,
> >
> >
> > # ps aux | grep loop
> > root 3822 0.0 0.0 0 0 ? S< 04:21 0:00
> > [loop0]
> > root 3876 0.0 0.0 0 0 ? S< 04:21 0:00
> > [loop1]
> > root 4631 0.0 0.0 2760 696 pts/1 S+ 04:36 0:00
> grep
> > loop
> >
> >
> >
> >> Please do what the warning recommends and try again.
> >
> >
> > I really don't understand what "There is no '/bin/ls' installed in
> the
> > new installation directory" refers. I have been googling around.
> Some
> > threads said it is a bug.
> >
> >
> > B.R.
> > satimis
> >
> > Send instant messages to your online friends
> http://uk.messenger.yahoo.com
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
>
>
>
> --
> Todd Deshane
> http://todddeshane.net
> check out our book: http://runningxen.com
>
Send instant messages to your online friends http://uk.messenger.yahoo.com
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home