From: "Dave Humphreys (Bob)" <dave@bob-the-boat.me.uk>
To: Richard Weinberger <richard@sigma-star.at>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Network related UML Crashing
Date: Sat, 12 Jan 2013 18:31:38 +0000 [thread overview]
Message-ID: <1492014.5OhtFxJ3yI@vault01> (raw)
In-Reply-To: <20130112105812.4eedc505@spider.haslach.nod.at>
Re: [uml-devel] "Couldn't grant pty"
Now that I have been able to run the Debiam 32 bit root_fs, I have returned to
the network related crashing.
This is by way of a status update, I will do more to tie down what is required
to demonstrate the problem as simply as possible.
However:
root@DEB1-32:~# rsync --archive --progress 10.0.10.30:/var/imap/ /var/imap/
The authenticity of host '10.0.10.30 (10.0.10.30)' can't be established.
RSA key fingerprint is ce:e4:0d:88:c0:07:01:8d:10:f8:91:52:b5:4b:e1:53.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.0.10.30' (RSA) to the list of known hosts.
receiving incremental file list
./
.bash_history
1970 100% 1.88MB/s 0:00:00 (xfer#1, to-check=1005/1007)
config/
config/annotations.db
144 100% 0.23kB/s 0:00:00 (xfer#2, to-check=1356/1362)
config/deliver.db
0 0% 0.00kB/s 0:00:00 ------------[ cut here ]------------
This is what happened on the Debian 32 bit system with the 3.8.0-rc3 UML
kernel.
The DEB1 UML is now completely dead and locked up, no further messages escaped
after this point.
If I try to kick it with uml_mconsole:
bash-4.1# uml_mconsole DEB1
(DEB1) halt
and nothing more happens.
10.0.10.30 is another 32 bit UML.
DEB1-32 is the Debian UML, with an IP address of 10.0.10.31.
Networking is via mcast.
This behaviour is consistent with what I have found all along.
I have seen the same on a 32 bit UML running on a genuinely 32 bit machine
that is remote to my current location and which I access via the Internet, so
the problem arises using real ethernet (via tun-tap) as well as mcast; and in
a genuine 32 bit environment.
I will try to characterise this more fully, and simplify the method of causing
failure as much as possible.
I still believe that there is a real problem here, not just me doing something
stupid.
Regards,
David
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2013-01-12 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 9:55 [uml-devel] "Couldn't grant pty" Dave (Bob)
2013-01-12 9:58 ` Richard Weinberger
2013-01-12 12:07 ` Dave Humphreys (Bob)
2013-01-12 12:34 ` Antoine Martin
2013-01-12 14:29 ` Richard Weinberger
2013-01-12 15:52 ` Dave Humphreys (Bob)
2013-01-12 16:00 ` Richard Weinberger
2013-01-12 17:05 ` Dave Humphreys (Bob)
2013-01-12 22:06 ` Richard Weinberger
2013-01-14 20:42 ` Dave (Bob)
2013-01-12 18:31 ` Dave Humphreys (Bob) [this message]
2013-01-12 22:11 ` [uml-devel] Network related UML Crashing Richard Weinberger
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=1492014.5OhtFxJ3yI@vault01 \
--to=dave@bob-the-boat.me.uk \
--cc=richard@sigma-star.at \
--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.