Thank you.......so does this mean that UML must always use tuntap for networking? Can we have any other alternatives than tuntap?
On Wed, Oct 15, 2008 at 5:20 PM, Maninder Singh <[EMAIL PROTECTED]> wrote: > Yes peter, I have come to know abt it.. actually tuntap is one of the > transport types available for packet exchange between the virtual machines > (UML clients) and the host OS. So, while invoking the uml client, we specify > how this client will be networked with the host. under tuntap transport > type, the procedure is to setup virtual nw devices like tap0, tap1 so on.. > in the host and then the network devices in client is linked to one of the > taps in host. > > General format for this is: > > eth<n>=<transport>,<transport args> > A very gud link describing transport types is: > > http://user-mode-linux.sourceforge.net/old/networking.html > > > > > > On Wed, Oct 15, 2008 at 9:48 AM, Peter Teoh <[EMAIL PROTECTED]> wrote: >> >> Check this out for SKAS: >> >> http://www.linux.com/feature/59404 >> >> http://user-mode-linux.sourceforge.net/skas.html >> >> And if u found out something on tuntap, let me know!!! >> >> searching "tuntap" indicated that it is a common term belong to that >> of Solaris, Linux, MacOS, BSD etc..... >> >> http://en.wikipedia.org/wiki/TUN/TAP >> >> Very interesting!!! >> >> On 10月15日, 上午1时34分, "Maninder Singh" <[EMAIL PROTECTED]> wrote: >> > I am trying to run UML. when i give the following command, error occurs >> > as >> > shown below: >> > *# ./linux-2.6.22-rc2 mem=128M eth0=tuntap,tap0* >> > >> > Now I want to know two things: >> > >> > 1) what does eth0=tuntap,tap0 means? I have configured tap0 in host and >> > can >> > understand if only eth0=tap0 would be specified. But why are we writing >> > tuntap,tap0? >> > >> > 2) why is command not giving success? does it demand for skas3 patch >> > to be >> > installed? >> > >> > >> > --------------------------------------------------------------------------------- >> > >> > *# ./linux-2.6.22-rc2 mem=128M eth0=tuntap,tap0* >> > >> > 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 >> > Adding 20402176 bytes to physical memory to account for exec-shield gap >> > Linux version 2.6.22-rc2 ([EMAIL PROTECTED]) (gcc version >> > 4.1.1 >> > 20070105 (Red Hat 4.1.1-51)) #342 Wed May 23 11:56:49 EDT 2007 >> > Built 1 zonelists. Total pages: 37455 >> > Kernel command line: mem=128M eth0=tuntap,tap0 root=98:0 >> > PID hash table entries: 1024 (order: 10, 4096 bytes) >> > Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) >> > Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) >> > Memory: 126548k 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: 2048 (order: 1, 8192 bytes) >> > TCP established hash table entries: 8192 (order: 4, 65536 bytes) >> > TCP bind hash table entries: 8192 (order: 3, 32768 bytes) >> > TCP: Hash tables configured (established 8192 bind 8192) >> > TCP reno registered >> > Checking host MADV_REMOVE support...OK >> > mconsole (version 2) initialized on /root/.uml/mi43lF/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 >> > Couldn't stat "root_fs" : err = 2 >> > Failed to initialize ubd device 0 :Couldn't determine size of device's >> > file >> > Choosing a random ethernet address for device eth0 >> > Netdevice 0 (0a:d4:37:a8:d3:ca) : TUN/TAP backend - >> > VFS: Cannot open root device "98:0" or unknown-block(98,0) >> > Please append a correct "root=" boot option; here are the available >> > partitions: >> > Kernel panic - not syncing: VFS: Unable to mount root fs on >> > unknown-block(98,0) >> > >> > EIP: 0073:[<00110402>] CPU: 0 Not tainted ESP: 007b:00114fc0 EFLAGS: >> > 00200246 >> > Not tainted >> > EAX: 00000000 EBX: 00001837 ECX: 00000013 EDX: 00001837 >> > ESI: 00001833 EDI: 00000011 EBP: 00114fd8 DS: 007b ES: 007b >> > 113a8e64: [<08069628>] show_regs+0xb4/0xb9 >> > 113a8e90: [<08057ca8>] panic_exit+0x25/0x3f >> > 113a8ea4: [<08078720>] notifier_call_chain+0x21/0x46 >> > 113a8ec4: [<080787bb>] __atomic_notifier_call_chain+0x17/0x19 >> > 113a8ee0: [<080787d2>] atomic_notifier_call_chain+0x15/0x17 >> > 113a8efc: [<0806daba>] panic+0x52/0xdd >> > 113a8f1c: [<08049af9>] mount_block_root+0x100/0x116 >> > 113a8f70: [<08049b5b>] mount_root+0x4c/0x54 >> > 113a8f94: [<08049c41>] prepare_namespace+0xde/0x10a >> > 113a8fa4: [<08049827>] kernel_init+0x79/0x85 >> > 113a8fb4: [<08063a39>] run_kernel_thread+0x37/0x42 >> > 113a8fe0: [<08058095>] new_thread_handler+0x57/0x7e >> > 113a8ffc: [<a55a5a5a>] 0xa55a5a5a >> > >> > Segmentation fault > > -- Regards, Peter Teoh
