=== ripps_ is now known as ripps
[01:05] <fta> jdstrand, i can't create a guest os for kvm because of apparmor
[01:06] <fta> jdstrand, operation="open" pid=11396 parent=1 profile="libvirt-16b5a997-ff4f-a3bf-94a4-1841414ab5cf" requested_mask="::rw" denied_mask="::w" fsuid=0 ouid=1000 name="/data2/qemu-vms/foo.iso"
[05:09] <jdstrand> fta: actually, that should be bug #453335 and the iso is readable
[05:09] <ubottu> Launchpad bug 453335 in libvirt "libvirt via virt-manager tries to write to a readonly ISO image" [Low,New] https://launchpad.net/bugs/453335
[05:09] <jdstrand> fta: it should still work (it certainly does here)
[05:10] <jdstrand> fta: I'm giong offline, but if you are having problems, please add apparmor deny messages and any other pertinent info to that bug
[05:15] <jdstrand> fta: let me clarify. when you create a new vm using the iso, if you see the guest boot the iso, then everything is ok despite that error (ie the guest clearly can read the iso)
[05:17] <jdstrand> fta: if the guest doesn't boot at all, try disabling apparmor by adding 'security = "none"' to /etc/libvirt/qemu.conf, then do 'sudo /etc/init.d/libvirt-bin restart'. if the guest still doesn't boot, it isn't apparmor. if it does, then please add info to the bug
[05:17] <jdstrand> fta: (boot the iso that is)
[05:21] <micahg> jdstrand: I just gave you another apparmor/ff bug
=== ripps_ is now known as ripps
[08:20] <eagles0513875> morning guys
[10:08] <nikolam> hi.
[10:08] <nikolam> I think Seamonkey2 is ready to be included in Ubuntu for testing.
[10:09] <nikolam> What do you think (it is ar RC at the present and it works just fine)
[14:47] <fta> jdstrand, hi, if it's not apparmor, i don't know what's wrong then. i create a vm from an iso, it creates the volume, puts some files in it, then it wants to reboot, but after reboot, i see the bios, then nothing, black screen with a cursor
[14:48] <nikolam> seamonkey leaks after few hours of use, and leaks very bad
[14:48] <fta> jdstrand, i had a guest os on that box before, it was working fine, but it can no longer boot. that's why i want to create a fresh one. maybe it's another problem..
[14:49] <nikolam> 1.1.17 and previous 1.1x
[14:53] <eagles0513875> fta: i find that i have bugs that surface in a vm that dont on my duelboot on my laptop
[14:53] <eagles0513875> you cant accuratly trust vms it seems like
[14:54] <fta> it used to work just fine.
[14:55] <eagles0513875> i have random lockups on my vbox vm with karmic fully updated where the mouse dont work
[14:56] <nikolam> eagles0513875, i think karmic is not released yet.
[14:56] <nikolam> please go to #ubuntu+1
[14:56] <nikolam> and do report a bug about
[14:57] <eagles0513875> nikolam: tyvm i know bout that channel im just saying is vms will give bugs that a duel boot wont
[14:57] <nikolam> eagles0513875, https://help.ubuntu.com/community/ReportingBugs
[14:57] <nikolam> and create launchpad account so you can report bugs in future
[14:58] <eagles0513875> nikolam: that mouse bug is a known bug from what i was told in +1 and i already have one
[14:58] <eagles0513875> i have been using kubuntu for quite some time fyi
[14:59] <nikolam> eagles0513875, sorry, I was thinking I am on #xubuntu, sorry
[14:59] <eagles0513875> its ok nikolam
[14:59] <eagles0513875> fta: you have a duel boot machine you can test on
[15:04] <fta> eagles0513875, i don't have any dual boot machines. i've been using linux only for a very long time
[15:05] <eagles0513875> same here but im finding the mouse issue only surfaces on my vm not on duelboot itself
[15:05] <eagles0513875> if there is anything i can teset let me know
[15:25] <jdstrand> fta: I'd look in the list of open bugs in libvirt and see if others are having the same problem. while I wrote the apparmor security driver for it, I'm not the maintainer and not sure what the problem could be
[15:25] <jdstrand> fta: feel free to open a new bug or bring it up in #ubuntu-virt
[15:25] <jdstrand> micahg1: ack
[15:27] <fta> jdstrand, ok. i guess i'm stuck for today then
[15:27] <jdstrand> sorry :/
[15:28] <jdstrand> fta: the way you described it, it sorta sounds like a guest/kvm interaction issue. you could try starting the guest without libvirt with kvm, and then with qemu to try to narrow down the problem
[15:34] <fta> kvm does the same, and qemu complains about missing /dev/kqemu
[15:35] <jdstrand> fta: so it is a kvm bug
[15:35] <jdstrand> fta: kirkland is who deals with those
[15:36] <jdstrand> fta: with qemu, try with '-no-kvm'
[15:39] <fta> no such option
[15:39] <fta> -no-kqemu ?
[15:39] <fta> it boots in loop
[15:45] <jdstrand> fta: I don't know why it is complaining about /dev/kqemu, since it isn't available in karmic. possibly another bug
[16:17] <fta> micahg1, just added you to my bot watchers list for umd (moz daily ppa) and usd (songbird daily)
[16:18] <fta> micahg1, let me know if you want to receive the FTBFS emails, i can relay them to you
[19:18] <micahg> fta, thanks
[19:22] <fta> micahg, you should have received 2 emails
[19:24] <micahg> got them
[19:32] <fta> there are a few things to check in those emails, like verify that new tarballs are not too big/small compared to the previous ones; check the reasons when the title doesn't say OK, etc..
=== asac_ is now known as asac
[21:33] <BUGabundo> g'nuit guys
=== micahg1 is now known as micahg