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 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 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] libvirt POSTIN scriplet failure
While updating a CentOS 6 Xen domU server with yum I received the following error: Updating : libvirt-0.10.2-29.el6_5.7.i686 65/168 Non-fatal POSTIN scriptlet failure in rpm package libvirt-0.10.2-29.el6_5.7.i686 warning: %post(libvirt-0.10.2-29.el6_5.7.i686) scriptlet failed, exit status 1 After a reboot everything seems to run fine. Anything I should be considered about? Regards, 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 [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] centos5 xen domu with X: screens not found
Hi, I am in a process to virtualize an existing non-virtualized CentOS5 system. Everything else works fine except X: virt-manager's console just hangs after bootup. I can use the text console though and what I see in X server's log is the error message "screens not found". The only graphics related setup I've done is in the domu config this line: vfb = [ "type=vnc,vncunused=1,keymap=fi" ] Is there something else I should configure on the guest or in dom0? Regards, Peter ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Xen4CentOS installation strangeness
Hi, On Tue, Mar 4, 2014 at 10:08 PM, Robert Dinse wrote: > > I'd look in the logs for Xorg failures. > Thanks Robert, it seems Xorg is indeed the one to blame in this case. Apparently the network issues I experienced at the same time were just bad luck and not related, so while booting another time I could SSH into the system. These errors are visible in the Xorg logs: " [ 128.186] (EE) [ 128.186] (EE) Backtrace: [ 128.186] (EE) 0: X (xorg_backtrace+0x36) [0x46d196] [ 128.186] (EE) 1: X (0x40+0x72f99) [0x472f99] [ 128.186] (EE) 2: /lib64/libpthread.so.0 (0x7fb7b6fa3000+0xf710) [0x7fb7b6fb2710] [ 128.186] (EE) 3: /usr/lib64/xorg/modules/drivers/xgi_drv.so (0x7fb7b4459000+0x21a95) [0x7fb7b447aa95] [ 128.186] (EE) 4: /usr/lib64/xorg/modules/drivers/xgi_drv.so (0x7fb7b4459000+0x23159) [0x7fb7b447c159] [ 128.186] (EE) 5: X (dixSaveScreens+0x15e) [0x4695ee] [ 128.186] (EE) 6: X (0x40+0x7d061) [0x47d061] [ 128.186] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7fb7b56a3d1d] [ 128.187] (EE) 8: X (0x40+0x26189) [0x426189] [ 128.187] (EE) [ 128.187] (EE) Segmentation fault at address 0x0 [ 128.187] Fatal server error: [ 128.187] Caught signal 11 (Segmentation fault). Server aborting [ 128.187] [ 128.187] (EE) Please consult the CentOS support " Some more googling revealed that other people have had similar problems. This is most likely caused by either Xen or the new Xen enabled kernel that was installed as with stock CentOS6 kernel it is not happening. I ran some hardware diagnostics tests for the motherboard and CPUs which passed ok. I tried creating a new Xorg configuration file and starting X with that, but it did not help. Changing the server's runlevel to 3 resulted the server to boot ok in non-graphical mode. As I can run virt-manager remotely, there is no reason for me to debug this further, and I just wanted to report the issues I've experienced here on the list. 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] proper way to snapshot
Hi, On Fri, Apr 27, 2012 at 12:48 AM, aurfalien 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; >>> >>> >>> UbuntuServer_10.10-16032011 >>> Snapshot of OS install and updates >>> >>> >>> 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 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. >> >> 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
[CentOS-virt] routing problem with domU bridged to two networks
As I received no response on the general CentOS list, I'll repost it here as the question is about Xen virtual machine routing. This is my network setup: http://pastebin.com/kyWpTQYU Lets assume my dom0's eth2 public ip is 1.2.3.33 and my dmz network 11.22.33.96/255.255.255.224 . I have created NAT from my LAN with iptables. You can see my /etc/sysconfig/iptables here: http://pastebin.com/1FqSTvPH And this is my dom0 routing table: http://pastebin.com/gNjTFHp5 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. What I tried: I attached the domU to both bridges using this Xen config: vif = [ "mac=00:0c:29:de:3a:fe,bridge=xenbr0","mac=00:0C:29:76:19:85,bridge=xenbr1" ] and then created two eth interfaces inside the domU mapping to the MAC addresses above, giving eth1 an IP from the DMZ (11.22.33.111) and giving eth2 an IP from the LAN (192.168.0.12). After this I mounted the NFS share from the file server (192.168.0.2). 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? Regards, 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ć : > 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
Replying to myself: On Sun, Oct 23, 2011 at 5:51 PM, Peter Peltonen wrote: > 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. After rebooting I seemed to have 2048M in dom0 regardless of how many domUs were running. But when trying to create the last domU, I was informed that xend was out of memory. At this time I still had something about 5G of real memory available for the last domU which I have configured to consume 4G of memory. I tweaked grub.conf and xend-config.sxp and set 4096M as the dom0 memory and rebooted again. I reduced the domU memory sizes accordingly and all domUs got created without errors. But the strange thing is again dom0 memory which has been reduced from 4096M to 2052M: [root@si ~]# cat /etc/xen/xend-config.sxp |grep dom0-min-mem # dom0-min-mem is the lowest permissible memory level (in MB) for dom0. (dom0-min-mem 4096) [root@si ~]# xl info |grep mem total_memory : 24567 free_memory: 5853 xen_commandline: dom0_mem=4096M dom0_max_vcpus=1 dom0_vcpus_pin [root@si ~]# xl list NameID Mem VCPUs State Time(s) Domain-0 0 2052 1 r- 265.6 xl top reports "(MEM)k" as "2101272" and "MAXMEM(k)" as "no limit". In CentOS5 with Xen3 I have been used to having the amount of memory in dom0 which I have specified. My Xen4 installation seems not to do this. If someone else is using the Xen4 packages from http://xenbits.xen.org/people/mayoung/EL6.xen I would be interested in hearing about your experiences? BR, 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 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 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 Wed, Oct 5, 2011 at 7:16 PM, Ed Heron 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
