I am trying to set up xen 4.0 on a debian system with a dual AMD64 CPU.
I installed linux-image-2.6.32-5-xen-amd64 and
xen-hypervisor-4.0-amd64.
When I boot, everything seems OK, but xend is not there.
The log says (last two lines):
xs_handle = xen.lowlevel.xs.xs()
Error: (2, ''No such file or directory'')
So I am asking:
what file is presumably missing or what should I do to make xend start.
TIA,
Ric
2012/1/18 Riccardo Orfei <r.orfei@gmail.com>:> > I am trying to set up xen 4.0 on a debian system with a dual AMD64 CPU.> When I boot, everything seems OK, but xend is not there.Sounds like it didn''t boot into Xen. Did you see Xen load before the Linux kernel messages? If no, then this is something to do with the grub configuration order in /etc/grub. There''s a few howtos for fixing most of the xen bugs in squeeze, a good one is in the debian wiki for example. Don''t ask me why it''s not just fixed though. Florian
Ric, I have it running on two servers and when I ran into this issue I had to have the Xen linux image, xen-hypervisor, AND the qemu-dm package which isn''t listed as a pre-req for Xen. I don''t remember because it''s been a while since I installed it, but some of the other packages you might need to manually install are xen-tools, xenstore-utils, xen-docs, and xen-tools-common. I will review my servers packages here in a little bit and if I forgot anything I will add then to this post. Shane On Wed, Jan 18, 2012 at 10:45 AM, Florian Heigl <florian.heigl@gmail.com>wrote:> 2012/1/18 Riccardo Orfei <r.orfei@gmail.com>: > > > > I am trying to set up xen 4.0 on a debian system with a dual AMD64 CPU. > > > When I boot, everything seems OK, but xend is not there. > > Sounds like it didn''t boot into Xen. Did you see Xen load before the > Linux kernel messages? > If no, then this is something to do with the grub configuration order > in /etc/grub. > > There''s a few howtos for fixing most of the xen bugs in squeeze, a > good one is in the debian wiki for example. > > Don''t ask me why it''s not just fixed though. > > Florian > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Oh I also forgot you need to go into /etc/defaults/grub and set the default to boot to the grub entry that says : Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64 If you don''t it will continue to boot without xend.(Remember grub menu entries are numbered starting with 0) Shane On Wed, Jan 18, 2012 at 11:08 AM, Shane Johnson <sdj@rasmussenequipment.com>wrote:> Ric, > I have it running on two servers and when I ran into this issue I had to > have the Xen linux image, xen-hypervisor, AND the qemu-dm package which > isn''t listed as a pre-req for Xen. I don''t remember because it''s been a > while since I installed it, but some of the other packages you might need > to manually install are xen-tools, xenstore-utils, xen-docs, and > xen-tools-common. I will review my servers packages here in a little bit > and if I forgot anything I will add then to this post. > > Shane > > > On Wed, Jan 18, 2012 at 10:45 AM, Florian Heigl <florian.heigl@gmail.com>wrote: > >> 2012/1/18 Riccardo Orfei <r.orfei@gmail.com>: >> > >> > I am trying to set up xen 4.0 on a debian system with a dual AMD64 CPU. >> >> > When I boot, everything seems OK, but xend is not there. >> >> Sounds like it didn''t boot into Xen. Did you see Xen load before the >> Linux kernel messages? >> If no, then this is something to do with the grub configuration order >> in /etc/grub. >> >> There''s a few howtos for fixing most of the xen bugs in squeeze, a >> good one is in the debian wiki for example. >> >> Don''t ask me why it''s not just fixed though. >> >> Florian >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > > > -- > Shane D. Johnson > IT Administrator > Rasmussen Equipment > > >-- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
2012/1/18 Shane Johnson <sdj@rasmussenequipment.com>:> Oh I also forgot you need to go into /etc/defaults/grub and set the default > to boot to the grub entry that says : > Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64 > > If you don''t it will continue to boot without xend.(Remember grub menu > entries are numbered starting with 0)After changes in /etc/defaults/grub you need to run update-grub. Regards, Marcin Kuk
Shane Johnson wrote:>Oh I also forgot you need to go into /etc/defaults/grub and set the >default to boot to the grub entry that says : >Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64Or rename files in /etc/grub so that Xen comes before the plain kernels - then it''s automatic. But in answer to the OP - it should all "just work" apart from the GRUB issue already noted. I''ve a box at work, and one at home, both running the same versions as you list. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books.
First of all, thanks to all who took the trouble to respond to my post! Well, I already knew about the boot order (xen first, then the linux kernel), so I think that is ok. Looking into dmesg I can see lots of "(xen)" tags. The booting sequence is too fast to actually see the distinct phases. About the qemu-dm module, I cannot recall, but I''ll take a look, maybe that''s the culprit. Thanks to your posts, now I feel more confident that everything is going OK. Ciao, Ric Il 18/01/2012 19:57, Simon Hobson ha scritto:> Shane Johnson wrote: >> Oh I also forgot you need to go into /etc/defaults/grub and set the default to boot to the grub >> entry that says : >> Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64 > > Or rename files in /etc/grub so that Xen comes before the plain kernels - then it''s automatic. > > But in answer to the OP - it should all "just work" apart from the GRUB issue already noted. I''ve > a box at work, and one at home, both running the same versions as you list. >
On 18 January 2012 19:57, Simon Hobson <linux@thehobsons.co.uk> wrote:> > Shane Johnson wrote: >> >> Oh I also forgot you need to go into /etc/defaults/grub and set the default to boot to the grub entry that says : >> Debian GNU/Linux, with Linux 2.6.32-5-xen-amd64 and XEN 4.0-amd64 > > > Or rename files in /etc/grub so that Xen comes before the plain kernels - then it''s automatic. > > But in answer to the OP - it should all "just work" apart from the GRUB issue already noted. I''ve a box at work, and one at home, both running the same versions as you list. > > -- > Simon Hobson > > Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed > author Gladys Hobson. Novels - poetry - short stories - ideal as > Christmas stocking fillers. Some available as e-books. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersTo check that you are in dom0, try to start the xend daemon. If you get an error message that''s likely you''re not in dom0. There are several ways to check that you are actually in dom0: http://wiki.xen.org/wiki/Xen_Common_Problems#Starting_xend_fails.3F Eva
I peeped into /var/log/xen/xend-debug.log and found: Xend started at Thu Jan 19 11:29:27 2012. cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory cat: /sys/bus/scsi/devices/host0/model: No such file or directory cat: /sys/bus/scsi/devices/host0/type: No such file or directory cat: /sys/bus/scsi/devices/host0/rev: No such file or directory cat: /sys/bus/scsi/devices/host0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host1/vendor: No such file or directory cat: /sys/bus/scsi/devices/host1/model: No such file or directory cat: /sys/bus/scsi/devices/host1/type: No such file or directory cat: /sys/bus/scsi/devices/host1/rev: No such file or directory cat: /sys/bus/scsi/devices/host1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host2/vendor: No such file or directory cat: /sys/bus/scsi/devices/host2/model: No such file or directory cat: /sys/bus/scsi/devices/host2/type: No such file or directory cat: /sys/bus/scsi/devices/host2/rev: No such file or directory cat: /sys/bus/scsi/devices/host2/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host3/vendor: No such file or directory cat: /sys/bus/scsi/devices/host3/model: No such file or directory cat: /sys/bus/scsi/devices/host3/type: No such file or directory cat: /sys/bus/scsi/devices/host3/rev: No such file or directory cat: /sys/bus/scsi/devices/host3/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host4/vendor: No such file or directory cat: /sys/bus/scsi/devices/host4/model: No such file or directory cat: /sys/bus/scsi/devices/host4/type: No such file or directory cat: /sys/bus/scsi/devices/host4/rev: No such file or directory cat: /sys/bus/scsi/devices/host4/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/host5/vendor: No such file or directory cat: /sys/bus/scsi/devices/host5/model: No such file or directory cat: /sys/bus/scsi/devices/host5/type: No such file or directory cat: /sys/bus/scsi/devices/host5/rev: No such file or directory cat: /sys/bus/scsi/devices/host5/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target0:0:0/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target0:0:1/vendor: No such file or directory cat: /sys/bus/scsi/devices/target0:0:1/model: No such file or directory cat: /sys/bus/scsi/devices/target0:0:1/type: No such file or directory cat: /sys/bus/scsi/devices/target0:0:1/rev: No such file or directory cat: /sys/bus/scsi/devices/target0:0:1/scsi_level: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/vendor: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/model: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/type: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/rev: No such file or directory cat: /sys/bus/scsi/devices/target2:0:0/scsi_level: No such file or directory Exception starting xend: (2, ''No such file or directory'') This sounds "good": where are my disks? I have got an ATA and an SATA disk, doesn''t xend find them? Ciao, Ric
Hey Ric, On Fri, Jan 20, 2012 at 11:58 AM, Riccardo Orfei <r.orfei@mclink.it> wrote:> I peeped into /var/log/xen/xend-debug.log and found: > > Xend started at Thu Jan 19 11:29:27 2012. > cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host0/model: No such file or directory[..]> Exception starting xend: (2, ''No such file or directory'') > > This sounds "good": where are my disks? I have got an ATA and an SATA > disk, doesn''t xend find them? >Still looks like your systems boots directly into Linux w/o starting the Xen hypervisor first. Try to manually select the Xen hypervisor in the grub boot menu when your system starts. Should be called something like "Debian GNU/Linux, with Linux 2.6.32-[..] and XEN 4.0-amd64''. Regards, Linus
Hi Linus! First of all, thanks a lot for taking the time to write down your suggestion... Well I am pretty sure that the hypervisor is running, because I see (flushing rapidly) a certain number of "(XEN) blabla" lines at boot time. Next, I checked the /sys/xen/capabilities file, which contains the string "control-d", and, as a xen-user (Eva) said earlier, it means that the hypervisor is in control. My (un)educated guess is that some (virtual) disk driver is missing or misplaced... Ciao, Ric Il 01/02/2012 23:28, Linus van Geuns ha scritto:> Hey Ric, > > On Fri, Jan 20, 2012 at 11:58 AM, Riccardo Orfei<r.orfei@mclink.it> wrote: >> I peeped into /var/log/xen/xend-debug.log and found: >> >> Xend started at Thu Jan 19 11:29:27 2012. >> cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory >> cat: /sys/bus/scsi/devices/host0/model: No such file or directory > [..] >> Exception starting xend: (2, ''No such file or directory'') >> >> This sounds "good": where are my disks? I have got an ATA and an SATA >> disk, doesn''t xend find them? >> > Still looks like your systems boots directly into Linux w/o starting > the Xen hypervisor first. > Try to manually select the Xen hypervisor in the grub boot menu when > your system starts. > > Should be called something like "Debian GNU/Linux, with Linux > 2.6.32-[..] and XEN 4.0-amd64''. > > Regards, Linus > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >
Ric, If you run the command : ps -A | grep xend do you see the process with a pid? if you do it is running if not you will have to see what is preventing it from running in the log files. Sincerely Shane On Thu, Feb 2, 2012 at 2:30 AM, Riccardo Orfei <r.orfei@mclink.it> wrote:> Hi Linus! > > First of all, thanks a lot for taking the time to write down your > suggestion... > > Well I am pretty sure that the hypervisor is running, because I see > (flushing rapidly) a certain number of "(XEN) blabla" lines at boot time. > > Next, I checked the /sys/xen/capabilities file, which contains the string > "control-d", and, as a xen-user (Eva) said earlier, it means that the > hypervisor is in control. > > My (un)educated guess is that some (virtual) disk driver is missing or > misplaced... > > Ciao, > Ric > > Il 01/02/2012 23:28, Linus van Geuns ha scritto: > >> Hey Ric, >> >> On Fri, Jan 20, 2012 at 11:58 AM, Riccardo Orfei<r.orfei@mclink.it> >> wrote: >> >>> I peeped into /var/log/xen/xend-debug.log and found: >>> >>> Xend started at Thu Jan 19 11:29:27 2012. >>> cat: /sys/bus/scsi/devices/host0/**vendor: No such file or directory >>> cat: /sys/bus/scsi/devices/host0/**model: No such file or directory >>> >> [..] >> >>> Exception starting xend: (2, ''No such file or directory'') >>> >>> This sounds "good": where are my disks? I have got an ATA and an SATA >>> disk, doesn''t xend find them? >>> >>> Still looks like your systems boots directly into Linux w/o starting >> the Xen hypervisor first. >> Try to manually select the Xen hypervisor in the grub boot menu when >> your system starts. >> >> Should be called something like "Debian GNU/Linux, with Linux >> 2.6.32-[..] and XEN 4.0-amd64''. >> >> Regards, Linus >> >> ______________________________**_________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/**xen-users<http://lists.xensource.com/xen-users> >> >> > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/**xen-users<http://lists.xensource.com/xen-users> >-- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Shane! Thank you for your suggestion, but, in effects xend is NOT running: that is the problem. If you take the burden to follow the thread backwards, you will find my previous posts that show all my findings. In a few words: xend does not start because a file is missing or misplaced, but I don''t know which one. Ciao, Ric Il 02/02/2012 16:04, Shane Johnson ha scritto:> Ric, > If you run the command : > ps -A | grep xend > > do you see the process with a pid? if you do it is running if not you will have to see what is > preventing it from running in the log files. > > Sincerely > Shane > > > On Thu, Feb 2, 2012 at 2:30 AM, Riccardo Orfei <r.orfei@mclink.it <mailto:r.orfei@mclink.it>> wrote: > > Hi Linus! > > First of all, thanks a lot for taking the time to write down your suggestion... > > Well I am pretty sure that the hypervisor is running, because I see (flushing rapidly) a > certain number of "(XEN) blabla" lines at boot time. > > Next, I checked the /sys/xen/capabilities file, which contains the string "control-d", and, as > a xen-user (Eva) said earlier, it means that the hypervisor is in control. > > My (un)educated guess is that some (virtual) disk driver is missing or misplaced... > > Ciao, > Ric > > Il 01/02/2012 23:28, Linus van Geuns ha scritto: > > Hey Ric, > > On Fri, Jan 20, 2012 at 11:58 AM, Riccardo Orfei<r.orfei@mclink.it > <mailto:r.orfei@mclink.it>> wrote: > > I peeped into /var/log/xen/xend-debug.log and found: > > Xend started at Thu Jan 19 11:29:27 2012. > cat: /sys/bus/scsi/devices/host0/vendor: No such file or directory > cat: /sys/bus/scsi/devices/host0/model: No such file or directory > > [..] > > Exception starting xend: (2, ''No such file or directory'') > > This sounds "good": where are my disks? I have got an ATA and an SATA > disk, doesn''t xend find them? > > Still looks like your systems boots directly into Linux w/o starting > the Xen hypervisor first. > Try to manually select the Xen hypervisor in the grub boot menu when > your system starts. > > Should be called something like "Debian GNU/Linux, with Linux > 2.6.32-[..] and XEN 4.0-amd64''. > > Regards, Linus > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > > > -- > Shane D. Johnson > IT Administrator > Rasmussen Equipment > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hey Ric, On Thu, Feb 2, 2012 at 10:30 AM, Riccardo Orfei <r.orfei@mclink.it> wrote:> Hi Linus! > > First of all, thanks a lot for taking the time to write down your > suggestion... > > Well I am pretty sure that the hypervisor is running, because I see > (flushing rapidly) a certain number of "(XEN) blabla" lines at boot time. > > Next, I checked the /sys/xen/capabilities file, which contains the string > "control-d", and, as a xen-user (Eva) said earlier, it means that the > hypervisor is in control. > > My (un)educated guess is that some (virtual) disk driver is missing or > misplaced...Sorry, somehow I must have skiped over that part in your emails. So, when booting your system with (Xen) hypervisor, what is the result of the following commands: lsb_release -a uname -a ls -lh /sys/hypervisor/ xm info xm list Regards, Linus
Hi Linus! This are the result of the issued commands: Ciao, Ric No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 6.0.3 (squeeze) Release: 6.0.3 Codename: squeeze Linux ares 2.6.32-5-xen-amd64 #1 SMP Mon Jan 9 22:09:26 UTC 2012 x86_64 GNU/Linux total 0 drwxr-xr-x 2 root root 0 Feb 3 09:59 compilation drwxr-xr-x 2 root root 0 Feb 3 09:59 properties -r--r--r-- 1 root root 4.0K Feb 3 09:56 type -r--r--r-- 1 root root 4.0K Feb 3 09:59 uuid drwxr-xr-x 2 root root 0 Feb 3 09:56 version Error: Unable to connect to xend: No such file or directory. Is xend running? Error: Unable to connect to xend: No such file or directory. Is xend running? Il 03/02/2012 09:08, Linus van Geuns ha scritto:> Hey Ric, > > On Thu, Feb 2, 2012 at 10:30 AM, Riccardo Orfei<r.orfei@mclink.it> wrote: >> Hi Linus! >> >> First of all, thanks a lot for taking the time to write down your >> suggestion... >> >> Well I am pretty sure that the hypervisor is running, because I see >> (flushing rapidly) a certain number of "(XEN) blabla" lines at boot time. >> >> Next, I checked the /sys/xen/capabilities file, which contains the string >> "control-d", and, as a xen-user (Eva) said earlier, it means that the >> hypervisor is in control. >> >> My (un)educated guess is that some (virtual) disk driver is missing or >> misplaced... > Sorry, somehow I must have skiped over that part in your emails. > > So, when booting your system with (Xen) hypervisor, what is the result > of the following commands: > lsb_release -a > uname -a > ls -lh /sys/hypervisor/ > xm info > xm list > > Regards, Linus >
I laughed when I saw the title of this thread, because it does seem that xen - when installed from the debian packages on squeeze - is broken in some fundamental places, which is why we''ve had to move to openSUSE for dom0 Domain locking does not work, and neither does and tapdisk2 - which is useful if you want to run a Windows HVM from a VHD file... There may be other things, as well! But in your case, I''d start by running xm list If you get this... WARNING! Can''t find hypervisor information in sysfs! Error: Unable to connect to xend: No such file or directory. Is xend running? ...then you have a problem with grub2, at the very least, which I solve by mv /etc/grub.d/20_linux_xen /etc/grub.d/07_linux_xen update-grub2 Regards On Wed, 2012-01-18 at 18:35 +0100, Riccardo Orfei wrote:> I am trying to set up xen 4.0 on a debian system with a dual AMD64 CPU. > > I installed linux-image-2.6.32-5-xen-amd64 and > xen-hypervisor-4.0-amd64. > > When I boot, everything seems OK, but xend is not there. > > The log says (last two lines): > > xs_handle = xen.lowlevel.xs.xs() > Error: (2, ''No such file or directory'') > > So I am asking: > what file is presumably missing or what should I do to make xend start. > > TIA, > Ric-- Dominic Mason <dominic@opusvl.com> OpusVL