Re: Testing DKIM handling

2022-07-15 Thread Michal Prívozník
On 7/15/22 14:37, dberra...@yahoo.com wrote:
> Hopefully the final test message, as DKIM is believed to be  correctly
> handled on the mailing lists now
> 

Yay! 🎉

Michal



Re: Testing DKIM handling

2022-07-15 Thread dberra...@yahoo.com
 Hopefully the final test message, as DKIM is believed to be  correctly handled 
on the mailing lists now
On Friday, 1 July 2022 at 16:27:46 BST, dberra...@yahoo.com 
 wrote:  
 
  Testing DKIM handling with new mail server settings

On Tuesday, 28 June 2022 at 17:24:05 BST, dberra...@yahoo.com 
 wrote:  
 
  
Another test of DKIM handling in Red Hat mail servers, apologies for the 
continued nuisance.
On Wednesday, 8 June 2022 at 13:58:39 BST, dberra...@yahoo.com 
 wrote:  
 
  
Further DKIM handling test, apologies for the noise.
On Friday, 13 May 2022, 10:03:32 BST, dberra...@yahoo.com 
 wrote:  
 
 Testing DKIM handling RH mail servers


Re: The default USB controller of pc machine type

2022-07-15 Thread Daniel P . Berrangé
On Fri, Jul 15, 2022 at 02:36:36PM +0800, Han Han wrote:
> On Wed, Jul 13, 2022 at 7:04 PM Daniel P. Berrangé 
> wrote:
> 
> > On Wed, Jul 13, 2022 at 07:00:17PM +0800, Han Han wrote:
> > > Hello,
> > > I found that the default USB controller for q35 machine type is qemu-xhci
> > > while for pc it is piix3-uhci. Here are the results(on qemu-kvm-7.0.0
> > > qemu-kvm-7.0.0):
> > > ➜  ~ cat /tmp/usb.xml
> > > 
> > >   USB
> > >   1a81d4ef-6537-4ae8-b257-8a15e0c0525f
> > >   2097152
> > >   2097152
> > >   1
> > >   
> > > hvm
> > > 
> > >   
> > >   
> > > /usr/libexec/qemu-kvm
> > >   
> > > 
> > >
> > > ➜  ~ virsh define /tmp/usb.xml && virsh dumpxml USB|grep usb
> > > Domain 'USB' defined from /tmp/usb.xml
> > >
> > > 
> > >
> > >
> > > ➜  ~ cat /tmp/usb-pc.xml
> > > 
> > >   USB
> > >   1a81d4ef-6537-4ae8-b257-8a15e0c0525f
> > >   2097152
> > >   2097152
> > >   1
> > >   
> > > hvm
> > > 
> > >   
> > >   
> > > /usr/libexec/qemu-kvm
> > >   
> > > 
> > >
> > > ➜  ~ virsh define /tmp/usb-pc.xml && virsh dumpxml USB|grep usb
> > > Domain 'USB' defined from /tmp/usb-pc.xml
> > >
> > > 
> > >
> > > And the default usb controller for q35 has been added since:
> > > ed2049ea19 qemu: auto-add generic xhci rather than NEC xhci to Q35
> > domains
> > >
> > > As I know, pc machine supports qemu-xhci as well.   Morever, the
> > > performance of qemu-xhci is better than piix3-uhci. So why not update the
> > > default usb controller of pc machine type to qemu-xhci? I think we can
> > > improve it here.
> >
> > A qemu-xhci controller can be added to any x86 machien type regardless
> > of the default, and most mgmt apps will do exactly that.
> >
> 
> Does that mean, the default USB controller for a specific x86 machine type
> does NOT matter?
> And leave the default USB controller to up-layer mgmt apps?

Yes, that's our general view for most defaults in fact. There's no
single perfect defaults, so we let mgmt apps select thigns explicitly

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|



Why can not get the expected cpu topology after setting the maxcpu in xml?

2022-07-15 Thread liang chaojun
Hello all,

I hit a issue that I'm not able to see the expected cpu topology in VM after 
setting the maxcpu arrtribute in domain.

the xml look like below:
8
  

  

I notice that the cpu topoloy looked like below capture output from 'lscpu' 
tool which is totally different with my setting.

CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 63
Model name:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz

Besides i found it looked correct if i relpace 'vcpu' line with "8" that remove maxcpu value.

Could you give me some information? Any comments are appreciated.

Thanks