10:19 a.m.
Hello, there,
I have been following the howto from
http://fedoraproject.org/wiki/FedoraCore5XenQuickstart on Fedora Core
5 Test 2.
in my grub.conf I added init 3, but each time it reboots my machine.
So i followed the rest of the tutorial in init 5.
I have even replace all sda1 by hda1 when applicable since my fdisk -l is
[root@goorah ~]# fdisk -l
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 132 4870 38066017+ 83 Linux
/dev/hda2 1 131 1052226 82 Linux swap / Solaris
Otherwise I did (i think) everything.
If I do xm create -c fedora-guest1, It will end each time with:
awk: cmd. line:1: fatal: cannot open file `/proc/mounts' for reading
(No such file or directory)
Welcome to Fedora Core
Press 'I' to enter interactive startup.
Setting clock : Sat Feb 11 11:11:31 EST 2006 [ OK ]
cat: /proc/cmdline: No such file or directory
mount: mount point /dev/pts does not exist
Setting hostname localhost: [ OK ]
raidautorun: unable to autocreate /dev/md0
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1
ext2fs_check_if_mount: No such file or directory while determining
whether /dev/hda1 is mounted.
fsck.ext3: No such file or directory while trying to open /dev/hda1
/dev/hda1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Press enter for maintenance
(or type Control-D to continue):
(Repair filesystem) 1 # exit
Unmounting file systems
warning: can't open /etc/mtab: No such file or directory
umount: cannot find list of filesystems to unmount
Automatic reboot in progress.
Restarting system.
do it have to do with the replacement of sda1 with hda1 ?
by the way
[root@goorah ~]# uname -r
2.6.15-1.51_FC5hypervisor
Chitlesh GOORAH
--
http://clunixchit.blogspot.com
10:51 a.m.
Anyone willing to troubleshoot this ? :)
On 2/11/06, Chitlesh GOORAH <chitlesh(a)fedoraproject.org> wrote:
Hello, there,
I have been following the howto from
http://fedoraproject.org/wiki/FedoraCore5XenQuickstart on Fedora Core
5 Test 2.
in my grub.conf I added init 3, but each time it reboots my machine.
So i followed the rest of the tutorial in init 5.
I have even replace all sda1 by hda1 when applicable since my fdisk -l is
[root@goorah ~]# fdisk -l
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 132 4870 38066017+ 83 Linux
/dev/hda2 1 131 1052226 82 Linux swap / Solaris
Otherwise I did (i think) everything.
If I do xm create -c fedora-guest1, It will end each time with:
awk: cmd. line:1: fatal: cannot open file `/proc/mounts' for reading
(No such file or directory)
Welcome to Fedora Core
Press 'I' to enter interactive startup.
Setting clock : Sat Feb 11 11:11:31 EST 2006 [ OK ]
cat: /proc/cmdline: No such file or directory
mount: mount point /dev/pts does not exist
Setting hostname localhost: [ OK ]
raidautorun: unable to autocreate /dev/md0
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1
ext2fs_check_if_mount: No such file or directory while determining
whether /dev/hda1 is mounted.
fsck.ext3: No such file or directory while trying to open /dev/hda1
/dev/hda1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Press enter for maintenance
(or type Control-D to continue):
(Repair filesystem) 1 # exit
Unmounting file systems
warning: can't open /etc/mtab: No such file or directory
umount: cannot find list of filesystems to unmount
Automatic reboot in progress.
Restarting system.
do it have to do with the replacement of sda1 with hda1 ?
by the way
[root@goorah ~]# uname -r
2.6.15-1.51_FC5hypervisor
Chitlesh GOORAH
--
http://clunixchit.blogspot.com
--
http://clunixchit.blogspot.com
11 a.m.
On Mon, Feb 13, 2006 at 05:51:19PM +0100, Chitlesh GOORAH wrote:
Anyone willing to troubleshoot this ? :)
On 2/11/06, Chitlesh GOORAH <chitlesh(a)fedoraproject.org> wrote:
> Hello, there,
> I have been following the howto from
> http://fedoraproject.org/wiki/FedoraCore5XenQuickstart on Fedora Core
> 5 Test 2.
>
> in my grub.conf I added init 3, but each time it reboots my machine.
> So i followed the rest of the tutorial in init 5.
> I have even replace all sda1 by hda1 when applicable since my fdisk -l is
the virtual device seen by the xen kernel will be sda1, not the physical
drive, so replacing this is just wrong.
> do it have to do with the replacement of sda1 with hda1 ?
yes.
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
11:10 a.m.
On Mon, 13 Feb 2006, Daniel Veillard wrote:
the virtual device seen by the xen kernel will be sda1, not the
physical
drive, so replacing this is just wrong.
You can in the /etc/xen/*config files pick either ide or scsi emulation for
xen. Is there a preference for scsi? I've always used ide so far, since in
general that gives less problems and dependancies (eg on initrd features).
Is one faster/better/more reliable/ then the other?
Paul
11:09 a.m.
On Mon, 2006-02-13 at 18:10 +0100, Paul Wouters wrote:
On Mon, 13 Feb 2006, Daniel Veillard wrote:
> the virtual device seen by the xen kernel will be sda1, not the physical
> drive, so replacing this is just wrong.
You can in the /etc/xen/*config files pick either ide or scsi emulation for
xen. Is there a preference for scsi? I've always used ide so far, since in
general that gives less problems and dependancies (eg on initrd features).
Is one faster/better/more reliable/ then the other?
In general, I'd suggest doing neither and instead using the LANANA
approved /dev/xvd devices.
If you pretend with either IDE or SCSI, the xen block driver does
heinous things with stealing block majors and I wouldn't expect this
support to stay as some of the Xen drivers start to move upstream
Jeremy
Jeremy
1:22 a.m.
On 2/13/06, Daniel Veillard <veillard(a)redhat.com> wrote:
drive, so replacing this is just wrong.
> > do it have to do with the replacement of sda1 with hda1 ?
yes.
Ive replaced the hda1 by sda1. But still, It hangs with
ext2fs_check_if_mount: No such file or directory while determining
whether /dev/sda1 is mounted.
[root@goorah ~]# xm create -c fedora-guest1
Using config file "/etc/xen/fedora-guest1".
Started domain fedora-guest1
Linux version 2.6.15-1.51_FC5guest
(bhcompile(a)hs20-bc1-6.build.redhat.com) (gcc version 4.1.0 20060206
(Red Hat 4.1.0-0.23)) #1 SMP Wed Feb 8 16:41:47 EST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000004000000 (usable)
0MB HIGHMEM available.
72MB LOWMEM available.
Using x86 segment limits to approximate NX protection
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line: root=/dev/sda1 ro selinux=0 3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 3064.480 MHz processor.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
vmalloc area: c5000000-fb3fe000, maxmem 34000000
Memory: 61204k/73728k available (1426k kernel code, 4272k reserved,
529k data, 116k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 7668.15 BogoMIPS (lpj=15336312)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Checking 'hlt' instruction... disabled
Brought up 1 CPUs
migration_cost=0
Grant table initialized
NET: Registered protocol family 16
Brought up 1 CPUs
xen_mem: Initialising balloon driver.
audit: initializing netlink socket (disabled)
audit(1139901147.631:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key F783BBA9D0D9CD97
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
NET: Registered protocol family 2
Registering block device major 8
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 4, 81920 bytes)
TCP bind hash table entries: 4096 (order: 4, 81920 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 116k freed
INIT: version 2.86 booting
awk: cmd. line:1: fatal: cannot open file `/proc/mounts' for reading
(No such file or directory)
Welcome to Fedora Core
Press 'I' to enter interactive startup.
Setting clock : Tue Feb 14 02:12:32 EST 2006 [ OK ]
cat: /proc/cmdline: No such file or directory
mount: mount point /dev/pts does not exist
Setting hostname localhost: [ OK ]
raidautorun: unable to autocreate /dev/md0
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
ext2fs_check_if_mount: No such file or directory while determining
whether /dev/sda1 is mounted.
fsck.ext3: No such file or directory while trying to open /dev/sda1
/dev/sda1:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Press enter for maintenance
(or type Control-D to continue):
--
http://clunixchit.blogspot.com
11:08 a.m.
On Mon, 13 Feb 2006, Chitlesh GOORAH wrote:
> Otherwise I did (i think) everything.
> If I do xm create -c fedora-guest1, It will end each time with:
>
> awk: cmd. line:1: fatal: cannot open file `/proc/mounts' for reading
> (No such file or directory)
Does your guest filesystem have an empty /proc directory?
Because:
> cat: /proc/cmdline: No such file or directory
> mount: mount point /dev/pts does not exist
You might also be missing an empty /dev directory.
Try mounting your guest system and create those two directories if they
are missing:
mkdir x
mount -o loop yourguest.img x
(not sure if the new xenguest.py creates a partition or a disk. I am not
sure how to mount partitions within a disk image)
ls x
and if they do not exist: mkdir x/dev x/proc
umount x
And try again.
Paul
1:20 a.m.
On 2/13/06, Paul Wouters <paul(a)xelerance.com> wrote:
Try mounting your guest system and create those two directories if
they
are missing:
mkdir x
mount -o loop yourguest.img x
(not sure if the new xenguest.py creates a partition or a disk. I am not
sure how to mount partitions within a disk image)
ls x
and if they do not exist: mkdir x/dev x/proc
umount x
And try again.
Paul
ls
bin boot dev etc home lib lost+found media misc mnt opt
proc root sbin selinux srv sys tmp usr var
--
http://clunixchit.blogspot.com
11:08 a.m.
On Sat, 2006-02-11 at 17:19 +0100, Chitlesh GOORAH wrote:
Hello, there,
I have been following the howto from
http://fedoraproject.org/wiki/FedoraCore5XenQuickstart on Fedora Core
5 Test 2.
I'd strongly suggest following the instructions at
http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 instead
Jeremy
1:24 a.m.
On 2/13/06, Jeremy Katz <katzj(a)redhat.com> wrote:
I'd strongly suggest following the instructions at
http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 instead
Jeremy
What is the difference? Why do we have 2 howto for FC5T* ?
by the way, under system-config-services, I get
Checking for xendomains:/etc/init.d/xendomains: line 69:
log_failure_msg: command not found
for xendomains.
--
http://clunixchit.blogspot.com
8:29 a.m.
On Tue, 2006-02-14 at 08:24 +0100, Chitlesh GOORAH wrote:
On 2/13/06, Jeremy Katz <katzj(a)redhat.com> wrote:
> I'd strongly suggest following the instructions at
> http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 instead
>
What is the difference? Why do we have 2 howto for FC5T* ?
Because Gawain was updating the FC4 instructions at the same time that I
was writing things up based on the newer capabilities in FC5. It's
probably worth just removing that page at this point.
by the way, under system-config-services, I get
Checking for xendomains:/etc/init.d/xendomains: line 69:
log_failure_msg: command not found
for xendomains.
Please file a bug in bugzilla.
Thanks,
Jeremy
11:30 a.m.
On Tue, 2006-02-14 at 09:29 -0500, Jeremy Katz wrote:
On Tue, 2006-02-14 at 08:24 +0100, Chitlesh GOORAH wrote:
> What is the difference? Why do we have 2 howto for FC5T* ?
Because Gawain was updating the FC4 instructions at the same time that I
was writing things up based on the newer capabilities in FC5. It's
probably worth just removing that page at this point.
Deleted :-)
6665
days inactive
6668
days old
11 comments
5 participants
participants (5)
-
Chitlesh GOORAH -
Daniel Veillard -
Gawain Lynch -
Jeremy Katz -
Paul Wouters