similar to: Upgrade to Xen 4.7

Displaying 20 results from an estimated 20000 matches similar to: "Upgrade to Xen 4.7"

2016 Aug 03
2
Downgrading from Xen 4.6 to 4.5
Dear All I have an up to date CentOS 7 with Xen 4.6 I have noticed in some posts here and there that PCI Passthrough is not working in 4.6 for some people, but is working in 4.5 How can I downgrade to Xen 4.5 so I can test this out? Many thanks Francis -------------- next part -------------- An HTML attachment was scrubbed... URL:
2017 Mar 28
0
Upgrade to Xen 4.7
On 03/28/2017 07:00 AM, Francis The Metman wrote: > Dear All > I am running CentOS 7 with Xen 4.6 > I see 4.7 is out now, and want to upgrade to see if the USB Passthrough will work. I have not been able to get it to work in 4.6 > What is the best way to upgrade. I am using the centos-release-xen at the moment. The 4.7 xen on the CBS is not production ready. At some point we will
2017 Jan 09
2
Updated libvirt packages (2.2.0-1) in testing
On Thu, Jan 5, 2017 at 6:38 PM, Francis The Metman <themetman at themetman.net> wrote: > I have tried updating using yum update and get the same error as before: > ========================================================================== > ---> Package libvirt-daemon.x86_64 0:1.3.0-1.el7 will be updated > --> Processing Dependency: libvirt-daemon = 1.3.0-1.el7 for package:
2017 Jan 09
1
Updated libvirt packages (2.2.0-1) in testing
George, Thank you SO much, problem solved using the testing repo. Regards Francis ----- Original Message ----- > From: "PJ Welsh" <pjwelsh at gmail.com> > To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org> > Sent: Monday, 9 January, 2017 12:18:12 PM > Subject: Re: [CentOS-virt] Updated libvirt packages (2.2.0-1) in testing
2016 Aug 08
1
Downgrading from Xen 4.6 to 4.5
> > working in 4.6 for some people, but is working in 4.5 > > How can I downgrade to Xen 4.5 so I can test this out? > > Many thanks > > We do not provide a CentOS-7 version of Xen lower than 4.6. At the > time > we started Xen support on CentOS-7, 4.6 was already stable and that > was > our first release for CentOS-7. > > We do currently have both
2016 Dec 31
2
yum update Failing with libvirt-daemon error
Dear Jean-Marc, Thank you for replying. I Installed CentOS 7 and centos-virt from the normal repos (CentOS-Xen) in December 2015 and have not had to build anything. I am running CentOS 7, not sure if it has automatically updated itself to 7.3, so I would expect the updates to come from the repo, and not need building from source. Regards Francis ----- Original Message ----- > From:
2016 May 12
2
PCI Passthrough not working
I am running Xen 4.6 on CentOS 7 in a Dell Poweredge T430 I need PCI Passthrough to get USB working. I am following the Xenproject Wiki I have enabled the Virtulasation in the BIOS. I have xen_pciback as a module I have issued the command: xl pci-assignable-add 00:1a0.0 and it shows up fine when I issue this xl pci-assignable-list I have pci=['00:1a.0'] on the DomU config file I
2016 Dec 30
2
yum update Failing with libvirt-daemon error
PJ My server is critical to me, but not the public, fortunately. I can take it down as I suggested, but am a bit reluctant to do so until I have heard more opinions. Presumably your system update failed using your script, so it will probably fail for me if I copy it. I will keep a copy anyway. ----- Original Message ----- > From: "PJ Welsh" <pjwelsh at gmail.com> > To:
2016 Jun 22
3
PCI Passthrough not working
Further to my messages back in May I have at last got round to trying to get my DomU to recognise USB devices. I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64. I have to manually make the port available before creating the DomU by issuing the command: xl pci-assignable-add 00:1a.0 otherwise nothing shows in: xl pci-assignable-list I have added this to my .cfg file as per the
2016 Jul 03
2
PCI Passthrough not working
Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does
2016 May 16
2
PCI Passthrough not working
Dear George please find attached the three files as requested. I have used iommu=soft in the grub command line for the kernel in the domU as explained before. many thanks Francis From: "George Dunlap" <dunlapg at umich.edu> To: "francis" <francis at choughs.net>, "centos-virt" <centos-virt at centos.org> Sent: Monday, 16 May, 2016 10:29:09
2016 May 16
1
PCI Passthrough not working
>On Mon, May 16, 2016 at 12:00 PM, Francis Greaves <francis at choughs.net> wrote: >> Dear George please find attached the three files as requested. >> I have used >> >> iommu=soft >> >> in the grub command line for the kernel in the domU as explained before. >> many thanks >The options are: >1. Figure out what the other device is and
2017 Jan 05
4
Updated libvirt packages (2.2.0-1) in testing
The CentOS 7.3 release updated to libvirt 2.0, which is now taking precedence over the previous virt sig libvirt packages (which were 1.3). I've pulled in the changes from Fedora 25, which uses libvirt 2.2.0. I've built and tested them for CentOS 7 and they work for me. (I'm having some infrastructure issue testing C6.) Please test them if you have an opportunity. I'll leave
2016 Jun 24
2
PCI Passthrough not working
On Wed, Jun 22, 2016 at 11:49 AM, Francis Greaves <francis at choughs.net> wrote: > More information... > I have pcifront showing as a module in the DomU and the usb shows in dmesg > as: > [ 3.167543] usbcore: registered new interface driver usbfs > [ 3.167563] usbcore: registered new interface driver hub > [ 3.167585] usbcore: registered new device driver usb >
2016 Feb 22
2
Garbled screen after RAM Scrub on boot
Yes I usually work headless, but I have been setting it up from new, so need to see what is going on. Regards Francis From: "Scot P. Floess" <sfloess at nc.rr.com> To: "Francis Greaves" <francis at choughs.net> Cc: "centos-virt" <centos-virt at centos.org> Sent: Monday, 22 February, 2016 17:02:12 Subject: Re: [CentOS-virt] Garbled screen
2016 Feb 23
2
Garbled screen after RAM Scrub on boot
Dear George, Thanks for the input and ideas. Unfortunately bootscrub=false dos not work, not does setting nothing for vga, still get the 'Little white squares'! I am asking the xen-users as you suggest Regards, Francis From: "George Dunlap" <dunlapg at umich.edu> To: "Francis Greaves" <francis at choughs.net>, "centos-virt" <centos-virt
2016 Dec 31
0
yum update Failing with libvirt-daemon error
Jiri Denemark has already proposed to help rebuild libvirt for CentOS-Xen but I don't know if he got all that is need to do so ? Maybe I could help also, but I would have to learn the Centos build system first. Regards, Jean-Marc Le 31/12/2016 ? 08:46, Francis The Metman a ?crit : > Dear Jean-Marc, Thank you for replying. > I Installed CentOS 7 and centos-virt from the normal repos
2016 Dec 31
0
yum update Failing with libvirt-daemon error
As libvirt from Xen is 1.3.0 and libvirt from CentOS 7.3 is now 2.0.0, libvirt from Xen has to be rebuild to upgrade the new libvirt 2.0.0 See my previous post : https://lists.centos.org/pipermail/centos-virt/2016-November/005255.html I've done it for my own repo : https://copr.fedorainfracloud.org/coprs/jmliger/virt7-upstream/ Regards, Jean-Marc Le 30/12/2016 ? 17:56, Francis The
2016 Feb 22
4
Garbled screen after RAM Scrub on boot
Dear All I am using Centos 7 with Xen 4.6 on a Dell Poweredge T430 When the machine boots, after the 'Scrubbing Free RAM' message, I get a screen filled with little white squares until the login prompt, so I cannot see what is happening as the machine boots. Also there is nothing on the screen when I reboot. My /etc/default/grub is GRUB_DISTRIBUTOR="$(sed 's, release
2017 Jan 09
0
Updated libvirt packages (2.2.0-1) in testing
Thank you. I will try the centos-virt-xen-testing in development hopefully soon. On Mon, Jan 9, 2017 at 4:32 AM, George Dunlap <dunlapg at umich.edu> wrote: > On Thu, Jan 5, 2017 at 6:38 PM, Francis The Metman > <themetman at themetman.net> wrote: > > I have tried updating using yum update and get the same error as before: > >