https://bugzilla.novell.com/show_bug.cgi?id=708680 https://bugzilla.novell.com/show_bug.cgi?id=708680#c5 melchiaros melchiaros <melchiaros@aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|melchiaros@aol.com | --- Comment #5 from melchiaros melchiaros <melchiaros@aol.com> 2011-07-31 15:08:20 UTC --- There are problems: First, btrfs(first install) is not able to boot with success. So when it is also impossible(and it is here) to perform another installation on this virtual disk which would lead to a working system, it is also not possible to get the logs. The only way is a direct extraction from the virtual disk(ha, good luck!->seems to be not recommend; it is possible do mount a .vdi in windows7 which I´ve done a while ago, but with KVM;???) Second, I´ve deleted the old btrfs .raw, so in the moment I can´t extract the logs from such a vm either it should be possible, I have just a fresh install here with LVM. Third, there was not long ago a other btrfs bug here also in early installation phase. An inspection of the logs has shown that there are no entries in such a early phase. ------------------------------------------------------------------------------- A suggestion: I´ve seen that openSUSE is performing automated testing. A bug like this is exactly what could be added to this test, because it would be only a test of installation works(with successful start of the system) or it do not. Exactly what your collegians are doing: http://en.opensuse.org/openSUSE:Build_Service_Concept_QA#Kind_of_QA_tests line: "product images have been build => an automatable installation shall run inside of a VM (also emulated, e.g. with QEMU)" ------------------------------------------------------------------------------- No hard feelings for, but I can´t see how to provide logs to you. Greetings melchiaros -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.