WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1773] new 3.0.0 kernel cannot connect to network, Device 0 (vif)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 29 Jul 2011 11:02:22 -0700
Delivery-date: Fri, 29 Jul 2011 11:07:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1773-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773





------- Comment #12 from johneed@xxxxxxxxxxx  2011-07-29 11:02 -------
Konrad;

new flaw.

On adjusting as you suggested, I get a completely different oddity.  Never mind
about vif for the moment.
topic is memory management.

gentoo64 bin # /etc/init.d/xencommons  start
Starting xenstored...
Setting domain 0 name...
Starting xenconsoled...
gentoo64 bin # /etc/init.d/xend  start
gentoo64 bin # xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  7473     4     r-----     78.9
fed12                                            612     2                 0.0
fedora9                                          450     2                 0.0
squeeze                                          400     2               157.8

I have removed half of them already.  Something in xen is killing the system.

My total ram is 8 gig.  xen has allocated 7473 to dom0.  However the other
dormant vms overstep that significantly.  I mem-set dom0 to a few selected
sensible settings, and xen kills the system;  cpu usage goes to 100%, some
runaway processes take over, no control in a console, unusable. 
No choice but to hard reset the computer.

Now;

gentoo64 bin # xm create -c Lenny.com.cfg
Using config file "/etc/xen/Lenny.com.cfg".
Started domain lenny.com (id=1)
xenconsole: Could not read tty from store: No such file or directory
gentoo64 bin # xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  7473     4     r-----    129.7
fed12                                            612     2                 0.0
fedora9                                          450     2                 0.0
lenny.com                                    1   128     1     r-----      9.0
squeeze                                          400     2               157.8

Could not read tty from store: No such file or directory is a frustrating error
I encountered back in debian lenny kernel 2.6.26.

Why is the console not working??  
idella@gentoo64 ~/bin $ ls /dev/pts/
0  1  2  3
'Please keep it up;


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>