virt

virt@lists.centos.org

2 participants
1613 discussions

Experimental 3.18.12 Kernel for Xen4CentOS 6
by Johnny Hughes 08 May '15

08 May '15

All, I have compiled an experimental 3.18.12 kernel from the 3.18 LTS kernel branch from kernel.org for the Xen4Centos 6 tree. http://people.centos.org/hughesjr/xen-kernel/x86_64/ This should be considered extremely experimental at this point and is unsigned. I have tested it on 2 generic servers and it worked fine on both of those with sata and gigabit ethernet. Please test this and provide feedback on this list and George can get this into the virt6-testing tree and I'll release it along with the xen-4.4.2 rpms from there. I would think this is the logical LTS kernel to use moving forward as the 3.10.x LTS will be discontinued soon (in September 2015), and it has the longest lifetime of all the LTAS choices: https://www.kernel.org/category/releases.html Thanks, Johnny Hughes

3 3

Any movement of Coherence?
by ToddAndMargo 08 May '15

08 May '15

Hi All, Anyone know if there has been any movement on Coherence (floating windows) yet with KVM? Would help with the no Wine 32 on RHEL 7. https://bugs.freedesktop.org/show_bug.cgi?id=39238 -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Xen 4.4.2 (with XSA-132) in virt6-testing
by George Dunlap 06 May '15

06 May '15

I've got Xen 4.4.2 in virt6-testing. I haven't had a chance to test it, and won't for another week or two; but if some volunteers can put it through its paces, I can ask Johnny to push it to the public repo sometome early next week. Thanks, -George

2 3

kubernetes 0.16.2 in virt7-testing
by Navid Shaikh 06 May '15

06 May '15

Hi, kubernetes 0.16.2 is in virt7-testing repo. Please test and feedback. -- Regards, Navid

1 0

Re: [CentOS-virt] Xen 4.4.2 (with XSA-132) in virt6-testing
by Karl Johnson 05 May '15

05 May '15

On Fri, Apr 24, 2015 at 4:32 AM, Pasi Kärkkäinen <pasik(a)iki.fi> wrote: > On Thu, Apr 23, 2015 at 05:09:56PM +0100, George Dunlap wrote: > > I've got Xen 4.4.2 in virt6-testing. I haven't had a chance to test > > it, and won't for another week or two; but if some volunteers can put > > it through its paces, I can ask Johnny to push it to the public repo > > sometome early next week. > > > > Great! Thanks a lot. > > I'll do some testing during the weekend. > > > Thanks, > > -George > > > -- Pasi > I've upgraded to Xen 4.4.2 and everything went fine. I've tested save/restore and few basic stuff, all good. [root@dev1 ~]# uname -r && xl info|grep xen_version 4.0.1-1.el6.elrepo.x86_64 xen_version : 4.4.2-1.el6 [root@dev1 ~]# Note; I'm using kernel-ml from elrepo because x4c kernel is too old LTS for me. Karl

2 2

Viet SIG meeting at 14:00 today
by Lars Kurth 05 May '15

05 May '15

Note that George is on vacation Lars

1 0

CentOS Images on AWS with partitions on /dev/xvda1 are awkwared to resize
by Nico Kadel-Garcia 30 Apr '15

30 Apr '15

I'm staring at the free CentOS images on AWS, and seeing that whoever set those up elected to use a partition for /dev/xvda1 rather than taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", etc. for each disk and use those directly as a file system. The result is that if you elect to allocate a larger base disk image, for example allocating 50 Gig to allow local home directories or space for "mock" or for bulky logs, and don't spend the time to select and allocate new disk images, it's awkward to simply expand the "/" partition. And with only 8 Gig allocated in the latest CentOS 6 images that I see in AWS, it's possible to get pretty pressed for space pretty quickly. Now, AWS published guidelines on manipulating partition size, and expanding a matching filesystem, but they're very clear to "unmount the parition before you touch it!!!" That's a bit difficult to unmount with a "/" partition, and they understandably don't have the kind of "boot from CD and work from the console" setup I'd normally use for that kind of work. So: why did the creators of that CentOS AMI elect to use such a small / partition? And how dangerous is it, with the system essentially idle, to use "parted" to expand the "/dev/xvda1" parition and then use "resize2fs" to expand the "/" file system while the system is alive? Note that, because I'm a complete weasel, I know at least one way around this: add a second disk, copy the OS to *that*, set grub to boot from the second disk, reboot from that, paritition the first disk as desired, copy the OS back, reset grub to boot from the first disk, and pray. I've had good success with the approach in the past, and have rebuilt rougly 15,000 Linux systems this way. But the work predates CentOS, and I dont't want to go through that again. So, has anyone resized "/" successfully and gracefully on AWS CentOS instances? Nico Kadel-Garcia

3 6

ipv6 routing problem
by Khapare Joshi 30 Apr '15

30 Apr '15

I have centos 6 running kvm. IPv4 works perfectly works. But I am having some problem with ipv6, looks like its bridge routing problem but stuck. here are my bridge detail: bridge name bridge id STP enabled interfaces br0 8000.000af75613f2 no eth1 vnet1 br4 8000.000af75613f0 no eth0 ip -6 route shows : unreachable ::/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 2a00:c88:4000:1431::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 2a00:c88:4000:1650::/64 dev br4 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 4294967295 fe80::/64 dev vnet0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet2 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev vnet3 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 fe80::/64 dev br4 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295 default via 2a11:c99:4111:110::11:211 dev br4 metric 1 mtu 1500 advmss 1440 hoplimit 4294967295 Then I added, /etc/sysconfig/network-script/ifcfg-br4 DEVICE=br4 TYPE=Bridge ONBOOT=yes BOOTPROTO=static IPADDR=ipv4address here NETMASK=255.255.255.0 DNS1=mydnsserver.org DELAY=0 NM_CONTROLLED=no IPV6INIT=yes IPV6_AUTOCONF=no #IPV6_DEFROUTE="yes" IPV6_FAILURE_FATAL=yes IPV6ADDR=2a11:c99:4111:110::11:65/64 IPV6_DEFAULTGW= 2a11:c99:4111:110::11:211 I can ping the gateway from the kvm host but I cannot ping6 out from the kvm guest, also I cannot ping kvm guest from external host that is in ipv6 network. I appreciate some guidance on this.

1 0

Recommendations for virt on Opteron 275 systems.
by Lamar Owen 30 Apr '15

30 Apr '15

Hello, CentOS-virt list. The institution where I work has been donated some older IBM BladeCenters with IBM's LS-20 blade servers installed. These LS-20's are equipped with Opteron 275 processors (dual-core, dual-socket). In researching my virtualization options, I initially wanted to do oVirt, but after thoroughly investigating, it appears that oVirt, being based on KVM, will not work due to the Opteron 275 not supporting AMD-V virtualization extensions. So, further investigation showed that Xen4CentOS, using paravirtualization, should be supportable. So I'm looking for advice on deployment, including some pointers to some howtos or other documents on how to go about setting up a moderately large virtualization farm with Xen4CentOS on up to 200+ LS-20 blades, most of which have smallish internal storage, but with iSCSI connectivity to an EMC SAN; the deployment would start small and would grow as needed. I'm looking for the ability to do HA-type things, live migration, etc, to replace an aging VMware ESX setup. Windows guests are not a requirement. Pointers to solid VM management tools, especially for the HA and live migration options, would be nice. Purchasing upgraded blade servers isn't really an option for us at this time. (Now, if you or your organization wanted to donate some HS-21's or later, we would be glad to accept them; we are a 501(c)(3) not-for-profit public foundation...... :-) and then I could run oVirt).

1 0

Can we get a copy of ks.cfg for varous images into /root/ks.cfg?
by Nico Kadel-Garcia 27 Apr '15

27 Apr '15

I've recently been dealing with various CentOS images on AWS, and am being forcibly reminded that the "/root/anaconda-ks.cfg" has only a passing resemblance to whatever the kickstart configuration file actually contained. But getting a copy of the actual "ks.cfg" is invaluable for updating and testing variations of the kickstart setup, especially when manipulating disk partitioning or package selection. In particular, anaconda-ks.cfg fails to include any but the first '%post' script and discards all comments that may have been in the original ks.cfg file. Coupled with the problems of system-config-kickstart, and you have no provenance for the kickstart file that was actually *used* to create a particular system. For people building kickstart based environments, what would it take to get you to put this in your ks.cfg? %post cp /tmp/ks.cfg /mnt/sysimage/root/ks.cfg %end For older releases, '%end' is not needed. And before anyone asks, *YES* I've reached out to the anaconda developers in the past about this. I can try again, but in the meantime, it would really help me, and I think it would help others. Nico Kadel-Garcia

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt