|
Well, I managed to clear the 'device could not be connected' issues by upgrading udev. I'm not sure if SuSE does something funny with the RPM version, or if the 068 version has some issue, but upgrading to 077 seems to fix that message.
But, I have a new problem. Now, when I go to boot the guests, the kernel boots and then the system just hangs. When I say hangs, I mean it is totally dead - console, SSH, everything. Attached is the output from the guest boot, which seems fairly normal. I'm also trying to watch all the log files to see if anything gets logged, but so far those look normal. Any suggestions on this one? Seems like maybe I need to disable something in the kernel somewhere, but I don't know what. BTW, I did remove the dom0_mem directive from the startup...
Thanks
Nick Couchman
Systems Integrator
SEAKR Engineering, Inc.
6221 South Racine Circle
Centennial, CO 80111
Main: (303) 790-8499
Fax: (303) 790-8720
Web: http://www.seakr.com
,
>>> On 2005/12/16 at 14:51:21, "Jamie Moore" <jmoore@xxxxxxxxxx> wrote:
Mine was the same way, any device caused this error. In fact my problems
was right when the guest was booting, after the kernel image was
uncompressed and it tried to mount the device it failed. We could be
talking about the same error. Try rebooting the host machine without the
memory directive in grub and see if it works.
Regards,
Jamie Moore
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nick
Couchman
Sent: Friday, December 16, 2005 1:19 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Error: Device ... could not be
connected.Hotplugscripts not working.
I'll give it a try, but this is actually happening on two different
systems. One has dom0_mem set to 131072 and one has dom0_mem set to
262144. It also isn't limited to the NIC, it seems to be any device
that the guest tries to access.
Thanks,
Nick Couchman
Systems Integrator
SEAKR Engineering, Inc.
6221 South Racine Circle
Centennial, CO 80111
Main: (303) 790-8499
Fax: (303) 790-8720
Web: http://www.seakr.com
>>> "Jamie Moore" <jmoore@xxxxxxxxxx> >>>
I got this same error but only when I set a Dom0 memory limit in the
host grup config (i.e. dom0_mem=...) I had mine set to 131072. I never
tried a different value but always when I had that one I got this error.
When I removed that it went away and the guest Nic booted fine. Not sure
if this is the same problem you have but it could be related and
possibly this points you somewhere :)
Regards,
Jamie Moore
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Nick
Couchman
Sent: Friday, December 16, 2005 1:10 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Error: Device ... could not be connected.
Hotplugscripts not working.
Well, it feels like I've been very needy lately, but I'm getting very
frustrated trying to get Xen 3 to work. My latest problem is errors
connecting devices. If I have a network card present in my domU
configuration, I get the following error message on the command line:
Error: Device 0 (vif) could not be connected. Hotplug scripts not
working.
If I set the configuration so that there are no NICs in the domU, I
receive the following error message, instead:
Error: Device 769 (vbd) could not be connected. Hotplug scripts not
working.
I have tried adding lines to the /etc/xen/scripts/block script (and
other scripts) to debug it, including redirecting stderr output to
another file, but I don't get anything logged in the file. There is
nothing to do with either udev or hotplug in my /var/log/messages file.
I have udev 068, so the Xen installer installed the files necessary for
using udev instead of hotplug. I've verified that the udev rule file is
installed in the correct place, and udevd is running:
xen-server00:~ # ps -ef | grep udev
root 4384 1 0 13:58 ? 00:00:00 /sbin/udevd --daemon
I've been through the list archives - both the user list and the
developer list - looking for solutions, but none of the postings seem to
apply to my situation, or at least trying the suggestions in those
posting haven't gotten me anywhere. I'm running a clean, lean install
of SuSE10. I didn't install the SuSE RPM's for XEN, I downloaded the
XEN source and built everything from source. Right now the only thing
I'm trying to run is the simple ttylinux image provided on the XEN site
for testing. I've attached the files xend.log, xend-debug.log,
xend.trace (bzipped), and the domain configuration file (ttylinux). Can
someone point out what in the world I'm missing that's causing this
headache?
Also, I've verified that I have the necessary packages installed.
bridge-utils is installed, and a quick glance at both "brctl show" and
"ifconfig -a" show the the ethernet interfaces are being connected. The
problems with the vbd seem to indicate that this isn't limited to
networking, though.
Thanks,
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
