[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[long] UML hangs



Greetings,

I'm experimenting with UML on Debian 5.0. In the virtual machine I run
debian 5.0 too.
I managed to get it to work. Well, sort of, because after 1-2 minutes
after I log on with
ssh, the whole virtual machine hangs. I need help. I have appended
some details below.

I start the whole thing with:

# screen -d -m -S prizm su uml -c "linux root=/dev/ubda
ubd0=/images/prizm.rootfs ubd1=/images/prizm.swapfs mem=128M con0=pty
eth0=tuntap,,,192.168.1.6 umid=prizm"


# ls -la /images
...
-rw-r--r--  1 uml  uml-net 17338204160 2009-03-21 16:04 prizm.rootfs
-rw-r--r--  1 uml  uml-net  4294967296 2009-03-19 19:22 prizm.swapfs
...

(prizm.rootfs is "sparse", filesystem is ext3fs)




#cat /mnt/uml/var/log/dmesg              (after the crash, the rootfs
image is temporary mounted on /mnt/uml)
Linux version 2.6.26 (2.6.26) (root@tadamune) (gcc version 4.3.1
(Debian 4.3.1-8) ) #2 Sat Aug 9 19:24:51 JST 2008
On node 0 totalpages: 35782
 Normal zone: 280 pages used for memmap
 Normal zone: 0 pages reserved
 Normal zone: 35502 pages, LIFO batch:7
 Movable zone: 0 pages used for memmap
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 35502
Kernel command line: root=/dev/ubda ubd0=/images/prizm.rootfs
ubd1=/images/prizm.swapfs mem=128M con=/dev/tty8
eth0=tuntap,,,192.168.1.6
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: 124884k available
SLUB: Genslabs=12, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 3814.19 BogoMIPS (lpj=19070976)
Mount-cache hash table entries: 512
Checking for host processor cmov support...Yes
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
net_namespace: 652 bytes
Using 2.6 host AIO
NET: Registered protocol family 16
NET: Registered protocol family 2
Switched to high resolution mode on CPU 0
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
NET: Registered protocol family 1
mconsole (version 2) initialized on /home/uml/.uml/prizm/mconsole
Checking host MADV_REMOVE support...OK
Mapper v0.1
mmapper_init - find_iomem failed
UML Watchdog Timer
Host TLS support detected
Detected host type: i386 (GDT indexes 6 to 9)
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFS: nTxBlock = 976, nTxLock = 7814
SGI XFS with ACLs, security attributes, realtime, large block numbers,
no debug enabled
SGI XFS Quota Management subsystem
msgmni has been set to 244
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
SoftDog: cannot register miscdev on minor=130 (err=-16)
TCP cubic registered
NET: Registered protocol family 17
Initialized stdio console driver
parse_chan_pair failed for device 0 : No match for configured backends
parse_chan_pair failed for device 1 : No match for configured backends
parse_chan_pair failed for device 2 : No match for configured backends
parse_chan_pair failed for device 3 : No match for configured backends
parse_chan_pair failed for device 4 : No match for configured backends
parse_chan_pair failed for device 5 : No match for configured backends
parse_chan_pair failed for device 6 : No match for configured backends
parse_chan_pair failed for device 7 : No match for configured backends
parse_chan_pair failed for device 8 : No match for configured backends
parse_chan_pair failed for device 9 : No match for configured backends
parse_chan_pair failed for device 10 : No match for configured backends
parse_chan_pair failed for device 11 : No match for configured backends
parse_chan_pair failed for device 12 : No match for configured backends
parse_chan_pair failed for device 13 : No match for configured backends
parse_chan_pair failed for device 14 : No match for configured backends
parse_chan_pair failed for device 15 : No match for configured backends
Console initialized on /dev/tty0
console [tty0] enabled
Initializing software serial port version 1
console [mc-1] enabled
 ubda: unknown partition table
 ubdb: unknown partition table
Choosing a random ethernet address for device eth0
Netdevice 0 (7e:21:a3:59:c5:9d) : <6>TUN/TAP backend - IP = 192.168.1.6
registered taskstats version 1
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Failed to open console 0, err = -19
Warning: unable to open an initial console.
Failed to open console 0, err = -19
Failed to open console 0, err = -19
Failed to open console 0, err = -19
Unable to find swap-space signature
EXT3 FS on ubda, internal journal
Unable to find swap-space signature
* modprobe tun
* ifconfig tap0 192.168.1.6 netmask 255.255.255.255 up
* bash -c echo 1 > /proc/sys/net/ipv4/ip_forward
* route add -host 192.168.1.7 dev tap0
* bash -c echo 1 > /proc/sys/net/ipv4/conf/tap0/proxy_arp
* arp -Ds 192.168.1.7 eth1 pub


#tail -10 /mnt/uml/var/log/syslog
Mar 21 14:01:22 prizm kernel: EXT3 FS on ubda, internal journal
Mar 21 14:01:22 prizm kernel: * modprobe tun
Mar 21 14:01:22 prizm kernel: * ifconfig tap0 192.168.1.6 netmask
255.255.255.255 up
Mar 21 14:01:22 prizm kernel: * bash -c echo 1 > /proc/sys/net/ipv4/ip_forward
Mar 21 14:01:22 prizm kernel: * route add -host 192.168.1.7 dev tap0
Mar 21 14:01:22 prizm kernel: * bash -c echo 1 >
/proc/sys/net/ipv4/conf/tap0/proxy_arp
Mar 21 14:01:22 prizm kernel: * arp -Ds 192.168.1.7 eth1 pub
Mar 21 14:01:22 prizm rsyslogd: [origin software="rsyslogd"
swVersion="3.18.6" x-pid="1683" x-info="http://www.rsyslog.com";]
restart
Mar 21 14:01:22 prizm kernel: NET: Registered protocol family 10
Mar 21 14:01:22 prizm kernel: lo: Disabled Privacy Extensions


Reply to: