<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 22, 2017 at 4:04 AM, Michal Privoznik <span dir="ltr"><<a href="mailto:mprivozn@redhat.com" target="_blank">mprivozn@redhat.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"><span class="gmail-">On 03/21/2017 07:04 PM, D L wrote:<br>
> Yes, I compiled, installed, and used the binaries successfully.<br>
> Could you confirm the location of bug list is the following, please?<br>
><br>
> <a href="https://bugzilla.redhat.com/buglist.cgi?component=libvirt&product=Virtualization%20Tools" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>buglist.cgi?component=libvirt&<wbr>product=Virtualization%20Tools</a><br>
<br>
</span>This will fetch all bug there are/ever were for upstream libvirt, regardless of their state. You want just opened ones. Thus this should be:<br>
<br>
<a href="https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&component=libvirt&product=Virtualization%20Tools&query_format=advanced" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>buglist.cgi?bug_status=NEW&<wbr>bug_status=ASSIGNED&component=<wbr>libvirt&product=<wbr>Virtualization%20Tools&query_<wbr>format=advanced</a><br>
<br>
> <a href="https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization%20Tools&component=libvirt" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/<wbr>enter_bug.cgi?product=<wbr>Virtualization%20Tools&<wbr>component=libvirt</a><br>
<br>
This is for entering a new bug. Unless you've found one, you don't need this.<br>
<span class="gmail-HOEnZb"><font color="#888888"><br>
Michal<br></font></span></blockquote><div>Hi Michal,</div><div><br></div><div>To keep the thread consistent, I am writing now about two Bugs here which probably </div><div>have been mentioned in other thread. So I am watching two bugs, and trying to decide </div><div>one to fix. They are 1431652 and 1434550.</div></div><div class="gmail_quote"><br></div><div class="gmail_quote">For 1434550, I am reading ./src/nodeinfo.c and several other related files for a bug </div><div class="gmail_quote">about possible incorrect number of socket when executing 'virsh capabilities' on a host.</div><div class="gmail_quote">It seems this totally depends on design decision. When showing cell number = 2 and </div><div class="gmail_quote">socket = 1 in the XML CPU topology in a 2 CPU sockets machine indeed kinda of </div><div class="gmail_quote">confusing, if one does not read the XML carefully, or is not familiar with the notion of </div><div class="gmail_quote">"cell". Would people want it to be changed or leave it in the current state?<br></div><div class="gmail_quote"><br></div><div class="gmail_quote">For 1431652, I am able to reproduce the error. And I also tried to use absolute path</div><div class="gmail_quote"> which resulted in different output and behavior as the following from 'history' command</div><div class="gmail_quote"><div><br></div><div><div> 513 truncate -s 100M test-backing.img</div><div> 514 pwd</div><div> 515 qemu-img create /var/tmp/test-overlay.img -f qcow2 -b 'json:{"driver":"raw","file":</div><div>{"driver":"file","filename":"/var/tmp/test-backing.img"}}'</div><div> 516 ls -lh</div><div> 517 history</div><div>root@<host> :/var/tmp# !507</div><div>qemu-img info test-overlay.img</div><div>image: test-overlay.img</div><div>file format: qcow2</div><div>virtual size: 100M (104857600 bytes)</div><div>disk size: 196K</div><div>cluster_size: 65536</div><div>backing file: json:{"driver":"raw","file":{"driver":"file","filename":"/var/tmp/test-backing.img"}}</div><div>Format specific information:</div><div> compat: 1.1</div><div> lazy refcounts: false</div><div> refcount bits: 16</div><div> corrupt: false</div><div>root@<host> :/var/tmp# !508</div><div>virt-install --import --name tmp-relpaths --memory 1024 --disk /var/tmp/test-overlay.img</div><div>WARNING No operating system detected, VM performance may suffer. Specify an OS</div><div> with --os-variant for optimal results.</div><div>WARNING Graphics requested but DISPLAY is not set. Not running virt-viewer.</div><div>WARNING No console to launch for the guest, defaulting to --wait -1</div><div><br></div><div>Starting install...</div><div>Creating domain... | 0 B 00:00:00</div><div>Domain installation still in progress. Waiting for installation to complete.</div></div><div><br></div><div>At the end, it hanged and I had to terminated the 'virsh install' by ctrl + C. So I guess</div><div> the expected behavior when using 'virsh install' with relative path should be the same. </div><div>Is that right?</div><div><br></div><div>I may want to try both of the bugs and maybe </div><div>one of them can be solved in a timely manner. Or would you recommend one, or other </div><div>one than those two? (I did attempt to search something like xml parser or cmd generation </div><div>bugs which could be closer to the fuzzing project)</div><div><br></div><div>Dan</div><div><br></div><div><br></div></div><br></div></div>