From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From nkadel at gmail.com Sun Feb 1 00:19:35 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 31 Jan 2015 19:19:35 -0500 Subject: [CentOS-virt] Using network-script with Xen 4.4.1 (aka what will I do without xend?) In-Reply-To: References: <0528E473-E5EB-4D37-9DBF-926C68DCF1AF@gmail.com> Message-ID: On Fri, Jan 30, 2015 at 4:39 PM, George Dunlap wrote: > On Thu, Jan 29, 2015 at 11:28 AM, Gene wrote: >> I have seen those documents, I did not see anything that indicates how >> _automatic_ bridge configuration could be enabled with xl. >> >> For my specific set up I have two bridges (xenbr0 -> peth0 & xenbr1 -> >> peth1). If I have to configure this manually with ifcfg scripts I will, but >> if an automatic method is provided or is possible with xl I'd prefer to use >> that. > > Thanks Gene -- I'll add a note about the transition to network-scripts > in the CentOS "migrating to xl" document. And coming around again: if you need pair bonding and VLAN tagging, the best guideline is probably my old one: for KVM at https://wikis.uit.tufts.edu/confluence/display/TUSKpub/Configure+Pair+Bonding,+VLANs,+and+Bridges+for+KVM+Hypervisor The more recent versions of NetworkManager for RHEL 7 and Fedora apparently support VLAN tagging and pair bonding, but the interface is poor. If you want it to be robust and reliable for virtualization server, I'll urge you to set "NM_CONTROLLED=no" in /etc/sysconfig/network, so it's inherited by default for all network ports. I'e some long rants about the unsuitability of NetworkManager for servers we could expolore some time if you need it. But especially for a virtualizaton server as opposed to a guest VM, It's dangerously destabilizing From pasik at iki.fi Tue Feb 3 08:26:50 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 3 Feb 2015 10:26:50 +0200 Subject: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002 In-Reply-To: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> References: <3FADFC87-1477-4872-99EA-BC9A145E65F6@gmail.com> Message-ID: <20150203082650.GP5962@reaktio.net> On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote: > Thanks for the info. > I am trying to connect to the Xen hypervisor, via a localhost connection > defined in the virt-manager configuration. > here is the detail provided in the error dialog: > ********* > Unable to open a connection to the Xen hypervisor/daemon. > Verify that: > - A Xen host kernel was booted > - The Xen service has been started > internal error: DBus support not compiled into this binary > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/connection.py", line 1168, in > _open_thread > self.vmm = self._try_open() > File "/usr/share/virt-manager/virtManager/connection.py", line 1152, in > _try_open > flags) > File "/usr/lib64/python2.6/site-packages/libvirt.py", line 105, in > openAuth > if ret is None:raise libvirtError('virConnectOpenAuth() failed') > libvirtError: internal error: DBus support not compiled into this binary > ********** > The hypervisor and VM*s work. If i start and manage VMs with virsh, the > work fine. it just is the virt-manager that seems broken, but that is > important for my operation. > i just applied the patches to a second machine - just in case it was > something about the first one - and the same results. > i am not as versed in python debugging as i would like to be, so this will > be a challenge. it sure seems like the issue is in the libvirtd library > from the error messages - > but i will keep poking at it as time permits and post here if i have any > answers... > What does "virsh version" command say ? Do you have selinux in enforcing mode? Try "getenforce" command. -- Pasi > thanks. > r. > > On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote: > > folks: > > > > after applying the updated rpms from advisory 2015:X002 i am having problems with libvirtd, and with virt-manager. > > > > if i run libvirtd in the foreground and look at the error messages, the error i see is > > 2015-01-29 04:45:27.342+0000: 6477: error : virDBusGetSystemBus:1742 : internal error: DBus support not compiled into this binary > > > > Hmm, weird, it works OK for me.. > > > and virt-manager is unable to connect to the hypervisor. this started after i applied the subject patches. > > > > is this an issue with the recent versions of libvirt? > > anybody else seeing this behavior? > > > > What hypervisor are you trying to use? Xen? KVM ? > > > btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64 > > > > I'm using the same kernel with Xen 4.4.1 rpms. > > > > thanks in advance. > > > > -- > > [1]rgritzo at gmail.com > > > > > * Pasi > > * > r. > > References > > Visible links > 1. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From rnicholsNOSPAM at comcast.net Thu Feb 5 22:13:21 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 16:13:21 -0600 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: In CentOS 6 with KVM, I have libguestfs-tools installed, but the "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? All the guests boot and run OK. I just can't get these tools to work. libguestfs-tools-1.20.11-11.el6.x86_64 libguestfs-tools-c-1.20.11-11.el6.x86_64 $ ls -lR /usr/lib64/guestfs /usr/lib64/guestfs: total 4 drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d /usr/lib64/guestfs/supermin.d: total 7020 -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Fri Feb 6 01:23:52 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Thu, 05 Feb 2015 19:23:52 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: References: Message-ID: On 02/05/2015 04:13 PM, Robert Nichols wrote: > In CentOS 6 with KVM, I have libguestfs-tools installed, but the > "virt-xxx" tools like "virt-df" just give, "libguestfs: error: cannot > find any suitable libguestfs supermin, fixed or old-style appliance on > LIBGUESTFS_PATH (search path: /usr/lib64/guestfs)". What am I missing? > > All the guests boot and run OK. I just can't get these tools to work. > > libguestfs-tools-1.20.11-11.el6.x86_64 > libguestfs-tools-c-1.20.11-11.el6.x86_64 > > $ ls -lR /usr/lib64/guestfs > /usr/lib64/guestfs: > total 4 > drwxr-xr-x. 2 root root 4096 Dec 3 13:16 supermin.d > > /usr/lib64/guestfs/supermin.d: > total 7020 > -rw-r--r--. 1 root root 5171200 Oct 17 11:50 base.img > -rw-r--r--. 1 root root 1858048 Oct 17 11:50 daemon.img > -rw-r--r--. 1 root root 139401 Oct 17 11:50 hostfiles > -rw-r--r--. 1 root root 4608 Oct 17 11:50 init.img > -rw-r--r--. 1 root root 2048 Oct 17 11:50 udev-rules.img Well, I still don't know what the real cause was, but rebooting has fixed it. And no, restarting the libvirtd service had no effect. If anyone has any ideas about what might have happened, I'd still like to hear them. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rjones at redhat.com Fri Feb 6 11:59:53 2015 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 6 Feb 2015 11:59:53 +0000 Subject: [CentOS-virt] libguestfs-tools not working Message-ID: <20150206115953.GB25961@redhat.com> You may be better off with the RHEL / CentOS 7.1 libguestfs packages which are available as a preview. This is a substantial rebase with many more features and somewhat faster too. Follow the instructions here: https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ From rnicholsNOSPAM at comcast.net Mon Feb 9 15:42:22 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 09 Feb 2015 09:42:22 -0600 Subject: [CentOS-virt] libguestfs-tools not working In-Reply-To: <20150206115953.GB25961@redhat.com> References: <20150206115953.GB25961@redhat.com> Message-ID: On 02/06/2015 05:59 AM, Richard W.M. Jones wrote: > > You may be better off with the RHEL / CentOS 7.1 libguestfs packages > which are available as a preview. This is a substantial rebase with > many more features and somewhat faster too. Follow the instructions here: > > https://www.redhat.com/archives/libguestfs/2014-May/msg00090.html Thanks for the offer, but (a) a reboot got it working, and (b) to get that into CentOS 6 I would have to rebuild from source. The dependency chain would essentially require me to upgrade to CentOS 7, and I have no intention of doing that. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From pasik at iki.fi Tue Feb 10 11:00:43 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 10 Feb 2015 13:00:43 +0200 Subject: [CentOS-virt] Building Xen 4.4 rpms for centos7 In-Reply-To: <20150120152748.GZ5962@reaktio.net> References: <20150120141047.GV5962@reaktio.net> <54BE67B3.6060409@centos.org> <20150120152748.GZ5962@reaktio.net> Message-ID: <20150210110043.GT18833@reaktio.net> On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi K?rkk?inen wrote: > > > > Agreed on this too .. let's use as much the same as we can, and we can > > use %if statements in the SPEC to differentiate el6 and el7 things, if > > necessary. systemd versus init and maybe some version number changes > > for buildrequires should be the changes we need to be concerned about. > > > > Yep! > > > > > We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it .. > > or we can shift to 3.14.x and that buys us at least one more year .. or > > wait until they name the next LTS kernel and go for that. Likely the > > next LTS kernel will be the easiest option (the RH modified kernel will > > not support xen and rolling in stuff externally will be hard because of > > the backports RH does to the kernel (things that go into a standard > > kernel will not apply cleanly to the RH kernel). > > > > But, I agree lets try to use the el6 kernel for xen el7 too .. and we > > can switch both kernels as required later. > > > > Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to work fine atm. > > Let's focus on getting the current rpms built for el7, > and then later we can update both el6 and el7 to later kernel/versions. > So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :) -- Pasi From lars.kurth.xen at gmail.com Tue Feb 10 12:23:51 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 10 Feb 2015 12:23:51 +0000 Subject: [CentOS-virt] Reminder: SIG meeting on IRC today at 14:00 UK time Message-ID: <98DA8277-D69B-46E2-9856-F8587AE12F46@gmail.com> * We hold every meeting on #centos-devel * Meetings will be minuted and IRC sessions are logged * To participate, just turn up on #centos-devel 5 minutes before the meeting and let us know you are there to participate From lsm5 at fedoraproject.org Fri Feb 13 19:18:28 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:18:28 -0600 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <54DDEAEB.2040504@centos.org> References: <54DDEAEB.2040504@centos.org> Message-ID: <20150213191828.GA12914@naruto> On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: > hi guys, > > docker 1.5 is now in virt7-testing repos, please test and feedback so we > can move to release.. > > thanks lokesh! > > - KB > Sure thing KB. Also, docker-registry will be ready for release by tonight (meaning working package and docs etc.) docker HEAD for c7 ------------------ I was hoping for wider feedback on daily rebuilds of docker master branch for c7 (which I already do for fedora rawhide), under a new package name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were for it. How does that sound to others? Or should I go ahead with this already? :) Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lsm5 at fedoraproject.org Fri Feb 13 19:28:44 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Fri, 13 Feb 2015 13:28:44 -0600 Subject: [CentOS-virt] etcd and kubernetes on virt7-testing Message-ID: <20150213192346.GB12914@naruto> I've rebuilt the latest kubernetes and etcd sources (from fedora rawhide) for c7. Builds are available on CBS and in the virt7-testing repo. kubernetes: https://cbs.centos.org/koji/taskinfo?taskID=7113 etcd: http://cbs.centos.org/koji/buildinfo?buildID=689 Please try them out and let me know if you see any issues. Thanks! -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From mail-lists at karan.org Fri Feb 13 19:28:49 2015 From: mail-lists at karan.org (Karanbir Singh) Date: Fri, 13 Feb 2015 19:28:49 +0000 Subject: [CentOS-virt] docker 1.5 in virt7-testing In-Reply-To: <20150213191828.GA12914@naruto> References: <54DDEAEB.2040504@centos.org> <20150213191828.GA12914@naruto> Message-ID: <54DE5071.9010305@karan.org> On 13/02/15 19:18, Lokesh Mandvekar wrote: > On Fri, Feb 13, 2015 at 12:15:39PM +0000, Karanbir Singh wrote: >> hi guys, >> >> docker 1.5 is now in virt7-testing repos, please test and feedback so we >> can move to release.. >> >> thanks lokesh! >> >> - KB >> > > Sure thing KB. Also, docker-registry will be ready for release by tonight > (meaning working package and docs etc.) > > > docker HEAD for c7 > ------------------ > I was hoping for wider feedback on daily rebuilds of docker master > branch for c7 (which I already do for fedora rawhide), under a new package > name (docker-unstable / docker-head / whatever). IIRC, KB and jperrin were > for it. How does that sound to others? > > Or should I go ahead with this already? :) I am still for it! > > Thanks! > > > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc From lsm5 at fedoraproject.org Mon Feb 16 06:45:35 2015 From: lsm5 at fedoraproject.org (Lokesh Mandvekar) Date: Mon, 16 Feb 2015 00:45:35 -0600 Subject: [CentOS-virt] "docker-master" package: daily builds of docker master branch Message-ID: <20150216064535.GA26153@naruto> Daily builds of docker master branch are available in the virt SIG repository as package 'docker-master': http://cbs.centos.org/koji/buildinfo?buildID=690 Should mostly work fine though use it AT YOUR OWN RISK. If you'd prefer to use something stable, you could choose between the RHEL-recompiled 'docker' package available in centos-extras and the 'docker' package available in the virt SIG repository. Feedback/comments/bugs/patches welcome. -- Lokesh Freenode, OFTC: lsm5 GitHub: @lsm5 GPG: 0xC7C3A0DD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From carlopmart at gmail.com Tue Feb 17 08:18:56 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Tue, 17 Feb 2015 08:18:56 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh Message-ID: Hi all, How can I stop/disable a nic in a virtual guest using a virsh command?? I am searching the same effect like if I unplug network cable ... Is it possible?? I have tried with "detach-interface" command without luck. I don't want to remove the nic from guest configuration, only to stop the nic ... Thanks. P.D: Host is CentOS 6.6 x86_64 fully patched. From nux at li.nux.ro Tue Feb 17 11:51:02 2015 From: nux at li.nux.ro (Nux!) Date: Tue, 17 Feb 2015 11:51:02 +0000 (GMT) Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <1195455377.68202.1424173862547.JavaMail.zimbra@li.nux.ro> I don't think it can be done. I would try to remove the VM's vnet from the bridge it's connected to. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "C. L. Martinez" > To: centos-virt at centos.org > Sent: Tuesday, 17 February, 2015 08:18:56 > Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... > > Thanks. > > P.D: Host is CentOS 6.6 x86_64 fully patched. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From s.kieske at mittwald.de Tue Feb 17 13:43:47 2015 From: s.kieske at mittwald.de (Sven Kieske) Date: Tue, 17 Feb 2015 14:43:47 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: Message-ID: <54E34593.1010402@mittwald.de> On 17/02/15 09:18, C. L. Martinez wrote: > Hi all, > > How can I stop/disable a nic in a virtual guest using a virsh > command?? I am searching the same effect like if I unplug network > cable ... Is it possible?? I have tried with "detach-interface" > command without luck. I don't want to remove the nic from guest > configuration, only to stop the nic ... Depending on your network architecture you could just ifdown the vmnet, but this just works if you don't have multiple vms on one vmnet (which you shouldn't). HTH -- Mit freundlichen Gr??en / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K?nigsberger Stra?e 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Gesch?ftsf?hrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplement?rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen From sbonazzo at redhat.com Wed Feb 18 07:35:57 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Wed, 18 Feb 2015 08:35:57 +0100 Subject: [CentOS-virt] oVirt gaps for Virtualization SIG Message-ID: <54E440DD.6040701@redhat.com> Hi, following up to CentOS Virt SIG meeting here is a quick review of the gaps we have for porting ovirt within CentOS Koji. On the manager side, in order to properly build ovirt-engine (the main package in oVirt project) we're missing several pre-requisites. We're relying on a binary packaging of jboss-as 7.1 we ship as ovirt-engine-jboss-as. So first step should be to rebuild Fedora 19 JBoss rpms within CentOS 7. We're also using maven for building ovirt-engine. A proper packaging for using koji as build system requires to re-package ovirt-engine following fedora guidelines [1]. Issue here is that we're missing lot of maven dependencies like google GWT not yet packaged in Fedora and also other dependencies available in Fedora but not in CentOS 7 like: apache-sshd >= 0.11.0 checkstyle >= 5.4 dbunit >= 2.4.8 infinispan >= 5.2.5 javapackages-local jboss-modules >= 1.1.1 maven-checkstyle-plugin >= 2.9.1 maven-jaxb2-plugin >= 0.8.1 maven-processor-plugin >= 1.3.7 openstack-java-client >= 3.0.6 openstack-java-glance-client >= 3.0.6 openstack-java-keystone-client >= 3.0.6 openstack-java-quantum-client >= 3.0.6 openstack-java-resteasy-connector >= 3.0.6 powermock-junit4 >= 1.5 quartz >= 2.1.2 snmp4j >= 2.2.2 spring-ldap >= 1.3.1 springframework-test >= 3.1.1 On the host side we've been able to build everything in koji. Some dependencies have been rebuilt from EPEL but other than that we should be fine[2]. Only blocker we have on this is qemu-kvm-rhev, we discussed about the rhev suffix during the meeting and we haven't reached an agreement yet within oVirt on how to handle it. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1168605 [2] http://wiki.centos.org/SpecialInterestGroup/Virtualization/Roadmap -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com From carlopmart at gmail.com Wed Feb 18 08:10:19 2015 From: carlopmart at gmail.com (C. L. Martinez) Date: Wed, 18 Feb 2015 08:10:19 +0000 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: <54E34593.1010402@mittwald.de> References: <54E34593.1010402@mittwald.de> Message-ID: On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > On 17/02/15 09:18, C. L. Martinez wrote: >> Hi all, >> >> How can I stop/disable a nic in a virtual guest using a virsh >> command?? I am searching the same effect like if I unplug network >> cable ... Is it possible?? I have tried with "detach-interface" >> command without luck. I don't want to remove the nic from guest >> configuration, only to stop the nic ... > > Depending on your network architecture you could just ifdown > the vmnet, but this just works if you don't have multiple > vms on one vmnet (which you shouldn't). > > HTH > > -- Ok, to do a ifdown of virtual bridge it seems the only option. Many thanks to all for your answers. From juergh at gmail.com Wed Feb 18 13:32:55 2015 From: juergh at gmail.com (Juerg Haefliger) Date: Wed, 18 Feb 2015 14:32:55 +0100 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 9:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> >> >> On 17/02/15 09:18, C. L. Martinez wrote: >>> Hi all, >>> >>> How can I stop/disable a nic in a virtual guest using a virsh >>> command?? I am searching the same effect like if I unplug network >>> cable ... Is it possible?? I have tried with "detach-interface" >>> command without luck. I don't want to remove the nic from guest >>> configuration, only to stop the nic ... There's a qemu monitor command for that. You can pass it in through virsh: $ virsh qemu-monitor-command --hmp 'set_link off' Example: # virsh list Id Name State ---------------------------------------------------- 3 dwarf-00000039 running # virsh qemu-monitor-command --hmp dwarf-00000039 'info network' net0: index=0,type=nic,model=virtio-net-pci,macaddr=52:54:00:a8:85:ea \ hostnet0: index=0,type=tap,fd=24 # virsh qemu-monitor-command --hmp dwarf-00000039 'set_link net0 off' ...Juerg >> Depending on your network architecture you could just ifdown >> the vmnet, but this just works if you don't have multiple >> vms on one vmnet (which you shouldn't). >> >> HTH >> >> -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From silvertip257 at gmail.com Wed Feb 18 16:59:22 2015 From: silvertip257 at gmail.com (SilverTip257) Date: Wed, 18 Feb 2015 11:59:22 -0500 Subject: [CentOS-virt] Disable/stop nic in a virtual guest with virsh In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! 1) down the vnetX interface from the host node ip link show dev vnetX ip link set down vnetX ip link show dev vnetX And if using bridged networking, you have one more option. 2) remove the vnetX interface from the bridge brctl delif vnetX Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ -- ---~~.~~--- Mike // SilverTip257 // -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 14:56:46 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 09:56:46 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> Message-ID: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> I'm dealing with an old Xen 3 server, and badly need to update it and all the vm's on it to more contemporary operating systems. So far, so good! Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm having real trouble getting a live cd or installation media to boot in full virtualization to do the update of the guests. I'd normally start by updating the Xen server first, but that's not workable right now. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 wrote: > >> On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez wrote: >> On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske wrote: >> > >> > >> > On 17/02/15 09:18, C. L. Martinez wrote: >> >> Hi all, >> >> >> >> How can I stop/disable a nic in a virtual guest using a virsh >> >> command?? I am searching the same effect like if I unplug network >> >> cable ... Is it possible?? I have tried with "detach-interface" >> >> command without luck. I don't want to remove the nic from guest >> >> configuration, only to stop the nic ... >> > >> > Depending on your network architecture you could just ifdown >> > the vmnet, but this just works if you don't have multiple >> > vms on one vmnet (which you shouldn't). >> > >> > HTH >> > >> > -- >> >> Ok, to do a ifdown of virtual bridge it seems the only option. >> >> Many thanks to all for your answers. > > > * Definitely look to Juerg Haefliger's solution. It's exactly what you want since you requested a method that can be done from the virsh interface. Thanks Juerg! > > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > > Certainly downing the interface using either Juerg's solution via virsh or mine via iproute2 tools is most ideal since it's easier/simpler to reinstate. You can use ifconfig if you prefer it over ip tools, but enjoy those tools and syntax while it remains! [0] ;-) > > [0] https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > > -- > ---~~.~~--- > Mike > // SilverTip257 // > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nkadel at gmail.com Fri Feb 20 15:07:54 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Fri, 20 Feb 2015 10:07:54 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. Nico Kadel-Garcia Email: nkadel at gmail.com Sent from iPhone From nkadel at gmail.com Sat Feb 21 18:20:15 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Sat, 21 Feb 2015 13:20:15 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: On Fri, Feb 20, 2015 at 9:56 AM, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > > Can the Xen server on CentOS 5 para-virtualized CentOS 6? And if not, I'm > having real trouble getting a live cd or installation media to boot in full > virtualization to do the update of the guests. > > I'd normally start by updating the Xen server first, but that's not workable > right now. Following up: I've gotten full virtualization of CentOS 6 on an SL 5 Xen server by using the "virt-install" command and avoiding manual editing of /etc/xen/ config files. I've also been reminded, forcibly, of why I hated the "/etc/xen" directory. The lack of distinction between a "/etc/xen/myserfer", the example files there, and any other unqualified files there as valid configation files means making safe backups of the files such as "myserver.hvm" or "myserver.old" quite painful. I wound up putting /etc/xen/ under git source control, just for tracking changes. From pasik at iki.fi Sun Feb 22 21:41:03 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:03 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <20150222214103.GB10634@reaktio.net> On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote: > I'm dealing with an old Xen 3 server, and badly need to update it and all > the vm's on it to more contemporary operating systems. So far, so good! > Can the Xen server on CentOS 5 para-virtualized CentOS 6? > Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests. > And if not, I'm having real trouble getting a live cd or installation media to boot in > full virtualization to do the update of the guests. > I'd normally start by updating the Xen server first, but that's not > workable right now. > Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV drivers (PVHVM). -- Pasi > Nico Kadel-Garcia > Email: n[1]kadel at gmail.com > Sent from iPhone > On Feb 18, 2015, at 11:59, SilverTip257 <[2]silvertip257 at gmail.com> wrote: > > On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez > <[3]carlopmart at gmail.com> wrote: > > On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske <[4]s.kieske at mittwald.de> > wrote: > > > > > > On 17/02/15 09:18, C. L. Martinez wrote: > >> Hi all, > >> > >> How can I stop/disable a nic in a virtual guest using a virsh > >> command?? I am searching the same effect like if I unplug network > >> cable ... Is it possible?? I have tried with "detach-interface" > >> command without luck. I don't want to remove the nic from guest > >> configuration, only to stop the nic ... > > > > Depending on your network architecture you could just ifdown > > the vmnet, but this just works if you don't have multiple > > vms on one vmnet (which you shouldn't). > > > > HTH > > > > -- > > Ok, to do a ifdown of virtual bridge it seems the only option. > > Many thanks to all for your answers. > > * Definitely look to Juerg Haefliger's solution. It's exactly what you > want since you requested a method that can be done from the virsh > interface. Thanks Juerg! > 1) down the vnetX interface from the host node > ip link show dev vnetX > ip link set down vnetX > ip link show dev vnetX > And if using bridged networking, you have one more option. > 2) remove the vnetX interface from the bridge > brctl delif vnetX > Certainly downing the interface using either Juerg's solution via virsh > or mine via iproute2 tools is most ideal since it's easier/simpler to > reinstate. You can use ifconfig if you prefer it over ip tools, but > enjoy those tools and syntax while it remains! [0] ;-) > [0] [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > -- > ---~~.~~--- > Mike > // SilverTip257 // > > _______________________________________________ > CentOS-virt mailing list > [6]CentOS-virt at centos.org > [7]http://lists.centos.org/mailman/listinfo/centos-virt > > References > > Visible links > 1. mailto:kadel at gmail.com > 2. mailto:silvertip257 at gmail.com > 3. mailto:carlopmart at gmail.com > 4. mailto:s.kieske at mittwald.de > 5. https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/ > 6. mailto:CentOS-virt at centos.org > 7. http://lists.centos.org/mailman/listinfo/centos-virt > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From pasik at iki.fi Sun Feb 22 21:41:42 2015 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sun, 22 Feb 2015 23:41:42 +0200 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> Message-ID: <20150222214142.GC10634@reaktio.net> On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: > Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. > > Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. -- Pasi > Nico Kadel-Garcia > Email: nkadel at gmail.com > Sent from iPhone > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt From nkadel at gmail.com Mon Feb 23 21:49:41 2015 From: nkadel at gmail.com (Nico Kadel-Garcia) Date: Mon, 23 Feb 2015 16:49:41 -0500 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: <20150222214142.GC10634@reaktio.net> References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> <91165FF3-DB52-4882-829B-D1B2C6F355CF@gmail.com> <20150222214142.GC10634@reaktio.net> Message-ID: On Sun, Feb 22, 2015 at 4:41 PM, Pasi K?rkk?inen wrote: > On Fri, Feb 20, 2015 at 10:07:54AM -0500, Nico Kadel-Garcia wrote: >> Sorry about the accidental bulky quoting! Boston public transit is still slow from storms, and I'm using my phone right now. >> >> Also, has Xen console access gotten any better for fully virtualized guests? I've just been forcibly reminded how awkward it was to access the Linux installation screens to manipulate kickstart setups. >> > > I haven't had problems accessing the graphical console of PV or HVM guests. I'm usually using virt-viewer to use the VNC console. > > -- Pasi I was referring to the TTY text console, the one that allows manipulation of boot options. It looks like it's still pretty awkward. Either way, I'm alive right now with fully virtualized CentOS 6 installations. I'd love to switch them to be paravirtualized for the performance benefits, especially since I can't do CD based installations of new hosts on para-virtualized setups, and I don't have a PXE server running for this setup. From Ed at Heron-ent.com Mon Feb 23 23:08:20 2015 From: Ed at Heron-ent.com (Edward L Heron) Date: Mon, 23 Feb 2015 16:08:20 -0700 Subject: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5 In-Reply-To: References: <54E34593.1010402@mittwald.de> <47BFB2B4-84E5-4F15-A1C9-8CF1EEADD4E2@gmail.com> Message-ID: <1424732900.6585.6.camel@elap.rgtravel.com> On Sat, 2015-02-21 at 13:20 -0500, Nico Kadel-Garcia wrote: > ... > Following up: I've gotten full virtualization of CentOS 6 on an SL 5 > Xen server by using the "virt-install" command and avoiding manual > editing of /etc/xen/ config files. > > I've also been reminded, forcibly, of why I hated the "/etc/xen" > directory. The lack of distinction between a "/etc/xen/myserfer", the > example files there, and any other unqualified files there as valid > configation files means making safe backups of the files such as > "myserver.hvm" or "myserver.old" quite painful. I wound up putting > /etc/xen/ under git source control, just for tracking changes. I use virsh list --all to get currently defined VMs and virsh dumpxml to get domain definitions. From rnicholsNOSPAM at comcast.net Tue Feb 24 04:11:06 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Mon, 23 Feb 2015 22:11:06 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest Message-ID: Would someone please point me to some reasonably current instructions for getting greater than 1024x768 video resolution for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online I find stuff from 2009 and 2010 saying, "For details see ...," and linking to a URL that no longer exists, or pages that say, "You need to switch from VNC to Spice," and giving a long list of out-of-date instructions for doing so. (With virt-manager it takes 2 clicks to do that. Of course it doesn't help -- still maxes out at 1024x768.) I've found that I can just append "vga=0x380" to the kernel command line and see Plymouth come up with the full graphical boot screen in the correct 1440x900 resolution, but as soon as gdm starts up, the display scrambles. I find suggestions to generate an xorg.conf file, but no mention of what to put in it. I can run "Xorg -configure", but the resulting file contains nothing about video modes, so it's not apparent what needs to be added. I find it particularly annoying that a Windows 7 guest can set any resolution I want up to 2560x1600, but a Linux guest can't go higher than 1024x768. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 04:53:40 2015 From: lists at alteeve.ca (Digimer) Date: Mon, 23 Feb 2015 23:53:40 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: Message-ID: <54EC03D4.10406@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 11:11 PM, Robert Nichols wrote: > Would someone please point me to some reasonably current > instructions for getting greater than 1024x768 video resolution for > a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online > I find stuff from 2009 and 2010 saying, "For details see ...," and > linking to a URL that no longer exists, or pages that say, "You > need to switch from VNC to Spice," and giving a long list of > out-of-date instructions for doing so. (With virt-manager it takes > 2 clicks to do that. Of course it doesn't help -- still maxes out > at 1024x768.) > > I've found that I can just append "vga=0x380" to the kernel > command line and see Plymouth come up with the full graphical boot > screen in the correct 1440x900 resolution, but as soon as gdm > starts up, the display scrambles. I find suggestions to generate > an xorg.conf file, but no mention of what to put in it. I can run > "Xorg -configure", but the resulting file contains nothing about > video modes, so it's not apparent what needs to be added. > > I find it particularly annoying that a Windows 7 guest can set any > resolution I want up to 2560x1600, but a Linux guest can't go > higher than 1024x768. I played with this and found that, in fact, I had to switch the spice / qxl. With that change, I had no trouble pushing EL6 to much higher resolutions. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7APUAAoJECChztQA3mh0OCoP/jW8jmGWWVdIirc+4G+kvo+S LZrJxIxZVDfJHioICZink8JJOKm9m5k8k0FKB6YonoLNWOgk8HlHfTTzG9dToT/C Rk3oTrI8pDCsMwccngd0VSVR2EQtmzQBp/O/38JHPM0/VjKnum/I1NWli8g5Xoq2 Q1BqAbrYJ2SAhVht2G91DKsP/nPLq93hBU+UrJkhg5bi3aFCw/Da53v5G3oOZTfr 9qS0RoibthrrF2yCIiXW0kdsEtwk8m+RYFroKjGh/PWcYIKhJdU2Rn8a6gDwRYPg 90fVCYwrqir1HChWsYGc0q+p3DNh/0WmPHjbfbs5o66erD2MZkkm7tbyM8gTcl3F 03wKyhO8qoFcCcgbLRBDb/pYKMX3ChOw7b1RFrYah1xWlZCNAWaBCVYm7DUGMfrV zqb70dVEkUch6f+rVxEo6mrWlj4927Pnp9pefTJ6aVibLZZBA040cVCMTpAwpa7H VsR3QhCcwhOpsCdn0WRCZFJyWlGO88Ry5A0RMUHrceBh0wPdTPPDhMiSg1qTlqCT 0VtaBiYeLevEzoMqnqcRI/+wW0/ooJzp5KjkxjFVVVLqwpqNQkHhEMvUBNLuF5Ui 6O5pZSwFk4K1c5sgOfxWkGuvYjKYmUW/BlnsTpulOzHsOVcJwREUC+IrXIftytfI BJ+4n8EX52YmiORmmGRJ =SO1z -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Tue Feb 24 11:11:28 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Tue, 24 Feb 2015 12:11:28 +0100 Subject: [CentOS-virt] Reminder: CentOS Virt SIG IRC meeting on #centos-devel at 14:00 UK time today Message-ID: See http://wiki.centos.org/SpecialInterestGroup/Virtualization -------------- next part -------------- An HTML attachment was scrubbed... URL: From rnicholsNOSPAM at comcast.net Tue Feb 24 21:15:25 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Tue, 24 Feb 2015 15:15:25 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54EC03D4.10406@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> Message-ID: On 02/23/2015 10:53 PM, Digimer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/02/15 11:11 PM, Robert Nichols wrote: >> Would someone please point me to some reasonably current >> instructions for getting greater than 1024x768 video resolution for >> a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I search online >> I find stuff from 2009 and 2010 saying, "For details see ...," and >> linking to a URL that no longer exists, or pages that say, "You >> need to switch from VNC to Spice," and giving a long list of >> out-of-date instructions for doing so. (With virt-manager it takes >> 2 clicks to do that. Of course it doesn't help -- still maxes out >> at 1024x768.) >> >> I've found that I can just append "vga=0x380" to the kernel >> command line and see Plymouth come up with the full graphical boot >> screen in the correct 1440x900 resolution, but as soon as gdm >> starts up, the display scrambles. I find suggestions to generate >> an xorg.conf file, but no mention of what to put in it. I can run >> "Xorg -configure", but the resulting file contains nothing about >> video modes, so it's not apparent what needs to be added. >> >> I find it particularly annoying that a Windows 7 guest can set any >> resolution I want up to 2560x1600, but a Linux guest can't go >> higher than 1024x768. > > I played with this and found that, in fact, I had to switch the spice > / qxl. With that change, I had no trouble pushing EL6 to much higher > resolutions. Thank you for the reassurance that it _should_ work. I finally got it going. The VM still always starts out in 1024x768 and I have to set the higher resolution every time I log in. For a while, that was working only the first time I set it, and on subsequent logins any attempt to change the resolution either locked up or caused the Xorg server to crash. All the RPMs verified OK and a forced fsck of the filesystems found nothing. I eventually just reinstalled the whole VM, and it's working now. The whole thing was bringing back bad memories of an ancient version of Slackware and kernel version 0.99pl53. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From lists at alteeve.ca Tue Feb 24 21:18:36 2015 From: lists at alteeve.ca (Digimer) Date: Tue, 24 Feb 2015 16:18:36 -0500 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: References: <54EC03D4.10406@alteeve.ca> Message-ID: <54ECEAAC.6050001@alteeve.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/02/15 04:15 PM, Robert Nichols wrote: > On 02/23/2015 10:53 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 23/02/15 11:11 PM, Robert Nichols wrote: >>> Would someone please point me to some reasonably current >>> instructions for getting greater than 1024x768 video resolution >>> for a CentOS 6 guest on a CentOS 6 KVM/qemu host? When I >>> search online I find stuff from 2009 and 2010 saying, "For >>> details see ...," and linking to a URL that no longer exists, >>> or pages that say, "You need to switch from VNC to Spice," and >>> giving a long list of out-of-date instructions for doing so. >>> (With virt-manager it takes 2 clicks to do that. Of course it >>> doesn't help -- still maxes out at 1024x768.) >>> >>> I've found that I can just append "vga=0x380" to the kernel >>> command line and see Plymouth come up with the full graphical >>> boot screen in the correct 1440x900 resolution, but as soon as >>> gdm starts up, the display scrambles. I find suggestions to >>> generate an xorg.conf file, but no mention of what to put in >>> it. I can run "Xorg -configure", but the resulting file >>> contains nothing about video modes, so it's not apparent what >>> needs to be added. >>> >>> I find it particularly annoying that a Windows 7 guest can set >>> any resolution I want up to 2560x1600, but a Linux guest can't >>> go higher than 1024x768. >> >> I played with this and found that, in fact, I had to switch the >> spice / qxl. With that change, I had no trouble pushing EL6 to >> much higher resolutions. > > Thank you for the reassurance that it _should_ work. I finally got > it going. The VM still always starts out in 1024x768 and I have to > set the higher resolution every time I log in. For a while, that > was working only the first time I set it, and on subsequent logins > any attempt to change the resolution either locked up or caused the > Xorg server to crash. All the RPMs verified OK and a forced fsck > of the filesystems found nothing. I eventually just reinstalled > the whole VM, and it's working now. > > The whole thing was bringing back bad memories of an ancient > version of Slackware and kernel version 0.99pl53. In my experience, once I set the resolution, it keeps that resolution through reboots/logins. The initial login page sits at 1024x768, but once logged in, it takes the resolution I asked for. - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU7OqsAAoJECChztQA3mh0PHkP/jUOw8IjIaUrAFyakd+1s9W+ wNCTeDRJqmrFbuw/FqLaU5SmiRYrOv1pl7Aaxw8SISDWngk2HGgBBByMC+rhWbL6 TwJjeEFZqeYbICz9IkWXBiOXnoqdvjFCegl5H5XaQVneXtyV586+wm+G+dvsX7op N3NxxsqBNND09VjOUrLWexaXtOtoWONhv/CN6UukMB2vcB5RTgm73blMvtW2EBCr 6Lj9L/y/BFEkq1UJFFk7b+VlI+U7YNtLyWi+XziKX613H7zhko8JRZcFhfaRCMwW 07dP1/EdaooFOLEXzOZ2FMLd0Tpp+enWdJfzZBzAZtXO8vB8pimlaB2G1FAbdyaU mOc6fDXLEW0H0kITLOlL6KAgFlYBTfb13O7u4x/5Enc4AYO6rpwrJmWIWiOPJEqa 8BKgSbVAB9fcaZZwvVNGNkvxpEZGBDWQSXxU4Ha7wRUq0WazHV97fms9Xa1Cs7I2 n4VAoMFK3+FOjA3N2UIKpZkDPwZUi811FRHKCN2vuByPDotfRj6JNYOCZuUKtsWC mR0BSmDsA4qk7ljkXbnX/fP29aXVAdtCYOOZwCJxpoPLbSNXtX/Cglbf8vn8/NDm ToIJxJlwz/JRuwIY2BLnThVK2wKASgA59bzHHdo0ouc4v5gbShmjEt+E0/uOLyC9 iqtmEdvyI6j1SAnudkcU =3tYH -----END PGP SIGNATURE----- From lars.kurth.xen at gmail.com Wed Feb 25 12:32:12 2015 From: lars.kurth.xen at gmail.com (Lars Kurth) Date: Wed, 25 Feb 2015 12:32:12 +0000 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday Message-ID: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> I would need a volunteer to kick off and start the meeting Lars From rnicholsNOSPAM at comcast.net Wed Feb 25 22:13:51 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 16:13:51 -0600 Subject: [CentOS-virt] Video resolution for CentOS guest In-Reply-To: <54ECEAAC.6050001@alteeve.ca> References: <54EC03D4.10406@alteeve.ca> <54ECEAAC.6050001@alteeve.ca> Message-ID: On 02/24/2015 03:18 PM, Digimer wrote: > In my experience, once I set the resolution, it keeps that resolution > through reboots/logins. The initial login page sits at 1024x768, but > once logged in, it takes the resolution I asked for. It's working that way for me now that I have installed kernel-ml-3.19.0 from elrepo in the guest. With the 2.6.32 kernel that CentOS 6 provides, the behavior could best be described as "confused." I might get a login screen at 1024x768 but with the content rendered as though it were 1440x900 and the login dialog half off the edge of the screen. Or, I might be logged in and looking at a screen properly drawn at 1024x768, but when I bring up the display preferences dialog it claims I am already at 1440x900 and refuses to change. And, occasionally when I would try to change the resolution the display would lock up and, one time, the whole X server crashed. All that goes away with the guest running 3.19.0 kernel, and that also makes sound work properly in the guest, so I'm happy now, at last. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From rnicholsNOSPAM at comcast.net Thu Feb 26 04:49:02 2015 From: rnicholsNOSPAM at comcast.net (Robert Nichols) Date: Wed, 25 Feb 2015 22:49:02 -0600 Subject: [CentOS-virt] Managing virt-manager's ever growing log file Message-ID: I'm looking for suggestions on managing the ever growing log file from virt-manager (~/.virt-manager/virt-manager.log). All the info I've read says that the log file is overwritten on each virt-manager startup. That is demonstrably not true, at least for virt-manager-0.9.0-28.el6. I see "virt-manager startup" entries going all the way back to the first time I started it. So, it looks like some arrangement with logrotate is in order. Does a running virt-manager have any facility for telling it to close and reopen its log file, or do I have to use the "copytruncate" function of logrotate? -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. From sbonazzo at redhat.com Thu Feb 26 07:13:07 2015 From: sbonazzo at redhat.com (Sandro Bonazzola) Date: Thu, 26 Feb 2015 08:13:07 +0100 Subject: [CentOS-virt] Virt SIG meeting on March 10th - I am on holiday In-Reply-To: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> References: <7355B237-D29D-4D31-872D-FD167DAF0859@gmail.com> Message-ID: <54EEC783.8040901@redhat.com> Il 25/02/2015 13:32, Lars Kurth ha scritto: > I would need a volunteer to kick off and start the meeting If nobody else step in, I can take care of starting the meeting. > Lars > _______________________________________________ > CentOS-virt mailing list > CentOS-virt at centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com