Displaying 7 results from an estimated 7 matches for "a880".
Did you mean:
880
2019 Jan 30
2
EPEL repo problem
...github.com/puiterwijk/check_metalink to
> see if we can pin down the proxy which is the problem (there are 14 and our
> checks are showing they are ok so I need to pin this down somewhere).
>
[sdstern at sugaree check_metalink]$ ./check_metalink --repo epel
--check-mirrors
Client IP: 2604:a880:800:a1::6ab:c001
Testing repo=epel, arch=x86_64
Metalink provided by: proxy11.fedoraproject.org
Server date: Wed, 30 Jan 2019 14:43:18 GMT
Repo epel, arch x86_64 errored: list index out of range
OK metalinks (0):
Bad metalinks (0):
Exception metalinks (1): epel.x86_64
OK metalink means that at l...
2019 Jan 31
1
EPEL repo problem
...which is the problem (there are 14 and
> >
> > our
> >
> > > checks are showing they are ok so I need to pin this down somewhere).
> >
> > [sdstern at sugaree check_metalink]$ ./check_metalink --repo epel
> > --check-mirrors
> > Client IP: 2604:a880:800:a1::6ab:c001
> >
> > Testing repo=epel, arch=x86_64
> >
> > Metalink provided by: proxy11.fedoraproject.org
> > Server date: Wed, 30 Jan 2019 14:43:18 GMT
> >
> > Repo epel, arch x86_64 errored: list index out of range
> > OK me...
2019 Jan 30
0
EPEL repo problem
...t; to
> > see if we can pin down the proxy which is the problem (there are 14 and
> our
> > checks are showing they are ok so I need to pin this down somewhere).
> >
> [sdstern at sugaree check_metalink]$ ./check_metalink --repo epel
> --check-mirrors
> Client IP: 2604:a880:800:a1::6ab:c001
>
> Testing repo=epel, arch=x86_64
> Metalink provided by: proxy11.fedoraproject.org
> Server date: Wed, 30 Jan 2019 14:43:18 GMT
> Repo epel, arch x86_64 errored: list index out of range
> OK metalinks (0):
> Bad metalinks (0):
> Exception m...
2019 Jan 30
5
EPEL repo problem
This keeps logging:
Could not get metalink
https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was
14: HTTPS Error 503 - Service Unavailable
I've removed the epel-release package, done a "yum clean all", then
reinstalled it, but still get the same error.
--
-- Steve
2011 May 17
6
Problems creating a Fedora 14 domU using XCP 1.0 and xe
Hi Folks:
I am having trouble creating a Fedora 14 domU on a XCP 1.0 dom0
hypervisor and am hoping that someone can help me figure out what I am
doing wrong.
Here is what I did (per the user''s guide and reference manual):
## Step 1. Create the VM:
# uuid=$(xe vm-install template=''Other install media''
new-name-label=''test'')
## Note: I also tried
2007 Nov 30
4
[PATCH 0/4] [AMD IOMMU] Enable PCI passthru for HVM guest
Hi,
The following 4 patches enable direct device assignment (PCI passthru)
for HVM guest
on AMD IOMMU platforms. Please apply them against C/S 16491 as the named
order.
To enable AMD IOMMU, please add "enable_amd_iommu" as xen boot
parameter.
1-cleanup.patch: code cleanup, bug fix, minor enhancements to existing
amd-iommu codes.
2-passthru-amd.patch: passthru support, modifications to
2009 Jan 31
14
[PATCH 2/3] xen: make direct versions of irq_enable/disable/save/restore to common code
Now that x86-64 has directly accessible percpu variables, it can also
implement the direct versions of these operations, which operate on a
vcpu_info structure directly embedded in the percpu area.
In fact, the 64-bit versions are more or less identical, and so can be
shared. The only two differences are:
1. xen_restore_fl_direct takes its argument in eax on 32-bit, and rdi on 64-bit.