<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 19, 2016 at 9:29 AM, Christian Ehrhardt <span dir="ltr"><<a href="mailto:christian.ehrhardt@canonical.com" target="_blank">christian.ehrhardt@canonical.<wbr>com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_extra">I'm now rebasing to integrate on top of your last 5 commits of Friday and check again.</div><div class="gmail_extra">But I assume I'll hit the same.</div><div class="gmail_extra">Qemu is not yet merged to latest yet, so still at 2.6.1 there - which is old, but not terribly old.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Tests take a while every time but I hope to come back with a solution later today.</div></blockquote></div><br>Hi again,</div><div class="gmail_extra">so on retesting the following issues are left for me:</div><div class="gmail_extra"><br></div><div class="gmail_extra">TL;DR:</div><div class="gmail_extra">- make vmlinuz/initrd accessible</div><div class="gmail_extra">- make sure vmlinuz/initrd are on the system</div><div class="gmail_extra">- do not use kvm when not needed (qemu instead)</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">###1 Permissions vs qemu://session</div><div class="gmail_extra">If I run non root I run into all sorts of trouble due to <br></div><div class="gmail_extra"><span style="font-family:monospace"><span style="color:rgb(0,0,0)">"Could not access KVM kernel module: Permission denied"</span><br></span></div><div class="gmail_extra"><span style="font-family:monospace"><br></span></div><div class="gmail_extra"><div class="gmail_extra">Maybe this is different due to the way Ubuntu does authenticate (via groups kvm / libvirtd) and Debian via policykit IIRC.</div><div><font face="monospace">But as our former discussion outlined root+</font><span style="font-family:monospace">qemu:///session is more or less = qemu://system - so not a huge reason to go there :-/.</span><br></div><div><br></div><div>For the time being I fixed that up locally and went on - solution came later, see #2.</div><div><br></div><div><br></div><div><div>###2 After passing the first hurdle I still crash into:<br></div></div></div><div>"host doesn't support requested feature: CPUID.80000001H:ECX.svm" and due to that "qemu: could not load kernel '/vmlinuz': Permission denied"<br><span style="color:rgb(0,0,0);font-family:monospace"><br></span>That is just as far as I got when I switched from kvm to qemu-system with TCG :-/<br>Which made me aware that the cpu feature really just be a warning (until failing later), but the real issue obviously is the permission denied.</div><div>Seems I looked at the wrong thing before :-)</div><div><br><div>Since I now thought deeper into the first issue that is rather clear:<br>With permissions of the user due to qemu://session the following file is hard to access:<br>lrwxrwxrwx 1 root root 29 Dec 19 11:22 /vmlinuz -> boot/vmlinuz-4.9.0-11-generic<br>-rw------- 1 root root 7452448 Dec 12 14:40 /boot/vmlinuz-4.9.0-11-generic<div class="gmail_extra"><span style="font-family:monospace"><span style="color:rgb(0,0,0)"><br></span></span></div><div class="gmail_extra">That is just the same on Debian, so I'd expect you to hit that as well.</div><div class="gmail_extra"><span style="color:rgb(0,0,0);font-family:monospace">lrwxrwxrwx 1 root root 26 Dec 19 11:03 /vmlinuz -> boot/vmlinuz-4.8.0-2-amd64</span><br></div><div class="gmail_extra"><span style="font-family:monospace"><span style="color:rgb(0,0,0)"><div class="gmail_extra">-rw-r--r-- 1 root root 4153384 Dec 3 15:17 /boot/vmlinuz-4.8.0-2-amd64<br></div></span></span></div><div class="gmail_extra"><br></div><div class="gmail_extra">Since this is a test env anyway we can mess with it - so why not just changing the perm to allow access.</div><div class="gmail_extra">Messing around means set isolation level to at least ioslation-container which it already is.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><span style="font-family:monospace">###3 we can't rely on /vmlinuz and initrd being there - it might not e.g. in containers</span></div><div class="gmail_extra"><span style="font-family:monospace"><br></span></div>Need to add a proper dependency to have /vmlinuz around.<br>Sounds trivial but we don't share a meta package for the kernel.<br>Since the test is amd64 only I picked the Debian meta package for amd64 and the general Ubuntu kernel meta package.<br>That should work well in both worlds, and never fail unless we drop the x86_64 if at the beginning of smoke-qemu-session.<br><br><br>###4 no need for KVM and impossible in some test environments<br>We discussed that before, the switch from kvm to qemu should fit the needs for the tests and helps to avoid the following issues in some environments:<br><br>error: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied<br>failed to initialize KVM: Permission denied<div class="gmail_extra"><br></div><div class="gmail_extra">Fixes attached as patch.</div><br>With that in place smoke-qemu-session is passing now again.<br>After lunch I'll look at the remaining lxc fails (different debbug) and cross arch tests after that.<div class="gmail_extra"><span style="font-family:monospace"><br></span></div><div class="gmail_extra"><span style="font-family:monospace"><br></span></div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail-m_1485698786039719364gmail_signature"><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(136,136,136);font-size:12.8px">Christian Ehrhardt</span><div style="color:rgb(136,136,136);font-size:12.8px">Software Engineer, Ubuntu Server</div><div style="color:rgb(136,136,136);font-size:12.8px">Canonical Ltd</div></div></div></div></div>
</div></div></div></div>