XenServer 7 has launched!
-
Can't wait till our lab boxes are back online so that we can get this installed!
-
@scottalanmiller What is the hold up?
-
@aaronstuder said in XenServer 7 has launched!:
@scottalanmiller What is the hold up?
I haven't even heard if it is racked yet or not.
-
@olivier said in XenServer 7 has launched!:
@FATeknollogee said in XenServer 7 has launched!:
If I'm understanding you guys correctly, most of these "features" are available via the XS Community ISO..?
Edited your post and sorted with what I believe is in "free" XenServer vs Enterprise. I'm not 100% sure for everything, but let's say at first sight.
Free :
• Support for SMB storage
• Export Pool Resource Data
• Direct Inspect APIs <- I'm not 100% sure about it, didn't checked yet
• Intel Secure Measured Boot (TXT)Enterprise:
• Dynamic Workload Balancing (via a Citrix Appliance)
• GPU Virtualization (vGPU) with NVIDIA GRID and Intel GVT-g (well, I don't have the hardware to try it)
• In-memory read cachingI don't know:
• Automated Windows VM Driver Updates
• Automatic updating of the Management Agent
• VMware vSphere to XenServer Conversion utilities (probably provided externally, but I think it's free)The vGPU is also available in the community edition.
.
-
So… why can't I use yum to install packages? I've enable the repos, but yum told me that
One of the configured repositories failed (Sconosciuto), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Disable the repository, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> 4. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot find a valid baseurl for repo: base/7-2.1511.el7.centos.2.10/x86_64Any idea about that?
-
It is telling you that the repo failed. Either your repo data is wrong or the repo has gone down.
-
@scottalanmiller said in XenServer 7 has launched!:
It is telling you that the repo failed. Either your repo data is wrong or the repo has gone down.
Ehm… it's the standard CentOS 7 base repo!
This one:[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
enabled=1
exclude=kernel kernel-abi-whitelists kernel-debug kernel-debug-devel kernel-devel kernel-doc kernel-tools kernel-tools-libs kernel-tools-libs-devel linux-firmware biosdevname centos-release systemd* stunnel kexec-tools ocaml*
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7And of course it's working on a standard CentOS 7!
-
Check your DNS.
-
@scottalanmiller said in XenServer 7 has launched!:
Check your DNS.
It seems to me that it's working…
[root@localhost ~]# ping google.it
PING google.it (216.58.198.35) 56(84) bytes of data.
64 bytes from mil04s04-in-f3.1e100.net (216.58.198.35): icmp_seq=1 ttl=54 time=69.4 ms
@scottalanmiller, have you try to use yum on any new XS7 installation? Try it yourself, I think that there's something wrong with the default setup… -
I'm running into this exact issue. I came back here while searching for answers.
-
Our cluster was scheduled to be up and running yesterday, but I've heard no news on it yet. So sadly have not been able to look into doing any testing, yet.
-
Right now I can't get HA-Lizard installed because I can't download the drbd packages. I've been messing with all the *.repo files, but no joy so far.
-
Same repo error as above?
-
Poking at it some more and it looks like there is something sideways about the $releasever variable in the /etc/yum.repos.d/CentOS.* The resulting URL is http://mirror.centos.org/centos/7-2.1511.el7.centos.2.10/os/x86_64/repodata/repomd.xml.
The one that I get manually navigating is: http://mirror.centos.org/centos/7.2.1511/os/x86_64/repodata/repomd.xml
-
That's what I have been thinking. Autodetecting repos are very fragile and I see them fail all of the time. Put in a static, direct link and I bet it will work just fine.
-
I replaced the references in CentOS-Base.repo with 7.2.1511 and that took away some of the errors, but it still failed. Looks like I'll need to update the other *.repo files unless there is a way to change what is going into the $releasever variable.
-
@Kelly said in XenServer 7 has launched!:
I replaced the references in CentOS-Base.repo with 7.2.1511 and that took away some of the errors, but it still failed. Looks like I'll need to update the other *.repo files unless there is a way to change what is going into the $releasever variable.
What does this show...
cat /etc/redhat-release
-
@scottalanmiller said in XenServer 7 has launched!:
@Kelly said in XenServer 7 has launched!:
I replaced the references in CentOS-Base.repo with 7.2.1511 and that took away some of the errors, but it still failed. Looks like I'll need to update the other *.repo files unless there is a way to change what is going into the $releasever variable.
What does this show...
cat /etc/redhat-release
XenServer release 7.0.0-125380c (xenenterprise)I get the same output from /etc/centos-release which is what the distroverpkg variable in yum.conf references.
-
Yup, there is the issue. The repos don't like that different name than what they handle.
-
Well, altering the distroverpkg to distroverpkg=7.2.1511 isn't fixing anything. Now $releasever is not expanding.
