Displaying 4 results from an estimated 4 matches for "l752".
Did you mean:
752
2015 Mar 11
1
Re: Name resolution not working inside virt-customize
On 03/10/2015 05:12 PM, Richard W.M. Jones wrote:
> Just for comparison, libguestfs 1.29.29 on Fedora host, plus
> virt-builder, with a Fedora guest does this:
Hmm, something weird is going in with the output of virt-customize.
leer@eng-leer:~$ virt-customize -a
trusty-server-cloudimg-amd64-disk1.img --firstboot update-resolv-conf.sh
--install mysql-server -v -x > virt-customize.log
2014 Apr 17
1
Re: LXC + USB passthrough = Operation not permitted
...c09f5b881d83b1#file-libvirtd-log-L296
> [5]
> https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302
> [6]
> https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685
> [7]
> https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799
> [8]
> https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075
> [9]
> https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1090
> [10]
> http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/lxc/lxc_cgroup.c;h=39d955cd8cc2e34b6157e126fbb45...
2014 Apr 17
0
Re: LXC + USB passthrough = Operation not permitted
.../gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L296
[5]
https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L302
[6]
https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L685
[7]
https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L752-L799
[8]
https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1075
[9]
https://gist.github.com/filmaj/207ab3c09f5b881d83b1#file-libvirtd-log-L1090
[10]
http://libvirt.org/git/?p=libvirt.git;a=blob;f=src/lxc/lxc_cgroup.c;h=39d955cd8cc2e34b6157e126fbb455d8f71e0647;hb=e8684eb541f01df...
2014 Apr 17
2
Re: LXC + USB passthrough = Operation not permitted
Further followups!
We are correlating DEBUG-level output from libvirt with the libvirt 1.2.2
code to try to figure out what libvirt is doing under the hood.
Even though we have the log level set to 1 (info) in our libvirtd.conf, we
are not seeing the VIR_DEBUG() [1] statements being printed out. There are
tons of other presumably-debug lines of output showing up in our log. We
are sort of