[05:55] <hashken> Hi, I am planning to create a custom Amazon image from Ubuntu Minimal CD.
[05:56] <hashken> After going through a few forums, I am under the impression that the kernel needs to have certain modules compiled, so that it runs in Amzon EC2.
[05:57] <hashken> Is the kernel in the Ubuntu Minimal CD, capable of runningin an Amazon EC2 instance?
[06:13] <hashken> Is the regular Ubuntu kernel capable of running in an Amazon EC2 instance?
[07:23] <smb> hashken, It varies depending on release. But in general all of them should. The only thing to check is whether xen-blkfront is built in or that the module is requested to be in the initrd.
[07:27] <smb> hashken, If you pull in the linux-virtual meta-package that gives you the same kernel as in the cloud-images.
[07:43] <hashken> thanks smb
[07:48]  * apw yawns ...
[07:48] <apw> it is very hot here
[07:49] <RAOF> apw: How are the bees finding it?
[07:49] <smb> They probably have been replaced by real-fire flies
[07:49] <apw> if they have any sense they are in the cup, hiding from the sun
[07:50] <apw> smb, turned into by the sun more like
[07:52] <smb> apw, You should get rid of that sun thing completely.
[07:55] <RAOF> The Daystar?
[07:57] <smb> Just place a huge solar panel over the UK... above cloud level so they can enjoy their rain still
[07:57] <apw> smb, good plan
[08:14]  * apw hs being promised some rain over the next two days, thats something
[08:56] <brendand> is this verification testing week for the -proposed kernels?
[09:08] <smb> "14-Jul - 20-Jul   Bug verification." (from the email everyone gets)
[09:16] <Guest46086> Can we get https://wiki.ubuntu.com/Kernel/LTSEnablementStack linked from https://wiki.ubuntu.com/Kernel/FAQ somewhere?
[12:34] <rtg> I've rebased saucy against v3.10.1 and ready to push. are you still looking at those arm dtb patches ?
[12:34] <rtg> apw, ^^
[13:03] <apw> rtg, i have them applied here indeed, but push away and i'll sort it out
[13:03] <rtg> are you gonna worry about 3.10 ? or just do it for 3.11 ?
[13:04] <apw> i was assuming i'd apply them to both once i had build tested them on both
[13:04] <apw> they seem sane if my chat with infinity is anytyhing to go by
[13:04] <rtg> ok
[13:06] <infinity> Oh dear.  I shouldn't be the yard stick for sanity.
[13:06] <rtg> apw, saucy pushed. still testing armhf build, but I expect it to be OK
[13:07] <apw> infinity, hey i am comparing to me
[13:24] <apw> rtg, don't we have a per kernel directory already
[13:24] <rtg> apw, for firmware in the kernel package
[13:24] <apw> for firmware, could we perhaps drop the linux-firmware-lts contents into those as if they were part of the kernel
[13:24] <rtg> but each one is ABI specific
[13:24] <apw> bah
[13:25] <rtg> apw, sounds like a sprint topic
[13:25] <apw> yeah shove it in, a plan indeed
[13:25] <apw> as we'll have infinity to poke too
[13:26] <rtg> apw, lemme know when you've pushed those arm patches. everything else is ready to go.
[13:26] <apw> rtg ack, just checking the udebs builds
[13:32] <rtg> apw, pushed saucy unstable rebase onto v3.11-rc1
[13:37] <apw> rtg, ack
[13:37] <apw> not far behind, just rebased and doing final checks
[13:37] <apw> missing some ?'s which i've added and fingers crossed
[13:53] <jibel> ogasawara, apw, there is a first iteration of dkms testing ready for review http://10.98.0.1:8080/view/DKMS/view/All/
[13:53] <jibel> It covers precise, precise+hwe kernels, saucy+proposed, saucy+prerelease ppa
[13:53] <jibel> This a build/install test but I disabled modprobing for the moment.
[13:54] <jibel> ogasawara, Could your team review the results, then we can schedule a call ?
[13:54] <ogasawara> jibel: awesome, thanks!  yes, we'll review. lets go ahead and schedule a call on the calendar for later this week?
[13:55] <jibel> ogasawara, this week is fine, I'll let you schedule it, your time will be mine.
[13:55] <ogasawara> jibel: ack
[14:13] <apw> rtg, ok i also need to fix linux-signed before you do your do on this one
[14:14] <rtg> apw, no problem, am pursuing an __udivdi3 issue on unstable i386
[14:46] <apw> rtg, ok saucy master-next is pushed, off to un-f*ck -signed
[14:46] <rtg> apw, ack
[15:07] <apw> rtg, ok i have pushed signed, but once you have linux in the pipe for upload i would like to do the update to ensure the update-versions is going to handle this situation, we have never had to test this before
[15:07] <apw> (do the update for linux-signed)
[15:08] <rtg> apw, If you want, then go ahead and package saucy master-next. I'm still messing with unstable.
[15:08] <rtg> (and upload)
[15:09] <apw> rtg ok will do
[15:10] <apw> rtg, you did a rebase on this right ?
[15:10] <rtg> yeah, to v3.10.1
[15:10] <apw> i don't see it in the changelog
[15:10] <rtg> apw, oh shit, forgot
[15:10] <apw> did you miss it (then i can add it) or do i have the wrong brnach
[15:10] <apw> if you missed it i can retrofit for you
[15:11] <rtg> apw, yeah, go ahead and run insert-mainline-changes
[15:11] <apw> will do
[16:14]  * _bjf -> dr. appt.
[16:15] <brendand> bjf - i noticed a couple of the kernels went to confirmed today, that doesn't imply a change in schedule does it?
[16:16] <brendand> bjf, the raring and quantal backports kernels were the ones
[17:14] <apw> brendand, those normally lag don't they, as in wait on their parent branches to build before being done (but i'll let bjf say for sure)
[17:16] <brendand> apw, i would have expected then for the raring and quantal proposed kernels to be confirmed prior then, rather than the other way around
[17:18] <psivaa> sbeattie: We are seeing https://jenkins.qa.ubuntu.com/view/All/job/sru_kernel-quantal_lts_hwe-generic_i386-intel_64-mga_g200ew/39/testReport/junit/autotest/ubuntu_qrt_apparmor/test_apparmor_py/ in regression testing.  
[17:19] <psivaa> sbeattie: guess you are the one to talk to?
[17:20] <apw> psivaa, if it is apparmor i expect jjohansen will be interested as well
[17:20] <psivaa> apw: ack, thanks :)
[17:23] <jjohansen> psivaa: thanks, this regression is known about and temporary
[17:23] <jjohansen> psivaa: its due to work item scheduling
[17:24] <apw> jjohansen, so we'll get some more bits in the mail :)
[17:24] <jjohansen> apw: oh yes, there will be at least two more syncs
[17:25] <apw> jjohansen, thanks
[17:26]  * bjf -> back
[17:27] <bjf> brendand, would be nice if you'd have stuck around :-(
[17:27] <psivaa> jjohansen: ack, not sure what i should do with the workflow task, (fix-release with qa-testing-passed ?) 
[17:30] <jjohansen> psivaa: err just a sec, this is the quantal backport?
[17:30] <psivaa> jjohansen: yes
[17:31] <jjohansen> psivaa: on i386?
[17:32] <psivaa> jjohansen: yes, on amd64 hardware i think
[17:32] <jjohansen> psivaa: sorry ignore what I said before, this just looks like a known bug. It is not. The quantal backport should be good here
[17:33] <jjohansen> psivaa: okay, we will poke at it
[17:33] <psivaa> jjohansen: ack, ill report a bug then
[17:33] <jjohansen> sbeattie: we have a regression on the quantal backport to investigate
[17:35] <sbeattie> jjohansen: looking at that output, it seems to be the tcp tests that failed?
[17:35] <jjohansen> sbeattie: yep
[17:54] <psivaa> jjohansen: sbeattie: reported bug #1201530 for the above failure. 
[17:54] <ubot2`> Launchpad bug 1201530 in ubuntu-kernel-tests "Failure in apparmor tests with quantal lts-hwe 3.5.0-37.58~precise1-generic 3.5.7.16" [Undecided,New] https://launchpad.net/bugs/1201530
[17:54] <jjohansen> psivaa: okay, thanks
[17:57]  * sbeattie is trying to reproduce the issue
[19:51] <rtg> apw,  pushed Ubuntu-3.10.0-3.12 on to saucy master
[19:51] <apw> rtg, how is it i keep forgetting to do that, spack
[19:51] <rtg> apw, I didn't notice until I went to do the LTS version
[21:30]  * rtg -> EOD