Re: [CentOS-virt] win2008r2 update on centos 6 host made system unbootable

[Nux!]

This is pretty epic if true.
I'm installing some Fail 2008r2 now to check.

Is your hypervisor running CentOS 6 or 7?

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Dennis Jacobfeuerborn" 
> To: "Discussion about the virtualization on CentOS" 
> Sent: Wednesday, 9 December, 2015 00:00:28
> Subject: Re: [CentOS-virt] win2008r2 update on centos 6 host made system 
> unbootable

> On 09.12.2015 00:39, NightLightHosts Admin wrote:
>> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
>>  wrote:
>>> Hi,
>>> today we ran into a strange problem: When performing a regular Windows
>>> 2008r2 update apparently among other things the following was installed:
>>> "SUSE - Storage Controller - SUSE Block Driver for Windows"
>>>
>>> Previously the disk drive was using the Red Hat virtio drivers which
>>> worked just fine but after the reboot after the update I just get a blue
>>> screen indicating that Windows cannot find a boot device.
>>>
>>> Does anyone understand what is going on here? Why is the windows update
>>> installing a Suse driver that overrides the Red Hat driver even though
>>> it is apparently incompatible with the system?
>>>
>>> Regards,
>>>   Dennis
>> 
>> Did you roll back the driver and did it work after that?
> 
> I can't roll back the driver for that device because I can't boot the
> system. The only way I can boot into the system is by changing the disk
> type to IDE but then I cannot roll back the driver because the entire
> device changed. As far as I can tell the Suse version of the virtio
> block driver is incompatible with the incompatible with the system but
> right now I see no way to tell windows "Uninstall the driver completely
> for the entire system" so that on the next boot it would fall back to
> the old virtio driver from Red Hat.
> I tried installing the current stable drivers from this URL:
> https://fedoraproject.org/wiki/Windows_Virtio_Drivers
> 
> But Windows refuses and says the driver is already up-to-date.
> 
> What worries me is that I want to update other win2008r2 guests as well
> but now fear that they will all be rendered unbootable by such an update.
> 
> Regards,
>  Dennis
> 
> ___
> 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] How to manually add a new interface to a bridge device?

[Zoltan Frombach]

The MAC address you gave is fine. I use random MAC addresses just like 
you did.


Your PCI bus address also has to be unique within a given VM. I'm sorry, 
I forgot to mention that. Look at my configuration example I sent. These 
are emulated (virtual) network cards attached to the emulated (virtual) 
PCI bus of the virtual machine. Two network cards cannot have the same 
MAC address and they cannot be on the same PCI bus address either. Your 
VM's are emulated physical machines with their own BIOS, etc.


Zoltan

On 12/9/2015 10:58 AM, Howard Leadmon wrote:


How do you decide what MAC address to use for that VM interface?   As 
I just tried to change the MAC to some other value close, like I made 
'52:54:00:34:e1:21' into say '52:54:00:34:e1:32', and when I try and 
load it in, I get the following:


error: XML error: Attempted double use of PCI Address '0:0:4.0'

Here is one of my network entries:









function='0x0'/>




---

Howard

*From:*centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] *On Behalf Of *Zoltan Frombach

*Sent:* Wednesday, December 9, 2015 4:24 AM
*To:* Discussion about the virtualization on CentOS 

*Subject:* Re: [CentOS-virt] How to manually add a new interface to a 
bridge device?



You most definitely do not need to destroy and re-create a VM just to 
add a 2nd network interface.


I don't think those vnet interfaces got created by the host OS. I 
believe those are created by KVM (or libvirt) when you start a VM. I 
could be wrong though. But I just checked on my CentOS 6 KVM host 
machine and I see as many vnet interfaces as many VMs are currently 
running (or if one VM has two virtual network cards then of course 
that VM results two vnet interfaces shown on the host). Here the 
relevant part from one such VM's XML file (those XML files are under 
the /etc/libvirt/qemu directory on my CentOS host ) :



  
  
  
  function='0x0'/>



  
  
  
  function='0x0'/>



As you can see, there are two interfaces defined in this VM's XML 
file. One is connected to the host's br0 interface and the 2nd is 
connected to the host's br600 interface. You must make sure that all 
your mac addesses are unique on your network though!!


After editing a VM's XML file with your favorite editor, you need to 
execute this command:

virsh define /etc/libvirt/qemu//your-vm-name/.xml
or just simply use this editor:
virsh edit /your-vm-name/
(but I hate vi, so I use my favorite editor and when I finished 
editing I just run virsh define.)


I edited VM's XML files many times and I can add/remove virtual 
network cards without problems.


Zoltan

On 12/9/2015 9:55 AM, Howard Leadmon wrote:

Tried that as well, but this has to be something that gets set at
the OS level and loaded, as if you look at dmesg output, you can
see all the vnet?? nodes as the OS comes online.So the
question is, what is virt-install doing that creates the needed
vnet interface that is part of the bridge.   I really had to kill
and reload the VM just to load a second interface..

---

Howard Leadmon

*From:*centos-virt-boun...@centos.org

[mailto:centos-virt-boun...@centos.org] *On Behalf Of *Zoltan Frombach
*Sent:* Wednesday, December 9, 2015 2:42 AM
*To:* Discussion about the virtualization on CentOS
 
*Subject:* Re: [CentOS-virt] How to manually add a new interface
to a bridge device?

I would stop the VM, edit its definition file (that's an XML file)
and then start it up. But be careful: After you edit the XML file,
you need to execute a command so KVM re-reads that file. I forgot
that command, but you can look it up on Google.

On Dec 9, 2015 7:52 AM, "Howard Leadmon" > wrote:

Maybe my google-fu is failing me, but I have spent the past
couple hours looking at how to add a vnet? Device to my KVM
host running CentOS 6, and for the life of me I can’t get this
going.

From all my research if I want to add a device I should just
do ‘brctl addif br1 vnet14’ if I want to add a vnet14 to
bridge br1.   When I do this, I get:

# brctl addif br0 vnet14

interface vnet14 does not exist!

If I run a ‘brctl show’ I get the following:

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

   vnet3

vnet4

vnet6

vnet8

br18000.00237dd22a50   no eth1

vnet1

vnet12

vnet5

   vnet7

Re: [CentOS] tsocks or equivalent for CentOS 7

[Nux!]

http://li.nux.ro/download/nux/misc/el7/x86_64/tsocks-1.8-0.14.beta5.el7.nux.x86_64.rpm
Stolen from Fedora 22.

Enjoy

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Leroy Tennison" 
> To: centos@centos.org
> Sent: Tuesday, 8 December, 2015 22:56:12
> Subject: [CentOS] tsocks or equivalent for CentOS 7

> Does such exist? I looked for dante and couldn't find that. I found and tried
> using a version from CentOS 6 but it didn't work. If anyone can point me to an
> rpm (or set of same) I would most certainly appreciate it. Thanks.
> 
> 
> Confidentiality Notice | This email and any included attachments may be
> privileged, confidential and/or otherwise protected from disclosure.  Access 
> to
> this email by anyone other than the intended recipient is unauthorized.  If 
> you
> believe you have received this email in error, please contact the sender
> immediately and delete all copies.  If you are not the intended recipient, you
> are notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this information is strictly prohibited.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial ramdisk

[George Dunlap]

On Tue, Dec 8, 2015 at 4:17 PM, President  wrote:
> Not sure if this actually made it to the list the first time.
>
>
> Here is the SERIAL output (bottom of message after your questions).
> Googling the error indicates it's something people ran into a few years back
> but was supposedly fixed.  Any ideas?
>
>
> I can verify that if I REMOVE the second CPU, it boots into Xen kernel no
> problem.  The CPU itself doesn't matter, as I can swap either CPU into the
> first slot, and it boots.  Only if there is a second CPU does it fail.

Great, thanks for the report.  This looks like a bug in upstream Xen
-- would you mind re-posting this (with the serial output) on the
xen-users mailing list?  That will get more eyeballs on the problem.

 -George

>
>
> -Original message-
> From: George Dunlap 
> Sent: Monday 30th November 2015 6:00
> To: Discussion about the virtualization on CentOS 
> Subject: Re: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial
> ramdisk
>
>
>
> On Fri, Nov 27, 2015 at 11:18 PM, Craig Thompson
>  wrote:
>>
>> First post to this list.  I would appreciate some help on this issue.
>>
>> As background, I installed CentOS 7 on a Dell server, and then ran the
>> following commands:
>>
>> yum update
>> http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-11.el7.x86_64.rpm
>> yum --enablerepo=centos-virt-xen-testing update
>> yum --enablerepo=centos-virt-xen-testing install xen
>>
>> Doing that, I was able to successfully install Xen, create a virtual
>> machine with its own HVM setup, logical volume, etc. and boot it just fine.
>>
>> I then tried to do the same on an IBM x3550 server I’m trying to install
>> with CentOS 7.  The CentOS 7 install went just fine.  I can boot into the
>> standard kernel and have a working machine.  But after running the commands
>> above to install the Xen hypervisor, the machine hangs on boot for a few
>> moments after displaying the lines below and then reboots in a loop over and
>> over and over:
>>
>> Loading Xen 4.6.0-2.el7 …
>> Loading Linux 3.18.21-16.el7.x86_64 …
>> Loading initial ramdisk …
>>
>> It never gets beyond that.  If I choose the stock kernel (no Xen) from the
>> Grub menu, it will continue to boot into that just fine.
>>
>> My grub.cfg file has these entries of note:
>>
>>  multiboot /xen-4.6.0-2.el7.gz placeholder  dom0_mem=1024M,max:1024M
>> cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all
>> ${xen_rm_opts}
>> echo'Loading Linux 3.18.21-16.el7.x86_64 ...'
>> module  /vmlinuz-3.18.21-16.el7.x86_64 placeholder
>> root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug
>> irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset
>> echo'Loading initial ramdisk ...'
>> module  --nounzip   /initramfs-3.18.21-16.el7.x86_64.img
>>
>>
>> What I have tried:
>>
>> 1) adding debug into the vmlinuz line
>> 2) disabling ipv6 in that line
>> 3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line
>> AFTER /initramfs ….
>>
>> Nothing so far has made any difference.  Obviously the process works, as
>> it works for me just fine on the Dell server.
>>
>> Underlying this machine is a SATA RAID 1 PCI card with two SSD drives
>> attached in a RAID 1 mirror.  Not that that should matter, but I’m including
>> it for reference. As noted previously, it boots into the stock kernel just
>> fine.
>>
>> Any help would be appreciated.
>
>
> Thanks for the testing and the report.
>
> Have you tried booting the Xen4CentOS kernel (Linux-3.18.21-16) by itself
> (i.e., not under Xen)?
>
> Also, is there any chance you could get the output of a serial console?
> That's pretty critical for debugging this sort of thing.
> CentOS-virt mailing list
>
> 
>
> ###  No such file or directory opening port
> (XEN) Bad console= option 'tty'
>  Xen 4.6.0-2.el7
> (XEN) Xen version 4.6.0-2.el7 (mockbu...@centos.org) (gcc (GCC) 4.8.3
> 20140911 (Red Hat 4.8.3-9)) debug=n Tue Nov  3 17:23:39 UTC 2015
> (XEN) Latest ChangeSet: Mon Oct 19 12:05:21 2015 +0100 git:36b6fe9-dirty
> (XEN) Bootloader: GRUB 2.02~beta2
> (XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo
> com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all
> (XEN) Video information:
> (XEN)  VGA is text mode 80x25, font 8x16
> (XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
> (XEN) Disc information:
> (XEN)  Found 1 MBR signatures
> (XEN)  Found 1 EDD information structures
> (XEN) Xen-e820 RAM map:
> (XEN)   - 0009c800 (usable)
> (XEN)  0009c800 - 000a (reserved)
> (XEN)  000e - 0010 (reserved)
> (XEN)  0010 - bffcba40 (usable)
> (XEN)  bffcba40 - bffcee00 (ACPI data)
> (XEN)  bffcee00 - c000 (reserved)
> (XEN)  fec0 - 

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Zoltan Frombach]

BTW, adding a 2nd virtual nic to a guest can also be done with command 
line tools (I just googled this for you) :

https://kashyapc.fedorapeople.org/virt/add-network-card-in-guest.txt
( It came up as 1st result when I searched for: virsh add network 
interface to existing guest )


But if you look at the bottom of this guide, they also mention that if 
something goes wrong, they resort to using virsh edit just like I 
suggested to you. See, I prefer to edit a configuration file rather then 
issuing long and complicated commands on the CLI. However, being able to 
add a 2nd nic to a live guest is nice though and that could only be 
achieved with the CLI command. As you can see, you can even add nic's to 
a VM without having to reboot it.


Zoltan

On 12/9/2015 10:58 AM, Howard Leadmon wrote:


How do you decide what MAC address to use for that VM interface?   As 
I just tried to change the MAC to some other value close, like I made 
'52:54:00:34:e1:21' into say '52:54:00:34:e1:32', and when I try and 
load it in, I get the following:


error: XML error: Attempted double use of PCI Address '0:0:4.0'

Here is one of my network entries:









function='0x0'/>




---

Howard

*From:*centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] *On Behalf Of *Zoltan Frombach

*Sent:* Wednesday, December 9, 2015 4:24 AM
*To:* Discussion about the virtualization on CentOS 

*Subject:* Re: [CentOS-virt] How to manually add a new interface to a 
bridge device?



You most definitely do not need to destroy and re-create a VM just to 
add a 2nd network interface.


I don't think those vnet interfaces got created by the host OS. I 
believe those are created by KVM (or libvirt) when you start a VM. I 
could be wrong though. But I just checked on my CentOS 6 KVM host 
machine and I see as many vnet interfaces as many VMs are currently 
running (or if one VM has two virtual network cards then of course 
that VM results two vnet interfaces shown on the host). Here the 
relevant part from one such VM's XML file (those XML files are under 
the /etc/libvirt/qemu directory on my CentOS host ) :



  
  
  
  function='0x0'/>



  
  
  
  function='0x0'/>



As you can see, there are two interfaces defined in this VM's XML 
file. One is connected to the host's br0 interface and the 2nd is 
connected to the host's br600 interface. You must make sure that all 
your mac addesses are unique on your network though!!


After editing a VM's XML file with your favorite editor, you need to 
execute this command:

virsh define /etc/libvirt/qemu//your-vm-name/.xml
or just simply use this editor:
virsh edit /your-vm-name/
(but I hate vi, so I use my favorite editor and when I finished 
editing I just run virsh define.)


I edited VM's XML files many times and I can add/remove virtual 
network cards without problems.


Zoltan

On 12/9/2015 9:55 AM, Howard Leadmon wrote:

Tried that as well, but this has to be something that gets set at
the OS level and loaded, as if you look at dmesg output, you can
see all the vnet?? nodes as the OS comes online.So the
question is, what is virt-install doing that creates the needed
vnet interface that is part of the bridge.   I really had to kill
and reload the VM just to load a second interface..

---

Howard Leadmon

*From:*centos-virt-boun...@centos.org

[mailto:centos-virt-boun...@centos.org] *On Behalf Of *Zoltan Frombach
*Sent:* Wednesday, December 9, 2015 2:42 AM
*To:* Discussion about the virtualization on CentOS
 
*Subject:* Re: [CentOS-virt] How to manually add a new interface
to a bridge device?

I would stop the VM, edit its definition file (that's an XML file)
and then start it up. But be careful: After you edit the XML file,
you need to execute a command so KVM re-reads that file. I forgot
that command, but you can look it up on Google.

On Dec 9, 2015 7:52 AM, "Howard Leadmon" > wrote:

Maybe my google-fu is failing me, but I have spent the past
couple hours looking at how to add a vnet? Device to my KVM
host running CentOS 6, and for the life of me I can’t get this
going.

From all my research if I want to add a device I should just
do ‘brctl addif br1 vnet14’ if I want to add a vnet14 to
bridge br1.   When I do this, I get:

# brctl addif br0 vnet14

interface vnet14 does not exist!

If I run a ‘brctl show’ I get the following:

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

  

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Howard Leadmon]

How do you decide what MAC address to use for that VM interface?   As I just
tried to change the MAC to some other value close, like I made
'52:54:00:34:e1:21' into say '52:54:00:34:e1:32', and when I try and load it
in, I get the following:

 

error: XML error: Attempted double use of PCI Address '0:0:4.0'

 

 

Here is one of my network entries:

 



  

  

  

  



 

 

---

Howard 

 

From: centos-virt-boun...@centos.org [mailto:centos-virt-boun...@centos.org]
On Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 4:24 AM
To: Discussion about the virtualization on CentOS 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge
device?

 


You most definitely do not need to destroy and re-create a VM just to add a
2nd network interface.

I don't think those vnet interfaces got created by the host OS. I believe
those are created by KVM (or libvirt) when you start a VM. I could be wrong
though. But I just checked on my CentOS 6 KVM host machine and I see as many
vnet interfaces as many VMs are currently running (or if one VM has two
virtual network cards then of course that VM results two vnet interfaces
shown on the host). Here the relevant part from one such VM's XML file
(those XML files are under the /etc/libvirt/qemu directory on my CentOS host
) :


  
  
  
  


  
  
  
  


As you can see, there are two interfaces defined in this VM's XML file. One
is connected to the host's br0 interface and the 2nd is connected to the
host's br600 interface. You must make sure that all your mac addesses are
unique on your network though!!

After editing a VM's XML file with your favorite editor, you need to execute
this command:
virsh define /etc/libvirt/qemu/your-vm-name.xml
or just simply use this editor:
virsh edit your-vm-name
(but I hate vi, so I use my favorite editor and when I finished editing I
just run virsh define.)

I edited VM's XML files many times and I can add/remove virtual network
cards without problems.

Zoltan

On 12/9/2015 9:55 AM, Howard Leadmon wrote:

Tried that as well, but this has to be something that gets set at the OS
level and loaded, as if you look at dmesg output, you can see all the vnet??
nodes as the OS comes online.So the question is, what is virt-install
doing that creates the needed vnet interface that is part of the bridge.   I
really had to kill and reload the VM just to load a second interface..

 

 

---

Howard Leadmon 

 

From: centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] On Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 2:42 AM
To: Discussion about the virtualization on CentOS
 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge
device?

 

I would stop the VM, edit its definition file (that's an XML file) and then
start it up. But be careful: After you edit the XML file, you need to
execute a command so KVM re-reads that file. I forgot that command, but you
can look it up on Google.

On Dec 9, 2015 7:52 AM, "Howard Leadmon"  > wrote:

 

Maybe my google-fu is failing me, but I have spent the past couple hours
looking at how to add a vnet? Device to my KVM host running CentOS 6, and
for the life of me I can't get this going.

 

>From all my research if I want to add a device I should just do 'brctl addif
br1 vnet14' if I want to add a vnet14 to bridge br1.   When I do this, I
get:

 

# brctl addif br0 vnet14

interface vnet14 does not exist!

 

 

If I run a 'brctl show' I get the following:

 

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

   vnet3

vnet4

vnet6

vnet8

br1 8000.00237dd22a50   no  eth1

vnet1

vnet12

vnet5

vnet7

vnet9

 

 

Needless to say the existing vnet?? Devices are in use on guest VM's
currently.

 

When I create a new VM using virt-install, I usually add the following 

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Zoltan Frombach]

You most definitely do not need to destroy and re-create a VM just to 
add a 2nd network interface.


I don't think those vnet interfaces got created by the host OS. I 
believe those are created by KVM (or libvirt) when you start a VM. I 
could be wrong though. But I just checked on my CentOS 6 KVM host 
machine and I see as many vnet interfaces as many VMs are currently 
running (or if one VM has two virtual network cards then of course that 
VM results two vnet interfaces shown on the host). Here the relevant 
part from one such VM's XML file (those XML files are under the 
/etc/libvirt/qemu directory on my CentOS host ) :



  
  
  
  function='0x0'/>



  
  
  
  function='0x0'/>



As you can see, there are two interfaces defined in this VM's XML file. 
One is connected to the host's br0 interface and the 2nd is connected to 
the host's br600 interface. You must make sure that all your mac 
addesses are unique on your network though!!


After editing a VM's XML file with your favorite editor, you need to 
execute this command:

virsh define /etc/libvirt/qemu//your-vm-name/.xml
or just simply use this editor:
virsh edit /your-vm-name/
(but I hate vi, so I use my favorite editor and when I finished editing 
I just run virsh define.)


I edited VM's XML files many times and I can add/remove virtual network 
cards without problems.


Zoltan

On 12/9/2015 9:55 AM, Howard Leadmon wrote:


Tried that as well, but this has to be something that gets set at the 
OS level and loaded, as if you look at dmesg output, you can see all 
the vnet?? nodes as the OS comes online.So the question is, what 
is virt-install doing that creates the needed vnet interface that is 
part of the bridge.   I really had to kill and reload the VM just to 
load a second interface..


---

Howard Leadmon

*From:*centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] *On Behalf Of *Zoltan Frombach

*Sent:* Wednesday, December 9, 2015 2:42 AM
*To:* Discussion about the virtualization on CentOS 

*Subject:* Re: [CentOS-virt] How to manually add a new interface to a 
bridge device?


I would stop the VM, edit its definition file (that's an XML file) and 
then start it up. But be careful: After you edit the XML file, you 
need to execute a command so KVM re-reads that file. I forgot that 
command, but you can look it up on Google.


On Dec 9, 2015 7:52 AM, "Howard Leadmon" > wrote:


Maybe my google-fu is failing me, but I have spent the past couple
hours looking at how to add a vnet? Device to my KVM host running
CentOS 6, and for the life of me I can’t get this going.

From all my research if I want to add a device I should just do
‘brctl addif br1 vnet14’ if I want to add a vnet14 to bridge
br1.   When I do this, I get:

# brctl addif br0 vnet14

interface vnet14 does not exist!

If I run a ‘brctl show’ I get the following:

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

   vnet3

vnet4

vnet6

vnet8

br18000.00237dd22a50   no  eth1

vnet1

vnet12

vnet5

   vnet7

vnet9

Needless to say the existing vnet?? Devices are in use on guest
VM’s currently.

When I create a new VM using virt-install, I usually add the
following to my command line:

--network=bridge:br0 --network=bridge:br1

I messed up building a new VM, and only added the br0 interface to
the VM, but need the br1 interface as well.  So my question is, or
a pointer to how I can add that br1 interface to my existing VM,
and create the needed vnet14 interface for it to attach to?

If anyone can explain how to do this, or give me a good pointer on
where the info is on how to do this, it would sure be a huge help..

Thanks…

---

Howard Leadmon


___
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] USB devices - libgphoto2 - PTP - hplip

[Michael H]

Hi All,

I'm trying to disable USB storage devices in Centos7.1.1503.

I've setup udev rules to block all usb devices and then additional rules
to allow specific vendors / products to be used (mainly keyboards and
mice). This is all working perfectly.

cat /etc/udev/rules.d/01-usblockdown.rules
# Block all USB devices
ACTION=="add", SUBSYSTEMS=="usb", RUN+="/bin/sh -c 'for host in
/sys/bus/usb/devices/usb*; do echo 0 > $host/authorized_default; done'"
# Allow devices
# Keyboards
ACTION=="add", ATTR{idVendor}=="04f3", ATTR{idProduct}=="0103"
RUN+="/bin/sh -c 'echo 1 >/sys$DEVPATH/authorized'"
..

Now I'm testing against mobile devices and when I connect an Asus mobile
telephone it's mounting the camera using PTP even though the device is
not allowed in my udev rules.

I removed libgphoto2 which has now stopped the PTP from automounting.

My issue is that I require hplip on my systems for certain printer
drivers and this package was removed along with libgphoto2. I added an
'exclude=libgphoto2*' to my /etc/yum.repos.d/CentOS-Base.repo and
installing hplip now fails on dependencies.

Is there a method of disable libgphoto2 PTP without having to remove the
package? or can I create further udev rules to stop PTP mounts?

thanks in advance,

Michael
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Howard Leadmon]

Tried that as well, but this has to be something that gets set at the OS level 
and loaded, as if you look at dmesg output, you can see all the vnet?? nodes as 
the OS comes online.So the question is, what is virt-install doing that 
creates the needed vnet interface that is part of the bridge.   I really had to 
kill and reload the VM just to load a second interface..

 

 

---

Howard Leadmon 

 

From: centos-virt-boun...@centos.org [mailto:centos-virt-boun...@centos.org] On 
Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 2:42 AM
To: Discussion about the virtualization on CentOS 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge 
device?

 

I would stop the VM, edit its definition file (that's an XML file) and then 
start it up. But be careful: After you edit the XML file, you need to execute a 
command so KVM re-reads that file. I forgot that command, but you can look it 
up on Google.

On Dec 9, 2015 7:52 AM, "Howard Leadmon"  > wrote:

 

Maybe my google-fu is failing me, but I have spent the past couple hours 
looking at how to add a vnet? Device to my KVM host running CentOS 6, and for 
the life of me I can’t get this going.

 

>From all my research if I want to add a device I should just do ‘brctl addif 
>br1 vnet14’ if I want to add a vnet14 to bridge br1.   When I do this, I get:

 

# brctl addif br0 vnet14

interface vnet14 does not exist!

 

 

If I run a ‘brctl show’ I get the following:

 

# brctl show

bridge name bridge id   STP enabled interfaces

br0 8000.00237dd22a4c   no  eth0

vnet0

vnet10

vnet11

vnet13

vnet2

   vnet3

vnet4

vnet6

vnet8

br1 8000.00237dd22a50   no  eth1

vnet1

vnet12

vnet5

vnet7

vnet9

 

 

Needless to say the existing vnet?? Devices are in use on guest VM’s currently.

 

When I create a new VM using virt-install, I usually add the following to my 
command line:

 

--network=bridge:br0 --network=bridge:br1

 

I messed up building a new VM, and only added the br0 interface to the VM, but 
need the br1 interface as well.  So my question is, or a pointer to how I can 
add that br1 interface to my existing VM, and create the needed vnet14 
interface for it to attach to?

 

If anyone can explain how to do this, or give me a good pointer on where the 
info is on how to do this, it would sure be a huge help..

 

Thanks…

 

 

---

Howard Leadmon 

 


___
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] win2008r2 update on centos 6 host made system unbootable

[Dennis Jacobfeuerborn]

On 09.12.2015 13:47, Patrick Bervoets wrote:
> 
> 
> Op 09-12-15 om 01:00 schreef Dennis Jacobfeuerborn:
>> On 09.12.2015 00:39, NightLightHosts Admin wrote:
>>> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
>>>  wrote:
 Hi,
 today we ran into a strange problem: When performing a regular Windows
 2008r2 update apparently among other things the following was
 installed:
 "SUSE - Storage Controller - SUSE Block Driver for Windows"

 [...]
 [...]
 What worries me is that I want to update other win2008r2 guests as well
 but now fear that they will all be rendered unbootable by such an
 update.

 Regards,
Dennis

 ___
 CentOS-virt mailing list
 CentOS-virt@centos.org
 https://lists.centos.org/mailman/listinfo/centos-virt

> 
> Which virtualization are you using? KVM?
> 
> How did you get that update offered?
> 
> I can't reproduce it, but then my servers are on a patch management
> software.
> And I can't check on WU because I don't want to install the new update
> client.
> 
> Anyway, I would uncheck that patch when updating the other guests if I
> were you. And work on a copy / snapshot.

Yes, this is a CentOS 6 Host using regular libvirt based virtualization.
The Suse driver is apparently an optional update that gets delivered
using the regular Microsoft update mechanism.
It's hard to believe that they didn't catch a completely broken driver
during QA so my hypothesis is that maybe the new Virtio driver is
incompatible only with the older Kernel of CentOS 6 and that this wasn't
properly tested. To verify this one could check if the same thing
happens on a CentOS 7 Host but at the moment I'm to busy the check this.

Regards,
  Dennis


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] win2008r2 update on centos 6 host made system unbootable

[Patrick Bervoets]

Op 09-12-15 om 01:00 schreef Dennis Jacobfeuerborn:

On 09.12.2015 00:39, NightLightHosts Admin wrote:

On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn
 wrote:

Hi,
today we ran into a strange problem: When performing a regular Windows
2008r2 update apparently among other things the following was installed:
"SUSE - Storage Controller - SUSE Block Driver for Windows"

[...]
[...]
What worries me is that I want to update other win2008r2 guests as well
but now fear that they will all be rendered unbootable by such an update.

Regards,
   Dennis

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt



Which virtualization are you using? KVM?

How did you get that update offered?

I can't reproduce it, but then my servers are on a patch management software.
And I can't check on WU because I don't want to install the new update client.

Anyway, I would uncheck that patch when updating the other guests if I were 
you. And work on a copy / snapshot.

Patrick



smime.p7s
Description: S/MIME-cryptografische ondertekening
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[James B. Byrne]

On Tue, December 8, 2015 11:05, Matthew Miller wrote:

>
>> I have been bitten by things done in Fedora that only have any use
>> on
>> a laptop and that should never have been allowed into a server
>> distribution.  But I cannot see how I would have been aware of them
>> until they manifested themselves on equipment under my care.  By
>> which
>
> ^ right, this.
>
>> time it is rather too late to influence the decision to include
>> them.
>
> Well, not if you get involved early. That's the point.
>
> If you don't *want* to, that's fine, but there's only so much
> complainy cake that you can have and eat at the same time.
>

So, the implication of your suggestion, if I understand it aright, is
that I should audit all of the communication forums in use by Fedora
developers and then point out whenever any of the many dozens or
hundreds of contributors introduces something that in my opinion may
impact a server installation.  To do this I am required to obtain such
intimate personal knowledge of the internal workings of the
distribution as to be able to identify these items as soon as they are
introduced.  naturally, I am also supposed to be able to immediately
identify the negative impact of these things and prepare and present a
cogent argument against their adoption or propose patches to correct
the deficiencies that I believe that I have detected.

I am to do this whilst running a CentOS installation that will not
allow Fedora onto the premises.  SO, no doubt, the intent is that I
should run Fedora on my home systems and work diligently in my off
hours to protect any future version of CentOS from that vantage.  And
of course, if I miss something then it is my fault for not having paid
enough attention to that item.

Am I correct?

-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 6, bareos, kerberos?

[m . roth]

After upgradeding to bareos 15.2, which also has a web ui, thereby making
it usable (since the command line tool, bconsole, does not have a paging
mechanism, and its sytax for choosing files to restore is, let us say,
arcane), I've got another question: is *anyone* using bareos with
kerberos? I see that they have in alpha(?) tls support, which isn't a
great idea, given the recent vulnerabilities If you've figured out how
to use kerberos, rather than hard-coding a password in the console
configuration, I'd love to hear it.

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Lamar Owen]

On 12/09/2015 08:54 AM, James B. Byrne wrote:

So, the implication of your suggestion, if I understand it aright, is
that I should audit all of the communication forums in use by Fedora
developers and then point out whenever any of the many dozens or
hundreds of contributors introduces something that in my opinion may
impact a server installation.  

Am I correct?
Yeah, pretty much.  At least you have the ability to have some input 
upstream, unlike with Windows.


Once it is in RHEL, it is simply *going* to be in CentOS, full stop.  If 
you don't want it in CentOS, then it needs to be yelled about when it 
appears in Fedora.  Yes, this is work.  But many are already doing this 
work; it is those people whose voices are being heard; it is also some 
of those people that are making dynamic networking happen (which is 
useful for more than just laptops).


If you want your voice to be heard, you have to use your voice in the 
venue where changes can happen.  Once it is in a particular major 
version of CentOS, it is simply not going away (unless RHEL removes it).



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-es] Algun buen manual para la configuración de un VPN - con Router

[Sergio Andres Aguirre Barragan]

Buenas dias,

Amigos linuxeros, alguien tiene algun manual con bunos paso a paso de la
configuracion de una vpn.


Quedo atento muchas gracias



Sergio Andrés Aguirre Barragan
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Scott Robbins]

On Wed, Dec 09, 2015 at 09:37:33AM -0500, Lamar Owen wrote:
> On 12/09/2015 08:54 AM, James B. Byrne wrote:
> >So, the implication of your suggestion, if I understand it aright, is
> >that I should audit all of the communication forums in use by Fedora
> >developers and then point out whenever any of the many dozens or
> >hundreds of contributors introduces something that in my opinion may
> >impact a server installation.  
> 
> If you want your voice to be heard, you have to use your voice in
> the venue where changes can happen.  Once it is in a particular
> major version of CentOS, it is simply not going away (unless RHEL
> removes it).
> 

The best place to keep track is probably the Fedora testing list.  Adam
Williamson, among others, does listen to reasonable disagreements and some
decisions that would be bad for a server O/S do get turned down.

-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Wed, Dec 09, 2015 at 08:54:56AM -0500, James B. Byrne wrote:
> So, the implication of your suggestion, if I understand it aright, is
> that I should audit all of the communication forums in use by Fedora
> developers and then point out whenever any of the many dozens or
> hundreds of contributors introduces something that in my opinion may
> impact a server installation.  To do this I am required to obtain such
> intimate personal knowledge of the internal workings of the
> distribution as to be able to identify these items as soon as they are
> introduced.  naturally, I am also supposed to be able to immediately
> identify the negative impact of these things and prepare and present a
> cogent argument against their adoption or propose patches to correct
> the deficiencies that I believe that I have detected.

Yes, that's basically how it works — but you don't actually have to go
to that elaborate scale to make a difference. That's why I suggested
getting involved with Fedora Server, not "auditing all of the
communication forums". We (Fedora) also work hard on making sure that
proposed and planned changes are communicated. Following the Devel
Announce list
 
   https://lists.fedoraproject.org/pipermail/devel-announce/

is a relatively low-traffic, low-effort way to stay informed of major
things.

Focus on something you're interested in. When enough people do that, it
adds up.

> I am to do this whilst running a CentOS installation that will not
> allow Fedora onto the premises.  SO, no doubt, the intent is that I
> should run Fedora on my home systems and work diligently in my off
> hours to protect any future version of CentOS from that vantage.  

Working with your employer to fix the "will not allow Fedora into the
premises" part seems like a good start.

Of course, if you don't like all of this — and from your tone, it
sounds very much like you don't — there's another obvious path where
you can have an impact. That's to pay for Red Hat Enterprise Linux, and
to submit feedback and problems through the official channels that
provides.


>And
> of course, if I miss something then it is my fault for not having paid
> enough attention to that item.

I don't think _fault_ comes into it. It's not about blame; it's just
that when no one does something, that something doesn't happen.

-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2015:2594 Moderate CentOS 6 libpng Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2594 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2594.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
e4b2fabf9c232b1a84e677df640aceab8b089e72781bec4fcca347d984e581d1  
libpng-1.2.49-2.el6_7.i686.rpm
c3b0f3d20047a8cef357a96171787aaffcf74ae93bb0b0faff1bca3001315586  
libpng-devel-1.2.49-2.el6_7.i686.rpm
c37977232c45d61ad118af010e21d611c4e98403b87ffd76bc645474c8754a2e  
libpng-static-1.2.49-2.el6_7.i686.rpm

x86_64:
e4b2fabf9c232b1a84e677df640aceab8b089e72781bec4fcca347d984e581d1  
libpng-1.2.49-2.el6_7.i686.rpm
0f18ee677b60fe81a24f200cc8db1c9bde26a404cc812e77a73b2bcfd4dd40de  
libpng-1.2.49-2.el6_7.x86_64.rpm
c3b0f3d20047a8cef357a96171787aaffcf74ae93bb0b0faff1bca3001315586  
libpng-devel-1.2.49-2.el6_7.i686.rpm
6e30263282f29b65af97733f7704647e615ff857902ebf87927ba276a5230e3a  
libpng-devel-1.2.49-2.el6_7.x86_64.rpm
8d2cc2d3ed0e4c3d794c847f79d98b63caae912e869ff2f6ada349b1c3c2772e  
libpng-static-1.2.49-2.el6_7.x86_64.rpm

Source:
e756441baabe4038f09eb9dbe4207e83d347f21cbe805eb4956c2cd961a891db  
libpng-1.2.49-2.el6_7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] tsocks or equivalent for CentOS 7

[Leroy Tennison]

Thanks, I got swamped after sending this but will get back to it soon.

- Original Message -
From: "Nux!" 
To: "CentOS mailing list" 
Sent: Wednesday, December 9, 2015 3:16:21 AM
Subject: Re: [CentOS] tsocks or equivalent for CentOS 7

http://li.nux.ro/download/nux/misc/el7/x86_64/tsocks-1.8-0.14.beta5.el7.nux.x86_64.rpm
Stolen from Fedora 22.

Enjoy

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
> From: "Leroy Tennison" 
> To: centos@centos.org
> Sent: Tuesday, 8 December, 2015 22:56:12
> Subject: [CentOS] tsocks or equivalent for CentOS 7

> Does such exist? I looked for dante and couldn't find that. I found and tried
> using a version from CentOS 6 but it didn't work. If anyone can point me to an
> rpm (or set of same) I would most certainly appreciate it. Thanks.
> 
> 
> Confidentiality Notice | This email and any included attachments may be
> privileged, confidential and/or otherwise protected from disclosure.  Access 
> to
> this email by anyone other than the intended recipient is unauthorized.  If 
> you
> believe you have received this email in error, please contact the sender
> immediately and delete all copies.  If you are not the intended recipient, you
> are notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this information is strictly prohibited.
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Confidentiality Notice | This email and any included attachments may be 
privileged, confidential and/or otherwise protected from disclosure.  Access to 
this email by anyone other than the intended recipient is unauthorized.  If you 
believe you have received this email in error, please contact the sender 
immediately and delete all copies.  If you are not the intended recipient, you 
are notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Wed, Dec 09, 2015 at 11:54:57AM -0500, m.r...@5-cent.us wrote:
> Matthew Miller wrote:
> > Working with your employer to fix the "will not allow Fedora into the
> > premises" part seems like a good start.
> 
> Why? Fedora is a development, rapid change distro. I just bugged one of my

Because of the context of this conversation. We can't have user
feedback and involvement without user feedback and involvement.




-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Wed, Dec 09, 2015 at 11:45:55AM -0500, m.r...@5-cent.us wrote:
> I'm sure it's *far* too much work for, say, the fedora development team to
> put out once a quarter a notice to upstream, and maybe CentOS, Scientific
> Linux, and whatever other main user groups to inform them of major
> changes, and see the feedback

I'm not sure what you mean by "to upstream".

But overall, why do you think I'm here suggesting that CentOS users
follow Fedora development?

And, if following the actual development cycle is too hard, we actually
do produce something else that's designed for exactly what you're
asking: the actual Fedora OS releases.



-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] How to manually add a new interface to a bridge device?

[Howard Leadmon]

That is exactly what I was looking for, and worked perfectly, and will now
be added to my notes on working with VM's.   I figured it was a matter of me
just not using the right search words in google, but damn if I could find
that page, and I tried.  

 

Using the info on that page, I added an interface, and it's live and
running..

 

 

---

Howard Leadmon 

 

From: centos-virt-boun...@centos.org [mailto:centos-virt-boun...@centos.org]
On Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 5:38 AM
To: Discussion about the virtualization on CentOS 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge
device?

 

BTW, adding a 2nd virtual nic to a guest can also be done with command line
tools (I just googled this for you) :
https://kashyapc.fedorapeople.org/virt/add-network-card-in-guest.txt
( It came up as 1st result when I searched for: virsh add network interface
to existing guest )

But if you look at the bottom of this guide, they also mention that if
something goes wrong, they resort to using virsh edit just like I suggested
to you. See, I prefer to edit a configuration file rather then issuing long
and complicated commands on the CLI. However, being able to add a 2nd nic to
a live guest is nice though and that could only be achieved with the CLI
command. As you can see, you can even add nic's to a VM without having to
reboot it.

Zoltan

On 12/9/2015 10:58 AM, Howard Leadmon wrote:

How do you decide what MAC address to use for that VM interface?   As I just
tried to change the MAC to some other value close, like I made
'52:54:00:34:e1:21' into say '52:54:00:34:e1:32', and when I try and load it
in, I get the following:

 

error: XML error: Attempted double use of PCI Address '0:0:4.0'

 

 

Here is one of my network entries:

 



  

  

  

  



 

 

---

Howard 

 

From: centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] On Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 4:24 AM
To: Discussion about the virtualization on CentOS
 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge
device?

 


You most definitely do not need to destroy and re-create a VM just to add a
2nd network interface.

I don't think those vnet interfaces got created by the host OS. I believe
those are created by KVM (or libvirt) when you start a VM. I could be wrong
though. But I just checked on my CentOS 6 KVM host machine and I see as many
vnet interfaces as many VMs are currently running (or if one VM has two
virtual network cards then of course that VM results two vnet interfaces
shown on the host). Here the relevant part from one such VM's XML file
(those XML files are under the /etc/libvirt/qemu directory on my CentOS host
) :


  
  
  
  


  
  
  
  


As you can see, there are two interfaces defined in this VM's XML file. One
is connected to the host's br0 interface and the 2nd is connected to the
host's br600 interface. You must make sure that all your mac addesses are
unique on your network though!!

After editing a VM's XML file with your favorite editor, you need to execute
this command:
virsh define /etc/libvirt/qemu/your-vm-name.xml
or just simply use this editor:
virsh edit your-vm-name
(but I hate vi, so I use my favorite editor and when I finished editing I
just run virsh define.)

I edited VM's XML files many times and I can add/remove virtual network
cards without problems.

Zoltan

On 12/9/2015 9:55 AM, Howard Leadmon wrote:

Tried that as well, but this has to be something that gets set at the OS
level and loaded, as if you look at dmesg output, you can see all the vnet??
nodes as the OS comes online.So the question is, what is virt-install
doing that creates the needed vnet interface that is part of the bridge.   I
really had to kill and reload the VM just to load a second interface..

 

 

---

Howard Leadmon 

 

From: centos-virt-boun...@centos.org 
[mailto:centos-virt-boun...@centos.org] On Behalf Of Zoltan Frombach
Sent: Wednesday, December 9, 2015 2:42 AM
To: Discussion about the virtualization on CentOS
 
Subject: Re: [CentOS-virt] How to manually add a new interface to a bridge
device?

 

I would stop the VM, edit its definition file (that's an XML file) and then
start it up. But be careful: After you edit the XML file, you need to
execute a command so KVM re-reads that file. I forgot that command, but you
can look it up on Google.

On Dec 9, 2015 7:52 AM, "Howard Leadmon"  > wrote:

 

Maybe my google-fu is failing me, but I have spent the past couple hours
looking at how to add a vnet? Device to my KVM host running CentOS 6, and
for the life of me I can't get this 

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[m . roth]

Matthew Miller wrote:
> On Wed, Dec 09, 2015 at 01:05:15PM -0500, m.r...@5-cent.us wrote:
>> >> Why? Fedora is a development, rapid change distro. I just bugged one
>> of
>> > Because of the context of this conversation. We can't have user
>> > feedback and involvement without user feedback and involvement.
>> So, you're saying that end users need to go poke their noses into the
>> development process, but that developers don't need to poke their noses
>> out to the end users... or at least, that's how I read what you're
>> saying.
>
> If you want to go out of your way to read it that way, it's hard to
> stop you. However, it's not what I'm saying. The development process is
> conducted in the open for a reason.

I don't see that as going "out of my way". Let's put it this way: how many
times have folks on the development side poked their nose in here - the
general redhat list is pretty dead - and asked anything? I've been here
since '09, and I *think* that maybe once, *maybe* twice, someone asked
something here, who was on that side of the house.

Perhaps, if it's open, it should be a two way street, not one way, for us
to take time from what we're being paid for, to hit that side.

Oh, and btw, we *do* have a few RH licenses... and for those who have to
deal with smart card ID cards, you can thank my manager for pushing
through native support in RHEL 7. So I guess you could say we do,
sometimes, go to the development side.

   mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-CR-announce] CEBA-2015:2562 CentOS 7 ipa BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2562 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2562.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
ad7c0dec8d5ee592d1b324b0d8403e806bd7d6b2838c5c653ab41999451a11d0  
ipa-admintools-4.2.0-15.el7.centos.3.x86_64.rpm
85ddb3435f112a139eb7d008f73132f2a823f48ccac0831875deea097b8a77af  
ipa-client-4.2.0-15.el7.centos.3.x86_64.rpm
5680100a1d32978f3df4d37208b84c10514b1743d90f5c1c869c32994e1a968a  
ipa-python-4.2.0-15.el7.centos.3.x86_64.rpm
f2cc2a982821847d506eb2fad3626b3681ec93062ae495ee047cd952a2bf183f  
ipa-server-4.2.0-15.el7.centos.3.x86_64.rpm
61a9457d063f3134a1b12a82d908ea92772a6f8c29a2bdf79c14b104faeb1569  
ipa-server-dns-4.2.0-15.el7.centos.3.x86_64.rpm
07db046a97a586d9a82fa375ee6ea2e303fdb3bfbe0286f3b22670b56b9c01e1  
ipa-server-trust-ad-4.2.0-15.el7.centos.3.x86_64.rpm

Source:
4bb02f6176c8e216a67498ed3d0f47f3f57d46329d70f47175f8386b67ea6b84  
ipa-4.2.0-15.el7.centos.3.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2572 CentOS 7 389-ds-base BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2572 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2572.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
7fa992db4a372dc71d79ea8aa7d602ab7c398d3a20a3b56927fb335a69dbb5fd  
389-ds-base-1.3.4.0-21.el7_2.x86_64.rpm
7cc5b12a09390c58771a7deba06e48f4569ac2a437f96d8a362ae31e3de0ea47  
389-ds-base-devel-1.3.4.0-21.el7_2.x86_64.rpm
b719404796df3d204edbf2a1f9784a50cbf4b6b8de01f1c21cdb5bb3a03984d0  
389-ds-base-libs-1.3.4.0-21.el7_2.x86_64.rpm

Source:
6d7f1ca53a181fc84ace0ba1393060d592df077b97c1b9e1f8bb807ace89435c  
389-ds-base-1.3.4.0-21.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CESA-2015:2552 Important CentOS 7 kernel Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2552 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2552.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
ba971bc760b43b09045ecce3cc189c2288d38a4ac234cd61038fdb82f4c69a2c  
kernel-3.10.0-327.3.1.el7.x86_64.rpm
f43d8ed284936508b8934b9907a65899f7a06e61aa84253e6187f65b0177450b  
kernel-abi-whitelists-3.10.0-327.3.1.el7.noarch.rpm
879edb6ccdeffefe015cab4f38b7624e6e9e6411641e202c8f05a7cccd258c54  
kernel-debug-3.10.0-327.3.1.el7.x86_64.rpm
ad3dcdd7fdbfb72378d3f87aed0b0c72059afe71ed97fbd05a1fab154714c0d0  
kernel-debug-devel-3.10.0-327.3.1.el7.x86_64.rpm
a7a2c92aca038115241fe0eed65a70060100a5843acf15dfd4c7b902c0fcc59a  
kernel-devel-3.10.0-327.3.1.el7.x86_64.rpm
e020ed78ae5aac637e02bec645e2e39fa07be658554599ea6eed77fb97c558a5  
kernel-doc-3.10.0-327.3.1.el7.noarch.rpm
7da46d6669072c7851c909587b57ad3fe6b2e3914da0b6003d5043a7995a6921  
kernel-headers-3.10.0-327.3.1.el7.x86_64.rpm
b9e1ce5fe49ea410f9261ed6ca0e73cf3910e481030a7552d41cb6e3a51a299a  
kernel-tools-3.10.0-327.3.1.el7.x86_64.rpm
597a75e56ec41fba5078e562c2da0e493c0178fc64c0c853d092899cfc770e06  
kernel-tools-libs-3.10.0-327.3.1.el7.x86_64.rpm
72f1f15c613957961d4900eb0bf0722069cb51010627ae4291440d3fb110575b  
kernel-tools-libs-devel-3.10.0-327.3.1.el7.x86_64.rpm
c159c6e6ce7627c52bafddd60d5c382fd299de843b96b319abc948acb55ec8ea  
perf-3.10.0-327.3.1.el7.x86_64.rpm
d7bf5f61e0808e77b9507eceacd6a9028f2e6d4e939d80a65670df5126bd7df6  
python-perf-3.10.0-327.3.1.el7.x86_64.rpm

Source:
d3a783ad75b75f32bf21fdf33596d39a2e8d80d7904f5f8e2bff6840e1a1aa4d  
kernel-3.10.0-327.3.1.el7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2567 CentOS 7 libvirt BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2567 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2567.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
3ae50e1fb098b52c5594b55b77f351bc24d179bd16ee60008a5b7ce48aedbb21  
libvirt-1.2.17-13.el7_2.2.x86_64.rpm
fda018173d27f92dbdc9b28ea518032eec6bc104059726fe7ee0bb25c5bf6009  
libvirt-client-1.2.17-13.el7_2.2.i686.rpm
496dcc0372676d0cd4327864221b29e771af9bee388c4131a898b9f4efaa846d  
libvirt-client-1.2.17-13.el7_2.2.x86_64.rpm
b55d2025fe1b587c9abc1c814ed172f916678544bc8531af31e871cdab4f9d91  
libvirt-daemon-1.2.17-13.el7_2.2.x86_64.rpm
ab21e98b79d7f212a2c7af3e490086b2741bd094a79d700b66bb9194393194a4  
libvirt-daemon-config-network-1.2.17-13.el7_2.2.x86_64.rpm
39ce4640d25fcd4126449a0d8f12855c5727c37784934968f2dc6035ccc9ce3d  
libvirt-daemon-config-nwfilter-1.2.17-13.el7_2.2.x86_64.rpm
443e1d4c6b26d10fe3b9f7584e411454657afa30aa7d369db7e3affec60f9845  
libvirt-daemon-driver-interface-1.2.17-13.el7_2.2.x86_64.rpm
e49ee89c5cd8ac5727a00090ad21d2ccd3e4347f4d8edf5e84ee6de96f2d2fe4  
libvirt-daemon-driver-lxc-1.2.17-13.el7_2.2.x86_64.rpm
1796e2b680474defdcdea98836a695f02e1d03e487b5b4b4fdddceb6ce93b024  
libvirt-daemon-driver-network-1.2.17-13.el7_2.2.x86_64.rpm
11bdbdcde3025fad061815c8c128c7e1317b6e72d42ae31c1948582a89ef9fc5  
libvirt-daemon-driver-nodedev-1.2.17-13.el7_2.2.x86_64.rpm
53f59c45f5e0f30aa984278efe3205442558789da7b11fc936804ac54a3776b8  
libvirt-daemon-driver-nwfilter-1.2.17-13.el7_2.2.x86_64.rpm
7df23976e99d3b8e00b716d22967e60290caceab81374c7410c913cd51d4c713  
libvirt-daemon-driver-qemu-1.2.17-13.el7_2.2.x86_64.rpm
db4f5c7b08508cc5c3c6bcd9630269a97917ab05f1a3500d01d48e855a17bd0c  
libvirt-daemon-driver-secret-1.2.17-13.el7_2.2.x86_64.rpm
8725def88f505cf104c3edb8cd76c097cfde4cfa874c54310ea2abea230186ae  
libvirt-daemon-driver-storage-1.2.17-13.el7_2.2.x86_64.rpm
78a957450685dfd63a4b4f6615a532fa8d67faee2831df033b45401c6ef52a71  
libvirt-daemon-kvm-1.2.17-13.el7_2.2.x86_64.rpm
cead36abe5ed36fcfcd314d44b8fc358220f8448c7ad7dac92ba8401c5745229  
libvirt-daemon-lxc-1.2.17-13.el7_2.2.x86_64.rpm
d370c02dbb51f4a12337ad9dbb954ca1de05ee0107d003172b9c677a5142d396  
libvirt-devel-1.2.17-13.el7_2.2.i686.rpm
be7791602023d18c9c4b76c445f19658d7e1517f0ab6d25f0fa76a1674371021  
libvirt-devel-1.2.17-13.el7_2.2.x86_64.rpm
8479de2a51bc2c2b07f5fb7ac44b56cac8402cd6981e25ef4ed02119c6475dfa  
libvirt-docs-1.2.17-13.el7_2.2.x86_64.rpm
44d38568199ec9687a157e33f9fc13beffdf99a11203a512fd4ba0285830a43f  
libvirt-lock-sanlock-1.2.17-13.el7_2.2.x86_64.rpm
3dee6e25a7546b0e9c6bd70b0282fbafdb510580dbf995f522f625be5c857918  
libvirt-login-shell-1.2.17-13.el7_2.2.x86_64.rpm

Source:
211af478115f9c0f8a977b3252f4e4d55152fd5688f238396242d41512a612fb  
libvirt-1.2.17-13.el7_2.2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2563 CentOS 7 mod_authnz_pam BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2563 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2563.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
eae3e64a67dca90c45662e7f4f08e48fddfb38facc58bf11a97f8e4f4f2d328a  
mod_authnz_pam-0.9.3-5.el7_2.x86_64.rpm

Source:
5683b6503d4bef5968730dcea528fc8b04f08fcf818aa930acd6128469a5197e  
mod_authnz_pam-0.9.3-5.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2566 CentOS 7 nuxwdog BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2566 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2566.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
eb5e205c05eda6d036dc1bccbc28181a58530d34c5f17a9e78c6956078db0a15  
nuxwdog-1.0.3-4.el7_2.i686.rpm
1f0c04331abf2ca51138ceac6b8febb63c57f7ae0459794da443763060d32f6e  
nuxwdog-1.0.3-4.el7_2.x86_64.rpm
61f1c48d2caeef8122b8091ee0f3ded1c4607d5c4c1b468a33dbec7cd3b93391  
nuxwdog-client-java-1.0.3-4.el7_2.x86_64.rpm
1692be8d37be572bbc5da115d8a9bf3582f5d204b2fcfe0e895fa6b746d3b488  
nuxwdog-devel-1.0.3-4.el7_2.i686.rpm
ae7d459b21cef18cf2eccacf862f8fd7cef16f2704d798ae3fd3f8a0e89a50f5  
nuxwdog-devel-1.0.3-4.el7_2.x86_64.rpm

Source:
e1e231e7da9583e249dc5664fe0090e8bd768e2a1d9c1cc4d3c9a59fa10adfae  
nuxwdog-1.0.3-4.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2573 CentOS 7 logrotate BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2573 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2573.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
1a7f89efafa8401567b0cfddec3e4aeb383a14b8d46d04b1be96d30f0e1ef794  
logrotate-3.8.6-7.el7_2.x86_64.rpm

Source:
b859fafb0f0e088cf3f41fdb969009cb8f9ec139c271b44c3cf2f0a87333c0df  
logrotate-3.8.6-7.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2568 CentOS 7 corosync BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2568 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2568.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
4b85f19375645d22c4ac665ccc7912551d35d4d3477b0061876cf83f6979bbc8  
corosync-2.3.4-7.el7_2.1.x86_64.rpm
19ddfeb74e0e58bd966f944831e0b995f35a76ebee8f45c47eb3d57c5a59ec9f  
corosynclib-2.3.4-7.el7_2.1.i686.rpm
31d81bf20d93fd784a55da62256f6a7ac711baf5a7d27f22aefc59c20109edb1  
corosynclib-2.3.4-7.el7_2.1.x86_64.rpm
071e08081530ebeadf9aca432335b152e67e4aecf8f313d1a531fbe2433b2adc  
corosynclib-devel-2.3.4-7.el7_2.1.i686.rpm
81a52d24fbeb4939daf5a58dca4c536f11816dbbff9928ed6ba28127bb8dfafb  
corosynclib-devel-2.3.4-7.el7_2.1.x86_64.rpm

Source:
f52f6aa371ec265a0c3030bc3eeca12ca11b1eb20577f976d96501e2e4fa4583  
corosync-2.3.4-7.el7_2.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2553 CentOS 7 crash BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2553 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2553.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
62051c4b07bb2b214744ad987a34819a2cc5f8be2a604247a2dde504f6a80c08  
crash-7.1.2-3.el7_2.x86_64.rpm
6cd87ea409ab8b3f7fd0fbd08b7922c761ffb811f3c7c12925d7c8fcb322ea8d  
crash-devel-7.1.2-3.el7_2.i686.rpm
ca5b55fc24114c3cd1c81d2ac2d87b476d03a301598b6a682e18f3460c7c0985  
crash-devel-7.1.2-3.el7_2.x86_64.rpm

Source:
100e4b2e407cd544007e9c4acf150ef3f46f34b7ce4d7df284983dacde870911  
crash-7.1.2-3.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CEBA-2015:2565 CentOS 7 resource-agents BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2015:2565 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-2565.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
a8d46df75574fae6ca791a7e7f21ce859f4aa9f83483181b9e5678853c4a4ff3  
resource-agents-3.9.5-54.el7_2.1.x86_64.rpm

Source:
7dc3c61770310f76ce20a5338a5479f26d126c1010525a2bbe059633a24302f8  
resource-agents-3.9.5-54.el7_2.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

[CentOS-CR-announce] CESA-2015:2595 Moderate CentOS 7 libpng12 Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2015:2595 Moderate

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-2595.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
5793f091ea43339e31b351be6e16389330c359bbb30cff2dfd9b91e71c190e14  
libpng12-1.2.50-7.el7_2.i686.rpm
1a00d6d4ea84df8fdf7ebe922fa1f3882412fb4acf4be289254cb89bc67d3798  
libpng12-1.2.50-7.el7_2.x86_64.rpm
e5c90fd9fdf2e42924b8a01ab8f6396a365e566bc0dc9a177400bf402f14877b  
libpng12-devel-1.2.50-7.el7_2.i686.rpm
57f350f0b9daa35dcc3fafce3a2d449d08aabc7165081d836f886a7f081423d8  
libpng12-devel-1.2.50-7.el7_2.x86_64.rpm

Source:
ba3dfc88fa5ffd64e9ae8fad2f880dfbd052111ea72e0b6db63c06a95a897a26  
libpng12-1.2.50-7.el7_2.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

___
CentOS-CR-announce mailing list
CentOS-CR-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-cr-announce

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Steve Clark]

On 12/09/2015 09:37 AM, Lamar Owen wrote:

On 12/09/2015 08:54 AM, James B. Byrne wrote:

So, the implication of your suggestion, if I understand it aright, is
that I should audit all of the communication forums in use by Fedora
developers and then point out whenever any of the many dozens or
hundreds of contributors introduces something that in my opinion may
impact a server installation.  

Am I correct?

Yeah, pretty much.  At least you have the ability to have some input
upstream, unlike with Windows.

Once it is in RHEL, it is simply *going* to be in CentOS, full stop.  If
you don't want it in CentOS, then it needs to be yelled about when it
appears in Fedora.  Yes, this is work.  But many are already doing this
work; it is those people whose voices are being heard; it is also some
of those people that are making dynamic networking happen (which is
useful for more than just laptops).

Hi,

I think saying that you can have some say as to what goes into Fedora is being 
a little
naive, look at systemd, many people complained about its inclusion but the 
powers to be
heard none of it, and the refrain I saw was if you don't like systemd then run 
something else.

Regards,
Steve



If you want your voice to be heard, you have to use your voice in the
venue where changes can happen.  Once it is in a particular major
version of CentOS, it is simply not going away (unless RHEL removes it).


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos




--
Stephen Clark
*NetWolves Managed Services, LLC.*
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[m . roth]

Matthew Miller wrote:
> On Wed, Dec 09, 2015 at 11:54:57AM -0500, m.r...@5-cent.us wrote:
>> Matthew Miller wrote:
>> > Working with your employer to fix the "will not allow Fedora into the
>> > premises" part seems like a good start.
>> 
>> Why? Fedora is a development, rapid change distro. I just bugged one of
>> my
>
> Because of the context of this conversation. We can't have user
> feedback and involvement without user feedback and involvement.

So, you're saying that end users need to go poke their noses into the
development process, but that developers don't need to poke their noses
out to the end users... or at least, that's how I read what you're saying.

mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Wed, Dec 09, 2015 at 01:05:15PM -0500, m.r...@5-cent.us wrote:
> >> Why? Fedora is a development, rapid change distro. I just bugged one of
> > Because of the context of this conversation. We can't have user
> > feedback and involvement without user feedback and involvement.
> So, you're saying that end users need to go poke their noses into the
> development process, but that developers don't need to poke their noses
> out to the end users... or at least, that's how I read what you're saying.

If you want to go out of your way to read it that way, it's hard to
stop you. However, it's not what I'm saying. The development process is
conducted in the open for a reason.


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Matthew Miller]

On Wed, Dec 09, 2015 at 01:15:56PM -0500, Steve Clark wrote:
> I think saying that you can have some say as to what goes into Fedora
> is being a little naive, look at systemd, many people complained
> about its inclusion but the powers to be heard none of it, and the

That's not a historically accurate picture of the process. And, I know,
because I was one of the people very skeptical of systemd's inclusion.
"Powers to be" didn't really come into it.

I'm not going to argue about systemd in specific, because that horse is
so dead that its zombie skeleton version is _also_ dead, but the
general point is important enough that I'll say it again: anyone who
puts in the effort to contribute can have a meaningful say in any and
every part of Fedora.


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[James Hogarth]

On 9 Dec 2015 9:07 p.m., "Lamar Owen"  wrote:
>

> No, it seems to me that a suitably motivated CentOS user needs to scratch
this itch; and, no, I am not volunteering, as I've followed Fedora
before..and just simply cannot give the time to it at this point in
time in my life.
>



>
> So who wants to be the CentOS-Users to Fedora liaison, likely to be one
of the most thankless jobs on the planet?
>
>

I'm an active Fedora packager and yet I dare say Mark would hate me as
liaison for I find the changes in EL7 most refreshing and look forward to
bring able to make better use of them in due course ;)

But I really do question whether someone in this industry is really not
able to spend 30 minutes or so every six months checking changes for
anything interesting.

And frankly if one isn't willing to get either get a subscription and
feedback as a paying customer or to get involved with the upstream sources
then no one does not have say in direction and one shouldn't be surprised
by that.

If it was a democracy with a vote on every possible choice then we'd never
get anywhere given the time to carry out such a survey and the vast
differences in opinions.

No, as the Debian folks say it is a meritocracy instead and those who get
stuck in and actively discuss at the right time provide the influence on
what happens next.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6, bareos, kerberos?

[m . roth]

Jonathan Billings wrote:
> On Wed, Dec 09, 2015 at 09:22:29AM -0500, m.r...@5-cent.us wrote:
>> After upgradeding to bareos 15.2, which also has a web ui, thereby
>> making it usable (since the command line tool, bconsole, does not
>> have a paging mechanism, and its sytax for choosing files to
>> restore is, let us say, arcane), I've got another question: is
>> *anyone* using bareos with kerberos? I see that they have in
>> alpha(?) tls support, which isn't a great idea, given the recent
>> vulnerabilities If you've figured out how
>> to use kerberos, rather than hard-coding a password in the console
>> configuration, I'd love to hear it.
>
> It might be worth asking this question on the bareos-users mailing
> list:
>
> https://groups.google.com/forum/#!forum/bareos-users

I tried asking questions there a couple-three times in the last month and
a half. The last time, in several days, no one even looked at the
questions, so there were zero responses.

Folks here are more willing to try to help.

I'm thinking, now, if there isn't, of just setting up apache security to
restrict the webpage, and then using a default password, like the system
name, once they're in.

mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Lamar Owen]

On 12/09/2015 11:45 AM, m.r...@5-cent.us wrote:

I'm sure it's *far* too much work for, say, the fedora development team to
put out once a quarter a notice to upstream, and maybe CentOS, Scientific
Linux, and whatever other main user groups to inform them of major
changes, and see the feedback
Someone just needs to spend the time to do it.  So who is that someone?  
The Fedora team already has their hands full; or is the Fedora team 
supposed to allocate already scarce volunteer resources to handle the 
needs of CentOS users?  (Red Hat likely already has one or more liaisons 
of this sort with the needs of Red Hat's customers in mind).


No, it seems to me that a suitably motivated CentOS user needs to 
scratch this itch; and, no, I am not volunteering, as I've followed 
Fedora before..and just simply cannot give the time to it at this 
point in time in my life.


So I shouldn't really complain, either, when a feature I use was removed 
way back then or a feature I would never use was added way back then, 
when I am getting many thousands of man-hours worth of work for free.  
If I want the right to complain, I need to ante up, either with money 
(and I did purchase and do annually renew my RHEL subscription) or with 
time (and I have done that, too, both as a Red Hat beta tester (prior to 
the Enterprise Linux / Fedora Core 'split') and by maintaining the 
PostgreSQL RPMs as a volunteer for five years, which is a far costlier 
thing to do!).  IMHO, of course.


So who wants to be the CentOS-Users to Fedora liaison, likely to be one 
of the most thankless jobs on the planet?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 6, bareos, kerberos?

[Jonathan Billings]

On Wed, Dec 09, 2015 at 09:22:29AM -0500, m.r...@5-cent.us wrote:
> After upgradeding to bareos 15.2, which also has a web ui, thereby making
> it usable (since the command line tool, bconsole, does not have a paging
> mechanism, and its sytax for choosing files to restore is, let us say,
> arcane), I've got another question: is *anyone* using bareos with
> kerberos? I see that they have in alpha(?) tls support, which isn't a
> great idea, given the recent vulnerabilities If you've figured out how
> to use kerberos, rather than hard-coding a password in the console
> configuration, I'd love to hear it.

It might be worth asking this question on the bareos-users mailing
list:

https://groups.google.com/forum/#!forum/bareos-users

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-virt] Xen4CentOS and XSA-142

[Sarah Newman]

It looks like no XSA-142 patch, which is "libxl fails to honour readonly flag 
on disks with qemu-xen" has been applied to Xen4CentOS. I assume this
was on purpose?

If not, I can have someone try adding the original patch from 
http://xenbits.xen.org/xsa/advisory-142.html and some variant of the commit from
ef6cb76026628e26e3d1ae53c50ccde1c3c78b1b 
http://xen.1045712.n5.nabble.com/xen-master-libxl-relax-readonly-check-introduced-by-XSA-142-fix-td5729704.html
 .

Thanks, Sarah
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Gordon Messmer]

On 12/09/2015 05:54 AM, James B. Byrne wrote:

So, the implication of your suggestion, if I understand it aright, is
that I should audit all of the communication forums in use by Fedora
developers and then point out whenever any of the many dozens or
hundreds of contributors introduces something that in my opinion may
impact a server installation.


I would offer that you could visit the Fedora ChangeSet page once every 
six months and see what's coming.  For the release of 24 (changes not 
yet final):

https://fedoraproject.org/wiki/Releases/24/ChangeSet

But generally, Free Software is a participation culture, where "Free" 
refers to liberty, not commerce.  You don't get to consume the goods for 
free, and also dictate your needs to the developers. If your employer 
needs features that the developers aren't currently working on, it needs 
to participate in development.  Maybe that means paying a developer.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[Gordon Messmer]

On 12/08/2015 07:46 AM, James B. Byrne wrote:

I have been bitten by things done in Fedora that only have any use on
a laptop and that should never have been allowed into a server
distribution.  But I cannot see how I would have been aware of them
until they manifested themselves on equipment under my care.  By which
time it is rather too late to influence the decision to include them.
Automatically powering down NICs comes to my mind; due the rather
nasty consequences that resulted.


Without any references, it's hard to know what you're referring to 
specifically.  However, I *think* you're talking about the Intel e1000 
ASPM bugs.  Those bugs were in the Intel NICs, and had nothing to do 
with decision making in the Fedora project.  If you're convinced that 
those features have no business in server class products, then you 
should provide that feedback to the hardware vendor who enabled ASPM in 
their BIOS (had they not done so, you would not have been affected by 
the bug).  I think you're upset at the wrong people, though I understand 
your frustration.  I was affected by that bug, too.


If you're referring to something else, I'd be curious to know what it was.


forcing highly qualified people to expend time, a very
limited resource in my experience, to learn yet another way to start a
computer system, without providing any readily discernible benefit to
them, is not likely to engender much in the way of sympathy.


Well, considerable effort was made to provide discernible benefit. If 
you find time to look at it later:

http://0pointer.de/blog/projects/systemd.html
http://0pointer.de/blog/projects/the-biggest-myths.html


We went to RedHat and ended up on CentOS because of its server
orientation.  Which to us implied something more than simple
compatibility of the software components.  If RedHats's intent is to
end up as a laptop distro then we will probably part ways at some
point.  We have a laptop distro that works well for us. It is called
OSX.  And the hardware is pretty good too.


I doubt you mean to imply that you'd use OS X as a server.  No one does 
that.  Even Apple uses Linux for its servers.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[m . roth]

Lamar Owen wrote:
> On 12/09/2015 08:54 AM, James B. Byrne wrote:
>> So, the implication of your suggestion, if I understand it aright, is
>> that I should audit all of the communication forums in use by Fedora
>> developers and then point out whenever any of the many dozens or
>> hundreds of contributors introduces something that in my opinion may
>> impact a server installation.  
>>
>> Am I correct?
> Yeah, pretty much.  At least you have the ability to have some input
> upstream, unlike with Windows.

Can't remember if I posted this here - I've posted this comment in a one
or two other places - but one thing that's always aggravated me is when
the development or architecture side simply DOES NOT TALK to end users,
but Knows How It Needs To Be.

I'm sure it's *far* too much work for, say, the fedora development team to
put out once a quarter a notice to upstream, and maybe CentOS, Scientific
Linux, and whatever other main user groups to inform them of major
changes, and see the feedback

Nahhh, who cares whether end users are happy, they'll just do what is
K3wl, never mind if it's appropriate, or overly complicated

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] wifi on servers and fedora [was Re: 7.2 kernel panic on boot]

[m . roth]

Matthew Miller wrote:
> On Wed, Dec 09, 2015 at 08:54:56AM -0500, James B. Byrne wrote:

> Working with your employer to fix the "will not allow Fedora into the
> premises" part seems like a good start.

Why? Fedora is a development, rapid change distro. I just bugged one of my
users yesterday that I'm *GOING* to update and reboot his system, since it
hasn't been rebooted in about a year and a third. And we've got cluster
members that they won't *let* us update, because it might break the
software that's running on them. Around 6.3, I think, one user found an
issue with the results from an updated system, and reran a completed job,
and the update did *not* give the correct results. We had to downgrade - I
forget what packages.

And some of these users have jobs that on bare metal (forget VMs, we can't
spare the cycles) run one to two *weeks*... and that's on clusters with
512 or over 1100 cores, or the boxes with *two* Tesla cards. Yes, we are
talking very serious scientific computing.

Absolute stability is what matters. For production machines, I worked out
a once a month maintenance window, to update and reboot.

In an environment like this, why would we want to do fedora, with its
how-many-updates in the last two days? This is why we're on CentOS, which
is *stable*.

 mark


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos