Re: [CentOS-virt] change network settings of VM depending on logged in user(s)?

[Mark L Sung]

> On 7 Sep 2017, at 21:48, hw  wrote:
> 
> [-=X.L.O.R.D=-] wrote:
>> 1guys,
>> I think it can be done via power management feature if PC idle a period of 
>> time, sleep it.
> 
> Access is exclusively via RDP-sessions.  I don´t know if I can get a VM to 
> hibernate
> when idle and to wake up when someone tries to connect; and delying logins as 
> mmight
> occur when the VM needs to wake up first is not an option.  Besides, internet 
> access
> would not be denied at all and only not used when the VM is hibernating.
X—> Yup and just make sure the power-save is set-to never, so RDP session 
should be ready for RDP call-in request from remote.
> 
>> For your message, to disallow an user to have internet access that can be 
>> done via his account profile at local security from Microsoft product 
>> itself. Alternatively GPO policy at the AD. When he logs on to the username 
>> and password, his profile will also download to that PC.
> 
> Thanks, that´s something I need to look into.  It would still be better than 
> no
> restiction at all.
> 
> 
> The intention is to quarantaine windoze machines as much as possible for 
> security
> reasons.  Hibernating doesn´t really help with that unless they´re never used 
> …
> X —> One thing you can append is once user logged off, use a reborn-software 
> to revert to the clean status or previous backup snapshot point.

> 
>> Hope that help!
>> 
>> Xlord
>> 
>> -Original Message-
>> From: CentOS-virt [mailto:centos-virt-boun...@centos.org] On Behalf Of hw
>> Sent: Saturday, September 2, 2017 7:50 PM
>> To: centos-virt@centos.org
>> Subject: Re: [CentOS-virt] change network settings of VM depending on logged 
>> in user(s)?
>> 
>> PJ Welsh wrote:
>>> I'm not a M$ expert, but I've seen enough GPO's to believe there is a way 
>>> to do it through Windows.
>>> PJWelsh
>> 
>> For the whole machine?
>> 
>> So far, I´ve only found information regarding blocking access for particular 
>> users.  I want it the other way round, i. e. the whole maching usually not 
>> having access and allowing access to only a particular user.
>> 
>> Allowing access to only a particular user can (should ideally) involve the 
>> whole machine still not having access.
>> 
>> 
>> Perhaps it seems like an unusual request --- yet the more I think about it, 
>> it seems like it should become the default.  Why should a machine have 
>> internet access all the time rather than only when it´s needed, and when 
>> it´s needed, why not restrict it to exactly what is needed and nothing else.
>> 
>> 
>>> 
>>> On Fri, Sep 1, 2017 at 11:43 AM, hw > 
>>> wrote:
>>> 
>>> 
>>>Hi,
>>> 
>>>is there a way to disable internet access for a windoze 7 VM depending
>>>on which user(s) is/are logged in?
>>> 
>>>It seems windoze 7 doesn´t really support this, especially when you want
>>>to disable internet access for the whole machine, so I´m wondering if
>>>there is a way to do this when the machine is a KVM-VM running on Centos.
>>> 
>>>The whole VM should only have internet access when a particular user logs
>>>in, and preferably for only this particular user.
>>>___
>>>CentOS-virt mailing list
>>>CentOS-virt@centos.org 
>>>https://lists.centos.org/mailman/listinfo/centos-virt
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> CentOS-virt mailing list
>>> CentOS-virt@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos-virt
>>> 
>> 
>> ___
>> CentOS-virt mailing list
>> CentOS-virt@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-virt
>> 
>> ___
>> CentOS-virt mailing list
>> CentOS-virt@centos.org 
>> https://lists.centos.org/mailman/listinfo/centos-virt 
>> 
>> 
> 
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org 
> https://lists.centos.org/mailman/listinfo/centos-virt 
> 
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-docs] Sending git changes on the centos-docs for centos.org website

[Mark L Sung]

Fabian,
Very nice and virsualizaed dashboard for CentOS ^_^.

Xlord

On Wed, Jul 12, 2017 at 11:46 AM, Mark L Sung <xlord...@gmail.com> wrote:

> Thank you Fabian :-)
> Xlord
>
> On Wed, Jul 12, 2017 at 1:47 AM, Fabian Arrotin <arr...@centos.org> wrote:
>
>> Hi,
>>
>> Just to let you know that we decided to send all the git notifications
>> to the centos-docs list for the centos.org website. The git repository
>> is hosted on https://git.centos.org/summary/?r=websites/centos.org.git
>> (will be open soon)
>>
>> It's low-traffic, so centos-docs list will not receive a huge amount of
>> notifications, but at least some people on the list will get
>> notification when a git commit was done.
>>
>> --
>> Fabian Arrotin
>> The CentOS Project | http://www.centos.org
>> gpg key: 56BEC54E | twitter: @arrfab
>>
>>
>> ___
>> CentOS-docs mailing list
>> CentOS-docs@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-docs
>>
>>
>
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] CentOS EDU Introduction

[Mark L Sung]

Dear Markus,
Good initiative, should you please share any sort of link for more details?

Xlord

On Wed, Jul 12, 2017 at 9:06 AM, Markus McLaughlin 
wrote:

> Karanbir Singh and I started a SIG called "CentOS EDU."  It is CentOS
> designed for the Education Community.
>
> It is CentOS with offline Wikipedia access and a library of free
> e-textbooks.  Windows and MACs have dominated
> Education for years, it's time to "fight back" with CentOS!!!
>
> We welcome anyone who would love to join us on this journey to make this a
> reality!  :D
>
> Markus McLaughlin
>
> ___
> CentOS-docs mailing list
> CentOS-docs@centos.org
> https://lists.centos.org/mailman/listinfo/centos-docs
>
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-docs] Sending git changes on the centos-docs for centos.org website

[Mark L Sung]

Thank you Fabian :-)
Xlord

On Wed, Jul 12, 2017 at 1:47 AM, Fabian Arrotin  wrote:

> Hi,
>
> Just to let you know that we decided to send all the git notifications
> to the centos-docs list for the centos.org website. The git repository
> is hosted on https://git.centos.org/summary/?r=websites/centos.org.git
> (will be open soon)
>
> It's low-traffic, so centos-docs list will not receive a huge amount of
> notifications, but at least some people on the list will get
> notification when a git commit was done.
>
> --
> Fabian Arrotin
> The CentOS Project | http://www.centos.org
> gpg key: 56BEC54E | twitter: @arrfab
>
>
> ___
> CentOS-docs mailing list
> CentOS-docs@centos.org
> https://lists.centos.org/mailman/listinfo/centos-docs
>
>
___
CentOS-docs mailing list
CentOS-docs@centos.org
https://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS-virt] Live Migration and LibVirt CPU Mode

[Mark L Sung]

Dear Oisin,
I would recommend you do the offline migration(Export/Import) instead due
to CPU spec are different, refer link--> "
https://bugs.launchpad.net/nova/+bug/1082414; and "
https://review.openstack.org/#/c/161944/2;. This save a lot more time
instead of bug digging.

Hope that helps.
Xlord

On Thu, Jul 6, 2017 at 9:29 AM, Oisin O'Malley 
wrote:

> Hi All,
>
> First time mailing here, I hope someone can help. We’re running a
> OpenStack Newton environment on top of CentOS-7.3, LibVirt and Qemu-KVM-EV.
> We are encountered an issue live migrating a VM between 2 hosts with
> different CPUs and LibVirt throws the following error:
>
> libvirtError: unsupported configuration: guest and host CPU are not
> compatible: Host CPU does not provide required features: fma, x2apic,
> movbe, tsc-deadline, xsave, osxsave, avx, f16c, rdrand, fsgsbase,
> tsc_adjust, bmi1, hle, avx2, smep, bmi2, erms, invpcid, rtm, rdseed, adx,
> smap, xsaveopt, abm, 3dnowprefetch; try using 'Broadwell-noTSX' CPU model.
>
>
> LibVirt appears to be comparing the source and destination host CPUs,
> instead of guest VM and destination host CPUs. The VM is configured with a
> common set CPU features that are compatible with both (see below) and can
> run on both hosts without issue. The hosts have Westmere and Broadwell CPUs
> (See host CPU capabilities below). The VM can be booted on the Westmere
> host, successfully live migrated to the Broadwell host, but then throws the
> above error when we attempt to live migrating back to the Westmere host.
>
> Due to how our Westmere hosts were configured in OpenStack Nova, the VMs
> CPU is configured with "cpu mode='host-model'", which fail to migrate. BUT
> if the VMs CPU is configured with "cpu mode='custom' match='exact'" it can
> be successfully migrate both ways. It appears that when a VMs CPU is
> configured with "cpu mode='host-model'" the guests CPU is ignored and the
> host CPUs are compared instead. Which I believe is incorrect behaviour, is
> this a known issue and/or have any workarounds.
>
> The VMs will be configure to use "cpu mode='custom'" with a Westmere model
> on their next reboot, but rebooting all VMs prior to migration is something
> we really want to avoid.
>
> There has already been some discussion on this issue on the OpenStack
> mailing list: http://lists.openstack.org/pipermail/openstack/2017-July/
> thread.html#45139
>
> The following package versions are being used;
> libvirt-daemon-kvm.x86_642.0.0-10.el7_3.4
> qemu-kvm-ev.x86_6410:2.6.0-28.el7_3.3.1
> kernel.x86_643.10.0-514.16.1.el7
>
>
> The Qemu-KVM processes CPU parameters of the running VMs;
>
> -cpu Westmere,+vme,+ds,+acpi,+ss,+ht,+tm,+pbe,+pclmuldq,+dtes64,
> +monitor,+ds_cpl,+vmx,+smx,+est,+tm2,+xtpr,+pdcm,+pcid,+
> dca,+arat,+pdpe1gb,+rdtscp
>
>
> Guest CPU Configuration that fails to migrate;
>
> 
> Westmere
> Intel
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>   
>
>
> Guest CPU Configuration that successfully migrates;
>
>   
> Westmere
> 
>   
>
>
> Westmere Hosts CPU capabilities;
>
> 
>   x86_64
>   Westmere
>   Intel
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>
> Broadwell Host CPU Capabilities;
>
> 
>   x86_64
>   Broadwell
>   Intel
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
> 
>
> Regards,
> Oisin
>
> Oisin O'Malley
> Systems Engineer
> Iocane Pty Ltd
> 763 South Road
> Black Forest SA 5035
>
> Office:+61 (8) 8413 1010
> Fax:+61 (8) 8231 2050
> Email:oisin.omal...@iocane.com.au
> Web:www.iocane.com.au
>
> Better for business
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] What is the purpose setting console=hvc0 in the dom0 grub config?

[Mark L Sung]

Jerry,
Refer to console=hvc0 from (https://wiki.xen.org/wiki/Xen_FAQ_Console)which
is dedicated for domO after Xen kernel loaded, so if it hangs it means
somewhere the booting process with xen is not right.

Suggest you to close look at the dmsg or log for debugging. Hope that helps
and cheers.

Xlord

On Wed, May 17, 2017 at 11:26 AM, Jerry  wrote:

> Howdy,
>
> I recently went through a frustrating experience trying to get Xen 4
> running on a CentOS 7 system.  After a fresh install, fully updating the
> system, rebooting, then trying to install Xen4CentOS it would fail to boot
> into the 4.9 kernel, sitting there with a blinking cursor indefinitely.
>
> I thought it was a failure with grub, but it turns out this was set in the
> grub config:
>
> GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT="console=hvc0 ..."
>
> So the kernel was loading successfully, but it was failing boot properly
> (hanging because it couldn't find the / file system, but that's a different
> story). Boot messages were not being displayed on my console because of the
> console=hvc0 setting, hampering the troubleshooting process.
>
> What is the purpose of setting console=hvc0?  I removed it so I could
> trouble shoot this problem, but I didn't re-add it and the system booted
> fine, Xen is working.  Is there something that depends on this?
>
> I always disable "rhgb quiet" on a fresh install because I don't like boot
> messages being hidden from me, and now this other thing does it.  I like
> details, I need the details, don't hide them from me.
>
> Thanks,
> Jerry
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

[Mark L Sung]

Hu, seems there are still stability issues on the
"4.9.2-26.el7.x86_64", recently hear many issue related to Supermicro
board! :-(

Peace!!!

On Fri, Apr 21, 2017 at 9:40 AM, Anderson, Dave 
wrote:

> Good news/bad news testing the new kernel on CentOS7 with my now
> notoriously finicky machines:
>
> Good news: 4.9.23-26.el7 (grabbed today via yum update) isn't any worse
> than 4.9.13-22 was on my xen hosts (as far as I can tell so far at least)
>
> Bad news: It isn't any better than 4.9.13 was for me either, if I don't
> set vcpu limit in the grub/xen config, it still panics like so:
>
> [6.716016] CPU: Physical Processor ID: 0
> [6.720199] CPU: Processor Core ID: 0
> [6.724046] mce: CPU supports 2 MCE banks
> [6.728239] Last level iTLB entries: 4KB 512, 2MB 8, 4MB 8
> [6.733884] Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32, 1GB 0
> [6.740770] Freeing SMP alternatives memory: 32K (821a8000 -
> 821b)
> [6.750638] ftrace: allocating 34344 entries in 135 pages
> [6.771888] smpboot: Max logical packages: 1
> [6.776363] VPMU disabled by hypervisor.
> [6.780479] Performance Events: SandyBridge events, PMU not available
> due to virtualization, using software events only.
> [6.792237] NMI watchdog: disabled (cpu0): hardware events not enabled
> [6.798943] NMI watchdog: Shutting down hard lockup detector on all cpus
> [6.805949] installing Xen timer for CPU 1
> [6.810659] installing Xen timer for CPU 2
> [6.815317] installing Xen timer for CPU 3
> [6.819947] installing Xen timer for CPU 4
> [6.824618] installing Xen timer for CPU 5
> [6.829282] installing Xen timer for CPU 6
> [6.833935] installing Xen timer for CPU 7
> [6.838565] installing Xen timer for CPU 8
> [6.843110] smpboot: Package 1 of CPU 8 exceeds BIOS package data 1.
> [6.849475] [ cut here ]
> [6.854091] kernel BUG at arch/x86/kernel/cpu/common.c:997!
> [6.855864] random: fast init done
> [6.863070] invalid opcode:  [#1] SMP
> [6.867088] Modules linked in:
> [6.870168] CPU: 8 PID: 0 Comm: swapper/8 Not tainted
> 4.9.23-26.el7.x86_64 #1
> [6.877298] Hardware name: Supermicro X9DRT/X9DRT, BIOS 3.2a 08/04/2015
> [6.883920] task: 880058a6a5c0 task.stack: c900400c
> [6.889840] RIP: e030:[]  []
> identify_secondary_cpu+0x57/0x80
> [6.898756] RSP: e02b:c900400c3f08  EFLAGS: 00010086
> [6.904069] RAX: ffe4 RBX: 88005d80a020 RCX:
> 81e5ffc8
> [6.911201] RDX: 0001 RSI: 0005 RDI:
> 0005
> [6.918335] RBP: c900400c3f18 R08: 00ce R09:
> 
> [6.925466] R10: 0005 R11: 0006 R12:
> 0008
> [6.932599] R13:  R14:  R15:
> 
> [6.939735] FS:  () GS:88005d80()
> knlGS:
> [6.947819] CS:  e033 DS: 002b ES: 002b CR0: 80050033
> [6.953565] CR2:  CR3: 01e07000 CR4:
> 00042660
> [6.960696] Stack:
> [6.962731]  0008  c900400c3f28
> 8104ebce
> [6.970205]  c900400c3f40 81029855 
> c900400c3f50
> [6.977691]  810298d0  
> 
> [6.985164] Call Trace:
> [6.987626]  [] smp_store_cpu_info+0x3e/0x40
> [6.993480]  [] cpu_bringup+0x35/0x90
> [6.998700]  [] cpu_bringup_and_idle+0x20/0x40
> [7.004706] Code: 44 89 e7 ff 50 68 0f b7 93 d2 00 00 00 39 d0 75 1c 0f
> b7 bb da 00 00 00 44 89 e6 e8 e4 02 01 00 85 c0 75 07 5b 41 5c 5d c3 0f 0b
> <0f> 0b 0f b7 8b d4 00 00 00 89 c2 44 89 e6 48 c7 c7 90 d3 ca 81
> [7.024976] RIP  [] identify_secondary_cpu+0x57/0x80
> [7.031528]  RSP 
> [7.035032] ---[ end trace f2a8d75941398d9f ]---
> [7.039658] Kernel panic - not syncing: Attempted to kill the idle task!
>
> So...other than my work around...that still works...not sure what else I
> can provide in the way of feedback/testing. But if you want anything else
> gathered, let me know.
>
> Thanks,
> -Dave
>
> --
> Dave Anderson
>
>
> > On Apr 19, 2017, at 10:33 AM, Johnny Hughes  wrote:
> >
> > On 04/19/2017 12:18 PM, PJ Welsh wrote:
> >>
> >> On Wed, Apr 19, 2017 at 5:40 AM, Johnny Hughes  >> > wrote:
> >>
> >>On 04/18/2017 12:39 PM, PJ Welsh wrote:
> >>> Here is something interesting... I went through the BIOS options and
> >>> found that one R710 that *is* functioning only differed in that
> "Logical
> >>> Processor"/Hyperthreading was *enabled* while the one that is *not*
> >>> functioning had HT *disabled*. Enabled Logical Processor and the system
> >>> starts without issue! I've rebooted 3 times now without issue.
> >>> Dell R710 BIOS version 6.4.0
> >>> 2x 

Re: [CentOS-virt] Xen C6 kernel 4.9.13 and testing 4.9.15 only reboots.

[Mark L Sung]

So interesting and challenging too, IT seems to Xen compatibility to Dell
board BIOS related.

I have Dell R710 and R7200 with same Xen version, but the outcome is
completely different, that R720 is slow in performance and reboot too.

xlord

On Apr 5, 2017 23:42, "PJ Welsh"  wrote:

> On Tue, Apr 4, 2017 at 11:13 AM, Johnny Hughes  wrote:
>
>> On 03/28/2017 04:55 PM, PJ Welsh wrote:
>> > The mystery gets more interesting... I now have a CentOS 7.3 Dell R710
>> > server doing the exact same thing of rebooting immediately after the Xen
>> > kernel load. Just to note this is a second system and not just the first
>> > system with an update. I hope I'm not introducing something odd. They
>> > only "interesting" thing I have done for historical reasons is to change
>> > the following /etc/sysconfig/grub line:
>> > GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=6G,max:8G cpuinfo com1=115200,8n1
>> > console=com1,tty loglvl=all guest_loglvl=all"
>> > But I've done that on other servers without issue. In fact I have a Dell
>> > R710 that DOES work with CentOS 7 and the new kernel... so confused.
>> >
>> > On Fri, Mar 24, 2017 at 1:44 PM, Sarah Newman > > > wrote:
>> >
>> > On 03/24/2017 11:35 AM, PJ Welsh wrote:
>> > > As a follow up I was able to test fresh install on Dell R710 and
>> a Dell
>> > > R620 with success on CentOS 7.3 without issue on the new kernel.
>> My new
>> > > plan will be to just move this C6 to one of the C7 I just created.
>> >
>> > That sounds like a compiler problem, since I think the C6 and C7
>> > kernels are built from the same source.
>> >
>>
>> OK, I have a new CentOS-6 4.9.20-26 kernel here for testing:
>>
>> https://people.centos.org/hughesjr/4.9.16/6/x86_64/
>>
>> I am building the el7 one right now as well, it will be at:
>>
>> https://people.centos.org/hughesjr/4.9.16/7/x86_64/
>>
>> George and I found some issues with the 4.9.x config files for the xen
>> kernel.  Hopefully this one is much more stable as it has many changes
>> from the fedora/rhel type configs now (what is built into the kernel,
>> what is loaded as a kernel module, etc.)
>>
>> Please test these kernels so we can get them released.
>>
>> Thanks,
>> Johnny Hughes
>>
>>
>>
>> ___
>> CentOS-virt mailing list
>> CentOS-virt@centos.org
>> https://lists.centos.org/mailman/listinfo/centos-virt
>>
>>
> CentOS-6 4.9.20-26 kernel exhibits the same constant
> kernel-start-then-reboot issue when booting under the "CentOS Linux, with
> Xen hypervisor" grub2 menu option. However, it *does* properly boot under
> the "CentOS Linux (4.9.20-25.el7.x86_64) 7 (Core)" grub2 menu option!
>
> A semi-close look at the /etc/grub2.cfg yields no discernible difference
> between a properly functional Dell R620 and the non-properly functioning
> Dell R710.
>
> Sorry, I had been distracted with other issues and have not yet submitted
> information to the xen-devel group yet.
>
> Thanks
> PJ
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] aarch64 / Raspberry Pi3

[Mark L Sung]

Great work..will test it.

xlord

On Oct 28, 2016 15:06, "Sandro Bonazzola"  wrote:

> Hi,
> some time ago we've been asked to provide aarch64 build of qemu-kvm-ev for
> CentOS Cloud SIG consumption.
> We did it, and while at it we also built oVirt 4.0 VDSM dependencies for
> aarch64 in CentOS Virt SIG.
>
> Testing repositories have been created and are now publicly available:
>
> [centos-qemu-ev-test]
> name=CentOS-$releasever - QEMU EV Testing
> baseurl=http://buildlogs.centos.org/centos/$releasever/
> virt/$basearch/kvm-common/
> gpgcheck=1
> enabled=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
>
> [centos-ovirt40-test]
> name=CentOS-$releasever - oVirt 4.0 Testing
> baseurl=http://buildlogs.centos.org/centos/$releasever/
> virt/$basearch/ovirt-4.0/
> gpgcheck=1
> enabled=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
>
> We don't officially support aarch64 and this is highly experimental so
> expect bugs. But if you've a Raspberry Pi 3 and you decide to give VDSM a
> run, please share your feedback.
>
> Thanks,
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
>
> ___
> CentOS-virt mailing list
> CentOS-virt@centos.org
> https://lists.centos.org/mailman/listinfo/centos-virt
>
>
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt