Hi,
I''m currently trying to install xapi on debian (unstable), following
the
following wiki page:
http://wiki.xensource.com/xenwiki/XAPI_on_debian
1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess
it wont work with 64-bit as the xapi *.deb files are for 32).
note: you must leave an unused 1mb partition somewhere when
creating your partitions or grub2 used in sid will complain
during the dist-upgrade. This will result into an unbootable
system. (at least it happened to me)
2. Edit sources.list to use unstable instead of squeeze
box# apt-get update
box# apt-get dist-upgrade
3. Add experimental sources, like in the following sources.list
----8<----------
deb http://mirror.switch.ch/ftp/mirror/debian/ unstable main non-free
contrib
deb-src http://mirror.switch.ch/ftp/mirror/debian/ unstable main
non-free contrib
deb http://mirror.switch.ch/ftp/mirror/debian/ experimental main
non-free contrib
deb-src http://mirror.switch.ch/ftp/mirror/debian/ experimental main
non-free contrib
----------->8---
4. apt-get install xen-hypervisor-4.1-amd64 linux-image-3.0.0-rc6-686-pae
5. apt-get install dkms linux-headers-3.0.0-rc6-686-pae stunnel hwdata
uuid-runtime
6. Download the debs from http://downloads.xen.org/XCP/debian/
box# wget http://downloads.xen.org/XCP/debian/blktap-dkms_0.1_all.deb
box# wget http://downloads.xen.org/XCP/debian/blktap_0.1-1_i386.deb
box# wget http://downloads.xen.org/XCP/debian/fe_0.1-1_i386.deb
box# wget http://downloads.xen.org/XCP/debian/squeezed_0.1-1_i386.deb
box# wget http://downloads.xen.org/XCP/debian/v6d_0.1-1_i386.deb
box# wget http://downloads.xen.org/XCP/debian/xapi_0.1-1_i386.deb
box# wget http://downloads.xen.org/XCP/debian/xen-sm_0.1-1_i386.deb
6b. Install the packages (that''s where it fails at the moment)
box# dpkg -i *deb
----8<----------
Selecting previously deselected package blktap.
(Reading database ... 37780 files and directories currently installed.)
Unpacking blktap (from blktap_0.1-1_i386.deb) ...
Selecting previously deselected package blktap-dkms.
Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ...
Selecting previously deselected package fe.
Unpacking fe (from fe_0.1-1_i386.deb) ...
Selecting previously deselected package squeezed.
Unpacking squeezed (from squeezed_0.1-1_i386.deb) ...
Selecting previously deselected package v6d.
Unpacking v6d (from v6d_0.1-1_i386.deb) ...
Selecting previously deselected package xapi.
Unpacking xapi (from xapi_0.1-1_i386.deb) ...
Selecting previously deselected package xen-sm.
Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ...
Setting up blktap (0.1-1) ...
Setting up blktap-dkms (0.1) ...
dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified
for record #0.
Error! Bad conf file.
File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf
does not represent a valid dkms.conf file.
Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz.
Common causes include:
- You must be using DKMS 2.1.0.0 or later to support binaries only
distribution specific archives.
- Corrupt distribution specific archive
dpkg: error processing blktap-dkms (--install):
subprocess installed post-installation script returned error exit status 2
Setting up fe (0.1-1) ...
Setting up squeezed (0.1-1) ...
Setting up v6d (0.1-1) ...
Setting up xapi (0.1-1) ...
Setting up xen-sm (0.1-1) ...
Processing triggers for python-support ...
Errors were encountered while processing:
blktap-dkms
----------->8---
Seems to be a version mismatch thing occuring here. I manually unpacked the
/usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz to check it was not corrupt:
----8<----------
./dkms_binaries_only/
./dkms_binaries_only/PACKAGE_NAME
./dkms_binaries_only/PACKAGE_VERSION
./dkms_binaries_only/dkms.conf
./dkms_main_tree/
./dkms_main_tree/dkms_dbversion
./dkms_main_tree/2.6.39-2-686-pae/
./dkms_main_tree/2.6.39-2-686-pae/i686/
./dkms_main_tree/2.6.39-2-686-pae/i686/module/
./dkms_main_tree/2.6.39-2-686-pae/i686/module/blktap.ko
./dkms_main_tree/2.6.39-2-686-pae/i686/log/
./dkms_main_tree/2.6.39-2-686-pae/i686/log/make.log
----------->8---
I''m noticing it''s talking about 2.6.39-2-686-pae kernel, but
here we use
3.0.0-rc6-686-pae.
Is the package outdated ?
Thanks in advance for your help.
Sébastien
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2011/7/17 Sébastien RICCIO <sr@swisscenter.com>:> Setting up blktap-dkms (0.1) ... > dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. > Error! Bad conf file.This looks like the fatal error.> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf > does not represent a valid dkms.conf file. > > > Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. > Common causes include: > - You must be using DKMS 2.1.0.0 or later to support binaries only > distribution specific archives.What version of dkms do you have installed? (dkms --version) what is the output of the following: var/lib/dkms/blktap/0.1/build/make.log try following the README in /var/lib/dkms/blktap/0.1/build There may be some build dependencies missing on your end.> - Corrupt distribution specific archive > > > dpkg: error processing blktap-dkms (--install): > subprocess installed post-installation script returned error exit status 2 > Setting up fe (0.1-1) ... > Setting up squeezed (0.1-1) ... > Setting up v6d (0.1-1) ... > Setting up xapi (0.1-1) ... > Setting up xen-sm (0.1-1) ... > Processing triggers for python-support ... > Errors were encountered while processing: > blktap-dkms > ----------->8--- > > > Seems to be a version mismatch thing occuring here. I manually unpacked the > /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz to check it was not corrupt: > > ----8<---------- > ./dkms_binaries_only/ > ./dkms_binaries_only/PACKAGE_NAME > ./dkms_binaries_only/PACKAGE_VERSION > ./dkms_binaries_only/dkms.conf > ./dkms_main_tree/ > ./dkms_main_tree/dkms_dbversion > ./dkms_main_tree/2.6.39-2-686-pae/ > ./dkms_main_tree/2.6.39-2-686-pae/i686/ > ./dkms_main_tree/2.6.39-2-686-pae/i686/module/ > ./dkms_main_tree/2.6.39-2-686-pae/i686/module/blktap.ko > ./dkms_main_tree/2.6.39-2-686-pae/i686/log/ > ./dkms_main_tree/2.6.39-2-686-pae/i686/log/make.log > ----------->8--- > > I''m noticing it''s talking about 2.6.39-2-686-pae kernel, but here we use > 3.0.0-rc6-686-pae. > Is the package outdated ? > > Thanks in advance for your help. > > Sébastien > > > >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
fixing the CC 2011/7/17 Todd Deshane <todd.deshane@xen.org>:> 2011/7/17 Sébastien RICCIO <sr@swisscenter.com>: >> Setting up blktap-dkms (0.1) ... >> dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. >> Error! Bad conf file. > > This looks like the fatal error. > >> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf >> does not represent a valid dkms.conf file. >> >> >> Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. >> Common causes include: >> - You must be using DKMS 2.1.0.0 or later to support binaries only >> distribution specific archives. > > What version of dkms do you have installed? > (dkms --version) > > > what is the output of the following: > > var/lib/dkms/blktap/0.1/build/make.log > > try following the README in /var/lib/dkms/blktap/0.1/build > > There may be some build dependencies missing on your end. > >> - Corrupt distribution specific archive >> >> >> dpkg: error processing blktap-dkms (--install): >> subprocess installed post-installation script returned error exit status 2 >> Setting up fe (0.1-1) ... >> Setting up squeezed (0.1-1) ... >> Setting up v6d (0.1-1) ... >> Setting up xapi (0.1-1) ... >> Setting up xen-sm (0.1-1) ... >> Processing triggers for python-support ... >> Errors were encountered while processing: >> blktap-dkms >> ----------->8--- >> >> >> Seems to be a version mismatch thing occuring here. I manually unpacked the >> /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz to check it was not corrupt: >> >> ----8<---------- >> ./dkms_binaries_only/ >> ./dkms_binaries_only/PACKAGE_NAME >> ./dkms_binaries_only/PACKAGE_VERSION >> ./dkms_binaries_only/dkms.conf >> ./dkms_main_tree/ >> ./dkms_main_tree/dkms_dbversion >> ./dkms_main_tree/2.6.39-2-686-pae/ >> ./dkms_main_tree/2.6.39-2-686-pae/i686/ >> ./dkms_main_tree/2.6.39-2-686-pae/i686/module/ >> ./dkms_main_tree/2.6.39-2-686-pae/i686/module/blktap.ko >> ./dkms_main_tree/2.6.39-2-686-pae/i686/log/ >> ./dkms_main_tree/2.6.39-2-686-pae/i686/log/make.log >> ----------->8--- >> >> I''m noticing it''s talking about 2.6.39-2-686-pae kernel, but here we use >> 3.0.0-rc6-686-pae. >> Is the package outdated ? >> >> Thanks in advance for your help. >> >> Sébastien >> >> >> >> > > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/ >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 07/18/2011 04:37 AM, Todd Deshane wrote:> >> What version of dkms do you have installed? >> (dkms --version) >> >>box# dkms --version dkms: 2.2.0.1>> what is the output of the following: >> >> var/lib/dkms/blktap/0.1/build/make.log >> >> try following the README in /var/lib/dkms/blktap/0.1/build >> >> There may be some build dependencies missing on your end. >>These files doesn''t exists. But I found out a way to extract the files in the *deb and dkms it manually. What I did : box# mkdir temp box# cd temp box# dpkg -x ../blktap-dkms_0.1_all.deb . box# cp -a usr / box# dkms add -m blktap -v 0.1 Creating symlink /var/lib/dkms/blktap/0.1/source -> /usr/src/blktap-0.1 DKMS: add Completed. box# dkms build -m blktap -v 0.1 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area.... make KERNELRELEASE=3.0.0-rc6-686-pae -C /lib/modules/3.0.0-rc6-686-pae/build M=/var/lib/dkms/blktap/0.1/build modules...... cleaning build area.... DKMS: build Completed. box# dkms install -m blktap -v 0.1 blktap: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.0.0-rc6-686-pae/kernel/../extra// depmod..... DKMS: install Completed. Now rebooting :) I''ll let you know how it goes. Thanks, Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Sébastien, Thanks for testing this out - as I wrote on the wiki page, I didn''t really expect any of it to work yet, so if anything actually did work, that''s a bonus! :-) On 17 Jul 2011, at 20:33, Sébastien RICCIO wrote:> Hi, > > I''m currently trying to install xapi on debian (unstable), following the > following wiki page: > http://wiki.xensource.com/xenwiki/XAPI_on_debian > > 1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess > it wont work with 64-bit as the xapi *.deb files are for 32). >Yes, 32 bit only at the moment. We''ve not tried any of this stuff in 64 bit, so we''re concentrating on that at the moment. I''d be very interested in knowing what happens on 64 bit though, and it is something that we''ll be wanting to look into longer term.> note: you must leave an unused 1mb partition somewhere when > creating your partitions or grub2 used in sid will complain > during the dist-upgrade. This will result into an unbootable > system. (at least it happened to me) >Interesting, I didn''t have this problem - when I upgraded I chose to throw out my original grub.conf and use the new one, and it does seem to boot.> 2. Edit sources.list to use unstable instead of squeeze >..snip..> box# dpkg -i *deb > > ----8<---------- > Selecting previously deselected package blktap. > (Reading database ... 37780 files and directories currently installed.) > Unpacking blktap (from blktap_0.1-1_i386.deb) ... > Selecting previously deselected package blktap-dkms. > Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ... > Selecting previously deselected package fe. > Unpacking fe (from fe_0.1-1_i386.deb) ... > Selecting previously deselected package squeezed. > Unpacking squeezed (from squeezed_0.1-1_i386.deb) ... > Selecting previously deselected package v6d. > Unpacking v6d (from v6d_0.1-1_i386.deb) ... > Selecting previously deselected package xapi. > Unpacking xapi (from xapi_0.1-1_i386.deb) ... > Selecting previously deselected package xen-sm. > Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ... > Setting up blktap (0.1-1) ... > Setting up blktap-dkms (0.1) ... > dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. > Error! Bad conf file. > File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf > does not represent a valid dkms.conf file. > > > Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. > Common causes include: > - You must be using DKMS 2.1.0.0 or later to support binaries only > distribution specific archives. > - Corrupt distribution specific archive > > > dpkg: error processing blktap-dkms (--install): > subprocess installed post-installation script returned error exit status 2 >Right, a broken package. We''ve not got a nice way of making these things yet - I''ve got some suggestions from Daniel Stodden on how to proceed, so between us maybe we''ll be able to make something that works. When I''ve got something new to test I''ll let you know. Thanks again for helping out! Jon _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
OK, there''s a new blktap deb there (which you can tell by the date - at some point I''ll sort things so that the version numbers aren''t all 0.1 and the release numbers aren''t all 1 :-) Jon On 18 Jul 2011, at 11:10, Jonathan Ludlam wrote:> Hi Sébastien, > > Thanks for testing this out - as I wrote on the wiki page, I didn''t really expect any of it to work yet, so if anything actually did work, that''s a bonus! :-) > > On 17 Jul 2011, at 20:33, Sébastien RICCIO wrote: > >> Hi, >> >> I''m currently trying to install xapi on debian (unstable), following the >> following wiki page: >> http://wiki.xensource.com/xenwiki/XAPI_on_debian >> >> 1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess >> it wont work with 64-bit as the xapi *.deb files are for 32). >> > > Yes, 32 bit only at the moment. We''ve not tried any of this stuff in 64 bit, so we''re concentrating on that at the moment. I''d be very interested in knowing what happens on 64 bit though, and it is something that we''ll be wanting to look into longer term. > >> note: you must leave an unused 1mb partition somewhere when >> creating your partitions or grub2 used in sid will complain >> during the dist-upgrade. This will result into an unbootable >> system. (at least it happened to me) >> > > Interesting, I didn''t have this problem - when I upgraded I chose to throw out my original grub.conf and use the new one, and it does seem to boot. > >> 2. Edit sources.list to use unstable instead of squeeze >> > > ..snip.. > >> box# dpkg -i *deb >> >> ----8<---------- >> Selecting previously deselected package blktap. >> (Reading database ... 37780 files and directories currently installed.) >> Unpacking blktap (from blktap_0.1-1_i386.deb) ... >> Selecting previously deselected package blktap-dkms. >> Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ... >> Selecting previously deselected package fe. >> Unpacking fe (from fe_0.1-1_i386.deb) ... >> Selecting previously deselected package squeezed. >> Unpacking squeezed (from squeezed_0.1-1_i386.deb) ... >> Selecting previously deselected package v6d. >> Unpacking v6d (from v6d_0.1-1_i386.deb) ... >> Selecting previously deselected package xapi. >> Unpacking xapi (from xapi_0.1-1_i386.deb) ... >> Selecting previously deselected package xen-sm. >> Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ... >> Setting up blktap (0.1-1) ... >> Setting up blktap-dkms (0.1) ... >> dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. >> Error! Bad conf file. >> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf >> does not represent a valid dkms.conf file. >> >> >> Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. >> Common causes include: >> - You must be using DKMS 2.1.0.0 or later to support binaries only >> distribution specific archives. >> - Corrupt distribution specific archive >> >> >> dpkg: error processing blktap-dkms (--install): >> subprocess installed post-installation script returned error exit status 2 >> > > Right, a broken package. We''ve not got a nice way of making these things yet - I''ve got some suggestions from Daniel Stodden on how to proceed, so between us maybe we''ll be able to make something that works. When I''ve got something new to test I''ll let you know. > > Thanks again for helping out! > > Jon > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2011/7/18 Jonathan Ludlam <Jonathan.Ludlam@eu.citrix.com>:> OK, there''s a new blktap deb there (which you can tell by the date - at some point I''ll sort things so that the version numbers aren''t all 0.1 and the release numbers aren''t all 1 :-) >The install works. I''ve cleaned up the wiki page a bit too. http://wiki.xensource.com/xenwiki/XAPI_on_debian I think I am running into a grub2 problem at the moment though. It won''t seem to boot to the Xen hypervisor (I''m grub blind since I am doing this over a serial connection that doesn''t show grub). I''ll try to work through the grub2 issue tomorrow, but any suggestions are welcome. here is the /etc/grub.d/20_linux_xen file that comes with debian unstable: http://pastebin.com/KivyRSsM Any ideas as to why it won''t boot into the Xen hypervisor? I''ve done this type of troubleshooting already: http://wiki.xensource.com/xenwiki/XenCommonProblems#head-26434581604cc8357d9762aaaf040e8d87b37752 It can''t even insert the modules for xen-evtchn (no such device), which makes sense if (like I suspect) the Xen hypervisor is not actually there. Xen booting messages don''t show up in dmesg or /var/log/messages, so grub2 seems like the problem for sure. Thanks, Todd> Jon > > On 18 Jul 2011, at 11:10, Jonathan Ludlam wrote: > >> Hi Sébastien, >> >> Thanks for testing this out - as I wrote on the wiki page, I didn''t really expect any of it to work yet, so if anything actually did work, that''s a bonus! :-) >> >> On 17 Jul 2011, at 20:33, Sébastien RICCIO wrote: >> >>> Hi, >>> >>> I''m currently trying to install xapi on debian (unstable), following the >>> following wiki page: >>> http://wiki.xensource.com/xenwiki/XAPI_on_debian >>> >>> 1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess >>> it wont work with 64-bit as the xapi *.deb files are for 32). >>> >> >> Yes, 32 bit only at the moment. We''ve not tried any of this stuff in 64 bit, so we''re concentrating on that at the moment. I''d be very interested in knowing what happens on 64 bit though, and it is something that we''ll be wanting to look into longer term. >> >>> note: you must leave an unused 1mb partition somewhere when >>> creating your partitions or grub2 used in sid will complain >>> during the dist-upgrade. This will result into an unbootable >>> system. (at least it happened to me) >>> >> >> Interesting, I didn''t have this problem - when I upgraded I chose to throw out my original grub.conf and use the new one, and it does seem to boot. >> >>> 2. Edit sources.list to use unstable instead of squeeze >>> >> >> ..snip.. >> >>> box# dpkg -i *deb >>> >>> ----8<---------- >>> Selecting previously deselected package blktap. >>> (Reading database ... 37780 files and directories currently installed.) >>> Unpacking blktap (from blktap_0.1-1_i386.deb) ... >>> Selecting previously deselected package blktap-dkms. >>> Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ... >>> Selecting previously deselected package fe. >>> Unpacking fe (from fe_0.1-1_i386.deb) ... >>> Selecting previously deselected package squeezed. >>> Unpacking squeezed (from squeezed_0.1-1_i386.deb) ... >>> Selecting previously deselected package v6d. >>> Unpacking v6d (from v6d_0.1-1_i386.deb) ... >>> Selecting previously deselected package xapi. >>> Unpacking xapi (from xapi_0.1-1_i386.deb) ... >>> Selecting previously deselected package xen-sm. >>> Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ... >>> Setting up blktap (0.1-1) ... >>> Setting up blktap-dkms (0.1) ... >>> dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. >>> Error! Bad conf file. >>> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf >>> does not represent a valid dkms.conf file. >>> >>> >>> Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. >>> Common causes include: >>> - You must be using DKMS 2.1.0.0 or later to support binaries only >>> distribution specific archives. >>> - Corrupt distribution specific archive >>> >>> >>> dpkg: error processing blktap-dkms (--install): >>> subprocess installed post-installation script returned error exit status 2 >>> >> >> Right, a broken package. We''ve not got a nice way of making these things yet - I''ve got some suggestions from Daniel Stodden on how to proceed, so between us maybe we''ll be able to make something that works. When I''ve got something new to test I''ll let you know. >> >> Thanks again for helping out! >> >> Jon >> >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users > >-- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I worked around this by renaming 20_linux_xen to 09_linux_xen, then running update-grub, to make sure that the xen entry was top of the list. An ugly quick-n-dirty thing, but it worked :-) Jon On 19 Jul 2011, at 05:02, Todd Deshane wrote:> 2011/7/18 Jonathan Ludlam <Jonathan.Ludlam@eu.citrix.com>: >> OK, there''s a new blktap deb there (which you can tell by the date - at some point I''ll sort things so that the version numbers aren''t all 0.1 and the release numbers aren''t all 1 :-) >> > > The install works. I''ve cleaned up the wiki page a bit too. > > http://wiki.xensource.com/xenwiki/XAPI_on_debian > > I think I am running into a grub2 problem at the moment though. It > won''t seem to boot to the Xen hypervisor (I''m grub blind since I am > doing this over a serial connection that doesn''t show grub). > > I''ll try to work through the grub2 issue tomorrow, but any suggestions > are welcome. > > here is the /etc/grub.d/20_linux_xen file that comes with debian unstable: > > http://pastebin.com/KivyRSsM > > Any ideas as to why it won''t boot into the Xen hypervisor? > > I''ve done this type of troubleshooting already: > > http://wiki.xensource.com/xenwiki/XenCommonProblems#head-26434581604cc8357d9762aaaf040e8d87b37752 > > It can''t even insert the modules for xen-evtchn (no such device), > which makes sense if (like I suspect) the Xen hypervisor is not > actually there. > > Xen booting messages don''t show up in dmesg or /var/log/messages, so > grub2 seems like the problem for sure. > > Thanks, > Todd > >> Jon >> >> On 18 Jul 2011, at 11:10, Jonathan Ludlam wrote: >> >>> Hi Sébastien, >>> >>> Thanks for testing this out - as I wrote on the wiki page, I didn''t really expect any of it to work yet, so if anything actually did work, that''s a bonus! :-) >>> >>> On 17 Jul 2011, at 20:33, Sébastien RICCIO wrote: >>> >>>> Hi, >>>> >>>> I''m currently trying to install xapi on debian (unstable), following the >>>> following wiki page: >>>> http://wiki.xensource.com/xenwiki/XAPI_on_debian >>>> >>>> 1. Install squeeze 32-bits (it''s not specified on the wiki, but I guess >>>> it wont work with 64-bit as the xapi *.deb files are for 32). >>>> >>> >>> Yes, 32 bit only at the moment. We''ve not tried any of this stuff in 64 bit, so we''re concentrating on that at the moment. I''d be very interested in knowing what happens on 64 bit though, and it is something that we''ll be wanting to look into longer term. >>> >>>> note: you must leave an unused 1mb partition somewhere when >>>> creating your partitions or grub2 used in sid will complain >>>> during the dist-upgrade. This will result into an unbootable >>>> system. (at least it happened to me) >>>> >>> >>> Interesting, I didn''t have this problem - when I upgraded I chose to throw out my original grub.conf and use the new one, and it does seem to boot. >>> >>>> 2. Edit sources.list to use unstable instead of squeeze >>>> >>> >>> ..snip.. >>> >>>> box# dpkg -i *deb >>>> >>>> ----8<---------- >>>> Selecting previously deselected package blktap. >>>> (Reading database ... 37780 files and directories currently installed.) >>>> Unpacking blktap (from blktap_0.1-1_i386.deb) ... >>>> Selecting previously deselected package blktap-dkms. >>>> Unpacking blktap-dkms (from blktap-dkms_0.1_all.deb) ... >>>> Selecting previously deselected package fe. >>>> Unpacking fe (from fe_0.1-1_i386.deb) ... >>>> Selecting previously deselected package squeezed. >>>> Unpacking squeezed (from squeezed_0.1-1_i386.deb) ... >>>> Selecting previously deselected package v6d. >>>> Unpacking v6d (from v6d_0.1-1_i386.deb) ... >>>> Selecting previously deselected package xapi. >>>> Unpacking xapi (from xapi_0.1-1_i386.deb) ... >>>> Selecting previously deselected package xen-sm. >>>> Unpacking xen-sm (from xen-sm_0.1-1_i386.deb) ... >>>> Setting up blktap (0.1-1) ... >>>> Setting up blktap-dkms (0.1) ... >>>> dkms.conf: Error! No ''BUILT_MODULE_NAME'' directive specified for record #0. >>>> Error! Bad conf file. >>>> File: /tmp/dkms.rTkg1a/dkms_binaries_only/dkms.conf >>>> does not represent a valid dkms.conf file. >>>> >>>> >>>> Unable to load DKMS tarball /usr/share/blktap-dkms/blktap-0.1.dkms.tar.gz. >>>> Common causes include: >>>> - You must be using DKMS 2.1.0.0 or later to support binaries only >>>> distribution specific archives. >>>> - Corrupt distribution specific archive >>>> >>>> >>>> dpkg: error processing blktap-dkms (--install): >>>> subprocess installed post-installation script returned error exit status 2 >>>> >>> >>> Right, a broken package. We''ve not got a nice way of making these things yet - I''ve got some suggestions from Daniel Stodden on how to proceed, so between us maybe we''ll be able to make something that works. When I''ve got something new to test I''ll let you know. >>> >>> Thanks again for helping out! >>> >>> Jon >>> >>> >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> >> > > > > -- > Todd Deshane > http://www.linkedin.com/in/deshantm > http://www.xen.org/products/cloudxen.html > http://runningxen.com/_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 07/19/2011 09:01 AM, Jonathan Ludlam wrote:> I worked around this by renaming 20_linux_xen to 09_linux_xen, then running update-grub, to make sure that the xen entry was top of the list. An ugly quick-n-dirty thing, but it worked :-) > > JonHi, Yes, by default the xen entry is at the bottom of the grub menu, changing the order in grub.d works well and I don''t think is that much dirty :). Now there is another issue with kernel 3.x and xen, at least with my hardware and seems it has been confirmed by other people too. As soon as the dom0 kernel is loaded, the screen on the console goes blank (black in fact...), but it still boot. If you have network configured, you can login to the box with ssh, otherwise you''re stuck :) There is a patch for this that I had tested and was working on some self compiled 3.x xen kernel: http://lists.xensource.com/archives/html/xen-devel/2011-06/msg00417.html but it doesn''t look like it reached the kernel tree yet... -- Jonathan, the new packages install fine, thanks for the fix. Going further with my testing :) Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-19 10:43 UTC
[Xen-users] XAPI on debian - openvswitch and ocfs2 support
Hi, Going deeper with my tests of xapi on debian, I would like to ask if there is any plan to support openvswitch for the network management and open-iscsi+multipath+ocfs2 as a backend for a vhd based SR ? -- For ocfs2 with iscsi the kernel module is already available in the kernel, you would just need to: box# apt-get install open-iscsi multipath-tools ocfs2-tools box# dpkg reconfigure ocfs2-tools Would it be possible to have a SR type ocfs2 acting like a nfs SR (using vhd files on ocfs2 instead of nfs), like for example: with multipath SR=`xe sr-create type=ocfs name-label=ocfs2 device-config:device=/dev/mapper/mpath0-part1 device-config:devicepath=/cloud/files` without SR=`xe sr-create type=ocfs name-label=ocfs2 device-config:device=/dev/sdc1 device-config:devicepath=/cloud/files` That would ofcs2 mount <device> somewhere on the system, and read/write the vhd files in <devicepath> subdirectory (or root of the device, if omitted) -- For openvswitch, seems the packages exists in the debian unstable repo, shouldn''t be a problem, except maybe for the datapath kernel module. I''m going to try it, something like apt-get install openvswitch-common openvswitch-datapath-source openvswitch-pki openvswitch-switch python-openvswitch -- Last question :) By default xend is started at boot, shouldn''t it be disabled when using xapi ? Cheers, Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mike McClurg
2011-Jul-19 11:57 UTC
[Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
On 19/07/11 11:43, Sébastien RICCIO wrote:> Hi, > > Going deeper with my tests of xapi on debian, I would like to ask if > there is any plan to support > openvswitch for the network management and open-iscsi+multipath+ocfs2 > as a backend for > a vhd based SR ?Comments below...> For ocfs2 with iscsi the kernel module is already available in the > kernel, you would just need to: > > box# apt-get install open-iscsi multipath-tools ocfs2-tools > box# dpkg reconfigure ocfs2-tools > > Would it be possible to have a SR type ocfs2 acting like a nfs SR (using > vhd files on ocfs2 instead of nfs), > like for example: > > with multipath > SR=`xe sr-create type=ocfs name-label=ocfs2 > device-config:device=/dev/mapper/mpath0-part1 > device-config:devicepath=/cloud/files` > > without > SR=`xe sr-create type=ocfs name-label=ocfs2 > device-config:device=/dev/sdc1 device-config:devicepath=/cloud/files` > > That would ofcs2 mount <device> somewhere on the system, and read/write > the vhd files in <devicepath> subdirectory (or root of the device, if > omitted)There are a couple new requests for different storage backend types, including GlusterFS. Unfortunately, we don''t really have the capacity with this project to take on writing new storage backends. Right now, we''re just trying to get the existing backends working on Debian ;) If you have experience with ocfs2, and you''d like to give SR backend writing a try, please do! Take a look at the existing SRs, and come back to the list if you have any questions. Expanding the number of storage backends we provide is definitely something that we''re interested in.> For openvswitch, seems the packages exists in the debian unstable repo, > shouldn''t be a problem, > except maybe for the datapath kernel module. I''m going to try it, > something like > > apt-get install openvswitch-common openvswitch-datapath-source > openvswitch-pki openvswitch-switch python-openvswitchXCP already supports openvswitch, so yes, this is on our to-do list for xapi on Debian. It''s not the highest priority on our list, though, as we have a lot of other things to get working first, such as basic bridge networking. If you would like to attempt to get it working, we would definitely incorporate any work you do into the xapi-on-Debian project. Feel free to edit the wiki page with anything you find.> Last question :) > > By default xend is started at boot, shouldn''t it be disabled when using > xapi ?Yes, you are correct. We still need to automate this in the xapi install package. Go ahead and do it manually for now. Jon, Todd and I really appreciate you being an early adopter. Keep coming back with questions! Hopefully we''ll get some more brave souls out there to give this a go... Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-19 12:40 UTC
Re: [Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
On 07/19/2011 01:57 PM, Mike McClurg wrote:> > There are a couple new requests for different storage backend types, > including GlusterFS. Unfortunately, we don''t really have the capacity > with this project to take on writing new storage backends. Right now, > we''re just trying to get the existing backends working on Debian ;) If > you have experience with ocfs2, and you''d like to give SR backend > writing a try, please do! Take a look at the existing SRs, and come back > to the list if you have any questions. Expanding the number of storage > backends we provide is definitely something that we''re interested in. >Okay I''ll give it a try taking example on existing SR types and try to build one for OCFS2 and let you know how it progresses.> > XCP already supports openvswitch, so yes, this is on our to-do list for > xapi on Debian. It''s not the highest priority on our list, though, as we > have a lot of other things to get working first, such as basic bridge > networking. If you would like to attempt to get it working, we would > definitely incorporate any work you do into the xapi-on-Debian project. > Feel free to edit the wiki page with anything you find. >This is on now on my todo list too :)>> Last question :) >> >> By default xend is started at boot, shouldn''t it be disabled when using >> xapi ? > Yes, you are correct. We still need to automate this in the xapi install > package. Go ahead and do it manually for now. > > Jon, Todd and I really appreciate you being an early adopter. Keep > coming back with questions! Hopefully we''ll get some more brave souls > out there to give this a go... >Ok. Thanks. That''s what I did actually. I would add this to the wiki page before the step "7. reboot" but I can''t edit it (immuable page): apt-get install chkconfig chkconfig xendomains off chkconfig xend off Thanks for your work, Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-19 15:20 UTC
Re: [Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
On 07/19/2011 02:40 PM, Sébastien RICCIO wrote:> > I would add this to the wiki page before the step "7. reboot" but I > can''t edit it (immuable page): > > apt-get install chkconfig > chkconfig xendomains off > chkconfig xend off > > > Thanks for your work, > Sébastien > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Please discard this comment. Disabling the xend init.d script disables xenstore too, as it seems the debian packages doesn''t ship with separated xencommons and xend startup scripts. My current dirty workaround is to only disable the xendomains init.d script and replace /etc/init.d/xend by one that I''ve edited to disable start_xend calls. I also recompiled and repackaged the 3.0.0-rc6 kernel with the vga fix for xen (black screens issue), if interested you can find these files here: http://xendev.swisscenter.com/xapi/debian/ -- Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Scott Damron
2011-Jul-19 15:22 UTC
Re: [Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
LMAO! - apt-get remove curiosity :) 2011/7/19 Sébastien RICCIO <sr@swisscenter.com>:> On 07/19/2011 02:40 PM, Sébastien RICCIO wrote: >> >> I would add this to the wiki page before the step "7. reboot" but I can''t >> edit it (immuable page): >> >> apt-get install chkconfig >> chkconfig xendomains off >> chkconfig xend off >> >> >> Thanks for your work, >> Sébastien >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > Please discard this comment. Disabling the xend init.d script disables > xenstore too, as it seems > the debian packages doesn''t ship with separated xencommons and xend startup > scripts. > > My current dirty workaround is to only disable the xendomains init.d script > and replace /etc/init.d/xend by > one that I''ve edited to disable start_xend calls. > > I also recompiled and repackaged the 3.0.0-rc6 kernel with the vga fix for > xen (black screens issue), if interested you can find > these files here: > > http://xendev.swisscenter.com/xapi/debian/ > > -- > Sébastien > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Never wrestle with a pig. You''ll only get dirty and the pig likes it. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-19 15:43 UTC
Re: [Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
On 07/19/2011 05:22 PM, Scott Damron wrote:> LMAO! - apt-get remove curiosity :) >Hehe, I was sure that someone would hit that page :) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2011-Jul-19 21:51 UTC
Re: [Xen-users] Re: XAPI on debian - openvswitch and ocfs2 support
2011/7/19 Sébastien RICCIO <sr@swisscenter.com>:> I would add this to the wiki page before the step "7. reboot" but I can''t > edit it (immuable page): >You need to create a wiki account, then email me your username and I will add you to the editors group. Thanks, Todd> apt-get install chkconfig > chkconfig xendomains off > chkconfig xend off > > > Thanks for your work, > Sébastien >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Continuing my tests with xapi on debian, I get into an issue trying to create a SR. box# xe sr-create type=ext name-label=local device-config:device=/dev/sda3 Error code: SR_BACKEND_FAILURE_1 Error parameters: , Error reporting error, unknown key NoRootDev, /usr/lib/xen-common/xapi/sm/util.py:17: DeprecationWarning: The popen2 module is deprecated. Use the subprocess module. import os, re, sys, popen2, subprocess Any idea what could be wrong ? Thanks a lot for your help. Sébastien _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Looks like the EXTSR was a bit broken in a couple of ways. Firstly, you''ll need to add a ''PRIMARY_DISK'' line to /etc/xensource-inventory (now mentioned in the wiki page) Secondly, the path the the LVM tools was incorrect. I''ve fixed this in a new deb that I''ve uploaded to downloads.xen.org. Thirdly, I''ve added to the instructions that LVM2 needs to be installed. I''ve also fixed a bunch of other things in the debs that I''ve uploaded - please pull down the latest versions and install them. Jon On 20 Jul 2011, at 14:22, Sébastien RICCIO wrote:> Hi, > > Continuing my tests with xapi on debian, I get into an issue trying to > create a SR. > > box# xe sr-create type=ext name-label=local device-config:device=/dev/sda3 > > Error code: SR_BACKEND_FAILURE_1 > Error parameters: , Error reporting error, unknown key NoRootDev, > /usr/lib/xen-common/xapi/sm/util.py:17: DeprecationWarning: The popen2 > module is deprecated. Use the subprocess module. > import os, re, sys, popen2, subprocess > > > Any idea what could be wrong ? > > Thanks a lot for your help. > > Sébastien >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-20 19:36 UTC
Re: [Xen-users] Re: XAPI on debian - sr-create issue
Hi Jon,
I''ve applied the new deb files and added the primary disk entry to the
xensource-inventory file.
It looks like the error I had was related to the PRIMARY_DISK missing
setting.
I can now create a local SR, create a vdi, and a vbd, but if i try to
plug it to the dom0 (i''ve not configured any VM yet as I''m
trying the
different storage layers) I get ugly kernel messages.
Here is what i''ve done:
box# xe sr-create content-type=user type=ext name-label=local
device-config:device=/dev/sda3
66597906-20ae-5ec6-e60a-e0dec55df506
box # xe vdi-create sr-uuid=66597906-20ae-5ec6-e60a-e0dec55df506
name-label=testtest type=user virtual-size=20GiB
ca4ba7bd-2901-45fb-a3f5-18b7d78e0232
box# xe vm-list
uuid ( RO) : 03753e00-3514-296c-52e1-26ba8f1dd068
name-label ( RW): Control domain on host: xen-blade13
power-state ( RO): running
box # xe vbd-create vm-uuid=03753e00-3514-296c-52e1-26ba8f1dd068
vdi-uuid=ca4ba7bd-2901-45fb-a3f5-18b7d78e0232 device=0 type=disk mode=rw
92a3b3bc-8b48-b13d-a53c-891c10fba1b9
box # xe vbd-plug uuid=92a3b3bc-8b48-b13d-a53c-891c10fba1b9
[hangs indefinitely]
doing a ctrl-c after one minute or so to get the shell back
Still, the device has been plugged as xvda appears in the dom0 and I can
fdisk it, mount it etc.
But there are not so nice messages in the dmesg, and If i try to attach
another vbd it doesn''t work anymore.
dmesg:
[ 237.487585] block tda: sector-size: 512/512+0 capacity: 209715200
discard: 0+0 flush: 0x0
[ 237.577587] xen-blkback:ring-ref 8, event-channel 90, protocol 1
(x86_32-abi)
[ 237.585893] blkfront: xvda: barrier or flush: disabled
[ 237.587430] ------------[ cut here ]------------
[ 237.587443] WARNING: at kernel/irq/handle.c:130
handle_irq_event_percpu+0xa3/0x158()
[ 237.587448] Hardware name: PowerEdge M610
[ 237.587457] irq 409 handler blkif_interrupt+0x0/0x1f7 [xen_blkfront]
enabled interrupts
[ 237.587462] Modules linked in: xen_blkfront(+) ocfs2 quota_tree
ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue
configfs dm_round_robin ext3 jbd iptable_filter ip_tables x_tables
xen_blkback openvswitch_mod xen_netback xen_evtchn xenfs ib_iser rdma_cm
ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi
scsi_transport_iscsi nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc
blktap loop snd_pcm snd_timer snd soundcore snd_page_alloc dcdbas pcspkr
ghes i7core_edac edac_core evdev joydev hed acpi_power_meter button
processor thermal_sys ext4 mbcache jbd2 crc16 dm_multipath scsi_dh
dm_mod sg ses enclosure sr_mod sd_mod cdrom crc_t10dif usbhid hid
usb_storage uas uhci_hcd bnx2x crc32c ehci_hcd usbcore megaraid_sas
scsi_mod libcrc32c mdio bnx2 [last unloaded: scsi_wait_scan]
[ 237.587710] Pid: 0, comm: swapper Not tainted 3.0.0-rc6-686-pae-vgafix #5
[ 237.587715] Call Trace:
[ 237.587726] [<c1033abc>] ? warn_slowpath_common+0x68/0x79
[ 237.587735] [<c10714b0>] ? handle_irq_event_percpu+0xa3/0x158
[ 237.587743] [<c1033b35>] ? warn_slowpath_fmt+0x29/0x2d
[ 237.587751] [<c10714b0>] ? handle_irq_event_percpu+0xa3/0x158
[ 237.587761] [<f748a4c8>] ? kick_pending_request_queues+0x27/0x27
[xen_blkfront]
[ 237.587770] [<c1071586>] ? handle_irq_event+0x21/0x37
[ 237.587778] [<c1072dab>] ? handle_edge_irq+0x7f/0x98
[ 237.587788] [<c11aadbf>] ? __xen_evtchn_do_upcall+0x126/0x1ad
[ 237.587797] [<c11abf25>] ? xen_evtchn_do_upcall+0x18/0x26
[ 237.587807] [<c12a73d7>] ? xen_do_upcall+0x7/0xc
[ 237.587816] [<c10023a7>] ? hypercall_page+0x3a7/0x1000
[ 237.587825] [<c100586a>] ? xen_safe_halt+0xf/0x19
[ 237.587834] [<c100cdee>] ? default_idle+0x52/0x87
[ 237.587841] [<c1007396>] ? cpu_idle+0x87/0xa1
[ 237.587850] [<c140a6f1>] ? start_kernel+0x32a/0x32f
[ 237.587858] [<c140bfe1>] ? xen_start_kernel+0x58a/0x591
[ 237.587864] ---[ end trace c7b0ff9f162240ee ]---
[ 237.588235] xvda: unknown partition table
Now, on the box I have open-iscsi/multipath/ocfs2 running. So I''m going
to try again with all that
stuff disabled to check if nothing is conflicting...
But, In the meantime if you have an idea ? :)
Thanks,
Sébastien
On 07/20/2011 06:49 PM, Jonathan Ludlam wrote:> Looks like the EXTSR was a bit broken in a couple of ways.
>
> Firstly, you''ll need to add a ''PRIMARY_DISK''
line to /etc/xensource-inventory (now mentioned in the wiki page)
> Secondly, the path the the LVM tools was incorrect. I''ve fixed
this in a new deb that I''ve uploaded to downloads.xen.org.
> Thirdly, I''ve added to the instructions that LVM2 needs to be
installed.
>
> I''ve also fixed a bunch of other things in the debs that
I''ve uploaded - please pull down the latest versions and install them.
>
> Jon
>
>
>
> On 20 Jul 2011, at 14:22, Sébastien RICCIO wrote:
>
>> Hi,
>>
>> Continuing my tests with xapi on debian, I get into an issue trying to
>> create a SR.
>>
>> box# xe sr-create type=ext name-label=local
device-config:device=/dev/sda3
>>
>> Error code: SR_BACKEND_FAILURE_1
>> Error parameters: , Error reporting error, unknown key NoRootDev,
>> /usr/lib/xen-common/xapi/sm/util.py:17: DeprecationWarning: The popen2
>> module is deprecated. Use the subprocess module.
>> import os, re, sys, popen2, subprocess
>>
>>
>> Any idea what could be wrong ?
>>
>> Thanks a lot for your help.
>>
>> Sébastien
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Sébastien RICCIO
2011-Jul-20 19:48 UTC
Re: [Xen-users] Re: XAPI on debian - sr-create issue
Additional infos: Disabled all the iscsi/multipath/ocfs2 things, no more ugly messages in the dmesg when attempting to vbd-plug but it still hangs after [ 223.619565] block tda: sector-size: 512/512+0 capacity: 62914560 discard: 0+0 flush: 0x0 [ 223.712070] xen-blkback:ring-ref 8, event-channel 90, protocol 1 (x86_32-abi) [ 223.719642] blkfront: xvda: barrier or flush: disabled [ 223.724288] xvda: xvda1 [ 223.725511] Setting capacity to 62914560 [ 223.725519] xvda: detected capacity change from 0 to 32212254720 box# xe vbd-plug uuid=92a3b3bc-8b48-b13d-a53c-891c10fba1b9 [never returns to shell] _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users