virt October 2012

virt@lists.centos.org

23 participants
10 discussions

Package lists for Cloud images
by Karanbir Singh 01 Jun '13

01 Jun '13

hi Guys, As we get ready to start publishing Cloud Images ( or rather images consumable in various virt platforms, including public and private clouds ) - it would be great to have a baseline package manifest worked out. What / how many images should we build. At this time we were thinking of doing : - CentOS-5 32bit minimal - CentOS-6 32bit minimal - CentOS-5 64bit minimal - CentOS-6 64bit minimal - CentOS-5 64bit LAMP - CentOS-6 64bit LAMP What would be the minimal functional requirements people would expect from these images ? and what rpms should be installed ? Should root login be enabled or should we require people to go in via a 'centos' user. Should the image be self-updating, or should we have a post-login message that indicates outstanding updates ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

12 37

(no subject)
by Hossein Lanjanian 29 Oct '12

29 Oct '12

Hi every body I am a new centos user. I installed centos 6 on my laptop and add some software to it. How can I create a full image (boot able) back up of it. ( some thing like windows full image backup). please help! -- With The Best H.Lanjanian

3 2

unknown command: 'snapshot_blkdev'
by Rudi Servo 28 Oct '12

28 Oct '12

I am trying to make a snapshot with this command: virsh snapshot-create vm01 --disk-only --atomic the error is: error: operation failed: Failed to take snapshot: unknown command: 'snapshot_blkdev the error come from the --disk-only argument Did tried to google on the subject but no solid information on the matter. Thanks in advance Regards Rudi

1 0

KVM + virsh nodeinfo + CentOS 6.3
by Matthias Hensler 25 Oct '12

25 Oct '12

Hi there, today I encountered the very same problem as described by Zoltan. We are running a system with the Intel serverboard S2600CP and two E5-2620 Xeon processors, with a total of 2 x 6 Cores with 2 threads each (resulting in a total CPU count of 24). Base system is a CentOS 6.3 with all recent updates. We are running the setup for some months now, without any problems. Most virtual machines only got 4 vCPUs, but some got 6 or 8 vCPUs. That setup was fine if running CentOS 5, CentOS 6 or Windows Server 2008 as guest systems. However, today I had to install two machines with Debian Squeeze. The first one got 4 vCPUs and runs fine, while the second one got 6 vCPUs and does not boot at all. Booting stops shortly after detecting the virtio harddisk with its partitions. When I switch back to 4 vCPUs everything is fine. Since the RHEL 5.8 and 6.3 kernels work fine, it seems to be a problem specific to the Debian kernel. Our default setup pins the different vCPUs to one fixed physical CPU each in an interleaving way. This would be the setup from /etc/libvirt/qemu/vm.xml: <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0-5,12-17'/> <vcpupin vcpu='1' cpuset='6-11,18-23'/> <vcpupin vcpu='2' cpuset='0-5,12-17'/> <vcpupin vcpu='3' cpuset='6-11,18-23'/> <vcpupin vcpu='4' cpuset='0-5,12-17'/> <vcpupin vcpu='5' cpuset='6-11,18-23'/> </cputune> <os> <type arch='x86_64' machine='rhel6.3.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <cpu mode='host-model'> <model fallback='allow'/> <topology sockets='6' cores='1' threads='1'/> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> Such a setup works fine for Redhat-kernels, but not for the Debian kernel (did only test the default 2.6.32-5 amd64 kernel so far). I played a bit with the pinning and topology, but even setting the config to do no pinning at all, and for example use 8 vCPUs divided in 2 sockets with 4 cores, or 1 socket with 8 cores or any other combination of it, does not work. The only way to get the Debian VM to boot, is to roll back to a total of 4 vCPUs (or less). As a reference, these are the cpuflags, seen from the host: processor : 23 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz stepping : 7 cpu MHz : 1995.156 cache size : 15360 KB physical id : 1 siblings : 12 core id : 5 cpu cores : 6 apicid : 43 initial apicid : 43 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2 x2apic popcnt aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid bogomips : 3989.83 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: and these are the cpuflags seen from the guest: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel Xeon E312xx (Sandy Bridge) stepping : 1 cpu MHz : 1995.191 cache size : 4096 KB fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc arch_perfmon rep_good pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm bogomips : 3990.38 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: The host is running this kernel: 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Packages are up to date: qemu-kvm-0.12.1.2-2.295.el6_3.2.x86_64 libvirt-0.9.10-21.el6_3.5.x86_64 The kvm commandline looks like this (for 4 vCPUs): /usr/libexec/qemu-kvm -S -M rhel6.3.0 -cpu SandyBridge,+pdpe1gb,+osxsave,+tsc-deadline,+dca,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 12288 -smp 4,sockets=4,cores=1,threads=1 -name xxxx -uuid xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/xxxxxxxxxxxxxx.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/drbd28,if=none,id=drive-virtio-disk0,format=raw,cache=none,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:xx:xx:xx,bus=pci.0,addr=0x5 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -vnc unix:/var/lib/libvirt/vnc/xxxxxxxxxxxxxx,password -k de -vga cirrus -incoming tcp:0.0.0.0:49152 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 Any clue on how to debug this further or how to fix is very appreciated. If any more information would be helpful, just ask. Regards, Matthias PS: please excuse if this mail is not correctly sorted into the existing thread, as I just write this after seeing the mails in the mailinglist archive without any possiblity to directly reply to the existing mails.

1 0

KVM + virsh nodeinfo + CentOS 6.3
by Zoltan Frombach 24 Oct '12

24 Oct '12

Hi, Please let me know in case I am posting my question to the wrong forum. I apologize if that is the case! Here is my question: We run CentOS 6.3 on a server with dual Xeon CPU's. Our "dual blade" server uses this motherboard: http://www.supermicro.com/products/motherboard/Xeon/C600/X9DRT-HF.cfm We have two of these CPUs installed and working: Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz ( http://ark.intel.com/products/64594/Intel-Xeon-Processor-E5-2620-15M-Cache-… ) cat /proc/cpuinfo correctly reports a total of 24 cores (2 x 6 phisycal cores plus 2 x 6 hyperthreading cores) However, I get this output from virsh nodeinfo : # virsh nodeinfo CPU model: x86_64 CPU(s): 24 CPU frequency: 2000 MHz CPU socket(s): 1 Core(s) per socket: 6 Thread(s) per core: 2 NUMA cell(s): 2 Memory size: 16303552 kB As you can see, virsh nodeinfo reports only 1 CPU socket while in fact we have two CPU's. I would like to know if this is normal? Why does virsh reports only one physical CPU ?? Also, when we try to run a guest OS (Debian Linux "squeeze") with more than 4 vcpu's assigned to the VM, the guest OS won't boot up. The guest's kernel stuck on a screen right after it detected the /dev/vda block device and its partitions. We're using the VirtIO driver, of course. If I assign only 4 (or less) vcpu's to the guest OS it works fine. I have tried to upgrade the Linux kernel on the guest from debian backports, it did not help, we're experiencing the same issue with both the 2.6.32 and 3.2 Linux kernels. What could be causing this? On the host, we use the Linux kernel that came with CentOS 6.3 : 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Thanks, Zoltan

2 3

Vendor Specific / Agnostic images
by Karanbir Singh 21 Oct '12

21 Oct '12

hi guys, I've been going round in circles trying to workout the best way to handle vendor agnostic images and in the interest of sanity and actually getting something out of the door - it looks like the best pln is to get the vendor specific requirements and push images with them ( and suitability marked ) With that in mind, AWS is a good target to start with. Do people have opinions on : - root or ec2-user for login ? - cloud-init ( we can use the one from EPEL, it needs a few things sorted, but that should not be too hard ) - selinux as enabled, with a hook in user-data that allows people to set permissive mode at time of instance creation For step1, I was thinking it would be best to just have c5/6 32/64bit minimal images ( using the pygrub AKI ) and make them available on instance-backed as well as EBS backed. Finally, would appreciate having some people help test the images privately before we start pushing publicly - if anyone can help with that, please get in touch with me at kbsingh@ project domain or the domain this email came from. Thanks, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

1 0

Cannot get kvm guests to connect to network
by James B. Byrne 15 Oct '12

15 Oct '12

This cross-posted from the main Centos discussion list. I installed a new CentOS-6.3 kvm guest on a recently provisioned kvm host also running CentOS-6.3. This guest will not connect to the network and the host cannot connect to it via its public IP address. I had previously installed a guest system on thst same kvm host using the same ISO and that system connects to the network without problem. I next created a third guest instance and this too does not connect with either the kvm host or the gateway. I have shutdown all the guests, restarted networking on the host and restarted the gueests and the problem persists on the two most recently added guests but does not happen on the first guest instance. I have installed litterally dozens of kvm guests this past year and I have never encountered this situation. Has anyone else? Does anyone have any idea what might be going on? ip addr 1: lo <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 52:54:00:a0:26:47 brd ff:ff:ff:ff:ff:ff inet 216.185.71.243/24 brd 216.185.71.255 scope global eth0 inet6 fe80::5054:ff:fea0:2647/64 scope link vaslid_lft forever preferred_lft forever ip route 216.185.71.0/24 dev eth0 proto kernel scope link scr 216.185.71.243 169.254.0.0/16 dev eth0 scope link metric 1002 default via 216.185.71.1 dev eth0 netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 216.185.71.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 default 216.185.71.1 0.0.0.0 UG 0 0 0 eth0 service iptables stop . . . ping 216.185.71.1 PING 216.185.71.1 (216.185.71.1) 56(84) bytes of data. >From 216.185.71.243 icmp_seq=2 Destination Host Unreachable >From 216.185.71.243 icmp_seq=3 Destination Host Unreachable >From 216.185.71.243 icmp_seq=4 Destination Host Unreachable ^C -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@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

2 2

Network failure on KVM guest
by lhecking＠users.sourceforge.net 04 Oct '12

04 Oct '12

I set up a KVM host a few months back with eight virtual machines running on it. Now, at least since yesterday, one of the guests (which apart from the MAC address is otherwise identical to six other guests) has lost its network connection. The other seven vms work fine. More bizarre, even rekickstarting does not work due to this issue. I suspect some issue on the host, but don't really have an idea what to check. Host and virtual machines all run CentOS6.3 plus all patches. The issue persists through a host reboot.

2 6

SNMP monitoring
by Lars Hecking 03 Oct '12

03 Oct '12

It seems it's not possible to monitor kvm virtual image network interfaces via SNMP. MRTG's cfgmaker says ### The following interface is commented out because: ### * has no ifSpeed property and other monitors are consistently reporting that vm's interfaces are exceeding traffic thresholds (even on lo ...). Which is no surprise if the threshold is zero. I found a hint on some Debian forum that this behaviour is caused by the virtio driver. So I was wondering, is it recommended or are there advantages to configuring one of the emulated drivers instead (ne2k_pci,i82551,i82557b, i82559er,rtl8139,e1000,pcnet)? Or can I "fake it" somehow in the vm's snmpd config?

2 2

Why is SCSI disabled in kvm on CentOS 5.8?
by Bill Campbell 03 Oct '12

03 Oct '12

Looking at the SRPM kvm-83-249.el5.centos.5, and the SRPM for qemu-kvm-0.12.1.2-2.209.el6.src.rpm on CentOS 6.2, I see many patches to remove SCSI support. The 5.2 kvm.spec file disables scsi in the configure run. Why has this been disabled? Many old OS's don't grok SATA, but have had SCSI support for years. Bill -- INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way Voice: (206) 236-1676 Mercer Island, WA 98040-0820 Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792 It does not require a majority to prevail, but rather an irate, tireless minority keen to set brush fires in people's minds. -- Samuel Adams

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt October 2012