Re: [Xen-users] XENBUS timeout connecting to device (Hard disks not detected)

["Philippe-A. Lemelin" <philippe.lemelin@xxxxxxxxxxxx>]

On 15-01-05 11:34 AM, George Dunlap wrote:
> On 01/05/2015 04:15 PM, Philippe-A. Lemelin wrote:
> > On 15-01-05 10:33 AM, Ian Campbell wrote:
> > > George, is blktap expected to work with the xen4centos (6) packages?
> > >
> > > (not trimming quotes for George's benefit)
> > >
> > > I wonder if tap vs. tap2 is a xend vs xl thing.
> > This is not the first installation of Xen we did but it is the first
> > time we have seen this behavior (see lower in this email, forcing tap2
> > solved the installation issue). We currently have 4 Dom0 running the
> > same hardware/OS but installed at different time in the last 6 months.
> > The installation is a manual process but respects the same written
> > procedure each time so there must have been a change in CentOS packages
> > somewhere at the end of November or the beginning of December. We are
> > still trying to figure what the difference is.
> Well the x4c packages have been getting minor updates fairly regularly.
>   What versions are installed on the working hosts?
>
> It's possible that one of the fixes backported to 4.2.5 actually broke
> something in xend and nobody noticed...
>
>   -George
That was my main issue, every hosts are running the same versions but 
the ones that have been shipped had not seen any installations of new 
guests since.
I requested access to one of the production host and tested installing a 
new guest and it could not detect the hard disks in the installer (all 
the other guest have their disks device set to tap2 and the new test 
installation has it set to tap). Uptime on this host is 54 days and it 
was last updated on Dec 15 (yum upgrade).
[root@host ~]# rpm -qa | grep -i -e xen -e libvirt
xen-libs-4.2.5-37.el6.centos.alt.x86_64
xen-runtime-4.2.5-37.el6.centos.alt.x86_64
libvirt-daemon-driver-qemu-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-config-network-0.10.2.8-8.el6.centos.alt.x86_64
centos-release-xen-6-4.el6.centos.x86_64
xen-4.2.5-37.el6.centos.alt.x86_64
libvirt-client-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-nwfilter-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-xen-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-nodedev-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-network-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-lxc-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-interface-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-storage-0.10.2.8-8.el6.centos.alt.x86_64
xen-licenses-4.2.5-37.el6.centos.alt.x86_64
libvirt-daemon-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-libxl-0.10.2.8-8.el6.centos.alt.x86_64
xen-hypervisor-4.2.5-37.el6.centos.alt.x86_64
libvirt-daemon-config-nwfilter-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-python-0.10.2.8-8.el6.centos.alt.x86_64
libvirt-daemon-driver-secret-0.10.2.8-8.el6.centos.alt.x86_64


I simply use virt-manager this time and did the simplest installation, 
selecting all the default values and using the Centos 6 mirrors for the 
packages.
At first I thought we had made some errors in the host installation but 
seeing that my production hosts are showing the same behavior, I guess 
something is indeed broken.
Would this be an issue with libvirt or xen ?

Best regards,

Philippe-A. Lemelin

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users