virt October 2014

virt@lists.centos.org

19 participants
10 discussions

Test new xen, centos-release-xen and kernel for auto grub update on kernel install
by Johnny Hughes 22 Oct '14

22 Oct '14

The new process for auto updates of grub upon kernel install is in the xen4centos testing repo. In order to test these as updates to an existing system, you can do this: 1. download the test repo file: http://dev.centos.org/centos/6/xen-c6-RC1/xen-c6-RC1.repo 2. Put it in /etc/yum.repos.d/ 3. Issue this command: yum --disablerepo=Xen4CentOS upgrade xen\* centos-release-xen (that should install all the new files required to make the kernel update work automatically) 4. Review the new file /etc/sysconfig/xen-kernel ... if there is any other items you want on the 'kernel /xen.gz' line, you would edit the file. For example, I like to add 'com1=115200,8n1 console=com1' to the end of that line so I can use consoles in virsh. So I would change the line: XEN_KERNEL_MBARGS="--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all" to XEN_KERNEL_MBARGS="--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all com1=115200,8n1 console=com1" (both of those should be one line if they wrap) This is also where you can assign more or less memory to the dom0. etc. This article has some other possible parameters for the xen.gz line: http://www.informit.com/articles/article.aspx?p=1187966&seqNum=4 5. Make sure this is set as well in /etc/sysconfig/xen-kernel: BOOT_XEN_AS_DEFAULT="yes" 6. issue this command to upgrade the kernel: yum --disablerepo=Xen4CentOS upgrade kernel-\* 7. This should upgrade your kernel and it should also automatically update your /boot/grub/grub.conf to boot for dom0 use. If, for some reason, you want to manually upgrade the grub.conf file yourself, set the BOOT_XEN_AS_DEFAULT to "no" instead of yes. 8. If you want to install the xen kernel in other places other than xen dom0 machines, just make sure not to install the xen package, and grub.conf will get standard and not xen kernel boot entries. ==================== Once ypu have done your updates, please delete /etc/yum.repos.d/xen-c6-RC1.repo =================== Please report positive and negative experiences here so we can move this into the CentOS-6 xen4 repository (or fix things that are broken). Thanks, Johnny HUghes

3 6

Reminder: Virt SIG meeting on IRC today, 2pm BST
by George Dunlap 21 Oct '14

21 Oct '14

Just a reminder to everyone, we'll be having our bi-weekly meeting on IRC this week, #centos-devel, at 2pm BST. Feel free to e-mail any agenda items you'd like to have covered. One thing I'd like to discuss a bit this week is blktap2 -- at the moment we're using a 2-year-old snapshot of XenServer's blktap2 fork (aka "blktap2.5"). At some point the whole project needs to figure out a better way to deal with this; so I'd like to ask what CentOS needs to get from blktap, so we can come up with the best solution. -George

1 0

Domain Controllers virtualized KVM
by Andry Michaelidou 16 Oct '14

16 Oct '14

Hello to you all! We are implementing here at the University KVM virtualization for our servers and services and i was wondering if anyone virtualized domain cotrollers to KVM. Does anyone done this before? Any advice? -- Andry Michaelidou Papa | IT Systems Administrator|Department of Computer Science| University of Cyprus Tel: +357.22.892734 | Fax: +357.22.8927231 | http://www.cs.ucy.ac.cy

7 9

virsh list hangs / guests not starting automatically
by Matt Garman 14 Oct '14

14 Oct '14

I followed the wiki[1] to create a KVM virtual machine using bridged network on CentOS 6.5. It seemed to work fine on initial setup. (FWIW I'm trying to run a MythBuntu guest.) However, after a reboot, it doesn't auto-start the VMs. Shortly after boot, if I go into "virsh", then do a "list", it just hangs. Likewise, if I go into "virt manager", it just hangs with the message "connecting". Kernel version is: 2.6.32-431.29.2.el6.x86_64 Relevant package versions: libvirt.x86_64 0.10.2-29.el6_5.12 libvirt-client.x86_64 0.10.2-29.el6_5.12 libvirt-python.x86_64 0.10.2-29.el6_5.12 python-virtinst.noarch 0.600.0-18.el6 virt-manager.x86_64 0.9.0-19.el6 virt-top.x86_64 1.0.4-3.15.el6 virt-viewer.x86_64 0.5.6-8.el6_5.3 qemu-img.x86_64 2:0.12.1.2-2.415.el6_5.14 qemu-kvm.x86_64 2:0.12.1.2-2.415.el6_5.14 CPU is a Xeon E3-1230v3. I have the virtualization setting enabled in the BIOS. I googled on this, and saw a bunch of talk about two years ago regarding issues with the libvirt packages having a deadlock bug. But I think the versions of the relevant packages that I have installed are new enough to have fixes for that. I also happened across an earlier post to this list[2], where it seemed someone was having a similar problem. I was previously attempting to use balance-rr and 802.3ad bonding modes on my host. However, I just changed to using "active-backup" and the problem remains. I have in /etc/libvirt/libvirtd.conf the following three lines (the rest is stock, i.e. all comments): log_level = 2 log_filters="" log_outputs="1:file:/var/log/libvirt/libvirt.log" Below I posted the contents of the libvirt log file after doing a "service libvirt start". Anyone ever fought this before? Thanks! [1] http://wiki.centos.org/HowTos/KVM [2] http://lists.centos.org/pipermail/centos-virt/2014-March/003722.html /var/log/libvirt/libvirt.log output: 2014-10-14 16:47:11.150+0000: 4657: info : libvirt version: 0.10.2, package: 29.el6_5.12 (CentOS BuildSystem <http://bugs.centos.org>, 2014-09-01-13:44:02, c6b8.bsys.dev.centos.org) 2014-10-14 16:47:11.150+0000: 4657: info : virNetlinkEventServiceStart:517 : starting netlink event service with protocol 0 2014-10-14 16:47:11.151+0000: 4657: info : virNetlinkEventServiceStart:517 : starting netlink event service with protocol 15 2014-10-14 16:47:11.154+0000: 4668: info : dnsmasqCapsSetFromBuffer:667 : dnsmasq version is 2.48, --bind-dynamic is NOT present, SO_BINDTODEVICE is NOT in use 2014-10-14 16:47:11.157+0000: 4668: info : networkReloadIptablesRules:1925 : Reloading iptables rules 2014-10-14 16:47:11.157+0000: 4668: info : networkRefreshDaemons:1287 : Refreshing network daemons 2014-10-14 16:47:11.278+0000: 4668: info : networkStartNetwork:2422 : Starting up network 'default' 2014-10-14 16:47:11.290+0000: 4668: info : virStorageBackendVolOpenCheckMode:1085 : Skipping special dir '.' 2014-10-14 16:47:11.290+0000: 4668: info : virStorageBackendVolOpenCheckMode:1085 : Skipping special dir '..' 2014-10-14 16:47:11.352+0000: 4668: info : qemudStartup:754 : Unable to create cgroup for driver: No such device or address 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'cpu' 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'cpuacct' 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'cpuset' 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'memory' 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'devices' 2014-10-14 16:47:11.353+0000: 4668: info : qemudLoadDriverConfig:411 : Configured cgroup controller 'blkio' 2014-10-14 16:47:11.509+0000: 4668: info : virDomainLoadAllConfigs:14696 : Scanning for configs in /var/run/libvirt/qemu 2014-10-14 16:47:11.527+0000: 4668: info : virDomainLoadAllConfigs:14696 : Scanning for configs in /etc/libvirt/qemu 2014-10-14 16:47:11.527+0000: 4668: info : virDomainLoadAllConfigs:14718 : Loading config file 'mythbuntu.xml' 2014-10-14 16:47:11.529+0000: 4668: info : qemuDomainSnapshotLoad:484 : Scanning for snapshots for domain mythbuntu in /var/lib/libvirt/qemu/snapshot/mythbuntu

1 1

problem with xen virtulization on centos 6.5
by moslem mosadegh 13 Oct '14

13 Oct '14

I have a .img file and it's config xml file that i downloaded from a website. I installed xen 4.2 on my centos 6.5. when i want to create a new domain for my .img file with this xml file with this command: "virsh create wiki.xml". that give me an error message:"unkonw os type xen". anyone know what's the problem?

2 2

Automate running grub-bootxen.sh for kernel installs in Xen4CentOS
by Johnny Hughes 09 Oct '14

09 Oct '14

We need a way to do two things to /usr/bin/grub-bootxen.sh in Xen4CentOS. 1. Automate running it if xen (the package) and the xen kernel are installed. But only if the user WANTS to run it. 2. Allow users to automatically modify the variables passed into the xen.gz line (that is, more or less memory, add console settings, etc.) If you look at the current script, "--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all" is hard coded in as the only option for the xen.gz line. While doing that we also still want to preserve the ability to run that kernel in other places than just for xen dom0 setups. Here is how I propose we do that. Currently the /usr/bin/grub-bootxen.sh file is in centos-release-xen ... that is a good place as it allows us to use a different file in different major versions of CentOS (so the file in 7 can be different than the file in 6, but still use the same auxiliary files, etc). So, what we can do is setup a file in /etc/sysconfig/ (probably from the xen package) that we call xen-boot or xen-kernel, etc. In this file we put some variables like these: BOOT_XEN_AS_DEFAULT="yes" XEN_KERNEL_MBARGS="--mbargs=dom0_mem=1024M,max:1024M loglvl=all guest_loglvl=all" Then we look for that file (/etc/sysconfig/xen-boot) as a post-install from the xen kernel. If the file exists, we source it ... an if BOOT_XEN_AS_DEFAULT is yes, and if /usr/bin/grub-bootxen.sh exists we run it passing in XEN_KERNEL_MBARGS as a variable. The user can set BOOT_XEN_AS_DEFAULT to no if they want, so they do not get a xen kernel entry in their grub config. That should mean that if either there is no '/etc/sysconfig/xen-boot' config file OR if '/usr/bin/grub-bootxen.sh' does not exist, we get only the standard kernel entry .. but if they do exist, we also get a user modifiable xen.gz kernel entry as well. Also, we should likely use the centos-release-xen package to handle the '/etc/sysconfig/xen-boot' file as well, since it already has the /usr/bin/grub-bootxen.sh script. Thoughts?

4 4

Xen4CentOS e1000e package
by George Dunlap 09 Oct '14

09 Oct '14

KB and I were looking at repositories to import into git.centos.org recently, and we found the e1000e package -- a rebuild of the Intel e1000 driver for the x4c kernel. Does anyone know if this externally-build module is still necesssary for Linux 3.10? Or for Linux 3.14, which we're planning on moving to at some point in the near future? -George

5 5

How to run cloud image for 6.5?
by Henning Sprang 07 Oct '14

07 Oct '14

Hi, On my way to run centOS 6.5 on OpenStack I found the cloud images at http://cloud.centos.org/centos/6.5/devel/ and while the corresponding image for centOS 7 seems to work fine, I still need the older version for some legacy application, but I cannot find a way to run the images provided in that directory. Especially I'm looking at http://cloud.centos.org/centos/6.5/devel/CentOS-6.5-x86_64-GA-03.img.gz, but as well uploading the unzppied .img file to OpenStack as image and trying to boot an instance with it, as well as runinng it locally with qemu-system-i386 CentOS-6.5-x86_64-GA-03.img both give me the same error - "Boot failed - not a bootable disk" Any idea what I could be doing wrong / should be doing to get it booting? Thanks, Henning

2 2

Re: [CentOS-virt] Automate running grub-bootxen.sh for kernel installs in Xen4CentOS
by rgritzo 03 Oct '14

03 Oct '14

although i am very new to the xen project, this approach makes good sense to me. consistent with the use of files within /etc/sysconfig and very predictable and sensible behavior. also seems like it is a good base to build from when adding future features. is it ready yet :} r. > We need a way to do two things to /usr/bin/grub-bootxen.sh in Xen4CentOS. > > 1. Automate running it if xen (the package) and the xen kernel are > installed. But only if the user WANTS to run it. > > 2. Allow users to automatically modify the variables passed into the > xen.gz line (that is, more or less memory, add console settings, etc.) > If you look at the current script, "--mbargs=dom0_mem=1024M,max:1024M > loglvl=all guest_loglvl=all" is hard coded in as the only option for the > xen.gz line. > > While doing that we also still want to preserve the ability to run that > kernel in other places than just for xen dom0 setups. > > Here is how I propose we do that. > > Currently the /usr/bin/grub-bootxen.sh file is in centos-release-xen ... > that is a good place as it allows us to use a different file in > different major versions of CentOS (so the file in 7 can be different > than the file in 6, but still use the same auxiliary files, etc). > > So, what we can do is setup a file in /etc/sysconfig/ (probably from the > xen package) that we call xen-boot or xen-kernel, etc. In this file we > put some variables like these: -- /*************************************************************************/ Russ Gritzo email: rgritzo(a)gmail.com /usr/games/gfortune: I know engineers. They love to change things. - Dr. McCoy /**************************************************************************/

1 0

updating for XSA-108 -
by Luke S. Crawford 03 Oct '14

03 Oct '14

So... it is theorized that XSA-108 is why amazon is rebooting. Is there any way for me to know when this update hits CentOS5 or xen4centos6? Do we know that it is *not* included in one of the centos patches?

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt October 2014