virt

virt@lists.centos.org

2 participants
1612 discussions

Cleaning up virt SIG related wiki pages
by Lars Kurth 04 Apr '14

04 Apr '14

Hi all, I took a little bit of stock in light of preparing the re-launch of the Virtualization SIG as per the board decision recently and noticed that there are quite a few old and out-of-date wiki pages lying around In particular the following pages seem very old (Iast edited in 2007) * http://wiki.centos.org/SpecialInterestGroup/Virtualization * http://wiki.centos.org/SpecialInterestGroup/Virtualization/Packages I suppose these pages should link to http://wiki.centos.org/Manuals/ReleaseNotes/Xen4-01 and the actual SIG description as was discussed and approved by the CentOS board. I don't seem to be able to create an account on the wiki. Do I and George need to wait for someone to create it, or is there a way to self-sign up Regards Lars

2 3

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

Xen4CentOS installation strangeness
by Peter Peltonen 14 Mar '14

14 Mar '14

Hi, I have a server with Supermicro X7DVL-3 (P9) motherboard, 16G ECC RAM and LSI SAS 1068e RAID controller. I installed CentOS 6.5 64bit on the machine without any problems, but after following the Xen setup steps at http://wiki.centos.org/HowTos/Xen/Xen4QuickStart which installed me the kernel 3.10.32-11.el6.centos.alt.x86_64, I encountered a problem: After "Starting certmonger [OK]" the screen went black and the system became unresponsive: keyboard was not working (NumLock did not respond) and SSH was not responding either. After first lockup I increased dom0 max mem to 2G, but rebooting after that produced the same result. The strange thing is, that after a third reboot everything worked ok: screen went black for a moment after "Staring certmonger [OK]" but after that the graphical login screen appeared and I could use the system normally. The fourth reboot went ok as well. Any ideas what could cause this kind of behaviour? Regards, Peter

4 4

Fwd: Xen4CentOS kernel panic on dom0 reboot
by Phillippe Welsh 14 Mar '14

14 Mar '14

Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel <david.vrabel at citrix.com>wrote: > > On 05/03/14 15:09, Karl Johnson wrote: > > > I've been using Xen4CentOS for the last 3 months. It's working fine and > > > dom0/domUs are stable but the server does a kernel panic when doing a > > > reboot and the server has to be hard reset manually. It has kernel panic > > on the 3 last reboot. > > > > There is a xenbus device still present and during shutdown it is trying > > to set it to CLOSED but at this point xenstored isn't running and the > > xenbus write stalls. > > > > Do you have VMs that are still running when you attempt a reboot? If so > > shutting them down will likely avoid this. > > > > Can you provide the output of xenstore-ls prior to attempting a reboot? > > > > > > > I though Xen init.d scripts would stop all of them before rebooting? Here's > the output of chkconfig and xenstore-ls: > > http://pastebin.centos.org/8186/ > > Thanks, > > Karl I've got the "me-too" on the reboot hang issue for 2 different Dell R710's with xen-4.2.4-29.el6 and at least the kernels kernel-3.10.25-11.el6.centos.alt.x86_64 and kernel-3.10.23-11.el6.centos.alt.x86_64. I have not tried to reboot with the latest kernel-3.10.32-11.el6.centos.alt.x86_64 (if kernel even makes a difference). I *have* had dom0_mem=1024M,max:1024M option in place for all of them with only 6 VM's. Any new suggestions? pjwelsh

3 6

Re: [CentOS-virt] [CentOS] KVM and DHCP
by James B. Byrne 13 Mar '14

13 Mar '14

On Thu, March 13, 2014 15:49, Reindl Harald wrote: > > > Am 13.03.2014 20:43, schrieb James B. Byrne: >> CentOS-6.5 >> >> We have a KVM guest running MS-WinV7pro. This guest is joined to an Active >> Directory Domain. That domain provides DHCP to the members. The KVM guest >> does not obtain its IP from the domain but from the local host's qemu >> hypervisor instead. >> >> Is there anyway to get around this and have the guest MS-Win OS get its DHCP >> from the same place as the rest of the domain members? > > smells like you are using NAT for your guest instead > bridge it to the host network, the guest does not > know from where it gets DHCP infos and there should > not be more than one dhcpd on a network segment, anything > else leads to race-conditions - the faster dhcpd wins > > http://www.dedoimedo.com/computers/kvm-bridged.html > > maybe the article is outdated, try google as i did > https://www.google.at/search?q=kvm+nat+versus+bridging > > Yes, that was it. Apparently if one creates a kvm guest via the virt-manager gui application then NAT is automatically selected as the default. It may be that the other guests were originally hand-crafted via virsh and the br0 interface was specified for them, but I doubt that. I have been using virt-manager since day one on this project and I am getting a queasy feeling that virt-manager's behaviour has obscurely changed in significant ways since I first began using it. This is not the first problem that I have had creating new guests with recent versions of virt-manager which were not in evidence with earlier use. In any case, to fix this via virt-manager's __virtual hardware details__ interface one must select the __NIC__ and change the settings from <Virtual network default 'NAT'> to <Specify shared device name> and then input the bridge interface name <br0> in the text box that subsequently appears. One must also change the Device model: from <Hypervisor default> to <virtio>. Thanks for the pointer. -- *** 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

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt