I may be way off course here, but this may be of some use:
I upgraded one of my testbed machines yesterday and found that I had to
manually upgrade from Xen 3.x to Xen 4.0. Once this was complete, I
found that I was unable to start xend with "/etc/init.d/xend start".
After some digging around, I found some errors pertaining to xenfs. I
rebooted and carefully inspected my GRUB (now GRUB2!) menu list and
found that while the first entry, "Debian GNU/Linux, with Linux
2.6.32-5-xen-686" was highlighted, there was another similar entry
below: "Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN 4.0-i386".
Booting with the latter allowed xend to start.
Best of luck with your problem!
On Thu, 2011-02-17 at 11:48 +0100, Alexander Solovyov wrote:
> I've updated my system from debian lenny to squeeze, got xen 4.0 and
> kernel 2.6.32.
> When I'm trying to start xen (running "xend start" or
> "/etc/init.d/xend start"), xend-debug.log is filled with such
> Xend started at Thu Feb 17 12:16:42 2011.
> 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
> [...a lot of similar lines skipped...]
> After that I can see "xend start" in list of processes; doing another
> "xend start" adds another process.
> xend status exits with status code 3. xend stop does nothing.
> Creation of new domain does not work as well:
> root@enclave:~# xm create -c test
> Using config file "/etc/xen/test".
> Error: Device 51713 (vbd) could not be connected. Hotplug scripts not working.
> /etc/xen/test contents:
> kernel = "/boot/vmlinuz-2.6.32-5-xen-amd64"
> memory = 128
> name = "test-vm0"
> root = "/dev/xvda1 ro"
> #vif = [ 'mac=aa:00:00:00:00:d2, bridge=eth0' ]
> disk = [ 'phy:/dev/virt/test,xvda1,w' ]
> >From what I've found in the web which can be a problem:
> - I have /etc/udev/rules.d/92-xen-backend.rules, so probably this is
> not a problem.
> - My /proc/sys/kernel/hotplug is empty, can this be a problem?
> Anything else I can provide to describe this situation? Any ideas what to do?
Xen-users mailing list