Hi Gema,<div><br></div><div>I've updated bug 1085171 But, I have now hit a bug of my own .. 1086974 I use guestfs to pull data from VM's (in this case, the guys on -release wanted details from /var/log). I'll switch over to my CentOS system and run KVM from that and hopefully grab the log files they are asking for.</div>
<div><br></div><div>Regards,</div><div><br></div><div>Phill.<br><br><div class="gmail_quote">On 5 December 2012 10:59, Gema Gomez <span dir="ltr"><<a href="mailto:gema.gomez-solano@canonical.com" target="_blank">gema.gomez-solano@canonical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 04/12/12 20:18, Jackson Doak wrote:<br>
> bug 1085171 will make things interesting<br>
<br>
</div>Hey, regarding this bug, I have been trying to figure out the extent and<br>
the cause.<br>
<br>
I'd like to ask everyone, that from now on, whenever you report a<br>
VirtualBox issue you also report (quoting xnox here, he was asking me<br>
all the things when I enquired about the bug) the VirtualBox version<br>
number (propietary vs opensource edition, from ubuntu archive vs from<br>
oracle).<br>
<br>
It would be also useful to know if the problem is reproducible in KVM or<br>
not, if you have the time to find out (very important because it helps<br>
determine whether the problem is in ubuntu code only or if it is just<br>
related to one virtualization solution). Or if you can reproduce it in<br>
hardware, so that devs know the extent of the problem.<br>
<br>
It'd be very good if you guys could try to add as many details as<br>
possible to the bugs, everything you've tried, to be able to assess the<br>
extent of the problem. Things like: Does it only occur in the live<br>
session? Does it happen when installing directly? Does it also happen in<br>
bare metal? How far into the install was I able to go through (and<br>
mention the screen)? Etc. Please, don't just see ubuntu fail and leave<br>
it there, that's just the beginning of getting a problem fixed! Ask<br>
yourselves all these questions and try to answer them on the bug<br>
(preempting the developers).<br>
<br>
All of these details will make your bugs to get picked up from the queue<br>
and fixed quicker, because the developer will be able to diagnose the<br>
problem quicker.<br>
<br>
Thanks a lot for all the good testing we are seeing lately, manual<br>
testing is keeping our images sane whilst we undergo the changes to<br>
smoke automated testing to get the tests up and running with UTAH, so I<br>
really appreciate all the effort that is going into keeping the images<br>
installable!!<br>
<br>
Regards,<br>
Gema<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Gema Gomez-Solano <<a href="mailto:gema.gomez-solano@canonical.com">gema.gomez-solano@canonical.com</a>><br>
Ubuntu QA Team <a href="https://launchpad.net/~gema.gomez" target="_blank">https://launchpad.net/~gema.gomez</a><br>
Canonical Ltd. <a href="http://www.canonical.com" target="_blank">http://www.canonical.com</a><br>
</font></span><div class="HOEnZb"><div class="h5"><br>
--<br>
Ubuntu-quality mailing list<br>
<a href="mailto:Ubuntu-quality@lists.ubuntu.com">Ubuntu-quality@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality<br clear="all"><div><br></div>-- <br></a><a href="https://wiki.ubuntu.com/phillw" target="_blank">https://wiki.ubuntu.com/phillw</a><br>
<br>
</div></div></blockquote></div></div>