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/
Home Products Support Community News


[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 13:02:35 -0700
Delivery-date: Fri, 29 Jul 2011 13:07:40 -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

------- Comment #18 from johneed@xxxxxxxxxxx  2011-07-29 13:02 -------
simply looked through the xend-config.sxp and found the kernel arg setting that
I hoped for.

Domain-0                                     0  7473     4     r-----    129.7

This is what I concluded was problematic.  I have 8 gig of ram, but dom0 has
claimed 7.473 Gb.

Now booting the other kernel, didn't have this setting.
It seemed any attempt to invoke xm mem-set with this kernel resulted and the
system being overtaken by renegade xen processes, well processes anyway, having
to hard rest.

Having no control in bash or anything, seeking and killing processes was ruled

So I nanoed xend-config.sxp; drew on 

Additionally you should use dom0_mem = <-Value> as a parameter in
# xen kernel to reserve the memory for 32-bit paravirtual domains, default
# is "0" (0GB).
(total_available_memory 8GB)

So actually I changed two things 
(total_available_memory 0)
(total_available_memory 8GB)

and added 


initially to /boot/xen-version.gz, which was unhelpful, so added it to 

        module   /boot/kernel-3.0.0-gentoo-amd64 root=/dev/sda3 ro console=tty0
which was where it belongs.

Memory settings is not my forte, but have had to adjust them in the past.
I guessed this
(total_available_memory 0)
was unhelpful.

> new flaw.
Then open a new bug. Don't pollute this bug.

I need not have entered that, should have left it out all together.  It was

Thanks heaps for the prompt assistance.

Is that clear enough?

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list