virt

virt@lists.centos.org

1608 discussions

C7 image that can boot on x4c6
by Venkat Rayaprolu 19 Jul '14

19 Jul '14

Hi All, I am new to this community. I have experience in testing different virtualization products such as VMware, Xen and Oracle Virtual Server for more than 8 years. Can I contribute to testing C7 image that can boot on x4c6? Please help me on whom to contact for this? Thanks, Venkat

1 0

Fwd: About Centos 7 + Virt-manager
by Pablo Silva 17 Jul '14

17 Jul '14

Dear Colleagues: I'm trying to use virt-manager to create a container with lxc, as the picture I attached, I indicated that I must point to a directory where the template is to manage it with virt-manager. I tried to use a template of http://wiki.openvz.org/Download/template/precreated, but not working, being on the console option displays a black screen with nothing. I wonder, where can I get a template to work with virt-manager, or what are the steps to follow so you can create a template with Centos Minimal, do not know if the template must be the same version of Centos 7 or can be a template with Centos 6.5 In advance, thank you very much. -Pablo http://picpaste.com/Captura_de_pantalla_2014-07-15_a_las_10.47.26-DHi28gtt.… http://picpaste.com/Captura_de_pantalla_2014-07-15_a_las_10.49.02-y4TkGxLY.…

4 12

Re: [CentOS-virt] Xen PV domU reported as Xen-HVM
by Karl Johnson 07 Jul '14

07 Jul '14

On Tue, Jun 17, 2014 at 5:36 AM, George Dunlap <dunlapg(a)umich.edu> wrote: > On Thu, Jun 12, 2014 at 11:23 PM, Karl Johnson <karljohnson.it(a)gmail.com> > wrote: > > Hello, > > > > I am running two dom0s, one on CentOS 5 with Xen 4.1.2 (from Gitco) and > the > > other one on CentOS 6 with Xen 4.2.4 (from Xen4CentOS). I host one LVM > based > > domU on both from the same template (CentOS 6 PV) with the same Xen > config > > (see below). However, the domU on Xen 4.1 reports itself as Xen PV while > the > > domU on Xen4CentOS reports itself as Xen HVM. > > > > > > == First domU == > > > > virt-what and cPanel scripts report domU as: xenpv > > > > dom0: 2.6.18-371.6.1.el5xen Xen 4.1.2 > > > > domU Config: > > > > bootloader = '/usr/bin/pygrub' > > extra = '' > > memory = 6144 > > hostname = 'web2.x.ca' > > cpu_weight = 256 > > name = 'vm115' > > vif = ['ip=205.X.X.X, vifname=vifvm115.0, mac=00:16:3e:7a:X:X'] > > vnc = 0 > > vcpus = 6 > > vncviewer = 0 > > serial = 'pty' > > disk = ['phy:/dev/xen/vm115_img,xvda1,w', > > 'phy:/dev/xen/vm115_swap,xvda2,w'] > > > > domU kernel: 2.6.32-431.5.1.el6.x86_64 > > > > root@web2 [~]# virt-what > > xen > > root@web2 [~]# > > > > > > > > == Second domU == > > > > virt-what and cPanel scripts report domU as: xenhvm > > > > dom0: 3.10.32-11.el6.centos.alt.x86_64 Xen 4.2.4-29.el6 > > > > domU Config: > > > > bootloader = '/usr/bin/pygrub' > > extra = '' > > memory = 6144 > > hostname = 'web3.x.ca' > > cpu_weight = 256 > > name = 'vm116' > > vif = ['ip=205.X.X.X, vifname=vifvm116.0, mac=00:16:3e:cf:X:X'] > > vnc = 0 > > vcpus = 6 > > vncviewer = 0 > > serial = 'pty' > > disk = ['phy:/dev/xen/vm116_img,xvda1,w', > > 'phy:/dev/xen/vm116_swap,xvda2,w'] > > > > domU kernel: 2.6.32-431.5.1.el6.x86_64 > > > > root@web3 [~]# virt-what > > xen > > xen-hvm > > root@web3 [~]# > > > > Any idea why? > > A lot of these tools use quirks of the hypervisor to detect these > kinds of changes. One such quirk in Xen PV is handling of the CPUID > instruction: normally there's no way to trap the CPUID instruction in > PV mode, so Xen introduced a special PV CPUID (which is just an > illegal instruction that Xen recognizes and emulates itself) that the > kernel is supposed to use instead; but that's an opt-in thing -- you > can still execute the normal CPUID. By executing the PV CPUID and the > normal CPUID and comparing the results, you can tell if you're in a PV > or an HVM VM. > > However, on recent architectures Intel has introduced functionality to > allow trapping os CPUID even in non-HVM mode. Support for this went > into 4.2. Now, if you have the right hardware, and the right Xen > version, you'll get the same results whether you execute the PV CPUID > or the native one. > > So virt-what's trick of comparing the two CPUID results to determine > if you're in a PV or an HVM domain doesn't work anymore. > > -George > Thanks for the reply George. Is there any other easy way in the domU to know if it's a pv or hvm with Xen 4.2+ and the right hardware? Karl

2 1

I have a question regarding the virtual scsi adapter.
by Eliezer Croitoru 03 Jul '14

03 Jul '14

I have a very old system which has a self compiled kernel. It' supports sata and megaraid but not LSI SCSI or BUSLOGIC scsi. I am not sure what SCSI adapter is being used on CentOS KVM host and there for what kernel options to enable in the new compiled kernel. I have tried to add LSI logic and it seems like still not recognizing the SCSI device. I have another kernel that do work but it was build with lots of modules and I am not sure which one of them is the appropriate one. The linux kernel version of the guest is 2.6.19. If someone has a .config file that has all the needed modules complied in the kernel I will be happy to see it. Thanks, Eliezer

1 0

Minutes of 1 July Virt SIG meeting (IRC)
by George Dunlap 01 Jul '14

01 Jul '14

Not too many people today. Present: - George - Pasi - Johnny H Covered - Update to 4.4.1 sooner, don't wait for the community build system to be up ACTION: George to rebase to 4.4.1-rc1, Johnny to build an RC for testing - virt-manager for C6 erroneously installs C7 as PV, even though it installs RH7 as HVM ACTION: hughesjr to send a bug report (or find someone to do so) - pv-grub-menu ACTION: pasi maybe to take a look in the next few weeks. ACTION: George to add to roadmap

1 0

[ Off Topic ] WorkShop Virtualização com Proxmox VE
by Gilberto Nunes 30 Jun '14

30 Jun '14

WorkShop Virtualização com Proxmox VE ------------------------------ <https://www.facebook.com/sharer/sharer.php?s=100&p[url]=http://blog.konnect…> Dia 12 de Julho, Sábado, a partir das 08hs00 acontecerá o WorkShop Virtualização com Proxmox VE. Venha conhecer uma das melhores ferramentas de Virtualização do Mercado. Com este treinamento, sua equipe de TI terá uma ótima ferramenta de virtualização. - O que é o Proxmox VE - Instalação e Configuração - Clusterização e Alta Disponibilidade de Virtual Machines - Backup de VM - Snapshot... - Desktop Virtual com Spice - Cluster e Alta Disponibilidade O evento acontecerá dia 21 de Julho de 2014, em Joinville - Santa Catarina. Será um Sábado, sendo que o horário o que segue abaixo: Início: 08hs00 Intervalo: 10hs00 Almoço: 12hs00 ( * ALMOÇO NÃO INCLUSO. ) Retorno: 13hs00 Encerramento: 16hs00 Será realizado nas dependências da Fundação Softville, cito no endereço abaixo: *R. Otto Boehm, 48 - América, Joinville - SC, 89201-700* Local do Evento <http://blog.konnectati.com.br/arquivos/1276> Rua Otto Boehm, 48 - América, Joinville - SC, República Federativa do Brasil Fundação Softville more >> <http://blog.konnectati.com.br/arquivos/1276> Aproveite! Facilidade de pagamento, certificado e apostila. Contato: gilberto.ferreira(a)konnectati.com.br (47) 9676-7530 Ementa do Treinamento: Clique aqui para ter acesso <http://www.konnectati.com.br/pasta/indica2.pdf>. Investimento: R$ 800,00 por pessoa. *Clique aqui e compre agora! <http://blog.konnectati.com.br/produto/treinamento-proxmox-ve>* ** Parcele em até 12 vezes nos cartões Visa, Master e American Express...* [image: WorkShop] <http://blog.konnectati.com.br/wp-content/uploads/treinamento-pve-softville.…> -- Gilberto Ferreira

1 0

Re: [CentOS-virt] MS-Win7 kvm guest gets dhcp from host bridge
by James B. Byrne 23 Jun '14

23 Jun '14

On Mon, June 23, 2014 00:29, Arun Khan wrote: > On Thu, Feb 20, 2014 at 3:36 AM, Dusty Mabe <dustymabe(a)gmail.com> wrote: >> >> On 02/19/2014 04:01 PM, James B. Byrne wrote: The root cause of the original problem was a change in the behaviour of libvirt (and the GUI of virt-manager) when creating new vms. The host system was already bridged and had other vms previously created and attached to the bridge without exhibiting this behaviour. I infer that at some point an update to libvirt altered the default configuration to always prefer NAT. A change that I failed to notice and was not conscious of given I had previous created vms without encountering this problem. Changing the configuration of the affected vms nic Source Device to 'Specify shared device name' and then specifying the Bridge Name fixed the problem. I have already commented elsewhere on the needlessly obtuse wording used for the Source Device when bridging is required. Why it does not say 'Specify bridge name' or 'Use named bridge' instead has not been plausibly explained by the maintainers. It is particularly vexatious given that when one selects 'Specify shared device name' the GUI immediately alters to display a text box labelled 'Bridge name:' Duhhh. -- *** 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

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

Preferred method of provisioning VM images
by Lars Kurth 20 Jun '14

20 Jun '14

Hi all, following the discussion on about documentation, I was wondering whether we need to look at a standard way in which we recommend how to provision images for VMs. Am starting this with a Xen hat, but the discussion should not be specific to this. There are a number of options, but all have some trade-offs == #1 virt-install == Advantages: similar to KVM Disadvantages: may cause weird issues / confusion with people switching back to xl. The core issue is that with the current version of xen and libvirt, this only works with xm (when xl is used, this can create some undefined behavior). However as we have seen in some recent threads on this list, people tend to mix which can cause problems. == #2 xen-tools == Advantages: Very flexible. Many other distros use xen-tools, so we have lots of beginners docs that just need to be tweaked Disadvantages: needs porting/packaging for CentOS. Does not work for kvm. Says "xen". (Maybe that's an advantage.) We know that xen-tools works with Fedora (see http://blog.xen.org/index.php/2013/01/24/using-xen-tools-on-fedora/), so the porting effort may be small Unknowns: What would be needed to make it work for CentOS == #3 virt-builder (http://libguestfs.org/virt-builder.1.html) == Advantages: supports KVM, Xen and other VM inages. Seems easy to use. - if so, it would avoid xm / xl confusion. Unknowns: Not sure at which level virt-builder integrates with Xen and other hypervisors. It seems to operate at disk image format (similar to xen-tools) . I don't know whether virt-builder is restricted to some hypervisors in RHEL7. Disadvantages: may need porting/packaging for CentOS. It appears as if it will be in RHEL7, so it may just appear with CentOS 7. If not, some porting work may need to be done. == #4 Cloud Image from Cloud Image SIG == We could rely on pre-built cloud images from the Cloud Images SIG. People could just download the cloud image once it's done and customize it, rather than installing / building their own. Advantages: seems easy Disadvantages: coordination with Cloud Images SIG. May not be flexible enough I just wanted to start a discussion about this and ask for input. This topic which has come up a number of times in SIG meetings as a facgtor influencing libvirt and other package versions. Regards Lars

12 31

How to create an OpenVZ OS Template for CentOS 7 Public QA
by Scott Dowdle 17 Jun '14

17 Jun '14

Greetings, First start of by working on a physical system, virtual machine, or container that matches the OS Template you are wanting to build. I used my CentOS 7 Public QA OS OpenVZ container to build it. You must of course have a working yum. Once we are beyond Public QA and there is stuff in /etc/yum.repos.d/ this won't be a problem. One thing to note is that the --enablerepo= must refer to a repo your build host has and viewable via "yum repolist". That repo should point to the desired CentOS 7 build tree directory. A note about the package list. Yes, listed out every individual packcage is tedious. Perhaps some package groups could be used but they typically drag in a lot of unwanted additional packages. Suggestions welcome. Here is a simple script and please don't nag at me because I'm a scripting novice. I hope email client word wrapping and screen sizes don't butcher it too bad: - - - - - # To get a package list without version numbers from a target system # rpm -qa --qf "%{n} " > packages.txt # Put contents of packages.txt after "-y install \" line below mkdir /ostemplate yum \ --installroot /ostemplate \ --nogpg \ --releasever=7 \ --enablerepo=centos7pubqa \ -y install \ centos-release filesystem ncurses-base mailcap tzdata glibc-common xz-libs \ ncurses-libs pcre libselinux info libdb popt sed libcom_err libuuid expat \ libacl libgpg-error dbus-libs gawk lua libxml2 glib2 shared-mime-info apr cpio \ gmp p11-kit tcp_wrappers-libs perl-parent perl-podlators perl-Text-ParseWords \ perl-Pod-Escapes perl-libs perl-threads perl-constant perl-Filter \ perl-Time-Local perl-threads-shared perl-File-Path perl-Scalar-List-Utils \ perl-Getopt-Long libcap-ng nss-softokn libassuan libunistring diffutils gpm-libs \ libnfnetlink keyutils-libs gettext-libs p11-kit-trust nettle \ gobject-introspection vim-minimal pinentry make libselinux-utils ncurses \ libverto libsemanage krb5-libs openldap cracklib libmount systemd-libs libuser \ pam libblkid util-linux python-libs dhcp-libs libcurl python-urlgrabber rpm-libs \ dhcp-common libselinux-python python-iniparse python-chardet yum-metadata-parser \ python-backports-ssl_match_hostname newt-python pyxattr binutils logrotate \ procps-ng mariadb-libs fipscheck-lib openssh libmnl iptables json-c \ device-mapper cryptsetup-libs dbus iputils cronie-anacron crontabs libestr \ gnupg2 rpm-python pygpgme libnl3 yum-utils man-db dhclient audit openssh-server \ libgudev1 net-tools elinks python-pyudev policycoreutils python-configobj \ pygobject3-base sudo wget file tar which psmisc libpcap libsysfs libdaemon lzo \ libgcc setup basesystem kbd-misc bind-license nss-softokn-freebl glibc libstdc++ \ bash libsepol zlib audit-libs nspr chkconfig bzip2-libs nss-util grep libattr \ libcap elfutils-libelf libgcrypt readline libidn libffi pkgconfig sqlite \ groff-base file-libs libtasn1 slang gdbm perl-HTTP-Tiny perl-Pod-Perldoc \ perl-Encode perl-Pod-Usage perl-macros perl-Storable perl-Carp perl-Exporter \ perl-Socket perl-File-Temp perl-PathTools perl-Pod-Simple perl apr-util libcroco \ cyrus-sasl-lib libgomp kmod-libs libedit hostname js newt ca-certificates less \ dbus-glib acl libdb-utils findutils xz sysvinit-tools ustr nss-tools \ openssl-libs gzip cracklib-dicts nss libpwquality coreutils shadow-utils \ libutempter nss-sysinit python libssh2 python-pycurl curl rpm python-decorator \ python-slip dbus-python python-kitchen python-backports python-setuptools \ pyliblzma centos-logos kmod openssl nss_compat_ossl bind-libs-lite fipscheck \ httpd-tools libnetfilter_conntrack iproute qrencode-libs device-mapper-libs \ systemd systemd-sysv initscripts cronie libpipeline pth rpm-build-libs gpgme yum \ libnl3-cli rsyslog mlocate kbd postfix httpd ebtables openssh-clients authconfig \ python-slip-dbus mc gettext screen passwd gnutls elfutils-libs libss nano snappy \ libndp ethtool hardlink rootfiles ln -sf /proc/mounts /ostemplate/etc/mtab # I want Mountain time to be the default ln -sf /usr/share/zoneinfo/America/Denver /ostemplate/etc/localtime # Now compress that sucker cd /ostemplate ; tar -cvJf /root/centos-7-x86_64-viayum.tar.xz . ; cd ls -lh /root/centos-7-x86_64-viayum.tar.xz echo "Done building OS Template. Now test it." - - - - - TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]

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