On 02/01/2008, Martin Paraskevov <[EMAIL PROTECTED]> wrote:
> The permissions are ok:
>
> [EMAIL PROTECTED]:uml$ ls -l
> total 3169828
> -rw-r--r-- 1 martin martin 1611019264 2008-01-02 08:36 cow1
> -rw-r--r-- 1 martin martin 1610613760 2008-01-02 08:36 FedoraCore5-x86-root_fs
> -rw-r--r-- 1 martin martin 1610613760 2008-01-02 08:28
> FedoraCore5-x86-root_fs-net
> -rwxr--r-- 1 martin martin   21447240 2007-12-19 21:57 linux-2.6.22-rc2
> -rw-r--r-- 1 martin martin 1073742848 2007-12-22 16:45 swap
>
> I have two fs images because I downloaded a fresh unmodified copy from
> the internet:
> http://uml.nagafix.co.uk/FedoraCore5/FedoraCore5-x86-root_fs.bz2
>
> Is it possible that there is something wrong with the fs image online.
Mmh, I don't know, but maybe. I've  never used a pre-built image from
nagafix.co.uk.
I always made filesystems by myself using debootstrap (if you need
details, please let me know).

I tought it was a permission issue becouse of this message:
VFS: Mounted root (ext3 filesystem) readonly.

But I guess the problem is here:
Creating "cow1" as COW file for "FedoraCore5-x86-root_fs"
 ubda: unknown partition table

It is so strange, you are able to start UML using the root_fs and not
if you start using a cow file.

Please, could you post the /etc/fstab of your UML filesystem?

Thank you,

Flavio

> I can't boot it
> specifying cow on the command line.
>
> - Martin
>
> On Jan 2, 2008 1:15 PM, Flavio <[EMAIL PROTECTED]> wrote:
> > On 02/01/2008, Martin Paraskevov <[EMAIL PROTECTED]> wrote:
> > > I tried it:
> > >
> > > [EMAIL PROTECTED]:uml$ ./linux-2.6.22-rc2 mem=128M ubda=cow1  umid=fedora1
> > >
> > > However, I'm still getting the same output and uml doesn't boot.
> >
> > Mmh... very strange issue this one....
> > I usually boot using my cow files doing as it follows:
> >
> > linux ubd0=mycow.cow ubd1=swapfs.debian eth0=tuntap,,,host_ip_address 
> > mem=512M
> >
> > Check also the cow file permission rights: I set my cow file in this way:
> > chmod 644 mycow.cow
> >
> > At the end, you will have something like that:
> >
> > -rw-r--r-- 1 root root 839909376 Nov 10 11:52 rootfs.debian
> > -rw-r--r-- 1 umluser umluser 840126464 Nov 10 11:57 mycow.cow
> >
> > Let me know! ;-)
> >
> > Flavio
> >
> >
> > >
> > > - Martin
> > >
> > > On Jan 2, 2008 12:59 PM, Flavio <[EMAIL PROTECTED]> wrote:
> > > > On 02/01/2008, Martin Paraskevov <[EMAIL PROTECTED]> wrote:
> > > > > This may be a simple question but I can't figure out what's wrong
> > > > > from the error messages and found nothing useful googling.
> > > > >
> > > > > I can start uml with the Fedora guest root fs from
> > > > > http://user-mode-linux.sourceforge.net/  like this:
> > > > >
> > > > > ./linux-2.6.22-rc2 mem=128M ubda=FedoraCore5-x86-root_fs  umid=fedora1
> > > > >
> > > > > However, when I try to specify a cow file the boot is unsuccessful:
> > > > >
> > > > > ./linux-2.6.22-rc2 mem=128M ubda=cow1,FedoraCore5-x86-root_fs  
> > > > > umid=fedora1
> > > > >
> > > > > The file cow1 does not exist but it is created. Here is the output 
> > > > > when I
> > > > > issue the command:
> > > > >
> > > > > [EMAIL PROTECTED]:uml$ ./linux-2.6.22-rc2 mem=128M
> > > > > ubda=cow1,FedoraCore5-x86-root_fs  umid=fedora1
> > > >
> > > > Hello,
> > > > I guess you should not pass the FedoraCore5-x86-root_fs argoument,
> > > > once you created the cow file.
> > > > Simply pass ubda=cow1, and try again.
> > > >
> > > > Flavio
> > > >
> > > >
> > > > > Core dump limits :
> > > > >         soft - 0
> > > > >         hard - NONE
> > > > > Checking that ptrace can change system call numbers...OK
> > > > > Checking syscall emulation patch for ptrace...OK
> > > > > Checking advanced syscall emulation patch for ptrace...OK
> > > > > Checking for tmpfs mount on /dev/shm...OK
> > > > > Checking PROT_EXEC mmap in /dev/shm/...OK
> > > > > Checking for the skas3 patch in the host:
> > > > >   - /proc/mm...not found: No such file or directory
> > > > >   - PTRACE_FAULTINFO...not found
> > > > >   - PTRACE_LDT...not found
> > > > > UML running in SKAS0 mode
> > > > > Linux version 2.6.22-rc2 ([EMAIL PROTECTED]) (gcc version 4.1.1 20070
> > > > > 105 (Red Hat 4.1.1-51)) #342 Wed May 23 11:56:49 EDT 2007
> > > > > Built 1 zonelists.  Total pages: 32512
> > > > > Kernel command line: mem=128M ubda=cow1,FedoraCore5-x86-root_fs 
> > > > > root=98:0
> > > > > PID hash table entries: 512 (order: 9, 2048 bytes)
> > > > > Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> > > > > Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> > > > > Memory: 126832k available
> > > > > Mount-cache hash table entries: 512
> > > > > Checking for host processor cmov support...Yes
> > > > > Checking for host processor xmm support...No
> > > > > Checking that host ptys support output SIGIO...Yes
> > > > > Checking that host ptys support SIGIO on close...No, enabling 
> > > > > workaround
> > > > > Using 2.6 host AIO
> > > > > NET: Registered protocol family 16
> > > > > NET: Registered protocol family 2
> > > > > IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
> > > > > TCP established hash table entries: 4096 (order: 3, 32768 bytes)
> > > > > TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
> > > > > TCP: Hash tables configured (established 4096 bind 4096)
> > > > > TCP reno registered
> > > > > Checking host MADV_REMOVE support...OK
> > > > > mconsole (version 2) initialized on /home/martin/.uml/fedora1/mconsole
> > > > > Host TLS support detected
> > > > > Detected host type: i386
> > > > > VFS: Disk quotas dquot_6.5.1
> > > > > Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> > > > > io scheduler noop registered
> > > > > io scheduler anticipatory registered (default)
> > > > > io scheduler deadline registered
> > > > > io scheduler cfq registered
> > > > > TCP cubic registered
> > > > > NET: Registered protocol family 1
> > > > > NET: Registered protocol family 17
> > > > > Initialized stdio console driver
> > > > > Console initialized on /dev/tty0
> > > > > Initializing software serial port version 1
> > > > > Creating "cow1" as COW file for "FedoraCore5-x86-root_fs"
> > > > >  ubda: unknown partition table
> > > > > kjournald starting.  Commit interval 5 seconds
> > > > > EXT3-fs: mounted filesystem with ordered data mode.
> > > > > VFS: Mounted root (ext3 filesystem) readonly.
> > > > > Kernel panic - not syncing: Operation too long
> > > > >
> > > > > EIP: 0073:[<400b60a3>] CPU: 0 Not tainted ESP: 007b:bf6e9a0c EFLAGS: 
> > > > > 00010297
> > > > >     Not tainted
> > > > > EAX: 00000073 EBX: 401aaff4 ECX: 00000073 EDX: 400b63be
> > > > > ESI: 400b63be EDI: 4007697d EBP: bf6ea000 DS: 007b ES: 007b
> > > > > 087f4c2c:  [<08069628>] show_regs+0xb4/0xb9
> > > > > 087f4c58:  [<08057ca8>] panic_exit+0x25/0x3f
> > > > > 087f4c6c:  [<08078720>] notifier_call_chain+0x21/0x46
> > > > > 087f4c8c:  [<080787bb>] __atomic_notifier_call_chain+0x17/0x19
> > > > > 087f4ca8:  [<080787d2>] atomic_notifier_call_chain+0x15/0x17
> > > > > 087f4cc4:  [<0806daba>] panic+0x52/0xdd
> > > > > 087f4ce4:  [<0805f8b3>] cowify_req+0x38/0xd9
> > > > > 087f4d04:  [<0805fa03>] prepare_request+0xaf/0xba
> > > > > 087f4d30:  [<0805faba>] do_ubd_request+0xac/0x13a
> > > > > 087f4d64:  [<08117f46>] __generic_unplug_device+0x20/0x26
> > > > > 087f4d74:  [<08117f5c>] generic_unplug_device+0x10/0x18
> > > > > 087f4d80:  [<08117f77>] blk_backing_dev_unplug+0x13/0x16
> > > > > 087f4d8c:  [<080bfc4c>] block_sync_page+0x32/0x36
> > > > > 087f4d9c:  [<0808ab9a>] sync_page+0x31/0x3b
> > > > > 087f4da8:  [<08181b74>] __wait_on_bit_lock+0x2f/0x5a
> > > > > 087f4dc4:  [<0808b132>] __lock_page+0x54/0x5d
> > > > > 087f4dfc:  [<0808be77>] filemap_nopage+0x1c8/0x25a
> > > > > 087f4e28:  [<080955a9>] do_no_page+0x6f/0x272
> > > > > 087f4e60:  [<08095954>] __handle_mm_fault+0xa7/0x180
> > > > > 087f4e90:  [<0805767a>] handle_page_fault+0xe2/0x1c2
> > > > > 087f4ec4:  [<080578c0>] segv+0xaa/0x250
> > > > > 087f4f78:  [<08057811>] segv_handler+0x55/0x5a
> > > > > 087f4f98:  [<08066c6b>] userspace+0x120/0x180
> > > > > 087f4fe8:  [<080580b0>] new_thread_handler+0x72/0x7e
> > > > > 087f4ffc:  [<a55a5a5a>] 0xa55a5a5a
> > > > >
> > > > > Segmentation fault
> > > > >
> > > > > Please let me know what's going wrong.
> > > > >
> > > > > - Martin
> > > > >
> > > > > -------------------------------------------------------------------------
> > > > > This SF.net email is sponsored by: Microsoft
> > > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > > _______________________________________________
> > > > > User-mode-linux-user mailing list
> > > > > User-mode-linux-user@lists.sourceforge.net
> > > > > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
> > > > >
> > > >
> > > > -------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Microsoft
> > > > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > > > _______________________________________________
> > > > User-mode-linux-user mailing list
> > > > User-mode-linux-user@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
> > > >
> > >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > User-mode-linux-user mailing list
> > User-mode-linux-user@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
> >
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user

Reply via email to