Re: HOWTO: xen tools within FreeBSD domU

2011-01-31 Thread Ion-Mihai Tetcu
On Mon, 31 Jan 2011 02:47:25 + (UTC)
Janne Snabb sn...@epipe.com wrote:

 On Sun, 30 Jan 2011, Nick Sayer wrote:
 
  If no one else is working on it, I might take a cut at a
  xen-domU-tools port that does what that page lists.
 
 I say give it a shot. It would be useful. Send me a message if you
 wish me to check/review the port before you send-pr it.
 
 In addition to patching the xenstore device name, I suppose that
 the shared library version numbering should be changed to match
 what it says in the Porters Handbook[1]:
 
  Try to keep shared library version numbers in the libfoo.so.0
  format. Our runtime linker only cares for the major (first) number.
 
 This probably requires patching tools/xenstore/Makefile.
 
 [1]:
 http://www.freebsd.org/doc/en/books/porters-handbook/special.html#PORTING-SHLIBS

Ping/CC me if you have any questions on the ports side.


-- 
IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B


signature.asc
Description: PGP signature


Re: XENHVM amd64 mouse issue

2011-01-31 Thread Janne Snabb
On Sun, 30 Jan 2011, Nick Sayer wrote:

 I have 8.2-RC2 + the netfront patch and a XENHVM kernel. I note
 that I wind up with both ums0 and psm0, but it turns out neither
 appears to work. My VNC console works for text video and keyboard,
 but trying to run a moused for either device doesn't result in the
 text console mouse pointer moving. Mouse clicks do appear to do
 something, however. I don't ever see the psm device show up in the
 vmstat -i output, FWIW.

I do not use a mouse much with Xen myself and have not had issues
with it when I had to, but in the past people have reported a lot
of issues with Xen and broken mouse. The solution for some people
seems to be to use a tablet emulation instead of mouse. Google for
xen tablet. I do not know if FreeBSD has the corresponding driver
and moused support, but it might be worth checking out.

--
Janne Snabb / EPIPE Communications
sn...@epipe.com - http://epipe.com/
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: xn0: Error 2 parsing device/vif/0/mac [PATCH]

2011-01-31 Thread Justin T. Gibbs
On 1/15/2011 3:12 AM, Janne Snabb wrote:
 On Sat, 15 Jan 2011, Janne Snabb wrote:

 It appears that that the netfront driver fails to get the vif mac
 address which leads to panic shortly afterwards.

 The patch at the bottom of this message solves the problem for me.
 After that the current 8.2RC2 system works fine on amd64 with XENHVM
 kernel with Xen 4.0.1 (have not tested other versions).

 If the mac node does not appear in the front-end vif directory
 (does it ever appear there? in my experience no), we fetch a link
 to the backend directory for the same vif and try to get the mac
 node from there.

 I am not sure if this is the proper way to fix this, but it works
 for me.

As with most things Xen, there is no official specification for what
xenstore nodes are where.  If we assume the Linux driver is the
definitive reference, then the current FreeBSD driver behavior is
correct:


http://xenbits.xensource.com/linux-2.6.18-xen.hg?file/5e08fff8dc05/drivers/xen/netfront/netfront.c

See talk_to_backend() and the xen_net_read_mac() function.

There are two environments that setup the xenstore nodes: the Xen cloud
platform, and the more common phython tool stack (aka xend).  I haven't
reviewed XCP, but Xend populates the MAC node in the frontend's tree
unless the ioemu tag is in the VIF configuration line for that interface.
Why this is the case, I have no idea - again the behavior is not documented.
However, it seems reasonable to do what you've done in this patch and to
rely on the backend's copy if the frontend's doesn't exist.  It would also
be good to add support to netfront to maintain the mac node in the frontend
tree and to allow it to be set just like a real device.  I believe netback
will pick up and use the updated MAC value if you bounce the Xenbus
connection after making the change.

--
Justin

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: kern/154428: xn0 network interface and PF - Massive performance drop

2011-01-31 Thread Alex
The following reply was made to PR kern/154428; it has been noted by GNATS.

From: Alex joo...@joovke.com
To: bug-follo...@freebsd.org
Cc:  
Subject: Re: kern/154428: xn0 network interface and PF - Massive performance
 drop
Date: Tue, 01 Feb 2011 14:29:58 +1100

 Confirmed problem still evident in 8.2 RC3 (did a full source csup and 
 buildworld).
 
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org