Re: FreeBSD now available on all EC2 instance types

2012-01-24 Thread Adrian Chadd
On 17 January 2012 15:34, Colin Percival cperc...@freebsd.org wrote:


 * ec2.patch is just tweaking some configuration files, so that doesn't
 need to
 be merged and isn't really a patch anyway.

 There's also some new rc.d scripts which get installed and more
 configuration
 files; I'm not sure if it makes sense to bring those rc.d scripts into
 FreeBSD
 proper since they're only relevant to the EC2 environment.


.. port?


Adrian
___
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: FreeBSD now available on all EC2 instance types

2012-01-17 Thread Colin Percival
On 01/17/12 13:06, Carsten Heesch wrote:
 There's a folder ec2-bits in the root directory, which contains a bunch of 
 patches. From your blog post I gather that they will not (much longer) be 
 required if one was to build their own kernel?

What gave you that idea?  The patches in that directory are the differences
between the 9.0-RELEASE source tree and the one I used to build the AMI.

 On the same subject: The kernel running in that AMI is apparently i386/XENHVM:
 
 FreeBSD ip-10-30-30-11 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Mon Jan 16 
 18:25:55 UTC 2012 
 root@ip-10-17-42-118:/usr/obj/i386.i386/usr/src/sys/XENHVM  i386
 
 The csup'ed source tree does not contain such configuration. It does for 
 amd64. And there's a XEN configuration for i386. But no XENHVM configuration 
 for i386.

Yep, that's why there's a patch in /root/ec2-bits which adds XENHVM. :-)

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
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: FreeBSD now available on all EC2 instance types

2012-01-17 Thread Carsten Heesch

 What gave you that idea?  The patches in that directory are the differences
 between the 9.0-RELEASE source tree and the one I used to build the AMI.

Oh, must have been wishful thinking then that it might go into FreeBSD and not 
remain a bunch of separate patches... :)


 The csup'ed source tree does not contain such configuration. It does for 
 amd64. And there's a XEN configuration for i386. But no XENHVM configuration 
 for i386.
 
 Yep, that's why there's a patch in /root/ec2-bits which adds XENHVM. :-)

Doh! Makes perfect sense. Less coffee and more actual sleep for me! :)
Thanks for the clarification!


Cheers
C.

___
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: FreeBSD now available on all EC2 instance types

2012-01-17 Thread Colin Percival
On 01/17/12 14:49, Carsten Heesch wrote:
 What gave you that idea?  The patches in that directory are the differences
 between the 9.0-RELEASE source tree and the one I used to build the AMI.
 
 Oh, must have been wishful thinking then that it might go into FreeBSD and 
 not remain a bunch of separate patches... :)

Working on it. :-)

The files rXX.patch are commits I've already made to HEAD but which weren't
in 9.0-RELEASE.  The others I hope to merge into FreeBSD in some form:
* blkfront.patch makes us compatible with the multi-page request ring protocol
used by Amazon's blkback and I'm waiting to confirm that I reverse-engineered
that protocol correctly;
* uart.patch is a workaround for a bug in the version of Xen which Amazon is
using, but it's a really ugly hack so I'm hoping some more talented device
driver hackers can improve it;
* tcp_mbuf_chain_limit.patch limits the length of mbuf chains sent via TCP TSO
due to limits in the linux netback driver, but currently it unconditionally
limits all TCP connections -- I need to talk to network stack people about how
the max-chain-length value should be passed from the network interface up the
stack to the TCP code;
* ec2.patch is just tweaking some configuration files, so that doesn't need to
be merged and isn't really a patch anyway.

There's also some new rc.d scripts which get installed and more configuration
files; I'm not sure if it makes sense to bring those rc.d scripts into FreeBSD
proper since they're only relevant to the EC2 environment.

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
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


FreeBSD now available on all EC2 instance types

2012-01-16 Thread Colin Percival
Details at
http://www.daemonology.net/blog/2012-01-16-FreeBSD-now-on-all-EC2-instance-types.html

-- 
Colin Percival
Security Officer, FreeBSD | freebsd.org | The power to serve
Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid
___
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