virt March 2014

virt@lists.centos.org

23 participants
17 discussions

MS-Win7 kvm guest gets dhcp from host bridge
by James B. Byrne 23 Jun '14

23 Jun '14

CentOS-6.5 i86_64 qemu-kvm-0.12.1.2-2.415.el6_5.4 MS-Windows v7proSP1 We have installed a MicroSoft Win7 system as a guest and have joined it to our MS AD domain. The system runs and has internet access. However, the IPv4 address it obtains and the gateway it is assigned are both sourced from the virtual machine host system and not from our AD DC DHCP server. To clarify, the virbr0 IP address is 192.168.122.1 and the Windows guest has that address as its gateway and an IP address in the 192.168.122.0/24 netblock. This is not as we desire as the internal addresses we regularly assign to MS workstations via DHCP are supposed to belong to a different netblock entirely. This permit filtering on incoming and outgoing traffic at the gateway. I realize that there is a DHCP service running on virbr0 for the purpose of provisioning guests with system control traffic but I do not know how to limit that to its intended purpose and allow another DHCP server to provide the IP address to the windows guests. I hope that problem description is not too confusing. Can anyone provide me with some guidance on the matter? Are kvm guests required to have either static ip addresses or dhcp addresses provided by the host system? Thanks in advance. -- *** 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

4 3

Xen Security patching
by Chris Elliott 07 Jun '14

07 Jun '14

Hi Guys When is the next update of Hypervisor packages going to be released? There appears to be no changes to the main hypervisor RPMs since September (Even in the BETA / RC1 tree) and there are 5+ Xen Security Advisories with patches which need to be added. "Security issues are handled and released in sync with public disclosure upstream with zero lag" I can rebuild my own, but that's not really the point. In other news I've been doing some testing of the 3.10 kernel and so far so good! Thanks - Chris

3 7

VMs failing to restart
by Lars Hecking 09 May '14

09 May '14

This is a problem I've had on and off under CentOS5 and CentOS6, with both xen and kvm. Currently, it happens consistently with kvm on 6.5, e.g. with every kernel update. I *think* it generally worked fine with the 6.4 kernels. There are 7 VMs running on a 6.5, x86_64, 8GB RAM host, each with 512MB RAM and using the e1000 NIC. I picked this specific NIC because the default does not allow reliable monitoring through SNMP (IIRC). The host has two bonded NICs with br0 running on top. When the host reboots, the VMs will generally hang bringing up the virtual NIC, and I need to go through several iterations of destroy/create, for each VM, to get them running. The always hang here (copy&paste from console): ... Welcome to CentOS Starting udev: udev: starting version 147 piix4_smbus 0000:00:01.3: SMBus Host Controller at 0xb100, revision 0 e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI e1000: Copyright (c) 1999-2006 Intel Corporation. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 e1000 0000:00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 e1000 0000:00:03.0: eth0: (PCI:33MHz:32-bit) 00:16:3e:52:e3:0b e1000 0000:00:03.0: eth0: Intel(R) PRO/1000 Network Connection Any suggestions on where to start looking?

4 9

AWS Images updated for new instance types
by Karanbir Singh 22 Apr '14

22 Apr '14

hi, · CentOS 6.3 (x86_64) – Release Media: https://aws.amazon.com/marketplace/pp/B00A6L6F9I · CentOS 6.4 (x86_64) – Release Media: https://aws.amazon.com/marketplace/pp/B00DGYP804 are now marked for and updated to run with the m3 and c3 instance types. I'm still working with the amazon crew to get the 6.5 images online and an automated pipeline proposed ( hopefully, also adopted ) to get this image injection speeded up in the future. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 6

injecting a key into the xen images
by Karanbir Singh 02 Apr '14

02 Apr '14

hi, As a part of the test suite for xen that I've started off - I needed a way to inject a ssh key into the image [1]; so have come up with this : https://github.com/CentOS/sig-virt-t_xen/blob/master/scripts/inject_ssh.sh ; its not pretty and it wont handle lots of use cases, but it does what is needed at hand. Comments ? I'm also considering if we should include this script within the .bz2 file for the image itself ( and for all such images ) Further feature creep, should we now extend this script a bit to also include a 'download and inject ssh key' with some param's like : ./get_image.sh 6.5 x86_64 <path to sshkey> and that can hit http://cloud.centos.org/<calculated path to image>/ ; download it, and add the key. This script could live within centos-release-xen dramatically reducing the barrier to entry and get-go with the xen4centos stack. thoughts ? - KB 1: qcow2, http://cloud.centos.org/centos/6/devel/CentOS-6-x86_64-xen-pv.bz2 -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 6

Xen updates / TODO
by Pasi Kärkkäinen 25 Mar '14

25 Mar '14

Hello, A couple of TODO items/suggestions: 1) Xen 4.2.4 was just released: http://lists.xen.org/archives/html/xen-devel/2014-02/msg01624.html I think we should first update Xen4Centos6 rpms to Xen 4.2.4 to have a "known good" release from the stable branch currently in use in Xen4Centos6. 2) After that, we should start packaging/testing Xen 4.3.2: http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html Xen 4.3 brings much improved XL toolstack in addition to a lot of other changes/fixes. 3) After updating to Xen 4.3.2 rpms start troubleshooting/debugging the libvirt libxl driver and get it working with Xen4Centos6 system.. How does that sound like? :) -- Pasi

6 34

Re: [CentOS-virt] centos5 xen domu with X: screens not found [SOLVED]
by Peter Peltonen 20 Mar '14

20 Mar '14

Hi, On Tue, Mar 18, 2014 at 3:55 PM, Stefano Stabellini < stefano.stabellini(a)eu.citrix.com> wrote: > > Strangely enough according to xenstore, vfb is running and connected. > > Can you try connecting to it using xm or vncviewer directly? > > Or maybe setup the guest to use a simple fbcon just to try out if it > works, and then setup the more complicated environment you are looking > for afterwards? Thank you Stefano for your help. Just to be sure I did the virtualization again (used dd to copy the machine's system and then edited Xen stuff in place) and - surprise, surprise - X login window appeared without any problems in virt-manager. So problem solved. Best, Peter

1 0

Problems with Windows on KVM machine
by engineer＠colocat.ru 20 Mar '14

20 Mar '14

Hello. We've started a virtualisation project and got stuck in one moment. Currently we are using the following: Intel 2312WPQJR as a node Intel R2312GL4GS as a storage with Intel Infiniband 2 ports controller Infiniband Mellanox SwitchX IS5023 for commutation. The nodes run CentOS 6.5 with built-in Infiniband package (Linux v0002 2.6.32-431.el6.x86_64), the storage - CentOS 6.4 also built-in drivers (Linux stor1.colocat.ru 2.6.32-279.el6.x86_64). On the storage is made an array, that is shown in system as /storage/s01. Then it is exported via NFS. The nodes connect to NFS by: /bin/mount -t nfs -o rdma,port=20049,rw,hard,timeo=600,retrans=5,async,nfsvers=3,intr 192.168.1.1:/storage/s01 /home/storage/sata/01 mount shows: 192.168.1.1:/storage/s01 on /home/storage/sata/01 type nfs (rw,rdma,port=20049,hard,timeo=600,retrans=5,nfsvers=3,intr,addr=192.168.1.1) Then we create a virtual machine with virsh with a disk bus virtio. All is OK, until we don't start Windows on KVM. It may work for 2 hours or 2 days, but under heavy load it hangs the mount (i.e. /sata/02 and 03 are accessible, but requesting 01 will result in a total hang of console). This can be beaten only by hardware reset of the node. If we mount without rdma - all is fine. What can we do in such case? If any debugs or info needed - please ask. Best regards, Nikolay.

3 8

centos5 xen domu with X: screens not found
by Peter Peltonen 18 Mar '14

18 Mar '14

Hi, I am in a process to virtualize an existing non-virtualized CentOS5 system. Everything else works fine except X: virt-manager's console just hangs after bootup. I can use the text console though and what I see in X server's log is the error message "screens not found". The only graphics related setup I've done is in the domu config this line: vfb = [ "type=vnc,vncunused=1,keymap=fi" ] Is there something else I should configure on the guest or in dom0? Regards, Peter

2 3

Fwd: Xen4CentOS kernel panic on dom0 reboot
by Karl Johnson 14 Mar '14

14 Mar '14

I don't think it's related to microcode_ctl as my server was rebooting just fine before switching to Xen4CentOS in December 2013, then the reboot issue started. Note that it's not only on Dell servers but also Supermicro so I don't think it's hardware related too. Karl On Thu, Mar 13, 2014 at 8:14 PM, PJ Welsh <pjwelsh(a)gmail.com> wrote: > Anyone think it's related to microcode_ctl as noted in > http://lists.us.dell.com/pipermail/linux-poweredge/2013-October/048538.html? > I will see about testing for this issue ASAP... > > pjwelsh > > > On Thu, Mar 13, 2014 at 6:58 PM, PJ Welsh <pjwelsh(a)gmail.com> wrote: > >> Comments at bottom: >> >> >> On Tue, Mar 11, 2014 at 12:32 PM, Phillippe Welsh <pjwelsh(a)gmail.com>wrote: >> >>> Comments inline: >>> >>> ----- Original Message ----- >>> > From: "Pasi Kärkkäinen" <pasik(a)iki.fi> >>> > To: "Discussion about the virtualization on CentOS" < >>> centos-virt(a)centos.org> >>> > Sent: Sunday, March 9, 2014 4:32:13 AM >>> > Subject: Re: [CentOS-virt] Fwd: Xen4CentOS kernel panic on dom0 reboot >>> > >>> > On Sat, Mar 08, 2014 at 09:09:07AM -0600, PJ Welsh wrote: >>> > > No, I have not followed those instructions yet. These were >>> > > production >>> > > servers that I had scheduled firmware updates late Sunday >>> > > evening. The >>> > > first time I though the error was a fluke and only began to >>> > > research it >>> > > after the second failure (and still no firmware updates due to >>> > > the >>> > > power-cycle). I may try to sneak in a restart of one of the >>> > > systems late >>> > > Sunday night US CT. >>> > > >>> > >>> > OK. >>> >>> I ran the "stop" for all of the xen related pieces in the order that the >>> /etc/rc3.d/ had them. >>> The VM's did not shutdown and the /usr/lib64/xen/bin/qemu-dm STUFF >>> entries were left behind running. >>> Since I could not xm shutdown any longer, I killed off all qemu-dm >>> proccesses and attempted a reboot... >>> HUNG on the reboot with the prepended umount error messages... >>> >>> > >>> > > Still not sure why the running vm's would stop the reboot... The >>> > > server >>> > > shows that it was suppose to be restarting. I have had a similar >>> > > stuck on >>> > > restarting message (minus all the umount errors) on some Dell >>> > > T105's >>> > > running CentOS 6.5 and the "reboot=pci" grub.conf kernel option >>> > > is what >>> > > ended up working for them. I have not tested that possible >>> > > option yet, >>> > > either since that would take 2 reboots to put into place. >>> > > >>> > >>> > Yeah, it's worth testing both, to figure out what's wrong. >>> >>> Next reboot attempt included the "reboot=pci" grub.conf kernel option... >>> No affect :( >>> HUNG on the reboot with the prepended umount error messages... >>> >>> I ran out of time to attempt an xm shutdown for each VM manually, then >>> reboot. >>> >>> What's interesting is that when I do an lsof on the file system that is >>> unable to umount, the *only* connected PID's are the qemu-dm ones, but not >>> *all* of them.??? >>> >>> Thanks >>> >>> PJ >>> ... >>> >> >> UPDATE: I cleanly shut down *all* vm's and unmounted the filesystem that >> had the umount issue noted previously and then issued the reboot command. >> *STILL* the Dell R710 will be hung at the rebooting line. >> >> No reboot possible on 2 Dell R710's with at least the 2 most recent >> CentOSXen4 kernels. >> >> Any other suggestions? >> >> Thanks >> >> pjwelsh >> > >

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt March 2014