From: "David Fernández" <david@dit.upm.es>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] ubd option parsing problem when using cow filesystems in kernel 3.4
Date: Tue, 19 Jun 2012 10:55:18 +0200 [thread overview]
Message-ID: <4FE03E76.7090400@dit.upm.es> (raw)
Hi,
It seems that the parsing of ubd option is broken in kernels 3.4.X when
using COW filesystems. Let me show the tests I've done so far.
When starting a virtual machine using a cow fs without pathname:
linux-3.4.1 udba=cow_fs,debian.img
it works, but the cow file created is named 'cow_fs,debian.img' instead
of 'cow_fs'.
However, when specifying full pathnames for the cow and root filesystem:
linux-3.4.1 udba=/pathto/cow_fs,/pathto/debian.img
you get a kernel panic and the following errors:
Open of COW file '/root/uml/test/cow_fs,/root/uml/test/debian.img'
failed, errno = 2
Failed to open '/root/uml/test/cow_fs,/root/uml/test/debian.img',
errno = 2
ubda: Can't open "/root/uml/test/cow_fs,/root/uml/test/debian.img":
errno = 2
Open of COW file '/root/uml/test/cow_fs,/root/uml/test/debian.img'
failed, errno = 2
Failed to open '/root/uml/test/cow_fs,/root/uml/test/debian.img',
errno = 2
ubda: Can't open "/root/uml/test/cow_fs,/root/uml/test/debian.img":
errno = 2
VFS: Cannot open root device "98:0" or unknown-block(98,0): error -2
Please append a correct "root=" boot option; here are the available
partitions:
6200 2097152 ubda driver: uml-blkdev
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(98,0)
The same tests work perfectly with kernel 3.3.8 and older versions. To
test I've used a debian 6.0 rootfs.
Any idea of the cause of the problem? A simple 'diff' between 3.3 and
3.4 versions shows the option parsing code has changed significantly.
Best regards,
David Fernández
Virtual Networks over linuX (VNX)
http://vnx.dit.upm.es
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2012-06-19 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 8:55 David Fernández [this message]
2012-06-19 9:03 ` [uml-devel] ubd option parsing problem when using cow filesystems in kernel 3.4 richard -rw- weinberger
2012-06-19 22:33 ` David Fernández
2012-06-20 7:17 ` richard -rw- weinberger
2012-06-20 17:02 ` David Fernández
2012-06-20 17:13 ` richard -rw- weinberger
2012-06-21 14:29 ` David Fernández
2012-06-21 14:42 ` richard -rw- weinberger
2012-06-21 14:49 ` Geert Uytterhoeven
2012-06-25 0:30 ` David Fernández
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE03E76.7090400@dit.upm.es \
--to=david@dit.upm.es \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.