Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation) packages making their way to centos-virt-xen-testing
Hi Nathan, On Thu, Jan 18, 2018 at 9:31 PM, Nathan March <nat...@gt.net> wrote: >> -Original Message- >> As there are now quite many options to choose from, what would be the >> best option performance wise for running 32bit domUs under xen-4.6? >> >> Best, >> Peter >> > > It's worth taking a look at the table in the latest XSA, it helps clarify a > fair bit: > > https://xenbits.xen.org/xsa/advisory-254.html thanks for pointing this out, but there is a disclaimer: "Everything in this section applies to 64-bit PV x86 guests only." It also reads in the advisory "32-bit PV guests cannot exploit SP3" So I am wondering if I just "yum update" will I get some fixes I do not need that will slow my guests down? Best, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation) packages making their way to centos-virt-xen-testing
Thanks George. As there are now quite many options to choose from, what would be the best option performance wise for running 32bit domUs under xen-4.6? Best, Peter On Wed, Jan 17, 2018 at 7:14 PM, George Dunlap <dunl...@umich.edu> wrote: > I've built & tagged packages for CentOS 6 and 7 4.6.6-9, with XPTI > "stage 1" Meltdown mitigation. > > This will allow 64-bit PV guests to run safely (with a few caveats), > but incurs a fairly significant slowdown for 64-bit PV guests on Intel > boxes (including domain 0). > > If you prefer using Vixen / Comet, you can turn it off by adding > 'xpti=0' to your Xen command-line. > > Detailed information can be found in the XSA-254 advisory: > > https://xenbits.xen.org/xsa/advisory-254.html > > Please test and report any issues you have. I'll probably tag then > with -release tomorrow. > > 4.8 packages should be coming to buildlogs soon. > > -George > ___ > CentOS-virt mailing list > CentOS-virt@centos.org > https://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Xen custom vifname
Hi, Centos 7 Xen4CentOS - 4.6.1 Open vSwitch When i specify custom name of the domU NIC than it refues to start vif = [ 'vifname=vNIC1' ] libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-openvswitch online [10168] exited with error status 1 libxl: error: libxl_device.c:1084:device_hotplug_child_death_cb: script: ip link set vif38.0 name vNIC1 failed libxl: error: libxl_create.c:1381:domcreate_attach_vtpms: unable to add nic devices libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 38 libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy guest with domid 38 libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 38 failed When removed the vifname settings the domU starts just fine. vif = [ '' ] Same error when used wi classic Bridge for networking. Is vifname setting still supported? On CentOS5 & Xen 3.4 this parameter works just fine. Regards ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] installing xen on c7
On 28/02/16 01:52, Yamaban wrote: > IMHO, the best way to solve this would a additional line in the spec-file: > "Provide: kernel-dom0" for those kernel that are provide this > functionality. > > Then the xen-packages could "Require: kernel-dom0" > no matter which way the kernel functionality came to be. The issue there is you can't expect every third-part kernel vendor to add that provide. Many of them won't even realize that their kernel is dom0 capable because any kernel from 3.0 and up is by default (Red Hat went to lengths to actually rip this functionality out of their kernels). So by doing this you still end up forcing people who want to use other legitimate kernels to jump through a lot more hoops. I think a better way would be to create a group that includes xen and the kernel (and possibly other things) and have the installation instructions install the group instead of individual packages. It becomes much easier to replace individual packages (or simply not install them) without breaking deps for yum that way. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing
On 11/02/16 06:07, George Dunlap wrote:
> BTW, we had a discussion about this particular idea at the Virt SIG
> meeting, and KB said that different naming of packages like this can
> cause dependency problems. For example, a package depends on
> "xen-version >= $N" will fail because as far as rpm is concerned, you
> don't have package 'xen' installed at all.
You explicitly provide it:
Provides: xen-%{version}-%{release}
This has the added benefit that once "xen" is removed from the repo,
attempts to install "xen" will actually install "xen46".
I'm rather surprised that kb didn't know to do that.
Peter
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] When will CentOS 7.1 become available as an AWS AMI?
I am in need of some AWS instances of this version. There are "community" instances of 7.1 but I would strongly prefer an official release from CentOS team over trusting my base image to an unknown publisher. Is there any plan/projection of when CentOS will publish 7.1 to the AWS marketplace? ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing
On 15/01/16 05:57, George Dunlap wrote: > As mentioned yesterday, Xen 4.6 packages are now available for > testing. These also include an update to libvirt 1.3.0, in line with > what's available for CentOS 7. Please test, particularly the upgrade > if you can, and report any problems here. Per conversation in IRC, Xen 4.6 no longer includes xend and therefore no longer has the "xm" command. This is problematic for people who may be using xm in various scripts on their host (such as home-brewed backup scripts). I think it's a bad idea to break this functionality without warning by allowing a simple "yum update" to remove it. You will take a lot of people by surprise and cause such scripts to stop working, if people are running yum cron the situation becomes even worse. I think that due to this lack of backwards compatibility with Xen 4.4 and earlier versions it would be a good idea to not force the upgrade on people who are not wary of it. I propose that the new packages carry the name "xen46" and they purposefully conflict with the old "xen" packages. That will require people to take positive action to do the upgrade and hence avoid breaking systems unintentionally. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS 6 Virt SIG Xen 4.6 packages available in centos-virt-xen-testing
On 22/01/16 01:32, George Dunlap wrote:
> 1. In the Xen 4.4 packages (first released October 2014), xend was
> disabled by default; so anyone using xend at the moment has already
> manually intervened to enable deprecated functionality
Xen4CentOS was first available in CentOS 6.4 with Xen 4.2, so we really
need to look back that far. You may be right here, though, because Xen
4.2 was the first version of Xen that used xl by default. xl was still
new at the time, though, and there were admins, especially ones who were
migrating from a CentOS 5 based Xen, who would have preferred XM and
were already using XM in other installs, so xm would have still seen
widespread use at the time. That means that those boxes could very well
still be using xm now.
> 2. In 4.4, the first time xm was executed, it printed this warning:
The warning was not in Xen 4.2 or 4.3. Considering that it is
reasonable for someone to expect enterprise-like behavior from an
enterprise distro, one would not assume that XEND would just disappear
overnight.
> Also, in most cases "s/xm/xl/g;" Just Works; most people have reported
> that changing from xm -> xl was pretty painless. So this isn't like
> upgrading from Python 2 to Python 3 (or QT 4 to 5, or...).
There are some notable differences that can break compatibility in many
cases:
1. xl does not support the "xl create foo" syntax, one must now use,
"xl create /path/to/foo.cfg". This I can actually see breaking
compatibility for a *lot* of people.
2. xl requires those that use the old xend networking setup to switch
to a distro-based networking setup. This can be a serious undertaking
for someone running a production machine with the easy possibility of
breaking networking and requiring either OOB or physical access to the
machine to fix. Therefore this in itself means that someone should be
able to plan for the upgrade at a convenient time rather than having it
sprung on them with a "yum update".
3. Config files no longer support embedded python.
...There are additional incompatibilities that could bite an unwary
admin in the ass.
> This would avoid breaking things for people still using xm, which
> certainly has some value. However it has some costs:
>
> * The packages between C6 and C7 will now be slightly different,
> increasing the maintenance burden. This is not only in the spec file,
> but also in all the associated scripting machinery for managing
> packages in the CBS and smoke-testing packages before pushing them
> publicly.
>
> * Instructions for installing Xen are now differend between C6 and C7,
> and slightly more complicated, as they have to explain about Xen 4.6
> vs alternatives.
>
> * Users who have heeded the warning and switched to xl will have to
> make an extra effort to switch to Xen 4.6. If they don't follow
> centos-virt, they may not notice that there's a new package to upgrade
> to.
These are certainly concerns, but there is precedence for doing it this way:
mysql (5.0), mysql51, mysql55 in EL5.
bind (9.3), bind97 in EL5.
...etc
These are all cases of Red Hat offering newer versions without wishing
to break older installs, and at least in the case of mysql, dropping
support for the older version alltogether, but still doing it in a way
that doesn't *force* the admin to upgrade and break their systems as a
result.
I do believe that looking to what Red Hat has done in the past is
appropriate when determining what action to take ourselves as people
expect the same level of stability from CentOS, and consequenty Xen4CentOS.
> On the other hand, explicitly moving to a "xen${VER}" (both for C6 and
> C7) would make it simpler for people to step up and maintain older
> versions in parallel if anybody wanted to do so.
This is true, and I'd leave that choice up to you.
Peter
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] CentOS 6 VM image for paravirtualizaton on CentOS Xen server
On 03/16/2015 11:25 AM, Nico Kadel-Garcia wrote: I've got CentOS VM's running fine, and have done them before. But previously, I deployed the same base OS on the VM as on the Xen server, so paravirtualization posed few risks. And I had control of the DHCP setup. so I could trivially set up a tftp server to do a non-CD installation, because Xen, at last look, doesn't support installing a paravirtualized host from a CD image. It does as long as (1) the kernel has Xen PV support (CentOS 6 standard kernel does) and (2) it has the necessary drivers in the initrd (I think this is where the CD image is lacking), then you should, in theory, be able to pv-grub boot to the CD. Alternatively you can boot to the CD on another box first, copy the kernel off to a USB stick, and generate a new initrd with the xen drivers included, then put those on the Xen host and boot to the VM CD image using those in the kernel= and initrd= lines in the domain.cfg file. The other way is to boot to the CD as an HVM domain and install, then convert it to a PV domain afterwards, which is not all that difficult to do. There is a third way which involves using yum to install the @core group plus kernel to an image, then tweak and boot to that as a PV domain. This is how I have done it in the past. So I'm right back to my effectively unanswered original questions. So please: I asked a very specific pair of questions, and they remain unanswered. CentOS 5 Xen server (hypervisor, or Dom0, whatever we want to call it this week): Does CentOS 6 work, paravirtualized, on such a server? Yes, I have done that until I upgraded the CentOS 5 host to CentOS 6 a couple years ago. And given my deployment issues, does anyone have a base OS image I can get a copy of? Sorry my image templates that I use are highly customized for my own work, but I have told you three different ways to accomplish it above. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] understanding problems
On 06/16/2014 08:55 PM, Sven Kieske wrote: A bridge does not need an ip address itself to pass traffic from interface A to interface C, Correct, but... so it could look like this: hw interface a --- bridge b --- vm interface c 192.168.1.3 none192.168.1.4 Wrong. In the above configuration the IP address 192.168.1.3 won't be recognized. That IP needs to be on the bridge in order to work on the host. This is what the OP was referring to with this statement: Am 14.06.2014 08:41, schrieb lee: But when you attach them to bridges and don't have IP addresses on the bridges, then they are unreachable. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
On 06/12/2014 05:17 PM, lee wrote: I knew before I started that network setup would be a PITA because years ago, I set up a VM for someone who didn't have a 64bit system to compile a 64bit version of some software. The network setup being so ridiculously difficult has kept me from touching VMs ever again for years. It's just too difficult and not worth the effort unless you're really forced to do it. Networking can be confusing until it clicks then it all seems to fall into place, there is a certain amount of understanding of the overall picture of how bridge networking (or other types of networking) works that once you get that understanding it becomes a lot simpler. One thing that probably confuses you is that there are certain parts of the networking that are done by the dom0 distro, certain parts are done by Xen scripts and front and backend drivers, and some parts are done by the domu operating system. Understanding how those parts fit together and how different distros do the same thing but perhaps with different configs helps a lot to getting a grasp on the whole. Obviously better documentation would help with this, but like anything of this nature there is a learning curve that you simply have to get over before you can really become proficient. As a user, I'm used to get an ISO of an installer or of a life system, put that into a DVD drive or write it to an USB stick and to boot from that to do the installation. Why can't I do that with xen? You can do that with Xen, KVM, and most other types of virtualization. The idea is that you need to block-attach the disk (or ISO file if you prefer not to use a physical disk) to the VM and then it can be mounted and used as install media (or any other type of media for that matter). This can be done from teh domain config file or from the xm (or xl) command line. Another quick note specifically for you. I have noticed in past messages that you seem to be having some confusion with xm vs xl commands and some explanation about that is probably in order to clear up that confusion. xm and xl are nearly identical commands to use, but xm is the old way and xl the new way. Basically put, xm interfaces with a daemon running in the dom0 (xend) which in turn interfaces with the hypervisor, while xl uses libraries to interface directly with the hypervisor and so eliminates the need for xend. You will see documentation refer to one or the other, sometimes almost interchangeably, because the two tools have almost identical usage, but what you should be aware of is that you really need to pick one and stick with it, Xen does not work well if you try to use xm for some commands and xl for others. Since you're new I would recommend xl because xm is deprecated in newer versions of Xen, so if you want to future-proof your knowledge xl is the way to go. Also if you're using xl then you should not be running the xend daemon, this is easily accomplished by using chkconfig and service to turn xend off. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
On 06/11/2014 04:21 AM, Lars Kurth wrote: Hi all, following the discussion on about documentation, I was wondering whether we need to look at a standard way in which we recommend how to provision images for VMs. Am starting this with a Xen hat, but the discussion should not be specific to this. There are a number of options, but all have some trade-offs == #1 virt-install == == #2 xen-tools == == #3 virt-builder (http://libguestfs.org/virt-builder.1.html) == == #4 Cloud Image from Cloud Image SIG == This is not a complete list of the ways you can install a VM either. My personal preference is to manually create the filesystem for the VM and then install the OS core with yum. Then after tweaking some config files you can start up the VM and finish installing whatever else you want with yum as well. While I don't think that this should be the recommended install method it might be worth mentioning and even giving a wiki page with some instructions on how to do it this way. Doing an install like this is actually very good for a newbie because you get your hands dirty and get a really good understanding of how yum works and the internals of the distro. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/13/2014 03:47 AM, Dario Faggioli wrote: If you're up for it, Xen wiki will be glad to host it! :-P I would love to do a writeup on this, but my time is extremely limited right now. I'll see what I can do. Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTmg3YAAoJEAUijw0EjkDvHKoH/RTd1myCecNTYALvO8l7nRo/ pDjImHlWaT1N5RUODIkZ66EeGF1BJYPaGMrmmjR9R7GGycUkp1eBG3kkGBc1tyMi Hhd9ZjQUvc5IH2BPh2ik8tCom4d6V2+KMEr1ZpYXfYCMi92HaB23xo52x5PKO4pc 4+PJSBe4Dq/UuBtHHyIbRL9WYXLlCybLPVAyQt65pKNyJduwt6M2yJgeRLFB4Iz+ clQ47+roC7UGEpbo6pxjEnU76/WYwZRFefbiBrl4i3Fpl6sWlwBuPH1zyYup3Cwa 0NSJcB6q0rulOcU24OQSWB3O2SpGXOn2WjcmmZQpBZphviMBPOUJeOSAHGU4e6Q= =xjTL -END PGP SIGNATURE- ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Preferred method of provisioning VM images
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/13/2014 08:30 AM, Peter wrote: On 06/13/2014 03:47 AM, Dario Faggioli wrote: If you're up for it, Xen wiki will be glad to host it! :-P I would love to do a writeup on this, but my time is extremely limited right now. I'll see what I can do. Actually, what I'll probably do is wait for CentOS 7 to drop and then do a writeup based on that. I'll be wanting to set up a VM from it anyways and so then I'll kill two birds with one stone. Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTmg9BAAoJEAUijw0EjkDv5yYIAK7seuXSzib/L4qmLqvXc/ME OgCa5T7PaOJEApDcjmLQttD4X2ln6VpWhua0KWJq0v+sWpuQSxduEfIF0Pqafi3B WmNoaKz5tHj1BzE20fxDumUX2C4OkKNuT438h6KyEBjVBTvcZEREw8YmS+k7ecsH CMl7KZdJ1ou5NRowurcfGZTpPIS3BBn1+ZmxL4X+cp/XBJ+tLdMAA74R9HHGTQPo wTG/tENHB1XFa8ePLFzGawzmbBglsCBHw5Aw5ugnUe9bklkMJYj3M2ldZVMHtjwK VGcqovyHNR4ZhxG8KnOYBT8S0p9qPXE1tWIABfJ9T89c0TUX2dKkaRMIO1/5vEY= =wpUX -END PGP SIGNATURE- ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] centos5 xen domu with X: screens not found [SOLVED]
Hi, On Tue, Mar 18, 2014 at 3:55 PM, Stefano Stabellini stefano.stabell...@eu.citrix.com wrote: Strangely enough according to xenstore, vfb is running and connected. Can you try connecting to it using xm or vncviewer directly? Or maybe setup the guest to use a simple fbcon just to try out if it works, and then setup the more complicated environment you are looking for afterwards? Thank you Stefano for your help. Just to be sure I did the virtualization again (used dd to copy the machine's system and then edited Xen stuff in place) and - surprise, surprise - X login window appeared without any problems in virt-manager. So problem solved. Best, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] centos5 xen domu with X: screens not found
Hi, On Mon, Mar 17, 2014 at 12:42 PM, Stefano Stabellini stefano.stabell...@eu.citrix.com wrote: That should be enough. Is the xen-fbfront module loaded in the guest? Not is not: # lsmod |grep xen xennet 62409 0 [permanent] xenblk 51497 2 I do not think on CentOS5 there is such module available? At least modinfo xen-fbfront does not find it. If that is same as kernel option CONFIG_XEN_FRAMEBUFFER=y then it should be compiled in the kernel? Can you post the output of xenstore-ls after creating the domU? Sure, you can find it here: http://pastebin.com/apZftdEq Little more info about my setup: dom0 is setup on CentOS6 and has the following xen related packages installed: [root@xen2 ~]# rpm -qa |grep xen centos-release-xen-6-2.el6.centos.x86_64 xen-licenses-4.2.4-29.el6.centos.alt.x86_64 xen-runtime-4.2.4-29.el6.centos.alt.x86_64 libvirt-daemon-xen-0.10.2.8-6.el6.centos.alt.x86_64 xen-hypervisor-4.2.4-29.el6.centos.alt.x86_64 xen-libs-4.2.4-29.el6.centos.alt.x86_64 xen-4.2.4-29.el6.centos.alt.x86_64 libvirt-daemon-driver-xen-0.10.2.8-6.el6.centos.alt.x86_64 The goal I am trying to achieve is to replicate the following setup which works ok on a physical server: to be able to run X and issue xhost + as the tomcat user, so a web app running on the same server can access MapXtreme maps provided by Tomcat. I tried installing FreenNX server which did give me a working desktop session for the tomcat user, but issuing xhost + there did not help me (the webapp couldn't access the map service). Best regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Xen4CentOS installation strangeness
Hi, I have a server with Supermicro X7DVL-3 (P9) motherboard, 16G ECC RAM and LSI SAS 1068e RAID controller. I installed CentOS 6.5 64bit on the machine without any problems, but after following the Xen setup steps at http://wiki.centos.org/HowTos/Xen/Xen4QuickStart which installed me the kernel 3.10.32-11.el6.centos.alt.x86_64, I encountered a problem: After Starting certmonger [OK] the screen went black and the system became unresponsive: keyboard was not working (NumLock did not respond) and SSH was not responding either. After first lockup I increased dom0 max mem to 2G, but rebooting after that produced the same result. The strange thing is, that after a third reboot everything worked ok: screen went black for a moment after Staring certmonger [OK] but after that the graphical login screen appeared and I could use the system normally. The fourth reboot went ok as well. Any ideas what could cause this kind of behaviour? Regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Fwd: Building Xen on RHEL7
On 12/22/2013 08:32 PM, Nico Kadel-Garcia wrote: On Sun, Dec 22, 2013 at 1:30 AM, Peter pe...@pajamian.dhs.org wrote: gcc is considered to be part of the standard build toolset and as such is not required to be listed as a dependency in any spec file. Part of a standard build toolset or not, it needs to be mentioned. The dev86 SRPM was pretty old, admittedly. But Fedora, and EPEL, and RHEL, all build their RPM's with mock and koji these days, and gcc is *not* part of the basic build environment. There are reasons, having to do with cross-compilation and alternative compiler toolchains. So RHEL, Fedora, and EPEL RPM's all specify cc or gcc as needed, Do take a good look at those Fedora SRPM's if you think I'm kidding.. I did check before I made the comment in the first place (this is for el6 from epel buildsys-build is the standard install for mock epel-6): $ yum groupinfo buildsys-build ... Group: Buildsystem building group Mandatory Packages: ... gcc gcc-c++ ... Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Fwd: Building Xen on RHEL7
On 12/22/2013 04:33 PM, Nico Kadel-Garcia wrote: My first thought on seeing this thread was Is there some reason to compile from source, rather than from an SRPM, say those at http://dev.centos.org/centos/6/xen-c6/SRPMS/ ? My thinking is that the sources from F19 would be better since RHEL7 is based on F19 they would be a lot closer to RHEL7 than the CentOS 6 Xen sources, although both would probably build with no modifications at all. One thing that the parent didn't mention is where he got the dom0 kernel from. The best place would be just to rebuild the RHEL7 kernel with Xen dom0 support enabled. It is possible that libvirt would need to be rebuilt with Xen support enabled as well, and as I said above, everything else (the Xen tools and hypervisor) could be gotten from Fedora 19. with the caveat that it did not have a gcc dependencies, which I've added to a .spec file, gcc is considered to be part of the standard build toolset and as such is not required to be listed as a dependency in any spec file. and the .spec file for dev86 and for Xen both have badly formatted dates in the %changelog stanza. RHEL 7 is much less tolerant of this than RHEL 6 was. Again, I've edited some .spec files and will try to submit some patches if I can fiind time. The F19 spec files should be fully compliant with the EL7 guidelines. Once I'd satisfied all the dependencies for the SRPM, I was able to build the Xen 4.3.1 tarball pretty easily. It just didn't work well to plug the tarball into the old SRPM and .spec file. Admittedly F19 comes with Xen 4.2.3, rawhide comes with 4.3.1, though, and can probably be directly rebuilt for EL7 without any fuss. But with all that said: why are you bothering with Xen when RHEL and thus CentOS have KVM support built right in? Is there some feature you require that isn't available in the built-in KVM support? Some people like Xen, people like a choice, and it's not all that difficult to add Xen to EL7 anyways. There's no reason to exclude it just because upstream made a political decision. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] new-kernel-pkg needs to be made Xen-aware
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/24/2013 08:14 AM, Johnny Hughes wrote: On 11/23/2013 12:07 PM, Kenneth Porter wrote: I ran yum update the other day on my dom0 and let it pull a new kernel. The RPM install scriptlet runs /sbin/new-kernel-pkg (part of the grubby package) to update grub.conf. It writes a new record to boot the Linux kernel instead of Xen. It would be nice if it noticed that it was running inside Xen and wrote a suitable record for that. We are aware of this issue and for now, you have to manually run /usr/bin/grub-bootxen.sh We are also aware that the setup that grub-bootxen.sh provides is very basic and does not learn/keep custom settings. This is something that we would love to receive community input to fix. Modifying the spec file for the Xen kernel package to call an additional script in %post should be trivial, and since this kernel package doesn't come from upstream you should be free to do so. The issue with using grubby is that grubby expects the kernel to be defined in the kernel line and the initrd in the initrd line. But with Xen boot entries both are defined in module lines instead. It shouldn't bee too difficult to eitehr write a new script that would work similar to grubby but looks at the module lines instead, or to modify grubby itself to do so. Note that I (and I would think some others) like to have two boot entries for each new kernel. One that boots via the Xen hypervisor and a second that boots directly to the kernel itself, I would love to see such a script be able to copy both of these entries when installing a new kernel. Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSkRyGAAoJEAUijw0EjkDvsacIAKIpNGtDDsu9Sbt6cJALmgaD VKHVGI7TJcam2Nebb8GLpKnJz6BNGf4xhD6cGMzG3FtHJ8DNcTiKmP7IlRfLpNsD i/jc+Wnis6LkJgMSHf1LlXkYvYLqCF+S4AZP+nqLvae5HPA4rfKf4h/8ULinYv88 ujoZvArToc0oIJGmQZQOGfeWO9aVPYrtm6LCRda0TqAvKRoL/EzE6/GWUzin+rOQ x346BdYymnEIS9UTTUl3t+Eo4qBKyFH3i92Dqe/KXongINiSt36UdsWvhpFWgurS W0gjdgUKE68Fh/NlbjddDWNIVsWHk+2AikDcaRTlvzn2Rw8i6DdNA8TCxtNq2zU= =2zVN -END PGP SIGNATURE- ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] convert xen to kvm
hi, yes it is possible. use the tool virt-v2v cheers peter mattias m...@mjw.se wrote: ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Upgrading libvirt and qemu to latest version
Hi, I am considering upgrading the libvirt to v0.10.1 and qemu-kvm to v1.2 qemu version because they are recommended by Ceph. I am wondering does CentOS kernel support upstream qemu well? And are there rpms for theses version somewhere? or I have to build myself? Thanks. Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] proper way to snapshot
Hi, On Fri, Apr 27, 2012 at 12:48 AM, aurfalien aurfal...@gmail.com wrote: On Apr 26, 2012, at 2:24 PM, Nux! wrote: On 26.04.2012 19:21, aurfalien wrote: On Apr 26, 2012, at 2:15 PM, Nux! wrote: On 26.04.2012 19:12, aurfalien wrote: On Apr 26, 2012, at 1:54 PM, Nux! wrote: On 26.04.2012 18:23, aurfalien wrote: Hi, While there are a few howtos floating around, what is the standard way to snapshot guests? I went through and converted from raw to pre allocated meta data qcow2 images for this purpose. Some howtos suggest to do an xml snapshot file as so; domainsnapshot nameUbuntuServer_10.10-16032011/name descriptionSnapshot of OS install and updates/description /domainsnapshot And then to run as so; virsh snapshot-create UbuntuServer_10.10 UbuntuServer_10.10-ss.xml Seems a bit over kill. I was thinking more along the lines of this; qemu-img snapshot -c $date $filename qemu-img convert -f qcow2 -O qcow2 -s $date $filename $filename-$date Or something like this.Anyways, hoping to see how you all are doing this for best practice sort of thing. Hi, I just use LVM snapshots; it's the fastest, most reliable way I could come with. Hi, I don't have LVMs. But if I did, would it be possible to only snapshot a directory or will it snapshot the entire file system? Assuming you use LVM on the host to provide the virtual machine with a (virtual) HDD, then snapshotting that will obviously be (virtual) disk-wise. I used a simple non LVM partitioning scheme. Can I do directory based snapshots in LVM or is it the entire FS? I can re implement or redo my host to use LVM. - aurf ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt Aurf, LVM is filesystem level, not directory level. What I'd recommend is to reinstall and use LVM, make a couple of volumes for / and swap and leave the rest for virtual machines. The real problem with this is that snapshots are still on the local box and I don't have a SAN. With KVM based qcow snaps, I can do snaps over NFS. You can copy LVM snapshots easily to some other location with dd (= create image file of the snapshot LVM volume) that you can restore where ever you like using dd again. Regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] routing problem with domU bridged to two networks
Hi, On Wed, Mar 7, 2012 at 10:13 PM, Ed Heron e...@heron-ent.com wrote: My goal: To access NFS shares on a (non-virtualized) file server in the LAN network from the domU web server in the DMZ network. snip My problem: If my domU web server is connected to both LAN and DMZ using the two bridges xenbr0 and xenbr1, I can access the NFS share from the domU web server and everything else works as expected, except for one thing -- my workstations in the LAN cannot anymore access the web server: web pages do not open anymore and from the workstations I cannot ping the domU. If the web server domU is only connected to DMZ via xenbr0, the workstations can access it ok. Any advice what I am doing wrong and I could fix my setup? The postrouting command uses -o eth2. To NAT LAN requests to your DMZ web server, shouldn't you be using xenbr0? Thanks Ed for your advice, that was the thing I was missing. After adding a postrouting command for xenbr0 everything works as expected. Cheers, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] XEN multiple bridge problem - VM won' start!
Hi, 2011/11/18 Matija Draganović mdra...@gmail.com: I've been using CentOS Xen on a server that has 2 VM's configured. The default configuration includes one physical iface that is propagated (by a default bridge) to the VM's. You do not mention which version of CentOS and Xen you are using? Since I wanted to configure additional physical iface, define a new bridge and propagate it to the viface-s of the VM's, i configured the bridge/phys. iface and brought it up (here are configurations that I set up): - eth3 DEVICE=eth3 BOOTPROTO=static HWADDR=D4:85:64:4B:76:AB ONBOOT=yes #HOTPLUG=no #DHCP_HOSTNAME=kdr-3k-4r-3o-07 BRIDGE=br0 TYPE=Ethernet - br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=none ONBOOT=yes If this is a CentOS5 machine with the CentOS provided Xen 3.0 packages, then here is info how i got my bridges to work with that setup: * For dom0 I configured eth0 and eth1 as usual in /etc/sysconfig/network-scripts * I did not configure br0 or br1 in network-scripts, but instead I created a file called /etc/xen/scripts/my-network-script having this contents: #!/bin/sh dir=$(dirname $0) $dir/network-bridge $@ vifnum=0 netdev=eth0 bridge=xenbr0 $dir/network-bridge $@ vifnum=1 netdev=eth1 bridge=xenbr1 * Then I modified in dom0 the file /etc/xen/xend-config.sxp in the following way: #(network-script network-bridge) (network-script my-network-script) * Now rebooting dom0 made the bridges available * After that I could configure them in my domU config: vif = [ mac=00:16:3E:69:29:25,bridge=xenbr0,script=vif-bridge,mac=00:16:3E:E6:B0:6D,bridge=xenbr1,script=vif-bridge ] * After starting the domU I could configure the interfaces in network-scripts using the hardware addresses specified in the domU config It seems that configuring bridging is done a bit differently in different Xen versions, so this might not work if you are using some other kind of config. With CentOS6 and 3rd party Xen 4.1 packages this procedure did not work at all and instead I needed to do the following: * in dom0 create the br0 and br1 devices in network-scripts * in dom0 /etc/xen/xend-config.sxp put instead: #(network-script network-bridge) (network-script /bin/true) * and in dom0 use different configuration for the domU config files like this: vif = [ mac=00:16:3E:69:29:25,bridge=br0,mac=00:16:3E:E6:B0:6D,bridge=br1 ] Hope this helps, unfortuantely I am not familiar with virsh at all. Best, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] centos6 and xen4 dom0 memory allocation
Hi, On Sat, Oct 22, 2011 at 4:21 PM, Pasi Kärkkäinen pa...@iki.fi wrote: and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduced to 1140M even though I think ballooning is disabled and there is free memory available? And the weird thing is that dom0 has done some swapping: Did you check the amount of memory in dom0 right after boot? You *might* need to add also mem=2028M cmdline option for dom0 linux kernel (vmlinuz). Thanks for the tip! I also googled a tip to set dom0-min-mem to the same amount. I will try this next. Shutting down domUs and making more memory available does not reverse the effect, dom0 does not allocate more memory. dom0 is not supposed to allocate more memory! dom0 is a virtual machine. Free memory goes into Xen hypervisor, check with xl info or xm info. I am aware that dom0 is a virtual machine. As I reported earlier, xl info shows: total_memory : 24567 free_memory : 3698 xen_commandline : dom0_mem=2048M There is free memory. Dom0 is supposed to have 2048M memory. Why is it I have only 1140M memory in use with dom0? When I first booted the machine I used to have 2048M memory and then Xen started reducing the memory when I started more domUs. So my problem is: Why is Xen reducing the amount of memory in dom0, even I have disabled ballooning and there is more than enough memory available for the dom0 and domUs? Just a moment ago I experienced the following: I shut down a domU having 4096M memory. Then I tried to start it again and Xen complained that there is no memory available. The second restart produced the following error: libxl: error: libxl_dom.c:168:libxl__build_pv xc_dom_kernel_file failed: Bad address cannot (re-)build domain: -3 There is something fishy going around... I will now try to yum update dom0 and domUs, set the dom0-min-mem to 2048M and reboot and see what happens. Best regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] centos6 and xen4 dom0 memory allocation
Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from http://xenbits.xen.org/people/mayoung/EL6.xen on my centos6 server. I am running 2.6.32-131.12.1.el6.xendom0.x86_64 kernel available from the same place. 'xl info' reports about available memory as follows: total_memory : 24567 free_memory: 3698 xen_commandline: dom0_mem=2048M and in xend-config.sxp I have: (dom0-min-mem 256) (enable-dom0-ballooning no) (total_available_memory 0) Now one would think that I should have 2048M memory for dom0, right? I started from there, but when starting domUs it has been reduced to 1140M even though I think ballooning is disabled and there is free memory available? And the weird thing is that dom0 has done some swapping: # free -mt total used free sharedbuffers cached Mem: 1140 1052 88 0 2 12 -/+ buffers/cache: 1038102 Swap: 8194 85 8109 Total:9335 1138 8197 Shutting down domUs and making more memory available does not reverse the effect, dom0 does not allocate more memory. What am I missing here or is my xen setup acting strangely here? Best regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Emergency help needed on host network randomly stop working.
Hi, On Wed, Oct 12, 2011 at 10:43 AM, Magicloud Magiclouds magicloud.magiclo...@gmail.com wrote: Hi, This is a Centos 5.5 host with one xen guest. About 2 weeks ago, the host randomly lost network connection. By this I mean I could not connect to the services on it, or ping it. Also was the status of the guest. From serial console, I connected to the host, trying to see what happened. No clue (any error messages) in messages or dmesg. ifdown/ifup the interface did not help, either. Only rebooting was my only choice. Searching through Google, I got the information that some other guys met similar problem, and resolved by setting stp on with the bridge interface. I set it, too. And the problem still occurs. Any idea what I should check now? So I assume that the problem occurs just with the xen domU and not with the dom0? And your solution is to reboot the domU (not dom0)? With loosing network you mean you cannot ping your gateway ip and/or you cannot ping the domU from your gw? You are running the latest kernel/xen packages provided by centos on your dom0 and domU? How have you configured network on this server, can you post your configs (vif line in dom0 config aand newtork config files from the domU)? And you are sure you have an unique MAC address in your LAN for your domU? Best, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Should I switch and if so what is the procedure
On 10/06/2011 12:58 PM, Rich wrote: Its seems that I should switch then. I have 2 servers using Xen. What is the procedure to conver them? Is there procedure I should use. I have to use the same boxes I can not export vm's. I've used the following links to migrate our office servers: http://www.gloudemans.info/migrate-paravirtualized-xen-to-kvm-under-rhel/ http://www.cyberciti.biz/faq/troubleshooting-kvm-virtualization-problem-with-log-files/ http://www.cyberciti.biz/faq/rhel-linux-kvm-virtualization-bridged-networking-with-libvirt/ In any case, be cautious, make backups and don't do this at 3:00 AM. Peter On Wed, Oct 5, 2011 at 7:46 PM, Dennis Jacobfeuerborn denni...@conversis.de mailto:denni...@conversis.de wrote: On 10/05/2011 06:16 PM, Ed Heron wrote: On Wed, 2011-10-05 at 10:55 -0400, Rich wrote: Since the Xen and Linux kernel people have finally made peace and Xen is going to be included with the kernel, should I keep using the Xen virtual server with Centos or should I switch to KVM? I am running Centos 5.7 now. I guess the real question is can I still use Xen with Centos 6? The support end of life for CentOS 5 is listed as March 31, 2014 (http://wiki.centos.org/FAQ/General#head-fe8a0be91ee3e7dea812e8694491e1dde5b75e6d). There isn't any pressure, at this point, to convert your VM hosts to CentOS 6 unless there is some feature you require. I doubt RH will add XEN support to RHEL 6. They don't like to add functionality to an existing product. We can hope they bring XEN back in RHEL 7. While Xen will probably return in RHEL 7 simply because it is part of the upstream kernel now I doubt it will be officially supported by Red Hat. Between buying Qumranet (http://www.redhat.com/promo/qumranet/) and now Gluster (https://www.redhat.com/promo/storage/) it is clear that Red Hat aims to become a provider of a complete independent virtualization stack and is unlikely to support competing products directly. The question is what does Xen offer that KVM cannot provide? Looking at the slides of the KVM Forum 2011 (http://www.linux-kvm.org/page/KVM_Forum_2011) there seem to be many interesting improvements in the pipeline so at some point the question really is why hold on to Xen at all when there is not real reason to? Regards, Dennis ___ CentOS-virt mailing list CentOS-virt@centos.org mailto:CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Should I switch and if so what is the procedure
On Wed, Oct 5, 2011 at 7:16 PM, Ed Heron e...@heron-ent.com wrote: There was some discussion about producing RPMs to add XEN support into CentOS 6, but I haven't seen any status updates, recently. I am succesfully using the dom0 EL6 kernel from: http://xenbits.xen.org/people/mayoung/testing/x86_64/ and xen4 packages for EL6 by provided by this repositry: http://xenbits.xen.org/people/mayoung/EL6.xen/ It would be great to get at least the dom0 kernel in the centosplus repo... Regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Connection stall when connecting to XEN guests
Hello I have a physical server (Dell Poweredge 1950III) running current CentOS 5.4 x86_64 and the XEN hypervisor, provided by CentOS. This machine has 2 virtual machines installed, both with CentOS 5.4 x86_64. Unfortunatly SSH connections coming both, from an external machine or from DOM0, regularly stall, for a period of some minutes. In other words, while working through SSH, at a given moment everything freezes and after some minutes thaws again. We have several other machines with similar hardware/software configurations, but none of these has similar stalls. Anyway, when attaching the console with xm console vm-name there are no stalls at all. Does anybody have any suggestion on where to start to trouble shoot this problem? Regards, Peter -- Dott. Peter Hopfgartner R3 GIS Srl - GmbH Via Johann Kravogl-Str. 2 I-39012 Meran/Merano (BZ) Email: peter.hopfgart...@r3-gis.com Tel. : +39 0473 494949 Fax : +39 0473 069902 www : http://www.r3-gis.com XING : http://www.xing.com/go/invita/8917535 ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Connection stall when connecting to XEN guests
compdoc wrote: Ive seen this happen in some distros when the option 'UseDNS' is set to yes in the file sshd_config Of course, there could be issues with your network setup as well... ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt Nothing seems to change. Indeed, also pinging the guest has the same problems. I'm also monitoring this machine since this morning and services are up and down and I can not understand why. iptables on dom0 and vm guest are, at the moment, turned off. Summarizing: 1. This happens on all XEN guests on this physical server, except dom0. It does not happen on any other server/xen guest. 2. Outgoing network connections are fine. 3. xm console xen_guest works fine. Peter -- Dott. Peter Hopfgartner R3 GIS Srl - GmbH Via Johann Kravogl-Str. 2 I-39012 Meran/Merano (BZ) Email: peter.hopfgart...@r3-gis.com Tel. : +39 0473 494949 Fax : +39 0473 069902 www : http://www.r3-gis.com XING : http://www.xing.com/go/invita/8917535 ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Migrating from VMWare Workstation
Peter Hopfgartner wrote: Dear virt list I have some virtual machines running on my notebook under VMWare 6.5.2 64 bit that I would like to move to a current 64 bit CentOS 5.3 machine with a current Intel Xeon processor. The virtual machines do use the GUI, e.g. they are not text only. Is it better to use VMware server or Xen? If using Xen, do I have to convert the images? Regards, Peter 1: you can not run XEN and VMWare server at the same time. VMWare refuses to install with a XEN-enabled kernel. 2: A How-To for migrating CentOS images is at http://www.funkypenguin.info/tutorial/how-to-convert-a-centos-5-vmware-image-to-xen/ Will try it next week. Peter -- Dott. Peter Hopfgartner R3 GIS Srl - GmbH Via Johann Kravogl-Str. 2 I-39012 Meran/Merano (BZ) Email: peter.hopfgart...@r3-gis.com Tel. : +39 0473 494949 Fax : +39 0473 069902 www : http://www.r3-gis.com ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Migrating from VMWare Workstation
Dear virt list I have some virtual machines running on my notebook under VMWare 6.5.2 64 bit that I would like to move to a current 64 bit CentOS 5.3 machine with a current Intel Xeon processor. The virtual machines do use the GUI, e.g. they are not text only. Is it better to use VMware server or Xen? If using Xen, do I have to convert the images? Regards, Peter -- Dott. Peter Hopfgartner R3 GIS Srl - GmbH Via Johann Kravogl-Str. 2 I-39012 Meran/Merano (BZ) Email: peter.hopfgart...@r3-gis.com Tel. : +39 0473 494949 Fax : +39 0473 069902 www : http://www.r3-gis.com ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
