Re: [CentOS-virt] Xen 4.12.2 rpms

[Pasi Kärkkäinen]

On Fri, Jan 03, 2020 at 12:26:58PM -0500, Karl Johnson wrote:
>On Fri, Jan 3, 2020 at 4:56 AM Pasi KÀrkkÀinen <[1]pa...@iki.fi> wrote:
> 
>  Hello and Happy 2020!
> 
>  Do we already have a plan to update the xen-412 branch to recent release
>  of Xen 4.12.2 ?
> 
>  I'm happy to test once the rpms are out.
> 
>Anthony built 4.12.2 few weeks ago, see
>[2]https://cbs.centos.org/koji/buildinfo?buildID=27840
>It's in testing for now. Happy 2020!
>

Oh, I somehow missed that. I'll give it a go!


Thanks a lot,

-- Pasi

>Karl
> 
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Xen 4.12.2 rpms

[Pasi Kärkkäinen]

Hello and Happy 2020!

Do we already have a plan to update the xen-412 branch to recent release of Xen 
4.12.2 ? 

I'm happy to test once the rpms are out.


Thanks a lot,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386

[Pasi Kärkkäinen]

Hi,

On Wed, May 22, 2019 at 10:46:25AM +0100, Anthony PERARD wrote:
> On Sun, May 05, 2019 at 02:23:22PM +0300, Pasi Kärkkäinen wrote:
> > Hello,
> 
> Thanks for the bug report.
> 
> > While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following 
> > problem with libvirt/virt-manager when manually installing a new HVM guest 
> > from virt-manager GUI.. basicly the VM installation won't start, because 
> > libvirt/virt-manager is not able to start the VM, due to "missing" 
> > qemu-system-i386 binary:
> > 
> > Unable to complete install: 'unsupported configuration: emulator 
> > '/usr/lib/xen/bin/qemu-system-i386' not found'
> > 
> > Traceback (most recent call last):
> >   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
> > cb_wrapper
> > callback(asyncjob, *args, **kwargs)
> >   File "/usr/share/virt-manager/virtManager/create.py", line 2553, in 
> > _do_async_install
> > guest.start_install(meter=meter)
> >   File "/usr/share/virt-manager/virtinst/guest.py", line 498, in 
> > start_install
> > doboot, transient)
> >   File "/usr/share/virt-manager/virtinst/guest.py", line 434, in 
> > _create_guest
> > domain = self.conn.createXML(install_xml or final_xml, 0)
> >   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in 
> > createXML
> > if ret is None:raise libvirtError('virDomainCreateXML() failed', 
> > conn=self)
> > libvirtError: unsupported configuration: emulator 
> > '/usr/lib/xen/bin/qemu-system-i386' not found
> 
> Starting a guest with libvirt works fine, libvirt is able to find the
> qemu binary. (Well, libxl can...)
> 
> Here is an osstest flight starting an HVM guest with libvirt:
> http://logs.test-lab.xenproject.org/osstest/logs/136701/test-amd64-amd64-libvirt-qemuu-debianhvm-amd64/info.html
> 
> Maybe the issue is that I need to rebuild `libvirt-python' and
> `virt-manager' packages?
> 

Hmm.. maybe. I guess we need to investigate a bit more where the directory path 
is actually coming from..


> > Quick'n'dirty fix is to create a symlink:
> > 
> > ln -s /usr/lib64/xen/bin/qemu-system-i386 
> > /usr/lib/xen/bin/qemu-system-i386
> > 
> > .. after creating that symlink the VM can be started just fine and works OK.
> > 
> > We need to fix that default directory path for qemu-system-i386 to be 
> > correct out-of-the-box..
> 
> I can certainly move the binary from "/usr/lib64" to "/usr/lib", and
> hope it doesn't break anything, with Xen 4.10 packages the qemu binary
> is in /usr/lib64. But to be honest I don't know which is best for CentOS
> between "lib64" and "lib".
> 

I think /usr/lib64/ is the correct location, as the qemu-system-i386 binary is 
64bit:

# file /usr/lib64/xen/bin/qemu-system-i386
/usr/lib64/xen/bin/qemu-system-i386: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, 
BuildID[sha1]=12576991824bc1611d8630aaa30df9b00f175980, stripped



> -- 
> Anthony PERARD


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386

[Pasi Kärkkäinen]

On Sun, May 05, 2019 at 02:23:22PM +0300, Pasi Kärkkäinen wrote:
> Hello,
> 
> While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following 
> problem with libvirt/virt-manager when manually installing a new HVM guest 
> from virt-manager GUI.. basicly the VM installation won't start, because 
> libvirt/virt-manager is not able to start the VM, due to "missing" 
> qemu-system-i386 binary:
> 
> Unable to complete install: 'unsupported configuration: emulator 
> '/usr/lib/xen/bin/qemu-system-i386' not found'
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
> cb_wrapper
> callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/create.py", line 2553, in 
> _do_async_install
> guest.start_install(meter=meter)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
> doboot, transient)
>   File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
> domain = self.conn.createXML(install_xml or final_xml, 0)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in 
> createXML
> if ret is None:raise libvirtError('virDomainCreateXML() failed', 
> conn=self)
> libvirtError: unsupported configuration: emulator 
> '/usr/lib/xen/bin/qemu-system-i386' not found
> 
> 
> Quick'n'dirty fix is to create a symlink:
> 
>   ln -s /usr/lib64/xen/bin/qemu-system-i386 
> /usr/lib/xen/bin/qemu-system-i386
> 
> .. after creating that symlink the VM can be started just fine and works OK.
> 
> We need to fix that default directory path for qemu-system-i386 to be correct 
> out-of-the-box..
> 

Oh, I forgot to paste the rpm versions I have:

libvirt-daemon-config-network-4.10.0-3.xen412.el7.x86_64
libvirt-libs-4.10.0-3.xen412.el7.x86_64
libvirt-python-4.5.0-1.el7.x86_64
libvirt-daemon-4.10.0-3.xen412.el7.x86_64
libvirt-daemon-driver-network-4.10.0-3.xen412.el7.x86_64
libvirt-daemon-driver-libxl-4.10.0-3.xen412.el7.x86_64
libvirt-bash-completion-4.10.0-3.xen412.el7.x86_64
libvirt-client-4.10.0-3.xen412.el7.x86_64
libvirt-glib-1.0.0-1.el7.x86_64

virt-manager-common-1.5.0-1.el7.noarch
virt-manager-1.5.0-1.el7.noarch
virt-viewer-5.0-11.el7.x86_64

xen-runtime-4.12.0-1.el7.x86_64
xen-libs-4.12.0-1.el7.x86_64
xen-ovmf-20180825-1.gitef529e6ab.el7.x86_64
centos-release-xen-common-8-7.el7.centos.x86_64
centos-release-xen-412-8-7.el7.centos.x86_64
qemu-xen-4.12.0-1.el7.x86_64
xen-4.12.0-1.el7.x86_64
xen-hypervisor-4.12.0-1.el7.x86_64
xen-livepatch-build-tools-4.12.0-1.el7.x86_64
xen-licenses-4.12.0-1.el7.x86_64


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] CentOS 7 Xen 4.12 libvirt/virt-manager wrong path for qemu-system-i386

[Pasi Kärkkäinen]

Hello,

While testing Virt-SIG Xen 4.12 rpms on CentOS7 I noticed the following problem 
with libvirt/virt-manager when manually installing a new HVM guest from 
virt-manager GUI.. basicly the VM installation won't start, because 
libvirt/virt-manager is not able to start the VM, due to "missing" 
qemu-system-i386 binary:

Unable to complete install: 'unsupported configuration: emulator 
'/usr/lib/xen/bin/qemu-system-i386' not found'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 2553, in 
_do_async_install
guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 498, in start_install
doboot, transient)
  File "/usr/share/virt-manager/virtinst/guest.py", line 434, in _create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3725, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: unsupported configuration: emulator 
'/usr/lib/xen/bin/qemu-system-i386' not found


Quick'n'dirty fix is to create a symlink:

ln -s /usr/lib64/xen/bin/qemu-system-i386 
/usr/lib/xen/bin/qemu-system-i386

.. after creating that symlink the VM can be started just fine and works OK.

We need to fix that default directory path for qemu-system-i386 to be correct 
out-of-the-box..


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Centos7 Xen hypervisor console= options broken in default grub2 config

[Pasi Kärkkäinen]

Hello,

While testing Virt-SIG Xen 4.12 rpms on CentOS 7, I noticed the default Xen 
hypervisor console= option parameters are broken, and result in an error from 
Xen, and no output on the physical vga console:

>From xen dmesg:

(XEN) Bad console= option 'tty'
 Xen 4.12.0-1.el7
(XEN) Xen version 4.12.0-1.el7 (mockbu...@centos.org) (gcc (GCC) 4.8.5 20150623 
(Red Hat 4.8.5-36)) debug=n  Tue Apr  2 13:09:41 UTC 2019
(XEN) Latest ChangeSet:
(XEN) Bootloader: GRUB 2.02~beta2
(XEN) Command line: placeholder dom0_mem=1024M,max:1024M cpuinfo 
com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all

.. and indeed, 'tty' is not a valid option for Xen hypervisor console= 
parameter. 
That can be easily fixed in "/etc/sysconfig/grub", and executing 
"grub2-mkconfig -o /boot/grub2/grub.cfg" afterwards, but we should fix the 
default..

Here is the working setting (console=com1,vga, instead of console=com1,tty):

# grep GRUB_CMDLINE_XEN_DEFAULT /etc/sysconfig/grub
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 
console=com1,vga loglvl=all guest_loglvl=all"


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Tue, Mar 26, 2019 at 05:36:42PM +, Anthony PERARD wrote:
> On Sun, Mar 24, 2019 at 01:12:53PM +0200, Pasi Kärkkäinen wrote:
> > On Sat, Mar 23, 2019 at 05:00:00PM -0400, Karl Johnson wrote:
> > >On Sat, Mar 23, 2019 at 2:07 PM Karl Johnson 
> > > <[1]karljohnson...@gmail.com>
> > >wrote:
> > > 
> > > 
> > >  Sure, I will update the PR in the next few days.
> > >  Karl
> > > 
> > >I've updated my PR and tested a build, it boots well:
> > >[root@node-tmp1 ~]# cat /proc/version
> > >Linux version 4.9.165-35.el6.x86_64 
> > > ([4]mockbu...@build.aerisnetwork.net)
> > >(gcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC) ) #1 SMP Sat Mar 
> > > 23
> > >14:44:16 EDT 2019
> > >Test rpms: [5]https://repo.aerisnetwork.com/archive/
> > >Anthony will be able to build it on the CBS as devtoolset has been 
> > > removed
> > >from the spec.
> > >
> > 
> > With quick testing the 4.9.165-35.el6 kernel seems to work OK for me!
> > 
> > Anthony: Can you please review the updated PR on github, merge it and kick 
> > of the builds for el6 and el7 ? 
> 
> Done, I've pushed kernel-4.9.165-35.el7 and kernel-4.9.165-35.el6 to
> testing.
> 

Great, thanks a lot! I grabbed kernel-4.9.165-35.el6 from testing, and it seems 
to boot and work OK for me with quick testing.


> -- 
> Anthony PERARD


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

On Sat, Mar 23, 2019 at 05:00:00PM -0400, Karl Johnson wrote:
>On Sat, Mar 23, 2019 at 2:07 PM Karl Johnson <[1]karljohnson...@gmail.com>
>wrote:
> 
> 
>  Sure, I will update the PR in the next few days.
>  Karl
> 
>I've updated my PR and tested a build, it boots well:
>[root@node-tmp1 ~]# cat /proc/version
>Linux version 4.9.165-35.el6.x86_64 ([4]mockbu...@build.aerisnetwork.net)
>(gcc version 4.4.7 20120313 (Red Hat 4.4.7-23) (GCC) ) #1 SMP Sat Mar 23
>14:44:16 EDT 2019
>Test rpms: [5]https://repo.aerisnetwork.com/archive/
>Anthony will be able to build it on the CBS as devtoolset has been removed
>from the spec.
>

With quick testing the 4.9.165-35.el6 kernel seems to work OK for me!

Anthony: Can you please review the updated PR on github, merge it and kick of 
the builds for el6 and el7 ? 



>Karl
> 

Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

On Tue, Mar 12, 2019 at 01:21:01PM +0200, Pasi Kärkkäinen wrote:
> > 
> > On Mon, Mar 04, 2019 at 04:22:19PM -0500, Karl Johnson wrote:
> > >  >
> > >  > I updated my PR: 
> > > [3]https://github.com/CentOS-virt7/xen-kernel/pull/18
> > > 
> > >  Hi Karl, I've build and tested your PR, but without the GCC7 patch, 
> > > and
> > >  when I've tested it on el6, none of the guests had network access.
> > >  I had to revert the bridge changes to have them working
> > >  (CONFIG_BRIDGE_NETFILTER=m and CONFIG_BRIDGE=m).
> > > 
> > >  Why did you want the BRIDGE built-in instead of a module?
> > > 
> > >  Maybe you have something to setup the bridge (probably filter) 
> > > properly,
> > >  or maybe something is different in the xen package between el6 and 
> > > el7.
> > >  Any idea?
> > > 
> > >  I still have to investigate the Xen pkg, and have a closer look at 
> > > those
> > >  tests I'm running.
> > > 
> > >Hum strange. I switched from module to built-in because I always had a
> > >deprecated warning about bridge when booting CentOS 6 (and I guess
> > >everyone needs bridge?). I don't remember what was the exact warning
> > >because it's been a long time since I switched it. I don't mind to put 
> > > it
> > >back as a module, both works for me but the warning is gone when 
> > > built-in.
> > 
> > Yeah better to keep things as modules, like they have been.
> > 
> > btw upstream Linux 4.9 LTS kernel is now at 4.9.162 :)
> > 
> 
> I suggest we:
> 
> 1) Rebase to linux 4.9.162.
> 2) Drop the "set bridge to built-in instead of module" changes. Let's keep 
> those settings like they were earlier.
> 3) Drop the use of gcc7 for now.
> 
> How does that sound? 
> 

Karl: Would you like to update the github PR ? Or should someone else pick up 
the kernel update work?


Thanks,

-- Pasi

> 
> Thanks,
> 
> -- Pasi
> 
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Tue, Mar 05, 2019 at 11:16:20PM +0200, Pasi Kärkkäinen wrote:
> Hi,
> 
> On Mon, Mar 04, 2019 at 04:22:19PM -0500, Karl Johnson wrote:
> >  >
> >  > I updated my PR: 
> > [3]https://github.com/CentOS-virt7/xen-kernel/pull/18
> > 
> >  Hi Karl, I've build and tested your PR, but without the GCC7 patch, and
> >  when I've tested it on el6, none of the guests had network access.
> >  I had to revert the bridge changes to have them working
> >  (CONFIG_BRIDGE_NETFILTER=m and CONFIG_BRIDGE=m).
> > 
> >  Why did you want the BRIDGE built-in instead of a module?
> > 
> >  Maybe you have something to setup the bridge (probably filter) 
> > properly,
> >  or maybe something is different in the xen package between el6 and el7.
> >  Any idea?
> > 
> >  I still have to investigate the Xen pkg, and have a closer look at 
> > those
> >  tests I'm running.
> > 
> >Hum strange. I switched from module to built-in because I always had a
> >deprecated warning about bridge when booting CentOS 6 (and I guess
> >everyone needs bridge?). I don't remember what was the exact warning
> >because it's been a long time since I switched it. I don't mind to put it
> >back as a module, both works for me but the warning is gone when 
> > built-in.
> >
> 
> Yeah better to keep things as modules, like they have been.
> 
> btw upstream Linux 4.9 LTS kernel is now at 4.9.162 :)
> 
>

I suggest we:

1) Rebase to linux 4.9.162.
2) Drop the "set bridge to built-in instead of module" changes. Let's keep 
those settings like they were earlier.
3) Drop the use of gcc7 for now.


How does that sound? 


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen-kernel: Update to 4.14 or 4.19?

[Pasi Kärkkäinen]

Hi,

On Thu, Mar 07, 2019 at 05:42:13PM +, George Dunlap wrote:
> Hey all,
> 
> We've been on 4.9 for some time now, and while it's still supported, I
> think it's time to start thinking about upgrading, and I'd like input
> from the community about which version to move up to.
> 

First let's get the current 4.9.16x PR merged and kernel update pushed out.
It should fix the tty/ldisc problem causing crashes in dom0.


> 4.19 has been out for almost 5 months now.  It will include PVH domU
> support, and PVH dom0 support in what _is believed_ to be the final
> form; so when the Virt SIG moves to a version of Xen that supports PVH
> dom0, the kernel will already be in place with no need to upgrade.
> 
> The other option would be to move to 4.14: Probably more stable (as
> it's been out for over a year now), but doesn't have either PVH domU
> or PVH dom0 support.
> 
> I'd suggest 4.19. Any other opinions?
> 

+1 for 4.19 kernel as the next version.

How about blktap2 driver? In our current 4.9 kernel we have the blktap2 patch 
included. 
I think Johnny originally ported the earlier 3.18 kernel blktap2 patch to 4.9.


>  -George
>

Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Mon, Mar 04, 2019 at 04:22:19PM -0500, Karl Johnson wrote:
>On Mon, Mar 4, 2019 at 6:13 AM Anthony PERARD
><[1]anthony.per...@citrix.com> wrote:
> 
>  On Wed, Feb 27, 2019 at 03:12:40PM -0500, Karl Johnson wrote:
>  > I built 4.9.161, works for me on el6:
>  >
>  > [root@node-tmp1 ~]# cat /proc/version
>  > Linux version 4.9.161-34.el6.x86_64
>  ([2]mockbu...@build.aerisnetwork.net) (gcc
>  > version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP Wed Feb 27
>  09:48:40
>  > EST 2019
>  >
>  > Only one strange thing, I had to run grub-install because Grub
>  couldn't
>  > find root device after reboot, not sure this has something to do with
>  the
>  > kernel upgrade.
>  > Kernel 4.9.161 doesn't have the patch for CVE-2019-8912 yet so we
>  might
>  > wait until it get released.
>  >
>  > I updated my PR: [3]https://github.com/CentOS-virt7/xen-kernel/pull/18
> 
>  Hi Karl, I've build and tested your PR, but without the GCC7 patch, and
>  when I've tested it on el6, none of the guests had network access.
>  I had to revert the bridge changes to have them working
>  (CONFIG_BRIDGE_NETFILTER=m and CONFIG_BRIDGE=m).
> 
>  Why did you want the BRIDGE built-in instead of a module?
> 
>  Maybe you have something to setup the bridge (probably filter) properly,
>  or maybe something is different in the xen package between el6 and el7.
>  Any idea?
> 
>  I still have to investigate the Xen pkg, and have a closer look at those
>  tests I'm running.
> 
>Hum strange. I switched from module to built-in because I always had a
>deprecated warning about bridge when booting CentOS 6 (and I guess
>everyone needs bridge?). I don't remember what was the exact warning
>because it's been a long time since I switched it. I don't mind to put it
>back as a module, both works for me but the warning is gone when built-in.
>

Yeah better to keep things as modules, like they have been.

btw upstream Linux 4.9 LTS kernel is now at 4.9.162 :)


>Karl
> 

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7.6 and Xen 4.6 / centos-release-xen broken

[Pasi Kärkkäinen]

Hi,

On Tue, Mar 05, 2019 at 01:32:38PM +, George Dunlap wrote:
> > >
> > > It seems currently "centos-release-xen" package is broken in CentOS7,
> > > it points to xen-46 repo, which isn't available anymore in CentOS 7.6:
> > >
> > > http://mirror.centos.org/centos/7/virt/x86_64/
> > >
> > >   -> xen-48/
> > >   -> xen-410/
> > >
> > >
> > > # yum clean all
> > > # yum search centos-release-xen
> > > ..
> > > centos-release-xen.x86_64 : CentOS Virt SIG Xen repo configs
> > > centos-release-xen-48.x86_64 : CentOS Virt Sig Xen repo configs for Xen 
> > > 4.8
> > > centos-release-xen-common.x86_64 : CentOS Virt Sig Xen support files
> > > ..
> > >
> > > # yum install centos-release-xen
> > > # cat /etc/yum.repos.d/CentOS-Xen.repo
> > >
> > > # CentOS-Xen.repo
> > > #
> > > # Please see http://wiki.centos.org/QaWiki/Xen4 for more
> > > # information
> > >
> > > [centos-virt-xen-46]
> > > name=CentOS-$releasever - xen
> > > baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-46
> > > gpgcheck=1
> > > enabled=1
> > > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
> > >
> > > [centos-virt-xen-46-testing]
> > > name=CentOS-$releasever - xen - testing
> > > baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-46
> > > gpgcheck=0
> > > enabled=0
> > > gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
> > >
> > >
> > > I guess two things should happen in CentOS7:
> > >
> > > 1) Publish centos-release-xen-410 package
> > >
> >
> > Ah, actually it's there already in xen-48 and xen-410 dirs, but not in 
> > CentOS extras.
> >
> >
> > > 2) Update centos-release-xen package to point to.. 410 ?
> > >
> >
> > So it seems the "centos-release-xen" package in "extras" repo has the 
> > xen-46 reference in it.
> > So we should update the package in extras.
> 
> Sorry, missed this -- yes, we've been trying to get the powers that be
> to update it for some time; we did finally manage to get it updated a
> week or two ago.  Could you give it a try now?
> 

Indeed, now "centos-release-xen" on centos7-extras gives xen-48 repo. That's 
better :)


Thanks a lot,

-- Pasi


>  -George
>

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Wed, Feb 27, 2019 at 03:12:40PM -0500, Karl Johnson wrote:
>On Wed, Feb 27, 2019 at 4:44 AM Pasi KÀrkkÀinen <[1]pa...@iki.fi> wrote:
> 
>  Hi,
> 
>  On Mon, Feb 11, 2019 at 12:49:30PM +0200, Pasi KÀrkkÀinen wrote:
>  > Hi,
>  >
>  > On Sun, Feb 10, 2019 at 10:35:56PM -0500, Karl Johnson wrote:
>  > >Â  Â  Hello,
>  > >Â  Â  I built 4.9.155 for both el6 and el7, you can test them here:
>  > >Â  Â
>  
> [1][2]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el6.x86_64.rpm
>  > >Â  Â
>  
> [2][3]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el7.x86_64.rpm
>  > >Â  Â  It works fine for me so far on el6, I'll update my pull request
>  later on
>  > >Â  Â  GitHub with this version.
>  > >Â  Â  [root@node-tmp1 ~]# cat /proc/version
>  > >Â  Â  Linux version 4.9.155-34.el6.x86_64
>  ([3][4]mockbu...@build.aerisnetwork.net)
>  > >Â  Â  (gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP
>  Sun Feb 10
>  > >Â  Â  11:20:04 EST 2019
>  >
>  > Great, thanks a lot! I'll give it a go.
>  >
> 
>  With initial testing seems to work OK for me!
>  Meanwhile upstream kernel is up to v4.9.161, so let's update the
>  sig-virt kernel to that version..
> 
>  Karl: Can you prepare a PR?
> 
>  Thanks,
> 
>  -- Pasi
> 
>I built 4.9.161, works for me on el6:
>

Nice!

>[root@node-tmp1 ~]# cat /proc/version
>Linux version 4.9.161-34.el6.x86_64 ([5]mockbu...@build.aerisnetwork.net)
>(gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP Wed Feb 27
>09:48:40 EST 2019
>Only one strange thing, I had to run grub-install because Grub couldn't
>find root device after reboot, not sure this has something to do with the
>kernel upgrade.
>Kernel 4.9.161 doesn't have the patch for CVE-2019-8912 yet so we might
>wait until it get released.
>I updated my PR: [6]https://github.com/CentOS-virt7/xen-kernel/pull/18
>[7]https://repo.aerisnetwork.com/archive/kernel-4.9.161-34.el6.x86_64.rpm
>[8]https://repo.aerisnetwork.com/archive/kernel-4.9.161-34.el7.x86_64.rpm
>

I'll give it a go soon.


>Anthony Perard already tried to build my PR on the CBS but he was not able
>to enable the SCL repo
>([9]http://mirror.centos.org/centos/$releasever/sclo/$basearch/rh/) to get
>devtoolset-7. We might need to get help from centos-devel.
>
>Karl
> 

OK. Something to discuss on #centos-devel perhaps?


Thanks a lot!

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Mon, Feb 11, 2019 at 12:49:30PM +0200, Pasi Kärkkäinen wrote:
> Hi,
> 
> On Sun, Feb 10, 2019 at 10:35:56PM -0500, Karl Johnson wrote:
> >Hello,
> >I built 4.9.155 for both el6 and el7, you can test them here:
> >[1]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el6.x86_64.rpm
> >[2]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el7.x86_64.rpm
> >It works fine for me so far on el6, I'll update my pull request later on
> >GitHub with this version.
> >[root@node-tmp1 ~]# cat /proc/version
> >Linux version 4.9.155-34.el6.x86_64 ([3]mockbu...@build.aerisnetwork.net)
> >(gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP Sun Feb 10
> >11:20:04 EST 2019
> 
> Great, thanks a lot! I'll give it a go.
> 

With initial testing seems to work OK for me!
Meanwhile upstream kernel is up to v4.9.161, so let's update the sig-virt 
kernel to that version.. 

Karl: Can you prepare a PR?



Thanks,

-- Pasi


> 
> -- Pasi
> 
> >Karl
> >
> >On Sat, Feb 9, 2019 at 10:32 AM Pasi KÀrkkÀinen <[4]pa...@iki.fi> 
> > wrote:
> > 
> >  Hello everyone,
> > 
> >  Some of you might remember discussions earlier in 2017 (huh, long time
> >  ago) on centos-virt list about Linux kernel tty/ldisc related bug, 
> > which
> >  caused Xen dom0 kernel crashes for some people (and also more easy to
> >  trigger crashes on other arches, like on hp pa-risc), but the bug was
> >  difficult to reproduce for others/most people.
> > 
> >  Fix for this issue was merged to centos virt-sig Linux 4.9.48-29 kernel
> >  earlier in 2017, but reverted/deleted in 4.9.75-30 due to problems with
> >  the patch. The patch in question was also merged to upstream Linux
> >  kernel, and later reverted there aswell.
> > 
> >  But now finally the issue has been resolved in upstream Linux, and the
> >  patches have been already backported to Linux 4.9.152 longterm stable
> >  kernel. Changelog:
> >  [5]https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.152
> >  You can find the tty/ldisc patches there.
> > 
> >  So I propose we build the latest 4.9.155 kernel for CentOS virt-sig for
> >  centos6 and centos7.
> > 
> >  Thanks,
> > 
> >  -- Pasi
> > 
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hi,

On Sun, Feb 10, 2019 at 10:35:56PM -0500, Karl Johnson wrote:
>Hello,
>I built 4.9.155 for both el6 and el7, you can test them here:
>[1]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el6.x86_64.rpm
>[2]https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el7.x86_64.rpm
>It works fine for me so far on el6, I'll update my pull request later on
>GitHub with this version.
>[root@node-tmp1 ~]# cat /proc/version
>Linux version 4.9.155-34.el6.x86_64 ([3]mockbu...@build.aerisnetwork.net)
>(gcc version 7.3.1 20180303 (Red Hat 7.3.1-5) (GCC) ) #1 SMP Sun Feb 10
>11:20:04 EST 2019

Great, thanks a lot! I'll give it a go.


-- Pasi

>Karl
>
>On Sat, Feb 9, 2019 at 10:32 AM Pasi KÀrkkÀinen <[4]pa...@iki.fi> wrote:
> 
>  Hello everyone,
> 
>  Some of you might remember discussions earlier in 2017 (huh, long time
>  ago) on centos-virt list about Linux kernel tty/ldisc related bug, which
>  caused Xen dom0 kernel crashes for some people (and also more easy to
>  trigger crashes on other arches, like on hp pa-risc), but the bug was
>  difficult to reproduce for others/most people.
> 
>  Fix for this issue was merged to centos virt-sig Linux 4.9.48-29 kernel
>  earlier in 2017, but reverted/deleted in 4.9.75-30 due to problems with
>  the patch. The patch in question was also merged to upstream Linux
>  kernel, and later reverted there aswell.
> 
>  But now finally the issue has been resolved in upstream Linux, and the
>  patches have been already backported to Linux 4.9.152 longterm stable
>  kernel. Changelog:
>  [5]https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.152
>  You can find the tty/ldisc patches there.
> 
>  So I propose we build the latest 4.9.155 kernel for CentOS virt-sig for
>  centos6 and centos7.
> 
>  Thanks,
> 
>  -- Pasi
> 
>  ___
>  CentOS-virt mailing list
>  [6]CentOS-virt@centos.org
>  [7]https://lists.centos.org/mailman/listinfo/centos-virt
> 
> References
> 
>Visible links
>1. https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el6.x86_64.rpm
>2. https://repo.aerisnetwork.com/archive/kernel-4.9.155-34.el7.x86_64.rpm
>3. mailto:mockbu...@build.aerisnetwork.net
>4. mailto:pa...@iki.fi
>5. https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.152
>6. mailto:CentOS-virt@centos.org
>7. 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 mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7.6 and Xen 4.6 / centos-release-xen broken

[Pasi Kärkkäinen]

Hi,

On Sat, Feb 09, 2019 at 06:39:59PM +0200, Pasi Kärkkäinen wrote:
> Hello George,
> 
> On Thu, Nov 01, 2018 at 12:06:49PM +, George Dunlap wrote:
> > Hey all,
> > 
> > In order to make sure SIG content is "fresh", whenever a new version
> > of CentOS comes out, content is discarded automatically unless SIG
> > chairs specifically request it to be moved over.
> > 
> > At the moment, Xen has three repos that are under consideration to be moved 
> > up:
> > 
> > virt/x86_64/xen-46
> > virt/x86_64/xen-48
> > virt/x86_64/xen-410
> > 
> > I'll request xen-48 and xen-410 to be updated for sure, but I wanted
> > to gauge how much interest there was in xen-46.  If you have strong
> > feelings about xen-46, let me know (and perhaps consider volunteering
> > to maintain the packages).
> > 
> 
> It seems currently "centos-release-xen" package is broken in CentOS7,
> it points to xen-46 repo, which isn't available anymore in CentOS 7.6:
> 
> http://mirror.centos.org/centos/7/virt/x86_64/
> 
>   -> xen-48/
>   -> xen-410/
> 
> 
> # yum clean all
> # yum search centos-release-xen
> ..
> centos-release-xen.x86_64 : CentOS Virt SIG Xen repo configs
> centos-release-xen-48.x86_64 : CentOS Virt Sig Xen repo configs for Xen 4.8
> centos-release-xen-common.x86_64 : CentOS Virt Sig Xen support files
> ..
> 
> # yum install centos-release-xen
> # cat /etc/yum.repos.d/CentOS-Xen.repo 
> 
> # CentOS-Xen.repo
> #
> # Please see http://wiki.centos.org/QaWiki/Xen4 for more 
> # information
> 
> [centos-virt-xen-46]
> name=CentOS-$releasever - xen
> baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-46
> gpgcheck=1
> enabled=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
> 
> [centos-virt-xen-46-testing]
> name=CentOS-$releasever - xen - testing
> baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-46
> gpgcheck=0
> enabled=0
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization
> 
> 
> I guess two things should happen in CentOS7:
> 
> 1) Publish centos-release-xen-410 package
>

Ah, actually it's there already in xen-48 and xen-410 dirs, but not in CentOS 
extras.


> 2) Update centos-release-xen package to point to.. 410 ? 
> 

So it seems the "centos-release-xen" package in "extras" repo has the xen-46 
reference in it.
So we should update the package in extras.


Thanks,

-- Pasi

> 
> Thanks,
> 
> -- Pasi
> 
> > Thanks,
> >  -George
> > 
> 
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7.6 and Xen 4.6 / centos-release-xen broken

[Pasi Kärkkäinen]

Hello George,

On Thu, Nov 01, 2018 at 12:06:49PM +, George Dunlap wrote:
> Hey all,
> 
> In order to make sure SIG content is "fresh", whenever a new version
> of CentOS comes out, content is discarded automatically unless SIG
> chairs specifically request it to be moved over.
> 
> At the moment, Xen has three repos that are under consideration to be moved 
> up:
> 
> virt/x86_64/xen-46
> virt/x86_64/xen-48
> virt/x86_64/xen-410
> 
> I'll request xen-48 and xen-410 to be updated for sure, but I wanted
> to gauge how much interest there was in xen-46.  If you have strong
> feelings about xen-46, let me know (and perhaps consider volunteering
> to maintain the packages).
> 

It seems currently "centos-release-xen" package is broken in CentOS7,
it points to xen-46 repo, which isn't available anymore in CentOS 7.6:

http://mirror.centos.org/centos/7/virt/x86_64/

-> xen-48/
-> xen-410/


# yum clean all
# yum search centos-release-xen
..
centos-release-xen.x86_64 : CentOS Virt SIG Xen repo configs
centos-release-xen-48.x86_64 : CentOS Virt Sig Xen repo configs for Xen 4.8
centos-release-xen-common.x86_64 : CentOS Virt Sig Xen support files
..

# yum install centos-release-xen
# cat /etc/yum.repos.d/CentOS-Xen.repo 

# CentOS-Xen.repo
#
# Please see http://wiki.centos.org/QaWiki/Xen4 for more 
# information

[centos-virt-xen-46]
name=CentOS-$releasever - xen
baseurl=http://mirror.centos.org/centos/$releasever/virt/$basearch/xen-46
gpgcheck=1
enabled=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization

[centos-virt-xen-46-testing]
name=CentOS-$releasever - xen - testing
baseurl=http://buildlogs.centos.org/centos/$releasever/virt/$basearch/xen-46
gpgcheck=0
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Virtualization


I guess two things should happen in CentOS7:

1) Publish centos-release-xen-410 package
2) Update centos-release-xen package to point to.. 410 ? 


Thanks,

-- Pasi

> Thanks,
>  -George
> 

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] CentOS virt-sig Linux kernel 4.9.155 build

[Pasi Kärkkäinen]

Hello everyone,

Some of you might remember discussions earlier in 2017 (huh, long time ago) on 
centos-virt list about Linux kernel tty/ldisc related bug, which caused Xen 
dom0 kernel crashes for some people (and also more easy to trigger crashes on 
other arches, like on hp pa-risc), but the bug was difficult to reproduce for 
others/most people.

Fix for this issue was merged to centos virt-sig Linux 4.9.48-29 kernel earlier 
in 2017, but reverted/deleted in 4.9.75-30 due to problems with the patch. The 
patch in question was also merged to upstream Linux kernel, and later reverted 
there aswell.

But now finally the issue has been resolved in upstream Linux, and the patches 
have been already backported to Linux 4.9.152 longterm stable kernel. 
Changelog: https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.152
You can find the tty/ldisc patches there.

So I propose we build the latest 4.9.155 kernel for CentOS virt-sig for centos6 
and centos7.



Thanks,

-- Pasi

___
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

[Pasi Kärkkäinen]

On Wed, Jan 24, 2018 at 09:30:33AM -0800, Nathan March wrote:
> 
> > -Original Message-
> > From: CentOS-virt [mailto:centos-virt-boun...@centos.org] On Behalf Of
> > Johnny Hughes
> > Sent: Wednesday, January 24, 2018 6:39 AM
> > To: centos-virt@centos.org
> > Subject: Re: [CentOS-virt] Xen 4.6.6-9 (with XPTI meltdown mitigation)
> > packages making their way to centos-virt-xen-testing
> > 
> > On 01/24/2018 01:01 AM, Pasi Kärkkäinen wrote:
> > > On Tue, Jan 23, 2018 at 06:20:39PM -0600, Kevin Stange wrote:
> > >> On 01/23/2018 05:57 PM, Karl Johnson wrote:
> > >>>
> > >>>
> > >>> On Tue, Jan 23, 2018 at 4:50 PM, Nathan March <nat...@gt.net
> > >>> <mailto:nat...@gt.net>> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> > Hmm.. isn't this the ldisc bug that was discussed a few months ago
> > on this
> > >>> list,
> > >>> > and a patch was applied to virt-sig kernel aswell?
> > >>> >
> > >>> > Call trace looks similar..
> > >>>
> > >>> Good memory! I'd forgotten about that despite being the one who ran
> > >>> into it.
> > >>>
> > >>> Looks like that patch was just removed in 4.9.75-30 which I just
> > >>> upgraded
> > >>> this system to: http://cbs.centos.org/koji/buildinfo?buildID=21122
> > >>> <http://cbs.centos.org/koji/buildinfo?buildID=21122>
> > >>> Previously I was on 4.9.63-29 which does not have this problem, and
> > does
> > >>> have the ldisc patch. So I guess the question is for Johnny, why 
> > >>> was it
> > >>> removed?
> > >>>
> > >>> In the meantime, I'll revert the kernel and follow up if I see any
> > >>> further
> > >>> problems.
> > >>>
> > >>>
> > >>> IIRC the patch has been removed from the spec file because it has been
> > >>> merged upstream in 4.9.71.
> > >>
> > >> The IRC discussion I found in my log indicates that it was removed
> > >> because it didn't apply cleanly due to changes when updating to 4.9.75,
> > >> yet I don't think anyone independently validated that the changes made
> > >> are equivalent to the patch that was removed.  I was never able to
> > >> reproduce this issue, so I didn't investigate it myself.
> > >>
> > >
> > > Sounds like the patch is still needed :)
> > >
> > > Anyone up to re-porting it to 4.9.75+ ?
> > 
> > It looked, at first glance, like 4.9.71 fixed it .. I guess not in all cases
> 
> I'm happy to do testing here if anyone's able to help with a patch, does look 
> like reverting to 4.9.63-29 solved it for me in the interm.
> 

Hello Nathan,

I noticed Upstream Linux now has some patches related to tty_ldisc .. as you 
seem to have an easily reproducible way of triggering the crashes, could you 
please try if these patches fix the issue, when applied to CentOS 4.9 kernel?


"tty: fix data race between tty_init_dev and flush of buf":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_ldisc.c?id=b027e2298bd588d6fa36ed2eda97447fb3eac078

"tty: Avoid possible error pointer dereference at tty_ldisc_restore().":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_ldisc.c?id=598c2d41ff44889dd8eced4f117403e472158d85

"tty: Don't call panic() at tty_ldisc_init()":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_ldisc.c?id=903f9db10f18f735e62ba447147b6c434b6af003

"tty: Use __GFP_NOFAIL for tty_ldisc_get()":
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/tty_ldisc.c?id=bcdd0ca8cb8730573afebcaae4138f8f4c8eaa20


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] kernel 4.9.86-30 missing mpt2sas module

[Pasi Kärkkäinen]

On Tue, Mar 06, 2018 at 04:27:05PM +0100, T.Weyergraf wrote:
> Hi
> 
> I am attempting to setup Xen 4.10 with kernel 4.9.86-30 (
> virt7-xen-410-testing, virt7-common-testing ) on CentOS7
> After installing everything, the machine was unable to boot and hung in
> dracut stating it could not find its root device.
> 
> The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx),
> using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7 reports
> mpt2sas module being used to access the controller.
> That module is not present in the modules directory of the 4.9.86:
> 
> 4.9.86-30:
> # pwd
> /lib/modules/4.9.86-30.el7.x86_64
> # find . -name "*mpt2*" -print
> #
> 
> stock 3.10.0-693:
> # pwd
> /lib/modules/3.10.0-693.el7.x86_64
> # find . -name "*mpt2*" -print
> ./kernel/drivers/scsi/mpt3sas/mpt2sas.ko.xz
> 
> The fun part is, that according to the shipped config, it should be there:
> # grep MPT2 /boot/config-4.9.86-30.el7.x86_64
> CONFIG_SCSI_MPT2SAS_MAX_SGE=128
> CONFIG_SCSI_MPT2SAS=m
> 
> Any idea, what happened? I will try myself to build a new kernel from the
> corresponding source package to check, what went wrong.
>

Upstream Linux kernel migrated both the mpt2sas and mpt3sas drivers to a single 
driver: mpt3sas, which should support all the devices.


-- Pasi
 
> As a side note: anyone here, who tried that combo? I know, it's somewhat
> cutting edge, but as I am finally looking into some sort of modern
> Xen4CentOS setup to replace our aged setup in our infrastructure, i thought
> i'd rather settle with something as new as possible to avoid running into
> "not supported anymore soon" issues. Check hypervisor support matrix on
> frontpage https://xenproject.org/
> 
> Regards
> Thomas Weyergraf
___
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

[Pasi Kärkkäinen]

On Tue, Jan 23, 2018 at 06:20:39PM -0600, Kevin Stange wrote:
> On 01/23/2018 05:57 PM, Karl Johnson wrote:
> > 
> > 
> > On Tue, Jan 23, 2018 at 4:50 PM, Nathan March  > > wrote:
> > 
> > Hi,
> > 
> > > Hmm.. isn't this the ldisc bug that was discussed a few months ago on 
> > this
> > list,
> > > and a patch was applied to virt-sig kernel aswell?
> > >
> > > Call trace looks similar..
> > 
> > Good memory! I'd forgotten about that despite being the one who ran
> > into it.
> > 
> > Looks like that patch was just removed in 4.9.75-30 which I just
> > upgraded
> > this system to: http://cbs.centos.org/koji/buildinfo?buildID=21122
> > 
> > Previously I was on 4.9.63-29 which does not have this problem, and does
> > have the ldisc patch. So I guess the question is for Johnny, why was it
> > removed?
> > 
> > In the meantime, I'll revert the kernel and follow up if I see any
> > further
> > problems.
> > 
> > 
> > IIRC the patch has been removed from the spec file because it has been
> > merged upstream in 4.9.71.
> 
> The IRC discussion I found in my log indicates that it was removed
> because it didn't apply cleanly due to changes when updating to 4.9.75,
> yet I don't think anyone independently validated that the changes made
> are equivalent to the patch that was removed.  I was never able to
> reproduce this issue, so I didn't investigate it myself.
>

Sounds like the patch is still needed :)

Anyone up to re-porting it to 4.9.75+ ?


-- Pasi
 
> -- 
> Kevin Stange
> Chief Technology Officer
> Steadfast | Managed Infrastructure, Datacenter and Cloud Services
> 800 S Wells, Suite 190 | Chicago, IL 60607
> 312.602.2689 X203 | Fax: 312.602.2688
> ke...@steadfast.net | www.steadfast.net
___
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

[Pasi Kärkkäinen]

Hi,

On Tue, Jan 23, 2018 at 10:35:24AM -0800, Nathan March wrote:
> > Thanks for the heads-up.  It's been running through XenServer's tests
> > as well as the XenProject's "osstest" -- I haven't heard of any
> > additional issues, but I'll ask.
> 
> Looks like I can reproduce this pretty easily, this happened upon ssh'ing
> into the server while I had a VM migrating into it. The system goes
> completely unresponsive (can't even enter a keystroke via console):
> 
> [64722.291300] vlan208: port 4(vif5.0) entered forwarding state
> [64722.291695] NOHZ: local_softirq_pending 08
> [64929.006981] BUG: unable to handle kernel paging request at
> 2260
> [64929.007020] IP: [] n_tty_receive_buf_common+0xa4/0x1f0
> [64929.007049] PGD 1f7a53067 [64929.007057] PUD 1ee0d4067 
> PMD 0 [64929.007069] 
> [64929.007077] Oops:  [#1] SMP
> [64929.007088] Modules linked in: ebt_ip6 ebt_ip ebtable_filter ebtables
> arptable_filter arp_tables bridge xen_pciback xen_gntalloc nfsd auth_rpcgss
> nfsv3 nfs_acl nfs fscache lockd sunrpc grace 8021q mrp garp stp llc bonding
> xen_acpi_processor blktap xen_netback xen_blkback xen_gntdev xen_evtchn
> xenfs xen_privcmd dcdbas fjes pcspkr ipmi_devintf ipmi_si ipmi_msghandler
> joydev i2c_i801 i2c_smbus lpc_ich shpchp mei_me mei ioatdma ixgbe mdio igb
> dca ptp pps_core uas usb_storage wmi ttm
> [64929.007327] CPU: 15 PID: 17696 Comm: kworker/u48:0 Not tainted
> 4.9.75-30.el6.x86_64 #1
> [64929.007343] Hardware name: Dell Inc. PowerEdge C6220/03C9JJ, BIOS 2.7.1
> 03/04/2015
> [64929.007362] Workqueue: events_unbound flush_to_ldisc
> [64929.007376] task: 8801fbc70580 task.stack: c90048af8000
> [64929.007415] RIP: e030:[]  []
> n_tty_receive_buf_common+0xa4/0x1f0
> [64929.007465] RSP: e02b:c90048afbb08  EFLAGS: 00010296
> [64929.007476] RAX: 2260 RBX:  RCX:
> 0002
> [64929.007519] RDX:  RSI: 8801dc0f3c20 RDI:
> 8801f9b8acd8
> [64929.007563] RBP: c90048afbb78 R08: 0001 R09:
> 8210f1c0
> [64929.007577] R10: 7ff0 R11:  R12:
> 0002
> [64929.007620] R13: 8801f9b8ac00 R14:  R15:
> 8801dc0f3c20
> [64929.007675] FS:  7fcfc0af8700() GS:880204dc()
> knlGS:
> [64929.007718] CS:  e033 DS:  ES:  CR0: 80050033
> [64929.007759] CR2: 2260 CR3: 0001f067b000 CR4:
> 00042660
> [64929.007782] Stack:
> [64929.007806]  c90048afbb38  8801f9b8acd8
> 000104dda030
> [64929.007858]  2260 fbc72700 880204dc48c0
> 
> [64929.007941]  880204dce890 8801dc0f3c00 8801f7f25c00
> c90048afbbf8
> [64929.007994] Call Trace:
> [64929.008008]  [] n_tty_receive_buf2+0x14/0x20
> [64929.008048]  [] tty_ldisc_receive_buf+0x23/0x50
>

Hmm.. isn't this the ldisc bug that was discussed a few months ago on this 
list, and a patch was applied to virt-sig kernel aswell? 

Call trace looks similar..


-- Pasi

> [64929.008088]  [] flush_to_ldisc+0xc8/0x100
> [64929.008133]  [] ? __switch_to+0x20b/0x690
> [64929.008176]  [] ? xen_clocksource_read+0x15/0x20
> [64929.008222]  [] process_one_work+0x170/0x500
> [64929.008268]  [] ? __schedule+0x238/0x530
> [64929.008310]  [] ? schedule+0x3a/0xa0
> [64929.008324]  [] worker_thread+0x166/0x530
> [64929.008368]  [] ? put_prev_entity+0x29/0x140
> [64929.008412]  [] ? __schedule+0x238/0x530
> [64929.008458]  [] ? default_wake_function+0x12/0x20
> [64929.008502]  [] ? maybe_create_worker+0x120/0x120
> [64929.008518]  [] ? schedule+0x3a/0xa0
> [64929.008555]  [] ? _raw_spin_unlock_irqrestore+0x16/0x20
> [64929.008599]  [] ? maybe_create_worker+0x120/0x120
> [64929.008616]  [] kthread+0xe5/0x100
> [64929.008630]  [] ? schedule_tail+0x56/0xc0
> [64929.008643]  [] ? __kthread_init_worker+0x40/0x40
> [64929.008659]  [] ? schedule_tail+0x56/0xc0
> [64929.008673]  [] ret_from_fork+0x41/0x50
> [64929.008685] Code: 89 fe 4c 89 ef 89 45 98 e8 aa fb ff ff 8b 45 98 48 63
> d0 48 85 db 48 8d 0c 13 48 0f 45 d9 01 45 bc 49 01 d7 41 29 c4 48 8b 45 b0
> <48> 8b 30 48 89 75 c0 49 8b 0e 8d 96 00 10 00 00 29 ca 41 f6 85 
> [64929.008894] RIP  [] n_tty_receive_buf_common+0xa4/0x1f0
> [64929.008914]  RSP 
> [64929.008923] CR2: 2260
> [64929.009641] ---[ end trace e1da1cdf77fed144 ]---
> [64929.009785] BUG: unable to handle kernel paging request at
> ffd8
> [64929.009804] IP: [] kthread_data+0x10/0x20
> [64929.009823] PGD 200d067 [64929.009831] PUD 200f067 
> PMD 0 [64929.009842] 
> [64929.009850] Oops:  [#2] SMP
> [64929.009864] Modules linked in: ebt_ip6 ebt_ip ebtable_filter ebtables
> arptable_filter arp_tables bridge xen_pciback xen_gntalloc nfsd auth_rpcgss
> nfsv3 nfs_acl nfs fscache lockd sunrpc grace 8021q mrp garp stp llc bonding
> xen_acpi_processor blktap xen_netback xen_blkback xen_gntdev xen_evtchn
> xenfs xen_privcmd dcdbas fjes pcspkr ipmi_devintf 

Re: [CentOS-virt] 4.4.4-26 with XSA-226, 227, 230 in centos-virt-testing

[Pasi Kärkkäinen]

Hi,

On Wed, Aug 23, 2017 at 04:02:46PM -0500, Kevin Stange wrote:
> Xen 4.4.4 along with kernel 4.9.44 containing patches for XSAs (226 -
> 230) from August 15th are now available in centos-virt-testing.  If
> possible, please test and provide feedback here so we can move these to
> release soon.
> 
> XSA-228 did not affect Xen 4.4
> XSA-229 only applies to the kernel
> 
> XSA-235 disclosed today only affects ARM and isn't going to be added to
> these packages.
>

Thanks for updating the Xen 4.4 branch! Are you still planning for additional 
updates there? 


-- Pasi

> 
> -- 
> Kevin Stange
> Chief Technology Officer
> Steadfast | Managed Infrastructure, Datacenter and Cloud Services
> 800 S Wells, Suite 190 | Chicago, IL 60607
> 312.602.2689 X203 | Fax: 312.602.2688
> ke...@steadfast.net | www.steadfast.net
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Crash in network stack under Xen

[Pasi Kärkkäinen]

On Thu, Nov 09, 2017 at 01:36:44PM -0800, Sarah Newman wrote:
> Hi,
> 
> We had a potentially network related crash on a dom0 with Linux 4.9.39 / Xen 
> 4.8 and as of today I can't find any fixes in stable/linux-4.9.y,
> xen/staging-4.8, or CPU microcode updates that look like a smoking gun. I 
> can't rule out that it's Xen related. The backtraces are:
> 
>  [ cut here ]
>  WARNING: CPU: 0 PID: 0 at net/ipv4/af_inet.c:1473 inet_gro_complete+0xbb/0xd0
>

Did you try tweaking network settings, disabling GRO for the network interface 
in question, and see if that changes anything?



Thanks,

-- Pasi


> 
> It looks to me like in the first backtrace, this check from inet_gro_complete 
> failed:
> 
> ops = rcu_dereference(inet_offloads[proto]);
> 
> Which I'm guessing means the packet didn't have a valid layer 4 protocol 
> definition, or we don't have that protocol enabled. Then when attempting to
> handle that failure there was a GPF, I believe by accessing invalid data in 
> shinfo->frag_list . "skb_release_data+0x73" is in __read_once_size, which
> I think is generated by "kfree_skb: if (likely(atomic_read(>users) == 
> 1))" .
> 
> --Sarah
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes

[Pasi Kärkkäinen]

On Tue, Sep 05, 2017 at 10:49:13AM -0700, Nathan March wrote:
> > > I have no issues rolling this patch in , while we wait on upstream, if
> > > it makes our tree more stable.
> > >
> > 
> > I think we should do that.. What do others think?
> > 
> 
> I've had the patch deployed to a group of 32 hosts (with hundreds of vms)
> for about 10 days now and no sign of any issues.
> 
> So I support it =)
> 

Thanks Nathan.

Johnny: Can you please add the patch to next Linux 4.9 kernel build? 


Thanks,

-- Pasi

> Cheers,
> Nathan

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes

[Pasi Kärkkäinen]

On Sat, Sep 02, 2017 at 08:12:53AM -0500, Johnny Hughes wrote:
> On 08/30/2017 03:10 PM, Pasi Kärkkäinen wrote:
> > Hello everyone,
> > 
> > Recently Nathan March reported on centos-virt list he's getting frequent 
> > Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch 
> > "tty: Fix ldisc crash on reopened tty".
> > 
> > The patch was already merged upstream here:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05
> > 
> > but then reverted here:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=896d81fefe5d1919537db2c2150ab6384e4a6610
> > 
> > Nathan confirmed if he applies the patch from 
> > 71472fa9c52b1da27663c275d416d8654b905f05 to his Linux 4.9 LTS kernel the 
> > bug/problem goes away, so the patch (or similar fix) is still needed, at 
> > least for 4.9 LTS kernel.
> > 
> > 
> > Mikulas reported he's able to trigger the same crash on Linux 4.10:
> > https://www.spinics.net/lists/kernel/msg2440637.html
> > https://lists.gt.net/linux/kernel/2664604?search_string=ldisc%20reopened;#2664604
> > 
> > Michael Neuling reported he's able to trigger the bug on PowerPC:
> > https://lkml.org/lkml/2017/3/10/1582
> > 
> > 
> > So now the question is.. is anyone currently working on getting this patch 
> > fixed and applied upstream? I think one of the problems earlier was being 
> > able to reliable reproduce the crash.. Nathan says he's able to reproduce 
> > it many times per week on his environment on x86_64.
> > 
> 
> I have no issues rolling this patch in , while we wait on upstream, if
> it makes our tree more stable.
> 

I think we should do that.. What do others think?


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes

[Pasi Kärkkäinen]

On Thu, Aug 31, 2017 at 03:22:05PM +1000, Michael Neuling wrote:
> On Thu, 2017-08-31 at 06:36 +0200, Greg Kroah-Hartman wrote:
> > On Wed, Aug 30, 2017 at 11:10:14PM +0300, Pasi Kärkkäinen wrote:
> > > Hello everyone,
> > > 
> > > Recently Nathan March reported on centos-virt list he's getting frequent
> > > Linux kernel crashes with Linux 4.9 LTS kernel because of the missing 
> > > patch
> > > "tty: Fix ldisc crash on reopened tty".
> > 
> > Crashes with "normal" operation, or crashes when running a fuzzer or
> > other type of program?
> 
> For me it crashed on boot.
>

Nathan said he's getting the crashes at runtime, randomly, but often.

 
> > 
> > > The patch was already merged upstream here:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
> > > d=71472fa9c52b1da27663c275d416d8654b905f05
> > > 
> > > but then reverted here:
> > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i
> > > d=896d81fefe5d1919537db2c2150ab6384e4a6610
> > > 
> > > Nathan confirmed if he applies the patch from
> > > 71472fa9c52b1da27663c275d416d8654b905f05 to his Linux 4.9 LTS kernel the
> > > bug/problem goes away, so the patch (or similar fix) is still needed, at
> > > least for 4.9 LTS kernel.
> > > 
> > > 
> > > Mikulas reported he's able to trigger the same crash on Linux 4.10:
> > > https://www.spinics.net/lists/kernel/msg2440637.html
> > > https://lists.gt.net/linux/kernel/2664604?search_string=ldisc%20reopened;#26
> > > 64604
> > > 
> > > Michael Neuling reported he's able to trigger the bug on PowerPC:
> > > https://lkml.org/lkml/2017/3/10/1582
> > > 
> > > 
> > > So now the question is.. is anyone currently working on getting this patch
> > > fixed and applied upstream? I think one of the problems earlier was being
> > > able to reliable reproduce the crash.. Nathan says he's able to reproduce 
> > > it
> > > many times per week on his environment on x86_64.
> > 
> > I don't know of anyone working on it, want to do it yourself?
> 
> I'm not anymore. We found it was only triggered on a bogus CONFIG option
> combination.  Once we removed that, it no longer happened.
> 
> The underlying bug was still there though.
> 


Yep.. and the bug seems to trigger at runtime.



> Mikey


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Status of reverted Linux patch "tty: Fix ldisc crash on reopened tty", Linux 4.9 kernel frequent crashes

[Pasi Kärkkäinen]

Hello everyone,

Recently Nathan March reported on centos-virt list he's getting frequent Linux 
kernel crashes with Linux 4.9 LTS kernel because of the missing patch "tty: Fix 
ldisc crash on reopened tty".

The patch was already merged upstream here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05

but then reverted here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=896d81fefe5d1919537db2c2150ab6384e4a6610

Nathan confirmed if he applies the patch from 
71472fa9c52b1da27663c275d416d8654b905f05 to his Linux 4.9 LTS kernel the 
bug/problem goes away, so the patch (or similar fix) is still needed, at least 
for 4.9 LTS kernel.


Mikulas reported he's able to trigger the same crash on Linux 4.10:
https://www.spinics.net/lists/kernel/msg2440637.html
https://lists.gt.net/linux/kernel/2664604?search_string=ldisc%20reopened;#2664604

Michael Neuling reported he's able to trigger the bug on PowerPC:
https://lkml.org/lkml/2017/3/10/1582


So now the question is.. is anyone currently working on getting this patch 
fixed and applied upstream? I think one of the problems earlier was being able 
to reliable reproduce the crash.. Nathan says he's able to reproduce it many 
times per week on his environment on x86_64.


Thanks a lot,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Major stability problems with xen 4.6.6

[Pasi Kärkkäinen]

Hi,

On Thu, Aug 24, 2017 at 03:45:46PM -0700, Nathan March wrote:
>Just in case anyone else on this list is running into similar issues, I
>can confirm that the patch appears to have resolved this.
> 
> 
>I've opened [1]https://bugs.centos.org/view.php?id=13713
> 
> 
>It was so bad that having the system under load (with rpmbuild) and
>opening another ssh window or two would almost always cause the oops.
>

It seems the patch you mentioned was merged to upstream Linux here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=71472fa9c52b1da27663c275d416d8654b905f05

and then reverted/removed here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=896d81fefe5d1919537db2c2150ab6384e4a6610

Do you know if there has been proper/fixed patch after that? has it been merged 
to upstream Linux kernel already? 


Thanks,

-- Pasi

> 
> 
>Cheers,
> 
>Nathan
> 
> 
> 
>From: CentOS-virt [mailto:centos-virt-boun...@centos.org] On Behalf Of
>Nathan March
>Sent: Wednesday, August 23, 2017 3:32 PM
>To: 'Discussion about the virtualization on CentOS'
>
>Subject: Re: [CentOS-virt] Major stability problems with xen 4.6.6
> 
> 
> 
>This appears to be a centos kernel issue rather than a xen one.
> 
> 
> 
>[2]https://lkml.org/lkml/2016/5/17/440
> 
> 
> 
>Digging through the posts and not clear why this never made it upstream...
> 
> 
> 
>I'm going to apply that patch to my systems and see if it resolves, but
>won't know for certain until a week or two of stability goes by.
> 
> 
> 
>- Nathan
> 
> 
> 
> 
> 
>From: CentOS-virt [[3]mailto:centos-virt-boun...@centos.org] On Behalf Of
>Nathan March
>Sent: Wednesday, August 23, 2017 2:48 PM
>To: [4]centos-virt@centos.org
>Subject: [CentOS-virt] Major stability problems with xen 4.6.6
> 
> 
> 
>Hi,
> 
> 
> 
>I'm seeing numerous crashes on the xen 4.6.6-1 / 4.6.6-2 releases, on both
>the 4.9.34-29 and 4.9.39-29 kernels.
> 
> 
> 
>I've attached a txt with two different servers outputs.
> 
> 
> 
>Xen-028: This crashed this morning while running 4.6.6-1 and 4.9.39-29
> 
>Xen-001: This crashed shortly after being upgraded to 4.6.6-2 and
>4.9.34-29
> 
> 
> 
>Both are on different hardware platforms, and have had a long history of
>being stable until these upgrades.
> 
> 
> 
>It sounds potentially related to
>
> [5]https://kernel.googlesource.com/pub/scm/linux/kernel/git/tiwai/sound-unstable/+/9ce119f318ba1a07c29149301f1544b6c4bea52a%5E%21/
>but I've confirmed this patch is in the above kernels.
> 
> 
> 
>Any suggestions / thoughts?
> 
> 
> 
>Cheers,
> 
>Nathan

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Recent Xen XSA's

[Pasi Kärkkäinen]

Hello,

Looking at CBS (http://cbs.centos.org/koji/packageinfo?packageID=88) I can't 
seem to find any recent builds of CentOS Xen, to include the recent XSA's.. any 
chance we could do new builds for centos6 and centos7 ? 



Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Linux 3.18.44 kernel with Dirty Cow fix (CVE-2016-5195)

[Pasi Kärkkäinen]

Hello,

I think we should build and release a new 3.18 kernel for the VirtSIG / Xen 
users..

It seems upstream 3.18.y tree has a release with the Dirty Cow security fix 
included, 3.18.44:
https://kernel.googlesource.com/pub/scm/linux/kernel/git/sashal/linux-stable/+log/linux-3.18.y-queue

(also includes a Xen SMAP/PVOPS fix).


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Cannot allocate Memory

[Pasi Kärkkäinen]

On Wed, Jun 22, 2016 at 05:45:05PM +, Shaun Reitan wrote:
>Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a
>guest because of what looks like an issue allocating memory even though xm
>info shows like 5x the amount of free memory needed? We are still
>unfortunately still using xm... it's on my list, i know..
>We've had this happen on a couple hosts now.  Only way to resolve seams to
>be rebooting the host.  I'm going to update the host to latest Xen 4.4 now
>hoping this is a old bug.
>Here's from xen logs
>[2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:105)
>XendDomainInfo.create(['vm', ['name', 'xxx'], ['memory', 2048],
>['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['vcpus', 2],
>['oos', 1], ['image', ['linux', ['kernel', '/kernels/vmlinux-2.6.18.8-4'],
>['videoram', 4], ['args', 'root=/dev/xvda ro xencons=tty console=tty1 '],
>['tsc_mode', 0], ['nomigrate', 0]]], ['s3_integrity', 1], ['device',
>['vbd', ['uname', 'phy:vg/fs_6818'], ['dev', 'xvda'], ['mode', 'w']]],
>['device', ['vbd', ['uname', 'phy:vg/fs_6819'], ['dev', 'xvdb'], ['mode',
>'w']]], ['device', ['vif', ['rate', '40mb/s'], ['mac',
>'FE:FD:48:01:F1:E7')
>[2016-06-22 09:13:50 1958] DEBUG (XendDomainInfo:2504)
>XendDomainInfo.constructDomain
>[2016-06-22 09:13:50 1958] DEBUG (balloon:187) Balloon: 7602632 KiB free;
>need 16384; done.
>

Hmm.. so you're using (dom0) memory ballooning? You might want to disable it.
Things worked better without ballooning (at least with xend).


-- Pasi

>[2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:2566) (12, 'Cannot
>allocate memory')
>Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 2561, in _constructDomain
>target = self.info.target())
>Error: (12, 'Cannot allocate memory')
>[2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:490) VM start failed
>Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 475, in start
>XendTask.log_progress(0, 30, self._constructDomain)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
>209, in log_progress
>retval = func(*args, **kwds)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 2572, in _constructDomain
>raise VmError(failmsg)
>VmError: Creating domain failed: name=xxx
>[2016-06-22 09:13:50 1958] ERROR (XendDomainInfo:110) Domain construction
>failed
>Traceback (most recent call last):
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 108, in create
>vm.start()
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 475, in start
>XendTask.log_progress(0, 30, self._constructDomain)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendTask.py", line
>209, in log_progress
>retval = func(*args, **kwds)
>  File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomainInfo.py",
>line 2572, in _constructDomain
>raise VmError(failmsg)
>VmError: Creating domain failed: name=xxx
>--
>Shaun

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] XSAs 170 and 154, repository layouts, and centos-release-xen 8-1

[Pasi Kärkkäinen]

On Wed, Feb 17, 2016 at 01:04:08PM +, George Dunlap wrote:
> On Wed, Feb 17, 2016 at 12:30 PM, George Dunlap  wrote:
> > I have the following packages going through the CBS:
> > * A CentOS 7 xen-4.6.1-2, with XSAs 170 and 154
> > * A CentOS 6 xen-4.6.1-2, with XSAs 170 and 154
> > * A CentOS 6 xen-4.4.3-11, with XSAs 170
> >
> > All these should show up in mirrors hopefully sometime later today.
> > As usual, please report any problems here.
> >
> > Xen 4.4 only has XSA 170 because at the time the embargo was lifted, I
> > didn't have a suitable backport of XSA-154.  It's only applicable when
> > PCI-passthrough is in effect, so it's not that critical.
> 
> I now have a build of Xen 4.4 with XSA-154 going through the build
> system.  For users who need it, it should be available on buildlogs
> (via centos-virt-xen-testing) sometime later this afternoon.  The
> signed version on mirrors may be delayed until tomorrow.
>

Great!
 
> And that really will be the last Xen 4.4 XSA update I personally port. :-)
> 

:)

> However, if anyone wants to push any further changes to 4.4, feel free
> to send a pull request to this tree:
> 
> https://github.com/CentOS-virt7/xen
> 
> And I'll be happy to review it and push it through the CBS.  I've made
> a detailed how-to, so hopefully it shouldn't be too difficult.
>

Thanks a lot! Howto looks good.


-- Pasi
 
> Peace,
>  -George

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen: XSAs 167-169, update to Xen 4.6

[Pasi Kärkkäinen]

Hi,

On Wed, Jan 13, 2016 at 05:21:31PM +, George Dunlap wrote:
> XSA 169 is out, but is low-priority and has a work-around, so I'm
> going to batch it together with XSAs 167-168 and release a new 4.4.3
> package when the embargo is lifted next Wednesday.
> 
> This will be the last XSA update for the 4.4.3 packages.  Today or
> tomorrow I will push the Xen 4.6.0 packages to buildlogs for testing;
> and sometime after the final 4.4.3 packages are released, I will push
> the Xen 4.6 packages as the main Xen packages.
> 

Thanks for the heads-up. 

Later when announcing the Xen 4.6 based rpms, we need to remember to remind 
people 
(once again) that Xen 4.6 doesn't have xm/xend anymore, so everyone needs to 
migratio to xl now, if they didn't already.


> The Virt SIG is a community project, so anyone wishing to maintain the
> Xen 4.4. packages going forward is welcome to step up to do so.
>

Thanks a lot for all the work with Xen 4.4 rpms. They've worked well for me,
and have been very stable (*knocking wood*) :)


I'll start testing the Xen 4.6 bits soon.


>  -George
>


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] new install of Xen 4.6 hangs on Loading initial ramdisk

[Pasi Kärkkäinen]

On Fri, Nov 27, 2015 at 06:18:05PM -0500, Craig Thompson wrote:
>First post to this list.  I would appreciate some help on this issue.
>As background, I installed CentOS 7 on a Dell server, and then ran the
>following commands:
>yum update
>
> [1]http://buildlogs.centos.org/centos/7/virt/x86_64/xen/centos-release-xen-7-11.el7.x86_64.rpm
>yum --enablerepo=centos-virt-xen-testing update
>yum --enablerepo=centos-virt-xen-testing install xen
>Doing that, I was able to successfully install Xen, create a virtual
>machine with its own HVM setup, logical volume, etc. and boot it just
>fine.
>I then tried to do the same on an IBM x3550 server I*m trying to install
>with CentOS 7.  The CentOS 7 install went just fine.  I can boot into the
>standard kernel and have a working machine.  But after running the
>commands above to install the Xen hypervisor, the machine hangs on boot
>for a few moments after displaying the lines below and then reboots in a
>loop over and over and over:
>Loading Xen 4.6.0-2.el7 *
>Loading Linux 3.18.21-16.el7.x86_64 *
>Loading initial ramdisk *
>It never gets beyond that.  
>

Weird. So you don't see any output from Xen? 

I guess that means GRUB gets stuck somehow, and doesn't even get to actually 
starting Xen..


> If I choose the stock kernel (no Xen) from the
>Grub menu, it will continue to boot into that just fine.
>My grub.cfg file has these entries of note:
> multiboot /xen-4.6.0-2.el7.gz placeholder
>dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty
>loglvl=all guest_loglvl=all ${xen_rm_opts}
>echo'Loading Linux 3.18.21-16.el7.x86_64 ...'
>module  /vmlinuz-3.18.21-16.el7.x86_64 placeholder
>root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde ro crashkernel=auto debug
>irqpoll ipv6.disable=1 console=hvc0 earlyprintk=xen nomodeset
>echo'Loading initial ramdisk ...'
>module  --nounzip   /initramfs-3.18.21-16.el7.x86_64.img
>What I have tried:
>1) adding debug into the vmlinuz line
>2) disabling ipv6 in that line
>3) adding root=UUID=9dc18146-f9b3-41cc-ba9c-7314689abcde to the last line
>AFTER /initramfs *.
>Nothing so far has made any difference.  Obviously the process works, as
>it works for me just fine on the Dell server.
>Underlying this machine is a SATA RAID 1 PCI card with two SSD drives
>attached in a RAID 1 mirror.  Not that that should matter, but I*m
>including it for reference. As noted previously, it boots into the stock
>kernel just fine.
>Any help would be appreciated.
>

Yeah it's not about options to Xen and/or Linux when GRUB fails to boot the 
entry in the first place.. 

Is this UEFI setup? Or legacy-BIOS? Did you try playing with the BIOS options? 


-- Pasi

>--
>Craig Thompson, President
>Caldwell Global Communications, Inc.
>423-559-5465
> 

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Pasi Kärkkäinen]

On Wed, Nov 25, 2015 at 03:02:00PM +, George Dunlap wrote:
> On Thu, Nov 19, 2015 at 12:28 PM, George Dunlap <dunl...@umich.edu> wrote:
> > On Wed, Nov 18, 2015 at 1:31 PM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> >> On Wed, Nov 18, 2015 at 02:20:49PM +0200, Manuel Wolfshant wrote:
> >>> On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:
> >>> >Hello,
> >>> >
> >>> >On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:
> >>> >>On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:
> >>> >>>On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:
> >>> >>>>So going forward, we're moving the CentOS 6 Xen packages from the
> >>> >>>>custom "xen4" repos that were introduced several years ago, to repos
> >>> >>>>based on its position as a sub-project of the Virt Sig.  That will
> >>> >>>>make things consistent between all the sigs, as well as between CentOS
> >>> >>>>6 and 7 Xen packages.
> >>> >>>>
> >>> >>>>Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
> >>> >>>>this transition.
> >>> >>>>
> >>> >>>>So please help us test the new repository structure, so that we can
> >>> >>>>with conscience push the updates to xen4 users in general.
> >>> >>>>
> >>> >>>Seems to work for me!
> >>> >>>
> >>> >>>
> >>> >>Except now on another system I see this problem:
> >>> >>
> >>> >Anyone else seeing this libvirt-python problem with virt-manager and/or 
> >>> >virt-viewer ?
> >>> >
> >>> >(happens on a freshly installed system, so no earlier libvirt rpms 
> >>> >installed)
> >>> >
> >>> It tries to install half of the OS, but it works for me.  It seems
> >>> that your yum does not like that you already have
> >>> libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in
> >>> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates
> >>>
> >>
> >> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 are the centos core 
> >> packages,
> >> while the libvirt-client-1.2.15-3.el6.x86_64 is the Virt SIG provided one,
> >> which has Xen support enabled.
> >>
> >> So I need the 1.2.15-3 versions, but it seems libvirt-python is not 
> >> included in the Virt SIG built ones..
> >>
> >> So that's an issue/problem..
> >
> > Right -- for 1.2.12 they decided to  have libvirt-python be a
> > completely separate package.  I  had apparently started getting that
> > package built at some time in the distant past but never finished.
> >
> > I've cloned & build Fedora's libvirt-python-1.2.15 (which is pretty
> > much what I did for libvirt-1.2.15); it should show up in buildlogs in
> > an hour or two.  Once that's in, if you go "yum
> > --enablerepo=centos-virt-xen-testing virt-manager", it should install.
> > (At least, the version in CBS works for me.)
> >
> > Let me know if it works.
> 
> OK, well in the absence of testing, it works for me, so I've tagged it
> to go to the main repo, and Johnny will be pushing the updated
> centos-release-xen to centos-extras tonight or tomorrow.
>

Sorry for the delay.

I grabbed libvirt-python-1.2.15-1.el6.x86_64.rpm from:
http://buildlogs.centos.org/centos/6/virt/x86_64/xen/

rpm installed fine. After that virt-manager and virt-viewer installed fine too. 
virt-manager seems to start/run fine aswell. I'll play with it more now.. 

So the main issue seems to be fixed with that libvirt-python build!


Thanks a lot,

-- Pasi

 
>  -George

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen package update (including XSA-156)

[Pasi Kärkkäinen]

On Wed, Nov 18, 2015 at 02:20:49PM +0200, Manuel Wolfshant wrote:
> On 11/18/2015 02:08 PM, Pasi Kärkkäinen wrote:
> >Hello,
> >
> >On Sun, Nov 15, 2015 at 06:42:18PM +0200, Pasi Kärkkäinen wrote:
> >>On Sun, Nov 15, 2015 at 02:04:58PM +0200, Pasi Kärkkäinen wrote:
> >>>On Thu, Nov 12, 2015 at 02:00:27PM +, George Dunlap wrote:
> >>>>So going forward, we're moving the CentOS 6 Xen packages from the
> >>>>custom "xen4" repos that were introduced several years ago, to repos
> >>>>based on its position as a sub-project of the Virt Sig.  That will
> >>>>make things consistent between all the sigs, as well as between CentOS
> >>>>6 and 7 Xen packages.
> >>>>
> >>>>Unfortunately, XSA-156 came up rather suddenly and is a bit blocked by
> >>>>this transition.
> >>>>
> >>>>So please help us test the new repository structure, so that we can
> >>>>with conscience push the updates to xen4 users in general.
> >>>>
> >>>Seems to work for me!
> >>>
> >>>
> >>Except now on another system I see this problem:
> >>
> >Anyone else seeing this libvirt-python problem with virt-manager and/or 
> >virt-viewer ?
> >
> >(happens on a freshly installed system, so no earlier libvirt rpms installed)
> >
> It tries to install half of the OS, but it works for me.  It seems
> that your yum does not like that you already have
> libvirt-client-1.2.15-3.el6.x86_64. Mine is happy to bring in
> libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 from updates
> 

libvirt-{python,client}-0.10.2-54.el6_7.2.x86_64 are the centos core packages,
while the libvirt-client-1.2.15-3.el6.x86_64 is the Virt SIG provided one,
which has Xen support enabled.

So I need the 1.2.15-3 versions, but it seems libvirt-python is not included in 
the Virt SIG built ones..

So that's an issue/problem..


-- Pasi


> wolfy
> 
> 
> >># yum install virt-manager
> >>..
> >>..
> >>..
> >>
> >>--> Finished Dependency Resolution
> >>Error: Package: libvirt-python-0.10.2-54.el6_7.2.x86_64 (updates)
> >>Requires: libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Available: libvirt-client-0.10.2-54.el6.x86_64 (base)
> >>libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Available: libvirt-client-0.10.2-54.el6_7.2.x86_64 (updates)
> >>libvirt.so.0(LIBVIRT_PRIVATE_0.10.2)(64bit)
> >>Installed: libvirt-client-1.2.15-3.el6.x86_64 (@centos-virt-xen)
> >>Not found
> >>  You could try using --skip-broken to work around the problem
> >>  You could try running: rpm -Va --nofiles --nodigest
> >>
> >>
> >>Are we missing a build of libvirt-python 1.2.15 package?
> 
> 
> ___
> 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

Re: [CentOS-virt] Resigning as lead of the Virt SIG

[Pasi Kärkkäinen]

On Tue, Nov 03, 2015 at 02:06:18PM -0600, Johnny Hughes wrote:
> On 11/03/2015 08:53 AM, Lars Kurth wrote:
> > Hi all,
> > 
> > I wanted to let you know that I feel I need to step down as leader of the 
> > Virtualisation SIG. When I originally was approached by KB to do this, it 
> > was always clear that this would be a temporary thing until the SIG got 
> > going. At the time, only Xen and CentOS folks were involved with the SIG. 
> > Since then, we added oVirt and Docker maintainers, have a total of 5 
> > maintainers and built good momentum.
> > 
> > There are two reasons why I feel I should step down as leader of the Virt 
> > SIG: a) I have been traveling too much and thus did not have the bandwidth 
> > to do this job justice in recent months. b) In addition, it would also make 
> > more sense for one of the Virt SIG maintainers who is more closely involved 
> > with day-to-day activities to pick up this job. I will still be able to 
> > help with PR and other items.  
> > 
> > When I was absent over the last few months, George Dunlap (gwd on irc) did 
> > most of the groundwork and led SIG meetings on my behalf, so I wanted to 
> > propose that George leads the SIG going forward. That is assuming that none 
> > of the other SIG maintainers want to step up. George agreed in principle.
> > 
> > In the last Virt SIG meeting, not all maintainers were present, so we 
> > couldn't make a formal decision. KB said the following:
> > 
> > kbsingh: I think if gwd is ok with it, and people are ok in the SIG, its 
> > good for me
> > 
> > This means that succession either has to be settled in the next SIG 
> > meeting, or by e-mail responding to this thread. I don't think there is any 
> > formal process, but I would suggest that the maintainers listed on 
> > https://wiki.centos.org/SpecialInterestGroup/Virtualization should have a 
> > say either at the next IRC meeting or by replying to this email thread.
> > 
> > Best Regards
> > Lars
> 
> Lars,
> 
> Slacker :)
> 
> George Dunlap is fine with me.
> 

+1 for George.


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Libvirt enhancement requests

[Pasi Kärkkäinen]

On Tue, Oct 27, 2015 at 05:19:16PM +, Nux! wrote:
> To clarify my own request:
> 
> RBD (for CEPH) support is available in the version bundled in RHEL 7.2 Beta, 
> so we'll have it in CentOS 7.2 (or whatever will be the identifying number).
> 
> The hooks seems just like a matter of creating files in the correct location.
> 
> ..So, all is good in the world once again.
>

Except the VirtSIG provides a different version/build of libvirt rpms, so we 
still need to enable RBD/Ceph support separately in VirtSIG provided version..


-- Pasi
 
> 
> Regards,
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
> > From: "Nux!" <n...@li.nux.ro>
> > To: "Discussion about the virtualization on CentOS" <centos-virt@centos.org>
> > Sent: Tuesday, 27 October, 2015 15:22:27
> > Subject: Re: [CentOS-virt] Libvirt enhancement requests
> 
> > So... how exactly do we proceed?
> > 
> > Anyone from the Virt SIG, please stand up?
> > 
> > --
> > Sent from the Delta quadrant using Borg technology!
> > 
> > Nux!
> > www.nux.ro
> > 
> > - Original Message -
> >> From: "Pasi Kärkkäinen" <pa...@iki.fi>
> >> To: "Discussion about the virtualization on CentOS" 
> >> <centos-virt@centos.org>
> >> Sent: Sunday, 25 October, 2015 11:02:22
> >> Subject: Re: [CentOS-virt] Libvirt enhancement requests
> > 
> >> On Wed, Oct 21, 2015 at 05:44:20PM +0100, Nux! wrote:
> >>> Hi folks,
> >>>
> >> 
> >> Hi,
> >> 
> >>> I know you're rebuilding livbirt for the SIG. Would it be possible to 
> >>> enable RBD
> >>> support in it?
> >>>
> >> 
> >> Yes, we should definitely enable RBD / Ceph support in libvirt!
> >> 
> >> 
> >> 
> >>> I know quite a few cases (in the Cloudstack community) that switched to 
> >>> Ubuntu
> >>> particularly because CEPH support was missing.
> >>> The recommendation is to rebuild the rpms, but this is not a viable thing 
> >>> for
> >>> everyone. E.g.
> >>> http://blog.widodh.nl/2015/04/rebuilding-libvirt-under-centos-7-1-with-rbd-storage-pool-support/
> >>> 
> >>> Another thing that I noticed on the CentOS ml recently is an alleged lack 
> >>> of
> >>> hooks, https://www.libvirt.org/hooks.html
> >>> 
> >>> And last but not least, where could I find the libvirt (s)rpms that the 
> >>> SIG
> >>> produces?
> >>> 
> >>> Lucian
> >>> 
> >> 
> >> 
> >> -- Pasi
> >> 
> >> ___
> >> 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 mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen virt* issues

[Pasi Kärkkäinen]

On Tue, Sep 29, 2015 at 12:37:25PM +0100, George Dunlap wrote:
> On Sat, Sep 26, 2015 at 9:29 PM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> > On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote:
> >> Hello,
> >>
> >> I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 
> >> and dom0 3.18.17 rpms, and noticed these new problems:
> >>
> >
> > And third issue aswell:
> >
> > 3) Creating an HVM guest using virt-manager with file-based storage uses 
> > loopback-mount, not blktap
> >
> > When I manually create a new Xen HVM guest using virt-manager, and choose 
> > file-based image for storage of the VM, it seems to be set up to use file: 
> > backend/driver with loopback-mounted image file:
> >
> > 
> >   
> >   
> >   
> >   
> > 
> >
> > # losetup -a
> > /dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img)
> >
> > With earlier versions of rpms similar setup used blktap2 backend.. (and 
> > yes, I do have blktap module loaded in dom0 kernel).
> 
> I remember having to patch some dependency of virt-manager to give it
> the correct default driver name (something like, it got 'tap' but
> needed to be 'tap2').  In all likelihood, someone has sussed that
> 'tap' doesn't work and just replaced it with 'file'.  Actually, it's
> fairly likely if they've updated stuff in CentOS that you're not
> getting the re-build virt-manager stuff either -- I may have to respin
> that one as well.
>

I think it's specified at least in python-virtinst. See these emails from a few 
years back about the tap/tap2-issue:

https://www.redhat.com/archives/virt-tools-list/2013-June/msg00037.html
https://www.redhat.com/archives/virt-tools-list/2013-June/msg00039.html

 
> While we're here, could you give me a couple of virt-install and
> virt-viewer "smoketest" commands that I could add to my automated test
> scripts?  ATM I'm testing libvirt by using virsh to import an xl .cfg
> file, but it would be better to have something that created the config
> end-to-end.  Using virt-manager directly is probably more work than
> I'm up for in most cases, but hopefully if I can test the things it
> depends on I can notice this sort of breakage.
> 

The problem with virt-viewer issue is that it gives the "error popup" in the 
GUI,
so there's no way to figure out it didn't work without looking at the GUI and 
interacting with the gui..

Not easy to script/automate..


> Thanks,
>  -George


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen virt* issues

[Pasi Kärkkäinen]

On Mon, Sep 28, 2015 at 03:22:10PM +0100, George Dunlap wrote:
> On Sat, Sep 26, 2015 at 7:04 PM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> > Hello,
> >
> > I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and 
> > dom0 3.18.17 rpms, and noticed these new problems:
> >
> >
> > 1) virt-manager fails to start with an error: "D-Bus library appears to be 
> > incorrectly set up; failed to read machine uuid: Failed to open 
> > "/var/lib/dbus/machine-id": No such file or directory"
> >
> > And indeed.. there was no such file. Running command "dbus-uuidgen 
> > --ensure" fixed it, and virt-manager starts OK after that. So this was more 
> > for the mailinglist archives, if someone else meets the same issue.
> 
> That's a bit strange -- maybe there was a post-processing thing added
> to 6.7 that does this, which my package lacks.  I'll take a look at it
> when I get a chance.
> 
> (Or let me know and I'll post the virt-manager source so you can look
> at it and maybe send a pull request!)
> 

Sure :)


> > 2) virt-viewer doesn't work anymore.
> >
> > It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 
> > 2.0-7, with a lot of changes..
> >
> > If I try to use virt-viewer and run "virt-viewer " command, I get 
> > an error popup dialog saying "Failed to connect: Display can only be 
> > attached through libvirt with --attach".
> >
> > verbose debug output:
> >
> >
> > # virt-viewer -v --debug -c "xen://" testvm
> >
> > (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: 
> > (null),(null),(null),-1,(null),(null),(null),0
> > [root@fdell01 rpm]# less testvm01.txt
> > (virt-viewer:9374): virt-viewer-DEBUG: connecting ...
> > (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with 
> > URI xen://
> > Opening connection to libvirt with URI xen://
> > (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520
> > (virt-viewer:9374): virt-viewer-DEBUG: initial connect
> > (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> > (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: 
> > UUID changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
> > (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, 
> > using fallback
> > (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> > (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining 
> > display
> > Guest testvm is running, determining display
> > (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> > (null),(null),(null),-1,(null),(null),(null),0
> > (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display
> > Guest testvm has a vnc display
> > (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
> > (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
> > access prevents virDomainOpenGraphics
> > (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1
> > (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7
> > (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820
> >
> > (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> > (null),(null),(null),-1,(null),(null),(null),0
> 
> 
> Searching around, it looks like the error above is pretty common as a
> first try, but that usually fall-backs are attempted which then
> succeed.  The normal thing following "After open connection callback
> fd=-1" is "DEBUG: Opening direct TCP connection to display at
> 127.0.0.1:5901:-1".
> 
> Can you try virt-viewer -v --debug on 6.6 to see what things look like there?
>

Yep, here's debug output from a working virt-viewer session with virt-viewer 
0.6.0-11.el6 (from centos 6.6):

(virt-viewer:3989): virt-viewer-DEBUG: Insert window 0 0x1fba020
(virt-viewer:3989): virt-viewer-DEBUG: fullscreen display 0: 0
(virt-viewer:3989): virt-viewer-DEBUG: connecting ...
(virt-viewer:3989): virt-viewer-DEBUG: Opening connection to libvirt with URI 
xen://
Opening connection to libvirt with URI xen://
(virt-viewer:3989): virt-viewer-DEBUG: Add handle 7 1 0x203dc30
(virt-viewer:3989): virt-viewer-DEBUG: initial connect
(virt-viewer:3989): virt-viewer-DEBUG: notebook show status 0x1fc8000
(virt-viewer:3989): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
changed to ce5bfb10-cd02-7cf2-45b0-7ee36d751987
(virt-viewer:3989): virt-viewer-DEBUG: notebook show status 0x1fc8000
(virt-viewer:3989): virt-viewer-DEBUG: Guest testvm is running, determining 
disp

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

On Sat, Sep 26, 2015 at 08:51:37PM +0300, Pasi Kärkkäinen wrote:
> On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote:
> > 
> > > Anyway, here's something I noticed while testing xend bits:
> > >
> > > # systemctl enable xend.service
> > > xend.service is not a native service, redirecting to /sbin/chkconfig.
> > > Executing /sbin/chkconfig xend on
> > > The unit files have no [Install] section. They are not meant to be enabled
> > > using systemctl.
> > > Possible reasons for having this kind of units are:
> > > 1) A unit may be statically enabled by being symlinked from another unit's
> > >.wants/ or .requires/ directory.
> > > 2) A unit's purpose may be to act as a helper for some other unit which 
> > > has
> > >a requirement dependency on it.
> > > 3) A unit may be started when needed via activation (socket, path, timer,
> > >D-Bus, udev, scripted systemctl call, ...).
> > >
> > >
> > > "systemctl start xend.service" works OK though.. and after that xm works 
> > > too.
> > 
> > Right -- I haven't tried xend under systemd.  Given that xend is gone
> > in 4.6, I'm considering whether to say "patches welcome" re fixing
> > xend in 4.4 for C7...
> > 
> 
> I'll try to investigate.. 
> 

Actually it seems those were "warnings" only.. xend does start automatically 
now on centos7. 
So it's not a problem really.


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen virt* issues

[Pasi Kärkkäinen]

Hello,

Replying to myself.. see below for more details about the problem.

On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote:
> 
> 2) virt-viewer doesn't work anymore. 
> 
> It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 
> 2.0-7, with a lot of changes..
> 
> If I try to use virt-viewer and run "virt-viewer " command, I get an 
> error popup dialog saying "Failed to connect: Display can only be attached 
> through libvirt with --attach".
> 
> verbose debug output:
> 
> 
> # virt-viewer -v --debug -c "xen://" testvm
> 
> (virt-viewer:9420): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> [root@fdell01 rpm]# less testvm01.txt 
> (virt-viewer:9374): virt-viewer-DEBUG: connecting ...
> (virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI 
> xen://
> Opening connection to libvirt with URI xen://
> (virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520
> (virt-viewer:9374): virt-viewer-DEBUG: initial connect
> (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> (virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
> changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
> (virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, 
> using fallback
> (virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
> (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining 
> display
> Guest testvm is running, determining display
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> (virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display
> Guest testvm has a vnc display
> (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
> access prevents virDomainOpenGraphics
> (virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1
> (virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7
> (virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> 
> 
> And trying with the "attach" option:
> 
> # virt-viewer -v --debug -c "xen://" -a testvm
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> [root@fdell01 rpm]# less testvm02.txt 
> (virt-viewer:9389): virt-viewer-DEBUG: connecting ...
> (virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI 
> xen://
> Opening connection to libvirt with URI xen://
> (virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580
> (virt-viewer:9389): virt-viewer-DEBUG: initial connect
> (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
> (virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
> changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
> (virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, 
> using fallback
> (virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
> (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining 
> display
> Guest testvm is running, determining display
> (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> (virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display
> Guest testvm has a vnc display
> (virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing 
> is not supported by this connection
> (virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1
> (virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7
> (virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820
> 
> (virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
> (null),(null),(null),-1,(null),(null),(null),0
> 
> 
> 
> So it seems both connection types/methods now fail.. I'm not sure if the 
> issue is in our custom libvirt build, or in Xen's qemu.. (googling for those 
> errors reveals some related patches which also have patches for qemu: 
> http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185)
> 
> Error from the first attempt:
> 
> (virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
> (virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
> access prevents virDomainOpenGraphics
> 
> Error from the second attempt:
> (virt-viewer:9389

[CentOS-virt] CentOS 6 Xen virt* issues

[Pasi Kärkkäinen]

Hello,

I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and 
dom0 3.18.17 rpms, and noticed these new problems:


1) virt-manager fails to start with an error: "D-Bus library appears to be 
incorrectly set up; failed to read machine uuid: Failed to open 
"/var/lib/dbus/machine-id": No such file or directory"

And indeed.. there was no such file. Running command "dbus-uuidgen --ensure" 
fixed it, and virt-manager starts OK after that. So this was more for the 
mailinglist archives, if someone else meets the same issue.


2) virt-viewer doesn't work anymore. 

It seems in el6.6 virt-viewer was version 0.6.0-11, but now in el6.7 it's 
2.0-7, with a lot of changes..

If I try to use virt-viewer and run "virt-viewer " command, I get an 
error popup dialog saying "Failed to connect: Display can only be attached 
through libvirt with --attach".

verbose debug output:


# virt-viewer -v --debug -c "xen://" testvm

(virt-viewer:9420): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0
[root@fdell01 rpm]# less testvm01.txt 
(virt-viewer:9374): virt-viewer-DEBUG: connecting ...
(virt-viewer:9374): virt-viewer-DEBUG: Opening connection to libvirt with URI 
xen://
Opening connection to libvirt with URI xen://
(virt-viewer:9374): virt-viewer-DEBUG: Add handle 7 1 0x865520
(virt-viewer:9374): virt-viewer-DEBUG: initial connect
(virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
(virt-viewer:9374): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
(virt-viewer:9374): virt-viewer-DEBUG: No guest-specific fullscreen config, 
using fallback
(virt-viewer:9374): virt-viewer-DEBUG: notebook show status 0x7f
(virt-viewer:9374): virt-viewer-DEBUG: Guest testvm is running, determining 
display
Guest testvm is running, determining display
(virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0
(virt-viewer:9374): virt-viewer-DEBUG: Guest testvm has a vnc display
Guest testvm has a vnc display
(virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
(virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
access prevents virDomainOpenGraphics
(virt-viewer:9374): virt-viewer-DEBUG: After open connection callback fd=-1
(virt-viewer:9374): virt-viewer-DEBUG: Remove handle 1 7
(virt-viewer:9374): virt-viewer-DEBUG: Disposing window 0x7e1820

(virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0


And trying with the "attach" option:

# virt-viewer -v --debug -c "xen://" -a testvm

(virt-viewer:9374): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0
[root@fdell01 rpm]# less testvm02.txt 
(virt-viewer:9389): virt-viewer-DEBUG: connecting ...
(virt-viewer:9389): virt-viewer-DEBUG: Opening connection to libvirt with URI 
xen://
Opening connection to libvirt with URI xen://
(virt-viewer:9389): virt-viewer-DEBUG: Add handle 7 1 0x13ef580
(virt-viewer:9389): virt-viewer-DEBUG: initial connect
(virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
(virt-viewer:9389): virt-viewer-DEBUG: virt_viewer_app_set_uuid_string: UUID 
changed to 587eb1bf-2427-a4d3-9113-d8bfb9911212
(virt-viewer:9389): virt-viewer-DEBUG: No guest-specific fullscreen config, 
using fallback
(virt-viewer:9389): virt-viewer-DEBUG: notebook show status 0x137a000
(virt-viewer:9389): virt-viewer-DEBUG: Guest testvm is running, determining 
display
Guest testvm is running, determining display
(virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0
(virt-viewer:9389): virt-viewer-DEBUG: Guest testvm has a vnc display
Guest testvm has a vnc display
(virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection
(virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing 
is not supported by this connection
(virt-viewer:9389): virt-viewer-DEBUG: After open connection callback fd=-1
(virt-viewer:9389): virt-viewer-DEBUG: Remove handle 1 7
(virt-viewer:9389): virt-viewer-DEBUG: Disposing window 0x136b820

(virt-viewer:9389): virt-viewer-DEBUG: Set connect info: 
(null),(null),(null),-1,(null),(null),(null),0



So it seems both connection types/methods now fail.. I'm not sure if the issue 
is in our custom libvirt build, or in Xen's qemu.. (googling for those errors 
reveals some related patches which also have patches for qemu: 
http://comments.gmane.org/gmane.comp.emulators.virt-tools/9185)

Error from the first attempt:

(virt-viewer:9374): virt-viewer-DEBUG: Using direct libvirt connection
(virt-viewer:9374): virt-viewer-DEBUG: Error operation forbidden: read only 
access prevents virDomainOpenGraphics

Error from the second attempt:
(virt-viewer:9389): virt-viewer-DEBUG: Using direct libvirt connection
(virt-viewer:9389): virt-viewer-DEBUG: Error argument unsupported: fd passing 
is not 

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote:
> 
> > Anyway, here's something I noticed while testing xend bits:
> >
> > # systemctl enable xend.service
> > xend.service is not a native service, redirecting to /sbin/chkconfig.
> > Executing /sbin/chkconfig xend on
> > The unit files have no [Install] section. They are not meant to be enabled
> > using systemctl.
> > Possible reasons for having this kind of units are:
> > 1) A unit may be statically enabled by being symlinked from another unit's
> >.wants/ or .requires/ directory.
> > 2) A unit's purpose may be to act as a helper for some other unit which has
> >a requirement dependency on it.
> > 3) A unit may be started when needed via activation (socket, path, timer,
> >D-Bus, udev, scripted systemctl call, ...).
> >
> >
> > "systemctl start xend.service" works OK though.. and after that xm works 
> > too.
> 
> Right -- I haven't tried xend under systemd.  Given that xend is gone
> in 4.6, I'm considering whether to say "patches welcome" re fixing
> xend in 4.4 for C7...
> 

I'll try to investigate.. 


Thanks,

-- Pasi


>  -George


___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen virt* issues

[Pasi Kärkkäinen]

On Sat, Sep 26, 2015 at 09:04:23PM +0300, Pasi Kärkkäinen wrote:
> Hello,
> 
> I just upgraded some of my el6xen boxes to latest CentOS 6.7, Xen 4.4.3 and 
> dom0 3.18.17 rpms, and noticed these new problems:
> 

And third issue aswell:

3) Creating an HVM guest using virt-manager with file-based storage uses 
loopback-mount, not blktap

When I manually create a new Xen HVM guest using virt-manager, and choose 
file-based image for storage of the VM, it seems to be set up to use file: 
backend/driver with loopback-mounted image file:


  
  
  
  


# losetup -a
/dev/loop0: [fd00]:1709109 (/var/lib/libvirt/images/testvm2.img)

With earlier versions of rpms similar setup used blktap2 backend.. (and yes, I 
do have blktap module loaded in dom0 kernel).


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] xen and centos7

[Pasi Kärkkäinen]

On Fri, Sep 25, 2015 at 09:49:01AM +0200, Christoph wrote:
> Hi
>

Hi,
 
> is there already a release of xen for centos7? If not it is on
> roadmap? If yes when could it be done?
>

Yeah the testing rpms for centos7/xen are in virt7-xen-44-testing repository 
(and virt7-xen-46-testing aswell).


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

On Mon, Sep 21, 2015 at 11:10:06AM +0300, Pasi Kärkkäinen wrote:
> Hi,
> 
> On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
> > Updated Xen 4.4.3 packages have passed my local smoke tests, and are
> > now available.
> > 
> > Full C7 release is still waiting on suitable testing for the libvirt 
> > packages.
> > 
> > If someone wants to step up to give the libvirt packages a decent
> > smoke test, that will speed the C7 release process significantly.
> > Otherwise it will have to wait until I get a chance to write some
> > automated smoke tests.
> >
> 
> I'm currently in the process of testing these latest Xen 4.4.3 rpms on 
> centos7.
> 

Actually I don't see libvirt rpms in the virt7-xen-44-testing repo. Which 
libvirt rpms should I be testing? 

Currently I have these installed:

virt-viewer-0.6.0-12.el7.x86_64
libvirt-daemon-1.2.8-16.el7_1.4.x86_64
virt-manager-common-1.1.0-12.el7.noarch
libvirt-client-1.2.8-16.el7_1.4.x86_64
libvirt-python-1.2.8-7.el7_1.1.x86_64
virt-manager-1.1.0-12.el7.noarch
libvirt-daemon-driver-network-1.2.8-16.el7_1.4.x86_64
libvirt-daemon-config-network-1.2.8-16.el7_1.4.x86_64
libvirt-glib-0.1.7-3.el7.x86_64

 
> > In the mean time, here's how to install the core Xen packages:
> > 
> > rpm -ivh 
> > http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-3.el7.x86_64.rpm
> > 
> 
> That link seems broken.. this one works:
> http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-5.el7.x86_64.rpm
> 
> 


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

Hi,

On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
> Updated Xen 4.4.3 packages have passed my local smoke tests, and are
> now available.
> 
> Full C7 release is still waiting on suitable testing for the libvirt packages.
> 
> If someone wants to step up to give the libvirt packages a decent
> smoke test, that will speed the C7 release process significantly.
> Otherwise it will have to wait until I get a chance to write some
> automated smoke tests.
>

I'm currently in the process of testing these latest Xen 4.4.3 rpms on centos7.
 
> In the mean time, here's how to install the core Xen packages:
> 
> rpm -ivh 
> http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-3.el7.x86_64.rpm
> 

That link seems broken.. this one works:
http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-5.el7.x86_64.rpm


> This will set up yum repositories for both the eventual release
> repositories (enabled by default), and the community build system
> repositories (disabled by default).
> 
> At the moment, all packages will be stored in the virt-xen-44-testing
> repository.  You can either enable this by default by editing
> /etc/yum.repos.d/VirtSIG-Xen.repo, or by adding
> "--enablerepo=virt-xen-44-testing".
> 
> If you want, you can edit defaults /etc/sysconfig/xen-kernel
> 
> Next, run 'yum update' to get the new kernel:
> 
> yum --enablerepo=virt-xen-44-testing update kernel
> 
> Now install xen:
> 
> yum --enablerepo=virt-xen-44-testing install xen
> 
> This should grab both xen and the updated kernel package.  It should
> also automatically:
> * Add default commandline parameters for Xen and Linux when booting under Xen
> * Arrange for xen to come up first in the grub
> * Set the default boot entry to Xen.
> 
> That's it!  Reboot and you should be good to go.
> 
> Please report any problems or feedback to this list.
> 
>  -George


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

On Mon, Sep 21, 2015 at 11:24:23AM +0100, George Dunlap wrote:
> On Mon, Sep 21, 2015 at 9:18 AM, Pasi Kärkkäinen <pa...@iki.fi> wrote:
> > On Mon, Sep 21, 2015 at 11:10:06AM +0300, Pasi Kärkkäinen wrote:
> >> Hi,
> >>
> >> On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
> >> > Updated Xen 4.4.3 packages have passed my local smoke tests, and are
> >> > now available.
> >> >
> >> > Full C7 release is still waiting on suitable testing for the libvirt 
> >> > packages.
> >> >
> >> > If someone wants to step up to give the libvirt packages a decent
> >> > smoke test, that will speed the C7 release process significantly.
> >> > Otherwise it will have to wait until I get a chance to write some
> >> > automated smoke tests.
> >> >
> >>
> >> I'm currently in the process of testing these latest Xen 4.4.3 rpms on 
> >> centos7.
> >>
> >
> > Actually I don't see libvirt rpms in the virt7-xen-44-testing repo. Which 
> > libvirt rpms should I be testing?
> 
> Oh, weird -- well I had it tagged for -candidate, but not for
> -testing.  Probably because I hadn't even done a smoke test on it. :-)
> 
> Anyway, I've tagged it now.
>

OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing 
repo,
but it seems yum still doesn't pick them up:

# yum clean all
# yum --enablerepo=virt-xen-44-testing update
..
No packages marked for update

# rpm -qa | grep -i libvirt-daemon-1
libvirt-daemon-1.2.8-16.el7_1.4.x86_64


I guess I'll install those 1.2.15-3.el7 rpms manually.


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

[Pasi Kärkkäinen]

On Mon, Sep 21, 2015 at 01:46:36PM +0300, Pasi Kärkkäinen wrote:
> 
> OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing 
> repo,
> but it seems yum still doesn't pick them up:
> 
> # yum clean all
> # yum --enablerepo=virt-xen-44-testing update
> ..
> No packages marked for update
> 
> # rpm -qa | grep -i libvirt-daemon-1
> libvirt-daemon-1.2.8-16.el7_1.4.x86_64
> 
> 
> I guess I'll install those 1.2.15-3.el7 rpms manually.
> 

It seems now the packages installed OK using yum aswell. I guess you or someone 
refreshed the repo :)

Anyway, here's something I noticed while testing xend bits:

# systemctl enable xend.service
xend.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig xend on
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).


"systemctl start xend.service" works OK though.. and after that xm works too.


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] poor performance with dom0 on centos7

[Pasi Kärkkäinen]

On Wed, Sep 16, 2015 at 09:46:52PM +0200, Christoph wrote:
> Hi
>

Hi,
 
> Im now pretty sure the problem is the DomU with NFS Server.
> 
> If I write on a NFS share from other Host (bare metal or other vm)
> then I see on my NFS server nearly the whole time 100% io at
> [jbd2/dm-5-8] process...
> If I write on a SMB share (same partition as nfs share) from other
> Host then it is a little bit better but still ever and ever again
> 100% io load
> 

Are you using nfs over UDP or TCP ? 

> If I write a 1GB file on the same partition (with nfs/samba share)
> with dd, I dont see the high io load...
> 
> Is there a known problem with nfs/smb shares and/or dm in xen domU's
> on centos 7 as dom0? With centos 6 as dom0 I didnt had the
> problem...
> (the partition with the shares is a raid5 software partition, soft
> raid is build in dom0 and as a xvd device passed through to the domU
> with the shares)
> 
> could selinux be the problem? I have it in permissive mode on all
> hosts here (dom0 and domU) not disabled...
> 

I don't think.

> Any hints for me?
> 

If you used NFS over UDP, try running it over TCP.

What does 'top' and/or 'iostat -x 1' say during the 'benchmark'  ?


-- Pasi

> Am 2015-09-01 06:47, schrieb Christoph:
> >Hi All
> >
> >it is possible to tune dom0/domU for better IO/network performance?
> >Since I have changed to Cenots7 dom0, I have a really poor IO
> >performance inside a PV VM.
> >
> >I have already done what is described on
> >http://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance
> >It is better now but still significantly worse than with centos6 dom0
> >
> >my settings:
> >
> >xen parameter: dom0_mem=1024M cpufreq=xen dom0_max_vcpus=2
> >dom0_vcpus_pin
> >
> >xl sched-credit
> >Cpupool Pool-0: tslice=30ms ratelimit=1000us
> >NameID Weight  Cap
> >Domain-0 0   10240
> >samael   12560
> >satan25120
> >amon 32560
> >leviathan45120
> >
> >echo 1048576 > /proc/sys/net/ipv4/tcp_limit_output_bytes on dom0
> >
> >the both domU's satan and leviathan are very IO performance oriented
> >(NFS server and downloading vm)
> >
> >Is there something more what I can do or try?
> >
> >could it be a selinux issue? I have it in permissive mode there, not
> >disabled. But permissive means only to collect the info not enforcing
> >the rules...
> >
> >(I use the xen45 pkgs)
> 
> -- 
> --
> Greetz
> ___
> 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

Re: [CentOS-virt] libvirt, xen PV, qemu-system-i386, root user

[Pasi Kärkkäinen]

On Sat, Sep 12, 2015 at 01:35:48AM +0200, Karel Hendrych wrote:
> Comparing simple dd bs=1M count=1 on dom0 vs domU. Qemu driver
> is achieving pretty much the same like dom0.
>

So you're measuring buffered speed. Try measuring non-buffered (iflag=direct or 
oflag=direct, depending if you're reading or writing).

-- Pasi

> Thanks
> --
> Karel
> 
> On 7.9.2015 21:45, Pasi Kärkkäinen wrote:
> >On Mon, Sep 07, 2015 at 05:47:39PM +0200, Karel Hendrych wrote:
> >>...
> >>
> >>changing from:  to:  makes
> >>the domain start without QEMU.
> >>
> >>However I see much better performance with QEMU (close to dom0,
> >>tested using simple dd writes) than with tap2 driver. Is that
> >>expected?
> >>
> >
> >How did you measure it? buffered or direct io?
> >
> >
> >-- Pasi
> >
> >
> >>What's best practise to file based storage on latest CentOS6-xen
> >>(Kernel 3.18.17, Xen 4.4.2-7)
> >>
> >>Are there any guides around running QEMU on CentOS6-xen as non-root user?
> >>
> >>Cheers
> >>--
> >>Karel
> >>
> >>On 7.9.2015 17:42, Karel Hendrych wrote:
> >>>Hi, spot on!
> >>>
> >>>
> >>>On 6.9.2015 12:56, Pasi Kärkkäinen wrote:
> >>>>On Sun, Sep 06, 2015 at 09:08:50AM +0200, Karel Hendrych wrote:
> >>>>>Hi, after migrating to libvirt/libxl according to:
> >>>>>
> >>>>
> >>>>Hi,
> >>>>
> >>>>>https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt
> >>>>>
> >>>>>I've noticed that my Xen PV domains are being launched by
> >>>>>qemu-system-i386 running under root privileges.
> >>>>>
> >>>>>I am wondering why is this? Previously no qemu process was used.
> >>>>>
> >>>>>If qemu is needed for some reason, are there any guidelines for
> >>>>>non-root operation?
> >>>>>
> >>>>
> >>>>In general qemu is used for the following purposes:
> >>>>
> >>>>- for certain domU disk backend types (image files), and/or if there's
> >>>>no blktap driver in dom0 kernel.
> >>>>- domU graphical console (PVFB) VNC server, if it's enabled for the domU.
> >>>>
> >>>>
> >>>>>--
> >>>>>Karel Hendrych
> >>>>
> >>>>
> >>>>-- Pasi
> >>>>
> >>>>___
> >>>>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 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 mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] libvirt, xen PV, qemu-system-i386, root user

[Pasi Kärkkäinen]

On Sun, Sep 06, 2015 at 09:08:50AM +0200, Karel Hendrych wrote:
> Hi, after migrating to libvirt/libxl according to:
>

Hi,
 
> https://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt
> 
> I've noticed that my Xen PV domains are being launched by
> qemu-system-i386 running under root privileges.
> 
> I am wondering why is this? Previously no qemu process was used.
> 
> If qemu is needed for some reason, are there any guidelines for
> non-root operation?
>

In general qemu is used for the following purposes:

- for certain domU disk backend types (image files), and/or if there's no 
blktap driver in dom0 kernel.
- domU graphical console (PVFB) VNC server, if it's enabled for the domU.

 
> --
> Karel Hendrych


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] poor performance with dom0 on centos7

[Pasi Kärkkäinen]

On Tue, Sep 01, 2015 at 06:47:18AM +0200, Christoph wrote:
> Hi All
> 

Hello,

> it is possible to tune dom0/domU for better IO/network performance?
> Since I have changed to Cenots7 dom0, I have a really poor IO
> performance inside a PV VM.
> 
> I have already done what is described on
> http://wiki.xenproject.org/wiki/Tuning_Xen_for_Performance
> It is better now but still significantly worse than with centos6 dom0
> 
> my settings:
> 
> xen parameter: dom0_mem=1024M cpufreq=xen dom0_max_vcpus=2
> dom0_vcpus_pin
> 
> xl sched-credit
> Cpupool Pool-0: tslice=30ms ratelimit=1000us
> NameID Weight  Cap
> Domain-0 0   10240
> samael   12560
> satan25120
> amon 32560
> leviathan45120
> 
> echo 1048576 > /proc/sys/net/ipv4/tcp_limit_output_bytes on dom0
> 
> the both domU's satan and leviathan are very IO performance oriented
> (NFS server and downloading vm)
> 
> Is there something more what I can do or try?
> 
> could it be a selinux issue? I have it in permissive mode there, not
> disabled. But permissive means only to collect the info not enforcing
> the rules...
> 
> (I use the xen45 pkgs)
> 

You forgot to mention the most important thing.. what kind of performance 
numbers are you seeing? What are you expecting? 


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Beta CentOS 7 Xen packages available

[Pasi Kärkkäinen]

On Wed, Jun 17, 2015 at 03:24:45PM +0100, George Dunlap wrote:
 At long last, I'd like to announce beta packages for CentOS 7,
 available from the community build system.
 
 Start by installing the centos-release-xen:
 
 rpm -ivh 
 http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-3.el7.x86_64.rpm
 
 This will set up yum repositories for both the eventual release
 repositories (enabled by default), and the community build system
 repositories (disabled by default).
 
 At the moment, all packages will be stored in the virt-xen-44-testing
 repository.  You can either enable this by default by editing
 /etc/yum.repos.d/VirtSIG-Xen.repo, or by adding
 --enablerepo=virt-xen-44-testing.
 
 If you want, you can edit defaults /etc/sysconfig/xen-kernel
 
 Next, run 'yum update' to get the new kernel:
 
 yum --enablerepo=virt-xen-44-testing update kernel
 
 Now install xen:
 
 yum --enablerepo=virt-xen-44-testing install xen
 
 This should grab both xen and the updated kernel package.  It should
 also automatically:
 * Add default commandline parameters for Xen and Linux when booting under Xen
 * Arrange for xen to come up first in the grub
 * Set the default boot entry to Xen.
 
 That's it!  Reboot and you should be good to go.
 
 Libvirt packages aren't available yet but should be on the way soon
 (I'll announce them here.)
 
 Please report any problems or feedback to this list.


Good stuff! I'll test these packages soon.


Thanks a lot.

-- Pasi

 
  -George

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Linux kernel 3.18.12 and libvirt 1.2.15 for Xen4CentOS in virt6-testing

[Pasi Kärkkäinen]

Hi,

On Wed, May 13, 2015 at 07:14:22PM +0100, George Dunlap wrote:
 Thanks to work from Johnny, linux 3.18.12 with all the x4c blktap
 goodness have been built and are now in the virt6-testing repo.  I've
 also uploaded libvirt 1.2.15.  As you may have seen earlier today,
 virt6-testing also includes an updated 4.4.2 package with the latest
 security update (XSA-133).
 
 The kernel has had some basic testing (by myself, Johnny, and another
 community member), but libvirt is at the moment untested, so caveat
 emptor.
 
 With such a large change, I want to leave both up for a few weeks
 before pushing them into the main repo.  Please test them and report
 any errors you find.
 

Great!

 As a reminder, you can use the virt6-testing repo by putting the
 following file into /etc/yum.repos.d:
 
 [virt-testing]
 name=VirtSIG-\$releasever - Xen Testing
 baseurl=http://cbs.centos.org/repos/virt6-testing/\$basearch/os/
 gpgcheck=0
 enabled=0
 
 For the adventurous, there are (as yet untested) kernel and xen
 packages in virt7-xen-44-candidate as well.  I'll be pushing those to
 testing once I've actually had a chance to do set up my testing
 environment.
 

Nice. I'll test these in the near future for sure :)


 Peace,
  -George



Thanks a lot,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] The future of blktap in Xen4CentOS

[Pasi Kärkkäinen]

Hello,

On Wed, May 06, 2015 at 03:27:54PM +0100, George Dunlap wrote:
 On Tue, May 5, 2015 at 2:07 PM, Johnny Hughes joh...@centos.org wrote:
  WRT a new kernel .. the 3.18.x kernel has been selected to be maintained
  as an LTS until Jan 2017.  I think we should start work on rebuilding
  this kernel and using it in the x4c projects.
 
  https://lwn.net/Articles/636289/
 
  Thoughts?
 
  I will grab this kernel and try to roll in all the patches, etc. and see
  if I can make it work.
 
 I did a little bit of work on building the 3.18 kernel a couple of
 weeks ago, but it looks like the blktap2.5 kernel code we were using
 before has totally bitrotted.
 
 I see three ways forward:
 
 1. Try to do a deep port of the functionality, continuing to
 maintain it going forward.


How badly has the blktap 2.5 kernel code bitrotted? What areas are the most 
problematic?
Any idea how much work would it be to get it working with 3.18 LTS ? 

 
 2. Start using the blktap3 code, which requires no kernel driver.
 
 3. Drop blktap support, and ask people to use qdisk for vhd.
 
 Re #1, I'm not really excited about the idea of trying to keep porting
 those patches forward (and finding and fixing bugs in the forward-port
 each time).
 
 Re #2, this would require getting the blktap3 stuff working upstream
 and then backporting it.
 

Yeah.. likely more work than the deep port of blktap 2.5 kernel code..

 #3 would be by far the easiest.


But not very nice.. 
 
 In parallel to the Xen for C7 work I've been doing, I've been working
 on getting upstream Xen to build against XenServer's blktap code, with
 then aim of moving to blktap3.  If we want to go with #2, then a major
 kernel update will have to wait until that work is done.

  -George


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen 4.4.2 (with XSA-132) in virt6-testing

[Pasi Kärkkäinen]

On Wed, May 06, 2015 at 12:30:55PM +0100, George Dunlap wrote:
 On Thu, Apr 23, 2015 at 5:09 PM, George Dunlap dunl...@umich.edu wrote:
  I've got Xen 4.4.2 in virt6-testing.  I haven't had a chance to test
  it, and won't for another week or two; but if some volunteers can put
  it through its paces, I can ask Johnny to push it to the public repo
  sometome early next week.
 
 Unless there are any objections, I'll ask for this to be pushed
 tomorrow (Wednesday).
 

I just finished my testing of Xen 4.4.2 rpms, and they seem to work OK for me!


  -George


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen 4.4.2 (with XSA-132) in virt6-testing

[Pasi Kärkkäinen]

On Thu, Apr 23, 2015 at 05:09:56PM +0100, George Dunlap wrote:
 I've got Xen 4.4.2 in virt6-testing.  I haven't had a chance to test
 it, and won't for another week or two; but if some volunteers can put
 it through its paces, I can ask Johnny to push it to the public repo
 sometome early next week.


Great! Thanks a lot.

I'll do some testing during the weekend.
 
 Thanks,
  -George


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Updating to Xen 4.4.2

[Pasi Kärkkäinen]

On Mon, Apr 13, 2015 at 12:08:24PM +0100, George Dunlap wrote:
 On Sat, Apr 11, 2015 at 1:09 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
  Hello,
 
  Sorry I've missed the last virt-sig meetings. Are we already working on 
  updating the el6 rpms to Xen 4.4.2 ?
 
 I should probably have that done this week on my CentOS day. :-)


OK :) I can test when it's built!
 
  -George


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Updating to Xen 4.4.2

[Pasi Kärkkäinen]

Hello,

Sorry I've missed the last virt-sig meetings. Are we already working on 
updating the el6 rpms to Xen 4.4.2 ? 


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 VM image for paravirtualizaton on CentOS Xen server

[Pasi Kärkkäinen]

On Sun, Mar 15, 2015 at 07:52:42PM -0700, Sarah Newman wrote:
  
  I'd really prefer to work from 'virsh' than from hand-writing xl
  configuration files.When I last did this sort of thing, I worked from
  a PXE environment that I controlled and could reserve DHCP settings
  based on MAC addresses, and tune PXE to boot from disk by default but
  allow users to select a clean re-install of the operating system they
  wanted.
 
 virt-install with --location maybe? Never tried it but it looks like what you 
 want.
 
 http://linux.die.net/man/1/virt-install
 

Yeah you can use virt-install on CentOS 5 Xen host to install CentOS 6 PV domUs,
I do that often, an example for GUI installation:

virt-install -d -n vmname -r 1024 --vcpus=2 -f /dev/vg01/vmname_disk0 -b virbr0 
--vnc -p -l http://ftp.funet.fi/pub/mirrors/centos.org/6.5/os/x86_64;

(you need to have virt-viewer installed, that'll be used to display the VNC GUI 
console).

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 VM image for paravirtualizaton on CentOS Xen server

[Pasi Kärkkäinen]

On Thu, Mar 12, 2015 at 10:34:39PM -0400, Nico Kadel-Garcia wrote:
 I'm looking at a CentOS 5  Xen server that I'd really like to put some
 more recent VM's. There are reasons not to touch it at the moment, so
 I can't upgrade it in place today.
 
 Has anyone successfully installed a CentOS 6 VM, paravirtualized, on a
 CentOS 5 Xen server , without significant Xen upgrades? If so, can I
 get a copy from a reputable source, or one that I can review before
 using? I'm having a bit of difficulty arranging a PXE enironment to do
 a paraviirtualized installation with, and there are apparently
 difficulties doing a paravirtualzed system with CD or DVD installation
 with Xen.
 
   Nico Kadel-Garcia nka...@gmail.com

Yep, CentOS 6 VMs run just fine on CentOS 5 Xen host.

-- Pasi


___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Upgrading Xen 3 on SL 5 server with CentOS 5 and SL 5

[Pasi Kärkkäinen]

On Fri, Feb 20, 2015 at 09:56:46AM -0500, Nico Kadel-Garcia wrote:
I'm dealing with an old Xen 3 server, and badly need to update it and all
the vm's on it to more contemporary operating systems.  So far, so good!
Can the Xen server on CentOS 5 para-virtualized CentOS 6?


Yes, CentOS 5 Xen host can run CentOS 6 PV domUs. Or CentOS 6 HVM guests.


And if not, I'm having real trouble getting a live cd or installation 
 media to boot in
full virtualization to do the update of the guests.
I'd normally start by updating the Xen server first, but that's not
workable right now.


Yeah CentOS 6 runs as Xen HVM (fully virtualized) aswell. With or without PV 
drivers (PVHVM).

-- Pasi

 
Nico Kadel-Garcia
Email: n[1]ka...@gmail.com
Sent from iPhone
On Feb 18, 2015, at 11:59, SilverTip257 [2]silvertip...@gmail.com wrote:
 
  On Wed, Feb 18, 2015 at 3:10 AM, C. L. Martinez
  [3]carlopm...@gmail.com wrote:
 
On Tue, Feb 17, 2015 at 1:43 PM, Sven Kieske [4]s.kie...@mittwald.de
wrote:


 On 17/02/15 09:18, C. L. Martinez wrote:
 Hi all,

 How can I stop/disable a nic in a virtual guest using a virsh
 command?? I am searching the same effect like if I unplug network
 cable ... Is it possible?? I have tried with detach-interface
 command without luck. I don't want to remove the nic from guest
 configuration, only to stop the nic ...

 Depending on your network architecture you could just ifdown
 the vmnet, but this just works if you don't have multiple
 vms on one vmnet (which you shouldn't).

 HTH

 --
 
Ok, to do a ifdown of virtual bridge it seems the only option.
 
Many thanks to all for your answers.
 
  * Definitely look to Juerg Haefliger's solution.  It's exactly what you
  want since you requested a method that can be done from the virsh
  interface.  Thanks Juerg!
  1) down the vnetX interface from the host node
ip link show dev vnetX
ip link set down vnetX
ip link show dev vnetX
  And if using bridged networking, you have one more option.
  2) remove the vnetX interface from the bridge
brctl delif bridge_int vnetX
  Certainly downing the interface using either Juerg's solution via virsh
  or mine via iproute2 tools is most ideal since it's easier/simpler to
  reinstate.  You can use ifconfig if you prefer it over ip tools, but
  enjoy those tools and syntax while it remains! [0]  ;-)
  [0] 
 [5]https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/
  --
  ---~~.~~---
  Mike
  //  SilverTip257  //
 
  ___
  CentOS-virt mailing list
  [6]CentOS-virt@centos.org
  [7]http://lists.centos.org/mailman/listinfo/centos-virt
 
 References
 
Visible links
1. mailto:ka...@gmail.com
2. mailto:silvertip...@gmail.com
3. mailto:carlopm...@gmail.com
4. mailto:s.kie...@mittwald.de
5. 
 https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/
6. mailto:CentOS-virt@centos.org
7. 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] Building Xen 4.4 rpms for centos7

[Pasi Kärkkäinen]

On Tue, Jan 20, 2015 at 05:27:48PM +0200, Pasi Kärkkäinen wrote:
  
  Agreed on this too .. let's use as much the same as we can, and we can
  use %if statements in the SPEC to differentiate el6 and el7 things, if
  necessary.  systemd versus init and maybe some version number changes
  for buildrequires should be the changes we need to be concerned about.
 
 
 Yep!
  
  
  We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it ..
  or we can shift to 3.14.x and that buys us at least one more year .. or
  wait until they name the next LTS kernel and go for that.  Likely the
  next LTS kernel will be the easiest option (the RH modified kernel will
  not support xen and rolling in stuff externally will be hard because of
  the backports RH does to the kernel (things that go into a standard
  kernel will not apply cleanly to the RH kernel).
  
  But, I agree lets try to use the el6 kernel for xen el7 too .. and we
  can switch both kernels as required later.
  
 
 Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to 
 work fine atm.
 
 Let's focus on getting the current rpms built for el7,
 and then later we can update both el6 and el7 to later kernel/versions.
 

So.. how do we get the Xen 4.4.1 rpms port to el7 going.. ? :)

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002

[Pasi Kärkkäinen]

On Fri, Jan 30, 2015 at 08:24:59PM -0700, rgritzo wrote:
Thanks for the info.
I am trying to connect to the Xen hypervisor, via a localhost connection
defined in the virt-manager configuration.
here is the detail provided in the error dialog:
*
Unable to open a connection to the Xen hypervisor/daemon.
Verify that:
 - A Xen host kernel was booted
 - The Xen service has been started
internal error: DBus support not compiled into this binary
Traceback (most recent call last):
  File /usr/share/virt-manager/virtManager/connection.py, line 1168, in
_open_thread
self.vmm = self._try_open()
  File /usr/share/virt-manager/virtManager/connection.py, line 1152, in
_try_open
flags)
  File /usr/lib64/python2.6/site-packages/libvirt.py, line 105, in
openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: internal error: DBus support not compiled into this binary
**
The hypervisor and VM*s work.  If i start and manage VMs with virsh, the
work fine.  it just is the virt-manager that seems broken, but that is
important for my operation.
i just applied the patches to a second machine - just in case it was
something about the first one - and the same results.
i am not as versed in python debugging as i would like to be, so this will
be a challenge.  it sure seems like the issue is in the libvirtd library
from the error messages -
but i will keep poking at it as time permits and post here if i have any
answers...


What does virsh version command say ? 

Do you have selinux in enforcing mode? Try getenforce command.


-- Pasi


thanks.
r.
 
  On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote:
   folks:
  
   after applying the updated rpms from advisory 2015:X002 i am having 
 problems with libvirtd, and with virt-manager.
  
   if i run libvirtd in the foreground and look at the error messages, the  
 error i see is
   2015-01-29 04:45:27.342+: 6477: error : virDBusGetSystemBus:1742 : 
 internal error: DBus support not compiled into this binary
  
 
  Hmm, weird, it works OK for me..
 
   and virt-manager is unable to connect to the hypervisor.  this started 
 after i applied the subject patches.
  
   is this an issue with the recent versions of libvirt?
   anybody else seeing this behavior?
  
 
  What hypervisor are you trying to use? Xen? KVM ?
 
   btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64
  
 
  I'm using the same kernel with Xen 4.4.1 rpms.
 
 
   thanks in advance.
  
   --
   [1]rgritzo at gmail.com
  
 
 
  * Pasi
 
*
r.
 
 References
 
Visible links
1. 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] Using network-script with Xen 4.4.1 (aka what will I do without xend?)

[Pasi Kärkkäinen]

On Thu, Jan 29, 2015 at 12:39:17AM -0800, Gene wrote:
I normally use the network-script parameter in the
'/etc/xen/xend-config.sxp' configuration file to configure network
bridges.  However, the latest release of Xen4CentOS (which comes with Xen
4.4.1) has xend disabled by default. Â
Can I continue to use network-script without xend?  If not what is the
recommended method for automatically configuring network bridges with the
latest release of Xen4CentOS?
I know I can just enable xend to continue using this script, but since Xen
4.5 is apparently dropping xend altogether I figure I should change my
standard configuration starting now.
Thanks in advance for your time.
-Gene

Hello,

You should set up the bridges using distro networking scripts, so 
/etc/sysconfig/network-scripts/ifcfg-* 
That's the supported and preferred way.

(It was the recommended way also with xend, that's why xen network-script was 
disabled as a default).


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] libvirt errors after applying RPMS from 2015:X002

[Pasi Kärkkäinen]

On Wed, Jan 28, 2015 at 09:54:54PM -0700, rgritzo wrote:
 folks:
 
 after applying the updated rpms from advisory 2015:X002 i am having problems 
 with libvirtd, and with virt-manager.
 
 if i run libvirtd in the foreground and look at the error messages, the  
 error i see is 
 2015-01-29 04:45:27.342+: 6477: error : virDBusGetSystemBus:1742 : 
 internal error: DBus support not compiled into this binary
 

Hmm, weird, it works OK for me..

 and virt-manager is unable to connect to the hypervisor.  this started after 
 i applied the subject patches.
 
 is this an issue with the recent versions of libvirt?
 anybody else seeing this behavior?
 

What hypervisor are you trying to use? Xen? KVM ? 

 btw - system is centos 6.6, kernel 3.10.63-11.el6.centos.alt.x86_64
 

I'm using the same kernel with Xen 4.4.1 rpms.


 thanks in advance.
 
 -- 
 rgri...@gmail.com
 


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Building Xen 4.4 rpms for centos7

[Pasi Kärkkäinen]

Hello,

Now that the Xen 4.4.1 rpms + libvirt 1.2.10 rpms for CentOS 6 seem to be in 
good shape
it would be a good time to start experimenting with el7 builds aswell.

I think it's best to start with the same set of packages we have for el6,
and just do the minimum required changes to get them working on centos7.

That probably means fixing some dependencies in the spec file, and some changes 
for systemd support. 

Note that all those changes are already done in Fedora 21 Xen rpms, for example:
ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/21/SRPMS/x/xen-4.4.1-12.fc21.src.rpm

A few months ago I also saw a Xen 4.4 el7 rpms port, so we could find those 
src.rpms aswell.


And then there's the dom0 kernel.. Stock rhel7/centos7 is based on Linux 3.10 
kernel,
so we probably can use the exact same 3.10.63 kernel we have today for CentOS 6 
Xen.

Any thoughts?


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Building Xen 4.4 rpms for centos7

[Pasi Kärkkäinen]

On Tue, Jan 20, 2015 at 08:35:31AM -0600, Johnny Hughes wrote:
 On 01/20/2015 08:10 AM, Pasi Kärkkäinen wrote:
  Hello,
  
  Now that the Xen 4.4.1 rpms + libvirt 1.2.10 rpms for CentOS 6 seem to be 
  in good shape
  it would be a good time to start experimenting with el7 builds aswell.
  
  I think it's best to start with the same set of packages we have for el6,
  and just do the minimum required changes to get them working on centos7.
  
  That probably means fixing some dependencies in the spec file, and some 
  changes for systemd support. 
  
  Note that all those changes are already done in Fedora 21 Xen rpms, for 
  example:
  ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/21/SRPMS/x/xen-4.4.1-12.fc21.src.rpm
  
  A few months ago I also saw a Xen 4.4 el7 rpms port, so we could find those 
  src.rpms aswell.
  
 
 Agreed on this too .. let's use as much the same as we can, and we can
 use %if statements in the SPEC to differentiate el6 and el7 things, if
 necessary.  systemd versus init and maybe some version number changes
 for buildrequires should be the changes we need to be concerned about.


Yep!
 
  
  And then there's the dom0 kernel.. Stock rhel7/centos7 is based on Linux 
  3.10 kernel,
  so we probably can use the exact same 3.10.63 kernel we have today for 
  CentOS 6 Xen.
 
 I agree that we can likely use the current centos-6 kernel.  We do need
 to decide when we want to shift the kernel to 3.14 .. the support for
 3.10 as a LTS kernel ends in September 2015 (so 9 months).
 
 https://www.kernel.org/category/releases.html
 
 We can try to take the RH 3.10 el7 kernel, mod it for xen, and use it ..
 or we can shift to 3.14.x and that buys us at least one more year .. or
 wait until they name the next LTS kernel and go for that.  Likely the
 next LTS kernel will be the easiest option (the RH modified kernel will
 not support xen and rolling in stuff externally will be hard because of
 the backports RH does to the kernel (things that go into a standard
 kernel will not apply cleanly to the RH kernel).
 
 But, I agree lets try to use the el6 kernel for xen el7 too .. and we
 can switch both kernels as required later.
 

Yeah we're not in a hurry with the dom0 kernel. Current Linux 3.10.x seems to 
work fine atm.

Let's focus on getting the current rpms built for el7,
and then later we can update both el6 and el7 to later kernel/versions.


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Xen 4.4 + libvirt 1.2 rpms test report with xl/libxl on CentOS 6

[Pasi Kärkkäinen]

Hello,

As discussed on the last Virt SIG meeting I promised to do some libvirt + libxl 
testing using the latest Xen 4.4 rpms.

Versions used:

xen-libs-4.4.1-5.el6.x86_64
xen-licenses-4.4.1-5.el6.x86_64
xen-hypervisor-4.4.1-5.el6.x86_64
xen-4.4.1-5.el6.x86_64
xen-runtime-4.4.1-5.el6.x86_64

kernel-3.10.63-11.el6.centos.alt.x86_64

libvirt-daemon-driver-nwfilter-1.2.10-3.el6.x86_64
libvirt-daemon-driver-xen-1.2.10-3.el6.x86_64
libvirt-daemon-driver-lxc-1.2.10-3.el6.x86_64
libvirt-daemon-1.2.10-3.el6.x86_64
libvirt-daemon-config-nwfilter-1.2.10-3.el6.x86_64
libvirt-daemon-driver-libxl-1.2.10-3.el6.x86_64
libvirt-daemon-driver-secret-1.2.10-3.el6.x86_64
libvirt-python-1.2.10-2.el6.x86_64
libvirt-daemon-driver-network-1.2.10-3.el6.x86_64
libvirt-daemon-config-network-1.2.10-3.el6.x86_64
libvirt-1.2.10-3.el6.x86_64
libvirt-client-1.2.10-3.el6.x86_64
libvirt-daemon-driver-interface-1.2.10-3.el6.x86_64
libvirt-daemon-driver-nodedev-1.2.10-3.el6.x86_64
libvirt-daemon-driver-qemu-1.2.10-3.el6.x86_64
libvirt-daemon-driver-storage-1.2.10-3.el6.x86_64

python-virtinst-0.600.0-25.el6.centos.alt.noarch


First I verified the baseline setup using xm/xend and libvirt:

- Install new PV domUs using virt-install, using LVM volumes.
- Install new PV domUs using virt-install, using file images (tap2).
- Install new PV domUs using virt-manager, using LVM volumes.
- Install new PV domUs using virt-manager, using file images (tap2).

And all that worked OK with xend, as we already know. tap2 backend was now 
automatically chosen for file images etc, all good.


Next I tried the same with xl/libxl. So I disabled xend with chkconfig xend 
off,
rebooted the server, and after the reboot verified xend is not running anymore.

And then I did the same PV domU installation tests as above.. and to my 
surprise it all worked out-of-the-box ! 
libvirt 1.2.10 seems to be happy with libxl aswell! Both virt-install and 
virt-manager worked OK for me for installing new guests,
and also for the basic lifecycle operations.


One difference compared to our earlier libvirt 0.x rpms is this:

# virsh version
Compiled against library: libvirt 1.2.10
Using library: libvirt 1.2.10
Using API: Xen 1.2.10
Running hypervisor: Xen 4.4.0

Now I get the same output from virsh version for both xm/xend and xl/libxl..
Earlier it would say Xen or xenlight on the Using API line depending 
which backend it was using.
I guess that has changed upstream, and both backends seem to work now anyway :)


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen 4.4.1 packages available on virt6-testing / libvirt blktap2 problems

[Pasi Kärkkäinen]

On Tue, Jan 06, 2015 at 12:15:25AM +0200, Pasi Kärkkäinen wrote:
 On Tue, Dec 16, 2014 at 10:29:53PM +0200, Pasi Kärkkäinen wrote:
   
   * xend is now disabled by default.  You can enable it by running
   chkconfig.  xend has been removed from the tree entirely in Xen 4.5,
   so this should (hopefully) serve as a wake-up-call for people to
   begin the transition over to xend.
   
   * A lot have things have changed -- please to test this so we can get
   a good idea what may have broken.
  
  
  I'll test soon. Thanks a lot!
  
 
 
 Ok I just used a couple of hours testing Xen 4.4.1 rpms on CentOS 6.6 with 
 Linux 3.10 dom0 kernel.
 This session was all about xm/xend testing. I manually enabled xend first. 
 
 
 What Works OK:
   - Manually creating/managing guests with xm and domU cfgfiles in 
 /etc/xen and LVM volumes as storage (phy backend).
   - Manually creating/managing guests with xm and domU cfgfiles in 
 /etc/xen and file images as storage (tap2:aio backend).
   - Using virt-install to install PV domUs using LVM volumes as storage 
 (phy backend).
   - Using virt-manager to install PV domUs using LVM volumes as storage 
 (phy backend).
 
 What doesn't work:
   - Using virt-manager to install PV domUs using file images as storage 
 (tap:aio backend).


Oh, and obviously virt-install fails aswell when trying to use file images, 
same problem as with virt-manager.

Here's the virt-install commandline example you can use for testing:

virt-install -d -n blktaptest01 -r 2048 --vcpus=2 --disk 
/var/lib/libvirt/images/blktaptest01.img,size=8 --vnc -p -b virbr0 -l 
http://ftp.funet.fi/pub/mirrors/centos.org/6.6/os/x86_64;


obviously you need to have a working libvirt-setup before running that command, 
and the libvirt/dnsmasq virbr0 bridge as created by libvirtd:

- yum install libvirt libvirt-daemon libvirt-daemon-network 
libvirt-driver-network libvirt-driver-xen virt-install virt-viewer virt-manager 
python-virtinst xorg-x11-xauth
- service xend restart
- service libvirtd restart


 
 This libvirt/blktap2 file images failure with Xen 4.4 rpms is a regression 
 from Xen 4.2 rpms, where blktap2 works OK with 
 libvirt/virt-install/virt-manager.
 
 The problem is most probably the fact that we had custom patches included in 
 the xen4c6 libvirt rpms that we shipped with the Xen 4.2 rpms. 
 We had to add two patches, one patch to fix the blktap2 backend type in 
 libvirt, and one patch to fix the blktap2 backend type in virt-install or 
 virt-manager, i'm not totally sure which one it was. Those patches should be 
 included in the earlier libvirt source rpms, so we can check there. Or I can 
 search thru my emails, because I hunted that down earlier aswell.
 
 It seems we still need those patches with the latest libvirt rpms too.
 
 The actual problem is libvirt/virt-manager tries to configure tap:aio: 
 backend, which won't work.
 It needs to be tap2:aio.
 
 I get the exactly same behaviour with xm/xend. tap:aio stalls and fails. 
 tap2:aio works OK.
 

Ok so digging into the email archives it seems earlier we patched 
python-virtinst src.rpm,
which seems to be the component used by both virt-install and virt-manager for 
new domain installations.

So we need to modify the virtinst/VirtualDisk.py file and change the:

DRIVER_TAP = tap

to

DRIVER_TAP = tap2

To change the default. 

After that change the libvirt generated domain xml looks like this, from both 
virt-install and virt-manager and works OK:

   disk type='file' device='disk'
  driver name='tap2' type='aio'/
  source file='/var/lib/libvirt/images/blktaptest01.img'/
  target dev='xvda' bus='xen'/
/disk


(virsh dumpxml domain)


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

[CentOS-virt] Xen4CentOS python-virtinst version issue, blktap2 problem

[Pasi Kärkkäinen]

Hello,

It seems currently when you yum update CentOS 6.6 Xen host you end up getting 
python-virtinst from c6 base repo:
python-virtinst-0.600.0-24.el6.noarch

and not from Xen4CentOS repo, because the version there is older: 0.600.0-19.

.. which means the centos/xen-specific patch in python-virtinst is lost. 
(default to tap2 instead of tap1, to make blktap2 work out-of-the-box with 
virt-install and virt-manager when using file based images as disks for VMs).

So.. who can build a new version of python-virtinst, with the blktap2 patch 
applied? 


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen4CentOS python-virtinst version issue, blktap2 problem

[Pasi Kärkkäinen]

On Tue, Jan 06, 2015 at 01:44:13PM -0600, Johnny Hughes wrote:
 On 01/06/2015 12:47 PM, Pasi Kärkkäinen wrote:
  On Tue, Jan 06, 2015 at 12:23:28PM -0600, Johnny Hughes wrote:
 
  I am doing a newer:
 
  1. kernel from kernel.org (3.10.63), also the e1000e kernel module for 
  that.
 
  2. libvirt rolling in the last patch in this tree:
  http://libvirt.org/git/?p=libvirt.git;a=shortlog;h=refs/heads/v0.10.2-maint
 
  3. newer xen-4.2.5 with all released XSAs  108 (including 116 .. but
  not 115 as it is not released)
 
  and that python-virtinstall
 
  I have already modified the the source code and I am building, I'll post
  when they are reading for testing.
 
 
  OK, the RPMS I am going to release are now in:
 
  http://people.centos.org/hughesjr/xen4-test/
 
  I am going to roll those into the main xen4 repo after some testing ..
  provide any feedback to this thread.
 
  With no negative feedback, this will likely go live tomorrow or Thursday
  if it works for the people who test it.
 
  
  Johnny: I tested the following:
  
  from http://people.centos.org/hughesjr/xen4-test/
  - kernel-3.10.63-11.el6.centos.alt.x86_64.rpm
  - python-virtinst-0.600.0-25.el6.centos.alt.noarch.rpm
  
  And they worked OK, no problems found!
  
  I'll try to get the latest Xen 4.2.5-38 and libvirt 0.10.2.8-9 rpms tested 
  soon aswell.
  
  
  -- Pasi
 
 I upgraded my current xen4centos test box with all the applicable
 packages in the link above and all my Xen VMs still start and run correctly.
 
 

Good to hear!


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen 4.4.1 packages available on virt6-testing / libvirt blktap2 problems

[Pasi Kärkkäinen]

On Tue, Jan 06, 2015 at 01:55:57PM -0600, Johnny Hughes wrote:
  
  Ok I just used a couple of hours testing Xen 4.4.1 rpms on CentOS 6.6 with 
  Linux 3.10 dom0 kernel.
  This session was all about xm/xend testing. I manually enabled xend first. 
  
  
  What Works OK:
  - Manually creating/managing guests with xm and domU cfgfiles in 
  /etc/xen and LVM volumes as storage (phy backend).
  - Manually creating/managing guests with xm and domU cfgfiles in 
  /etc/xen and file images as storage (tap2:aio backend).
  - Using virt-install to install PV domUs using LVM volumes as storage 
  (phy backend).
  - Using virt-manager to install PV domUs using LVM volumes as storage 
  (phy backend).
  
  What doesn't work:
  - Using virt-manager to install PV domUs using file images as storage 
  (tap:aio backend).
  
  
  This libvirt/blktap2 file images failure with Xen 4.4 rpms is a regression 
  from Xen 4.2 rpms, where blktap2 works OK with 
  libvirt/virt-install/virt-manager.
  
  The problem is most probably the fact that we had custom patches included 
  in the xen4c6 libvirt rpms that we shipped with the Xen 4.2 rpms. 
  We had to add two patches, one patch to fix the blktap2 backend type in 
  libvirt, and one patch to fix the blktap2 backend type in virt-install or 
  virt-manager, i'm not totally sure which one it was. Those patches should 
  be included in the earlier libvirt source rpms, so we can check there. Or I 
  can search thru my emails, because I hunted that down earlier aswell.
  
  It seems we still need those patches with the latest libvirt rpms too.
  
  The actual problem is libvirt/virt-manager tries to configure tap:aio: 
  backend, which won't work.
  It needs to be tap2:aio.
  
  I get the exactly same behaviour with xm/xend. tap:aio stalls and fails. 
  tap2:aio works OK.
  
 
 Now with the new python-virtinst and then new kernel from here:
 
 
 http://people.centos.org/hughesjr/xen4-test/
 
 But with the new libvirt-1.2 and xen 4.4 from this repo, everything
 seems to work with xend enabled.
 

Yep, with the updated python-virtinst all works now, also with the Xen 4.4 rpms.

Thanks a lot!

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen4CentOS python-virtinst version issue, blktap2 problem

[Pasi Kärkkäinen]

On Tue, Jan 06, 2015 at 12:23:28PM -0600, Johnny Hughes wrote:
  
  I am doing a newer:
  
  1. kernel from kernel.org (3.10.63), also the e1000e kernel module for that.
  
  2. libvirt rolling in the last patch in this tree:
  http://libvirt.org/git/?p=libvirt.git;a=shortlog;h=refs/heads/v0.10.2-maint
  
  3. newer xen-4.2.5 with all released XSAs  108 (including 116 .. but
  not 115 as it is not released)
  
  and that python-virtinstall
  
  I have already modified the the source code and I am building, I'll post
  when they are reading for testing.
  
 
 OK, the RPMS I am going to release are now in:
 
 http://people.centos.org/hughesjr/xen4-test/
 
 I am going to roll those into the main xen4 repo after some testing ..
 provide any feedback to this thread.
 
 With no negative feedback, this will likely go live tomorrow or Thursday
 if it works for the people who test it.
 

Johnny: I tested the following:

from http://people.centos.org/hughesjr/xen4-test/
- kernel-3.10.63-11.el6.centos.alt.x86_64.rpm
- python-virtinst-0.600.0-25.el6.centos.alt.noarch.rpm

And they worked OK, no problems found!

I'll try to get the latest Xen 4.2.5-38 and libvirt 0.10.2.8-9 rpms tested soon 
aswell.


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen4CentOS python-virtinst version issue, blktap2 problem

[Pasi Kärkkäinen]

On Tue, Jan 06, 2015 at 09:38:53AM -0500, Philippe-A. Lemelin wrote:
 
 
 On 15-01-06 09:21 AM, George Dunlap wrote:
 On Tue, Jan 6, 2015 at 11:42 AM, Pasi Kärkkäinen pa...@iki.fi wrote:
 Hello,
 
 It seems currently when you yum update CentOS 6.6 Xen host you end up 
 getting python-virtinst from c6 base repo:
 python-virtinst-0.600.0-24.el6.noarch
 
 and not from Xen4CentOS repo, because the version there is older: 
 0.600.0-19.
 
 .. which means the centos/xen-specific patch in python-virtinst is lost. 
 (default to tap2 instead of tap1, to make blktap2 work out-of-the-box with 
 virt-install and virt-manager when using file based images as disks for 
 VMs).
 
 So.. who can build a new version of python-virtinst, with the blktap2 patch 
 applied?
 
 Looks like Johnny's built an updated version and placed it here:
 
 http://people.centos.org/hughesjr/xen4-test/
 
 Maybe we can leave it there for a day or so for people to test it, and
 push it to the main xen4 repo at EOD tomorrow?
 
   -George
 
 
 I just successfully completed the installation of a CentOS guest
 with this version of python-virtinst.
 

Yep, it works for me too!


-- Pasi


 Thank you,
 
 Philippe-A. Lemelin
___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] CentOS 6 Xen 4.4.1 packages available on virt6-testing

[Pasi Kärkkäinen]

On Mon, Dec 15, 2014 at 06:24:36PM +, George Dunlap wrote:
 At long last, I've got some beta CentOS 6 4.4.1 packages up on the CBS.
 

Great!

 Major updates include:
 * Update to Xen 4.4.1. Also includes all XSAs through 114
 * Update to latest blktap 2.5
 * Updated libvirt packages (1.2.10), which work well with libxl
 
 To use, add the following to a file in /etc/yum.repos.d:
 
 [virt-testing]
 name=CentOS-$releasever - virt-testing
 baseurl=http://cbs.centos.org/repos/virt6-testing/$basearch/os/
 gpgcheck=0
 enabled=1
 
 Notes:
 * git repo with all the changes to xen can be found here:
  https://github.com/gwd/sig-virt-xen out/virt6/update-4.4.1-4
 
 * The signing infrastructure is not in place, so the binaries are not signed.
 
 * xend is now disabled by default.  You can enable it by running
 chkconfig.  xend has been removed from the tree entirely in Xen 4.5,
 so this should (hopefully) serve as a wake-up-call for people to
 begin the transition over to xend.
 
 * A lot have things have changed -- please to test this so we can get
 a good idea what may have broken.


I'll test soon. Thanks a lot!

Oh and sorry that I couldn't make it to the Virt SIG call today, I was 
busy/offline..

 
  -George


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Reminder: CentOS Virt SIG call today, 2pm GMT

[Pasi Kärkkäinen]

On Tue, Dec 02, 2014 at 12:07:11PM +, George Dunlap wrote:
 Just a reminder to everyone, we've got our bi-weekly Virt SIG meeting
 today.  It's on a phone bridge this time; e-mail me if you want the
 dial-in information.
 
 Lars, will you be hosting the call, or shall I?


Unfortunately I won't be able to make it to the call today.. sorry about that.


-- Pasi

 
  -George
 ___
 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] Xen4CentOS e1000e package

[Pasi Kärkkäinen]

On Tue, Oct 07, 2014 at 02:47:12PM -0500, Johnny Hughes wrote:
 On 10/07/2014 12:05 PM, George Dunlap wrote:
  KB and I were looking at repositories to import into git.centos.org
  recently, and we found the e1000e package -- a rebuild of the Intel
  e1000 driver for the x4c kernel.
  
  Does anyone know if this externally-build module is still necesssary
  for Linux 3.10?  Or for Linux 3.14, which we're planning on moving to
  at some point in the near future?
 
 It is required for some e1000e devices .. I started building it because
 several new Dell machines did not work with the driver in 3.4.x or
 3.10.x kernels.
 
 Not sure why, but there were issues and this solved them, so I would say
 it is required.
 
 There is also in kernel mods to get newer bn* drivers as well that is
 patched into the 3.10.x kernel as patches.
 

Yeah it sucks a bit that the drivers aren't really up-to-date in the latest 
upstream kernels, or the LTS kernels :(

Basing the x4c kernel on the el7 kernel would give all those driver updates and 
maintenance for free,
but the maintenance cost would be elsewhere, obviously..

I guess the x4c 3.14 kernel just needs to deal with certain amount of driver 
updates to keep the most common hardware working..


-- Pasi

 Thanks,
 Johnny Hughes
 
 

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Reminder: Phone meeting today / CentOS 7 Xen rpms

[Pasi Kärkkäinen]

On Tue, Sep 09, 2014 at 03:43:54PM +0100, George Dunlap wrote:
 
 - Someone has alraeady ported 4.4.1 to C7 -- may be useful as a head start
 

That was Pry Mar, added to CC. 
His .spec files and src.rpms for Xen 4.4 on Centos7 are here: 
http://www.tlviewer.org/xen/cent7/dom0/

Pry: Can you briefly tell about the status of your el7 xen rpms? Are they 
working good for you? They're originally based on Fedora Xen .spec files, right?



   -George


Thanks,

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen 4.4.1-rc1+ rebase

[Pasi Kärkkäinen]

On Mon, Aug 18, 2014 at 01:22:55PM -0500, Johnny Hughes wrote:
 On 08/18/2014 01:01 PM, Pasi Kärkkäinen wrote:
  On Mon, Aug 04, 2014 at 03:47:52PM -0400, George Dunlap wrote:
  On Mon, Jul 14, 2014 at 8:44 PM, Johnny Hughes jhug...@hughesjr.com 
  wrote:
  On 07/14/2014 08:07 AM, George Dunlap wrote:
  Johhny / KB -- Ping?
 
   -George
  Are we ready to try this build on our builders?
  I don't know?  :-)  I gave it a quick smoke-test (booted, started some
  guests).  That should have shaken out any really weird cases.  Is that
  good enough, or would you like further dev testing before putting it
  on the CentOS builders?
 
  Should we update the rpms to 4.4.1-rc2 ? 

 Well ... I do not know how to use George's git formating to produce
 patches .. so he would need to do that part.
 
 I can build something on the new CBS.centos.org though.  (Well, I have
 the required access ... still learning how to use it)
 
 

And now there's Xen 4.4.1 final available as well.. 

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen 4.4.1-rc1+ rebase

[Pasi Kärkkäinen]

On Mon, Aug 04, 2014 at 03:47:52PM -0400, George Dunlap wrote:
 On Mon, Jul 14, 2014 at 8:44 PM, Johnny Hughes jhug...@hughesjr.com wrote:
  On 07/14/2014 08:07 AM, George Dunlap wrote:
  Johhny / KB -- Ping?
 
   -George
 
  Are we ready to try this build on our builders?
 
 I don't know?  :-)  I gave it a quick smoke-test (booted, started some
 guests).  That should have shaken out any really weird cases.  Is that
 good enough, or would you like further dev testing before putting it
 on the CentOS builders?
 

Should we update the rpms to 4.4.1-rc2 ? 

  -George

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen 4.4.1-rc1+ rebase

[Pasi Kärkkäinen]

re-ping :)

-- Pasi

On Mon, Jul 14, 2014 at 02:07:13PM +0100, George Dunlap wrote:
 Johhny / KB -- Ping?
 
  -George
 
 On Mon, Jul 7, 2014 at 6:28 PM, George Dunlap dunl...@umich.edu wrote:
  On Mon, Jul 7, 2014 at 5:21 PM, George Dunlap dunl...@umich.edu wrote:
  I've got a first cut of the rebase here:
 
  git://github.com/gwd/sig-virt-xen out/update-4.4.1-rc1-ee81dda-RFC
 
  To build it, you'll need to download the polarssl tarball:
 
  http://xenbits.xen.org/xen-extfiles/polarssl-1.1.4-gpl.tgz
 
  And you'll need a tarball based on (unfortunately) a private tree,
  which you can find here:
 
  git://github.com/gwd/xen base/update-4.4.1-rc1-ee81dda-RFC
 
  This branch is based on upstream ee81dda (the current staging-4.4),
  with an additional two backported commits.
 
  To reproduce the tarball, checkout the above branch, then:
 
  ./configure
  make -C tools qemu-xen-dir-find
  make -C tools qemu-xen-traditional-find
  make src-tarball
 
  *sigh*  This is wrong.  It should be:
 
  tools/misc/mktarball $PWD
 
  If you do the above command, you'll end up with a release-looking
  tarball, rather than one with the git commit ID in the name.
 
  Also NB, two things:
 
  * The src-tarball build target (and the mktarball script) is not
  available in the normal 4.4 tree; it's a draft of a bit of
  functionality I'm in the process if pushing upstream.  It may or may
  not end up backported to 4.4.1.
  * If you've already cloned the qemu trees, you need to run make -C
  tools qemu-xen-dir-force-update instead.
 
   -George
 ___
 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] Xen PV domU reported as Xen-HVM

[Pasi Kärkkäinen]

On Thu, Jul 03, 2014 at 11:42:25AM -0400, Karl Johnson wrote:
 
Thanks for the reply George. Is there any other easy way in the domU to
know if it's a pv or hvm with Xen 4.2+ and the right hardware?
 

Did you try dmidecode? 


-- Pasi

Karl
 

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Virt SIG roadmap

[Pasi Kärkkäinen]

On Tue, Apr 22, 2014 at 05:23:57PM +0100, George Dunlap wrote:
 On Tue, Apr 15, 2014 at 5:53 PM, George Dunlap dunl...@umich.edu wrote:
  As promised, in preparation for next week's SIG meeting, here's a
  kick-off discussion about the Virtualization SIG roadmap.
 
  I'm mainly tossing out ideas here -- see this is an invitation to
  discussion.
 
  Key things I think should be on the roadmap:
 
  * Release process
   - General cadence
   - Estimate of the next release (if any)
  * Specification of targets
   - Right now, mainly xen4centos
  - What packages?
  * Backlog of work items
   - Updates (mostly suggested by Pasi)
   - Items caveats from Russ P's CentOS talk
 
  == Release process ==
 
  I don't have any real opinions on this -- KB / Johnny, did you guys
  have a vision for what the release schedule for any of the SIGs would
  look like?  Are we going to have specific releases, or just continue
  to do rolling updates?  If so, how frequent should the updates be?
 
  Obviously estimates for releases will need to wait until all the
  infrastructure has been set up, and we've discussed cadence / targets,
  c.
 
  == Targets ==
 
  Targets will depend on community support.  I'll be committing to
  extending the Xen4CentOS project.  There was talk of having an OpenVZ
  variant, but that would require someone to actually step up and do the
  work to integrate and support it.
 
  == Backlog ==
 
  Most of the items below are from the discussion Pasi started in
  February; a couple are from Russ Pavliczek's slides at a talk given
  recently.
 
  * Pull in updates f/ XenServer
Suggested by dvrabel in http://marc.info/?l=centos-virtm=139289353315469
   - 0001-x86-xen-rename-early_p2m_alloc-and-early_p2m_alloc_m.patch
   - 0008-x86-remove-the-Xen-specific-_PAGE_IOMAP-PTE-flag.patch
   -  0160676bba69523e8b0ac83f306cce7d342ed7c8 (xen/p2m: check MFN is in range
  before using the m2p table)
   - 7cde9b27e7b3a2e09d647bb4f6d94e842698d2d5 (xen: Fix possible user space
  selector corruption)
  * Xen 4.4 (Xen + qemu)
  * libvirt: 1.2.2
   - Possibly with migration / pci pass-through back-ported?
  * dom0 / xen serial console
  * Ballooning bug?
http://bugs.centos.org/view.php?id=6893
  * UEFI?
 
 
  Anything else we need to discuss / plan?
 
 At our bi-weekly meeting today, we talked about what the general
 approach to releases has been.
 

Sorry I couldn't make it to the meeting!

 For Xen, major updates to packages will happen when the upstream
 releases.  The plan at the moment is to do this every other release;
 so we would update to 4.4, but probably not update again until 4.5.
 
 Between those times, we will generaly be pulling in bug fixes by
 consuming point releases when they happen.  Security updates will of
 course be pushed out immediately, as will bugs that affect a
 significant number of users.
 
 We didn't discuss this, but I would expect that libvirt might be similar to 
 Xen.
 
 For Linux, the plan is to consume one of the LTS kernels.  At the
 moment, that's 3.10.  In general, the plan is to update to a new LTS
 kernel every 2 years.  However, whenever there is a major release (for
 example, with RHEL 7 coming out soon), we may consider moving to a
 newer kernel for CentOS 6 sooner, so that the Virt SIG can maintain
 only a single kernel version across all CentOS releases.
 

Makes sense. RHEL7 (rc) seems to be based on 3.10.x aswell:

http://ftp.redhat.com/redhat/rhel/rc/7/Server/x86_64/os/Packages/

 The initial target for the Virt SIG will be to update the packages
 inherited from xen4centos to Xen 4.4 and libvirt 1.2.2.
 

RHEL7 (rc) is based on libvirt-1.1.1. 

It would be nice to share the same base version as el7 does,
but I guess the recent libvirt/Xen/libxl work by Jim is only in libvirt 1.2.x ? 


 We're currently in the process of brainstorming a backlog of work
 items that might be a good idea.  Some things we've come up with so
 far:
 
 * CentOS 7 testing branch
 
 * Making a useful Xen CD image
  - Live CD?
  - With pre-made CentOS guest images?
  - Ready to be set up as an OpenStack node?
 
 * Getting some kind of automated testing infrastructure set up
 
 KB / Lars / Johnny, anything I missed / didn't get quite right?
 
  -George


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Wed, Mar 12, 2014 at 05:18:57AM -0500, Johnny Hughes wrote:
 On 03/11/2014 03:05 AM, Pasi Kärkkäinen wrote:
  On Tue, Mar 11, 2014 at 10:01:28AM +0200, Pasi Kärkkäinen wrote:
  I should be back home and ready to go by Tuesday morning though ... so
  if I don't get time to do it at SCALE, I will on Tuesday.
 
  Ok so Xen 4.2.4 and Linux 3.10.32 dom0 kernel are out in the xen4centos 
  repo now.
  Also upstream released Xen 4.4.0 today.
 
  In general Xen upstream supports live migrations from (current-1) to 
  (current) version.
  So if we want to provide a (live) migration path from Xen 4.2.* to 4.4.* 
  we probably
  should package Xen 4.3.2 first.. So people could migrate from 4.2.4 - 
  4.3.2 - 4.4.0.
 
  What do you think? 
 
  (Fedora 20 has Xen 4.3.2 rpms in the updates repo, for .spec foo, if 
  needed).
 
  Well, I would hope we can migrate from 4.2.4 to 4.4.x without requiring
  anything in between.  Not sure if that would be possible or not.
 
  Well I guess we just need to test that.. 
 
  We do need to start trying to do 4.4.x builds.
 
  That's what we should do :)
 
  Fedora has rpms at least for 4.4.0-rc4, not sure about the rc5/rc6 or the 
  final.. 
  but I don't think the .spec file really needs to change between rc4 and 
  the final.
 
  Information for task build (f20, xen-4.4.0-0.rc4.1.fc20.src.rpm):
  http://koji.fedoraproject.org/koji/taskinfo?taskID=6540303
 
  http://kojipkgs.fedoraproject.org//work/tasks/304/6540304/xen-4.4.0-0.rc4.1.fc20.src.rpm
 
 I get a forbidden on that SRPM ... do you have a copy somewhere?
 

Yep, here goes: 
http://pasik.reaktio.net/fedora/xen/xen-4.4.0-0.rc4.1.fc20.src.rpm

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Tue, Mar 11, 2014 at 10:01:28AM +0200, Pasi Kärkkäinen wrote:
  
   I should be back home and ready to go by Tuesday morning though ... so
   if I don't get time to do it at SCALE, I will on Tuesday.
  
   Ok so Xen 4.2.4 and Linux 3.10.32 dom0 kernel are out in the xen4centos 
   repo now.
   Also upstream released Xen 4.4.0 today.
  
   In general Xen upstream supports live migrations from (current-1) to 
   (current) version.
   So if we want to provide a (live) migration path from Xen 4.2.* to 4.4.* 
   we probably
   should package Xen 4.3.2 first.. So people could migrate from 4.2.4 - 
   4.3.2 - 4.4.0.
  
   What do you think? 
  
   (Fedora 20 has Xen 4.3.2 rpms in the updates repo, for .spec foo, if 
   needed).
  
  
  Well, I would hope we can migrate from 4.2.4 to 4.4.x without requiring
  anything in between.  Not sure if that would be possible or not.
  
 
 Well I guess we just need to test that.. 
 
  We do need to start trying to do 4.4.x builds.
  
 
 That's what we should do :)
 
 Fedora has rpms at least for 4.4.0-rc4, not sure about the rc5/rc6 or the 
 final.. 
 but I don't think the .spec file really needs to change between rc4 and the 
 final.
 

Information for task build (f20, xen-4.4.0-0.rc4.1.fc20.src.rpm):
http://koji.fedoraproject.org/koji/taskinfo?taskID=6540303

http://kojipkgs.fedoraproject.org//work/tasks/304/6540304/xen-4.4.0-0.rc4.1.fc20.src.rpm

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Thu, Feb 20, 2014 at 10:26:04AM -0600, Johnny Hughes wrote:
 
  2) After that, we should start packaging/testing Xen 4.3.2:
 http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html
 
 Xen 4.3 brings much improved XL toolstack in addition to a lot of 
  other changes/fixes.
  my understanding was that we might skip 4.3, and rebase from 4.2 to 4.4
  once that hits the released path
  I am OK with either path, although my understanding is 4.2 = 4.4 as well.
 
  Yep. Let's see when Xen 4.4 gets released.
 
  Shall we start with the first step, which is upgrading to Xen 4.2.4? :)
 
 
 I am getting ready to shutdown my machine and pack it up to head out for
 the airport right now, to go to Scale12x:
 
 http://www.socallinuxexpo.org/scale12x
 
 I should be back home and ready to go by Tuesday morning though ... so
 if I don't get time to do it at SCALE, I will on Tuesday.
 

Ok so Xen 4.2.4 and Linux 3.10.32 dom0 kernel are out in the xen4centos repo 
now.
Also upstream released Xen 4.4.0 today.

In general Xen upstream supports live migrations from (current-1) to (current) 
version.
So if we want to provide a (live) migration path from Xen 4.2.* to 4.4.* we 
probably
should package Xen 4.3.2 first.. So people could migrate from 4.2.4 - 4.3.2 - 
4.4.0.

What do you think? 

(Fedora 20 has Xen 4.3.2 rpms in the updates repo, for .spec foo, if needed).

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Fwd: Xen4CentOS kernel panic on dom0 reboot

[Pasi Kärkkäinen]

On Sat, Mar 08, 2014 at 09:09:07AM -0600, PJ Welsh wrote:
No, I have not followed those instructions yet. These were production
servers that I had scheduled firmware updates late Sunday evening. The
first time I though the error was a fluke and only began to research it
after the second failure (and still no firmware updates due to the
power-cycle). I may try to sneak in a restart of one of the systems late
Sunday night US CT.
 

OK.

Still not sure why the running vm's would stop the reboot... The server
shows that it was suppose to be restarting. I have had a similar stuck on
restarting message (minus all the umount errors) on some Dell T105's
running CentOS 6.5 and the reboot=pci grub.conf kernel option is what
ended up working for them. I have not tested that possible option yet,
either since that would take 2 reboots to put into place.
 

Yeah, it's worth testing both, to figure out what's wrong.


-- Pasi

On Fri, Mar 7, 2014 at 10:43 PM, Pasi Kärkkäinen [1]pa...@iki.fi wrote:
 
  On Thu, Mar 06, 2014 at 01:54:22PM -0600, Phillippe Welsh wrote:
  
   Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot
  
   On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel david.vrabel at
  [2]citrix.comwrote:
  
 On 05/03/14 15:09, Karl Johnson wrote:
  I've been using Xen4CentOS for the last 3 months. It's working
  fine and
  dom0/domUs are stable but the server does a kernel panic when
  doing a
  reboot and the server has to be hard reset manually. It has
  kernel panic
 on the 3 last reboot.

 There is a xenbus device still present and during shutdown it is
  trying
 to set it to CLOSED but at this point xenstored isn't running and
  the
 xenbus write stalls.

 Do you have VMs that are still running when you attempt a reboot?
   If so
 shutting them down will likely avoid this.

 Can you provide the output of xenstore-ls prior to attempting a
  reboot?



I though Xen init.d scripts would stop all of them before rebooting?
  Here's
the output of chkconfig and xenstore-ls:
   
[3]http://pastebin.centos.org/8186/
   
Thanks,
   
Karl
  
   I've got the me-too on the reboot hang issue for 2 different Dell
  R710's with xen-4.2.4-29.el6 and at least the kernels
  kernel-[4]3.10.25-11.el6.centos.alt.x86_64 and
  kernel-3.10.23-11.el6.centos.alt.x86_64. I have not tried to reboot with
  the latest kernel-3.10.32-11.el6.centos.alt.x86_64 (if kernel even makes
  a difference). I *have* had dom0_mem=1024M,max:1024M option in place for
  all of them with only 6 VM's.
  
   Any new suggestions?
  
 
  So did you make sure all the VMs are shut down before trying to reboot
  dom0?
 
  -- Pasi
 
  ___
  CentOS-virt mailing list
  [5]CentOS-virt@centos.org
  [6]http://lists.centos.org/mailman/listinfo/centos-virt
 
 References
 
Visible links
1. mailto:pa...@iki.fi
2. http://citrix.com/
3. http://pastebin.centos.org/8186/
4. file:///tmp/tel:3.10.25-11
5. mailto:CentOS-virt@centos.org
6. 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] Fwd: Xen4CentOS kernel panic on dom0 reboot

[Pasi Kärkkäinen]

On Thu, Mar 06, 2014 at 01:54:22PM -0600, Phillippe Welsh wrote:
 
 Subject: Re: [CentOS-virt] Xen4CentOS kernel panic on dom0 reboot
 
 On Wed, Mar 5, 2014 at 10:17 AM, David Vrabel david.vrabel at 
 citrix.comwrote:
 
   On 05/03/14 15:09, Karl Johnson wrote:
I've been using Xen4CentOS for the last 3 months. It's working fine and
dom0/domUs are stable but the server does a kernel panic when doing a
reboot and the server has to be hard reset manually. It has kernel panic
   on the 3 last reboot.
  
   There is a xenbus device still present and during shutdown it is trying
   to set it to CLOSED but at this point xenstored isn't running and the
   xenbus write stalls.
  
   Do you have VMs that are still running when you attempt a reboot?  If so
   shutting them down will likely avoid this.
  
   Can you provide the output of xenstore-ls prior to attempting a reboot?
  
  
  
  I though Xen init.d scripts would stop all of them before rebooting? Here's
  the output of chkconfig and xenstore-ls:
  
  http://pastebin.centos.org/8186/
  
  Thanks,
  
  Karl
 
 I've got the me-too on the reboot hang issue for 2 different Dell R710's 
 with xen-4.2.4-29.el6 and at least the kernels 
 kernel-3.10.25-11.el6.centos.alt.x86_64 and 
 kernel-3.10.23-11.el6.centos.alt.x86_64. I have not tried to reboot with the 
 latest kernel-3.10.32-11.el6.centos.alt.x86_64 (if kernel even makes a 
 difference). I *have* had dom0_mem=1024M,max:1024M option in place for all of 
 them with only 6 VM's.
 
 Any new suggestions?
 

So did you make sure all the VMs are shut down before trying to reboot dom0? 

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen4CentOS installation strangeness

[Pasi Kärkkäinen]

On Tue, Mar 04, 2014 at 02:50:40PM +0200, Peter Peltonen wrote:
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
[1]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?


No idea really.. but what you should do is to enable/configure a serial console,
probably by using the IPMI SOL, so you can capture and log all the Xen and dom0 
kernel
boot messages.. 

So we can hopefully *see* what the issue is, and not have to guess :)

-- Pasi

Regards,
Peter
 

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Sat, Feb 22, 2014 at 06:10:41AM -0800, Johnny Hughes wrote:
 On 02/19/2014 03:51 AM, David Vrabel wrote:
  On 18/02/14 20:54, Pasi Kärkkäinen wrote:
  On Tue, Feb 18, 2014 at 07:19:07PM +, Karanbir Singh wrote:
  On 02/18/2014 04:43 PM, Pasi Kärkkäinen wrote:
  Hello,
 
  A couple of TODO items/suggestions:
 
  1) Xen 4.2.4 was just released:
 http://lists.xen.org/archives/html/xen-devel/2014-02/msg01624.html
 
 I think we should first update Xen4Centos6 rpms to Xen 4.2.4 
 to have a known good release from the stable branch currently in 
  use in Xen4Centos6.
 
 
  2) After that, we should start packaging/testing Xen 4.3.2:
 http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html
 
 Xen 4.3 brings much improved XL toolstack in addition to a lot of 
  other changes/fixes.
 
  my understanding was that we might skip 4.3, and rebase from 4.2 to 4.4
  once that hits the released path
 
  Hmm, I'm not sure if skipping 4.3 is a good idea.. 
 
  I believe the following distros/products are (or will be) shipping Xen 4.3:
 
  - Next version of XenServer
  We have been testing the 4.4 RCs in XenServer and it is likely that we
  will switch to using 4.4 soon after its release.
 
 
 David,
 
 Is this the proper qemu-xen snapshot to use for xen-4.2.4 ?
 
 http://xenbits.xen.org/gitweb/?p=qemu-upstream-4.2-testing.git;a=commit;h=6d17c397dfadb29e641d5da1eb3381d240decedc
 

It seems to have the qemu-xen-4.2.4 tag, so yes, it's the one.
You can also always fetch the xen 4.2.4 tarball and compare to it (it includes 
the qemu bits aswell).


 Do we need any other patches in that?
 

Not that i'm aware of.. did we have any extra qemu patches on top of 4.2.3 ? 


 Also, we are currently using
 blktap-9960138790b9d3610b12acd153bba20235efa4f5.tar.gz .. is that still
 the best version to use?
 

David has to answer that..


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Sat, Feb 22, 2014 at 05:32:56PM +0200, Pasi Kärkkäinen wrote:
  
  David,
  
  Is this the proper qemu-xen snapshot to use for xen-4.2.4 ?
  
  http://xenbits.xen.org/gitweb/?p=qemu-upstream-4.2-testing.git;a=commit;h=6d17c397dfadb29e641d5da1eb3381d240decedc
  
 
 It seems to have the qemu-xen-4.2.4 tag, so yes, it's the one.
 You can also always fetch the xen 4.2.4 tarball and compare to it (it 
 includes the qemu bits aswell).
 

And the Xen qemu-dm (traditional) is here:
http://xenbits.xen.org/gitweb/?p=qemu-xen-4.2-testing.git;a=commit;h=8d7e96f625c4a58d721db413b032fd0bb5671b96

I don't think qemu-upstream is really in good shape in Xen 4.2.x, so it's 
mostly the qemu-dm traditional that people will use with Xen 4.2.x.


-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Sat, Feb 22, 2014 at 07:37:42AM -0800, Johnny Hughes wrote:
 On 02/22/2014 07:35 AM, Pasi Kärkkäinen wrote:
  On Sat, Feb 22, 2014 at 05:32:56PM +0200, Pasi Kärkkäinen wrote:
  David,
 
  Is this the proper qemu-xen snapshot to use for xen-4.2.4 ?
 
  http://xenbits.xen.org/gitweb/?p=qemu-upstream-4.2-testing.git;a=commit;h=6d17c397dfadb29e641d5da1eb3381d240decedc
 
  It seems to have the qemu-xen-4.2.4 tag, so yes, it's the one.
  You can also always fetch the xen 4.2.4 tarball and compare to it (it 
  includes the qemu bits aswell).
 
  And the Xen qemu-dm (traditional) is here:
  http://xenbits.xen.org/gitweb/?p=qemu-xen-4.2-testing.git;a=commit;h=8d7e96f625c4a58d721db413b032fd0bb5671b96
 
  I don't think qemu-upstream is really in good shape in Xen 4.2.x, so it's 
  mostly the qemu-dm traditional that people will use with Xen 4.2.x.
 
 
  -- Pasi
 
 We have been using the upstream one in the previous builds ... not sure
 why, its just in my notes as the one to use :)
 

Hmm, the normal Xen source build builds and installs both the qemu traditional 
and the upstream one..

Maybe I should read the el6 spec file :)

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Thu, Feb 20, 2014 at 11:02:17AM +0200, Pasi Kärkkäinen wrote:
 On Wed, Feb 19, 2014 at 11:51:40AM +, David Vrabel wrote:
  On 18/02/14 20:54, Pasi Kärkkäinen wrote:
   On Tue, Feb 18, 2014 at 07:19:07PM +, Karanbir Singh wrote:
   On 02/18/2014 04:43 PM, Pasi Kärkkäinen wrote:
   Hello,
  
   A couple of TODO items/suggestions:
  
   1) Xen 4.2.4 was just released:
  http://lists.xen.org/archives/html/xen-devel/2014-02/msg01624.html
  
  I think we should first update Xen4Centos6 rpms to Xen 4.2.4 
  to have a known good release from the stable branch currently in 
   use in Xen4Centos6.
  
  
   2) After that, we should start packaging/testing Xen 4.3.2:
  http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html
  
  Xen 4.3 brings much improved XL toolstack in addition to a lot of 
   other changes/fixes.
  
  
   my understanding was that we might skip 4.3, and rebase from 4.2 to 4.4
   once that hits the released path
  
   
   Hmm, I'm not sure if skipping 4.3 is a good idea.. 
   
   I believe the following distros/products are (or will be) shipping Xen 
   4.3:
   
   - Next version of XenServer
  
  We have been testing the 4.4 RCs in XenServer and it is likely that we
  will switch to using 4.4 soon after its release.
  
 
 That's good to know.
 

Oh, another question.. are there any important not-yet-upstream patches in the 
XS dom0 kernel queue for Linux 3.10? 

We should probably update the xen4centos6 linux 3.10 dom0 kernel rpms aswell.

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Thu, Feb 20, 2014 at 10:51:57AM +, David Vrabel wrote:
 On 20/02/14 09:04, Pasi Kärkkäinen wrote:
  
  Oh, another question.. are there any important not-yet-upstream
  patches in the XS dom0 kernel queue for Linux 3.10?
 
 You can view the current XenServer patch queue at:
 
 https://github.com/xenserver/linux-3.x.pg
 
 There are only two things I would recommend taking but they're not ready
 yet.
 
 1. Fix for high MMIO regions.
 
 0001-x86-xen-rename-early_p2m_alloc-and-early_p2m_alloc_m.patch
 ...
 0008-x86-remove-the-Xen-specific-_PAGE_IOMAP-PTE-flag.patch
 
 These require more testing.
 

OK.

 2. Preemptible privcmd hypercalls.
 
 The current set of patches is broken and the fixed version is not ready yet.
 

OK.

So we need to wait a bit with those.. 


 I also note two fixes for 32-bit guests were not tagged for stable. I
 have now asked for these to be added to the stable trees.  These are:
 
 0160676bba69523e8b0ac83f306cce7d342ed7c8 (xen/p2m: check MFN is in range
 before using the m2p table)
 
 7cde9b27e7b3a2e09d647bb4f6d94e842698d2d5 (xen: Fix possible user space
 selector corruption)
 

Thanks a lot!

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] Xen updates / TODO

[Pasi Kärkkäinen]

On Tue, Feb 18, 2014 at 02:55:12PM -0600, Johnny Hughes wrote:
 On 02/18/2014 01:19 PM, Karanbir Singh wrote:
  On 02/18/2014 04:43 PM, Pasi Kärkkäinen wrote:
  Hello,
 
  A couple of TODO items/suggestions:
 
  1) Xen 4.2.4 was just released:
 http://lists.xen.org/archives/html/xen-devel/2014-02/msg01624.html
 
 I think we should first update Xen4Centos6 rpms to Xen 4.2.4 
 to have a known good release from the stable branch currently in use 
  in Xen4Centos6.
 
 
  2) After that, we should start packaging/testing Xen 4.3.2:
 http://lists.xen.org/archives/html/xen-devel/2014-02/msg01622.html
 
 Xen 4.3 brings much improved XL toolstack in addition to a lot of other 
  changes/fixes.
 
  my understanding was that we might skip 4.3, and rebase from 4.2 to 4.4
  once that hits the released path
 
 I am OK with either path, although my understanding is 4.2 = 4.4 as well.
 

Yep. Let's see when Xen 4.4 gets released.

Shall we start with the first step, which is upgrading to Xen 4.2.4? :)



 
 
  3) After updating to Xen 4.3.2 rpms start troubleshooting/debugging the 
  libvirt libxl driver
 and get it working with Xen4Centos6 system..
  I believe Dario Faggioli has some of this ironed out already. Dario are
  you on the centos-virt list ?
 
 WRT the libvirt, libxl issues (and other libvirt things as well) ... I
 am fairly sure both OpenShift Origin and RDO are going to need a newer
 version of libvirt ... maybe we should start testing to try and get a
 newer version of libvirt in this stack as well (and use the same version
 on all 3 projects).
 
 The current version of libvirt is close enough to the main CentOS
 version that virt-manager and other pieces of the current main stack
 works .. a newer libvirt will likely also mean recompiling or newer
 versions of other pieces as well.
 

Yeah.. I think the latest upstream libvirt libxl driver requires some libxl 
fixes which are only in Xen 4.4.

-- Pasi

___
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt