Re: [Xen-users] Error: Device 0 not connected

["Todd Deshane" <deshantm@xxxxxxxxx>]

On Feb 1, 2008 12:16 PM, Code Monkey <have.an.email@xxxxxxxxx> wrote:

Hi,

I'm new to Xen and I've set up a few domUs using Debian (I suspect
there may be a problem there, see at end).

To begin with everything worked OK, I rebooted domUs without any
problems, but twice now when I try when I try to restart or shutdown a
domain, the xm command locks up.

# xm list
Error: Device 0 not connected
Usage: xm list [options] [Domain, ...]

List information about all/some domains.
 -l, --long                     Output all VM details in SXP
 --label                        Include security labels

First time this happened was when I shutdown -r from inside a domU,
the domU never restarted, I rebooted the dom0, everything came up OK.
Then I created a new domU for testing and did an xm shutdown without
ever logging in, it happened again.

The domUs I did not shut down continue to work, and xentop continues
to work, though it displays

Found interface vif4.0 but domain 4 does not exist.
Found interface vbd-4-2050 but domain 4 does not exist.
Found interface vbd-4-2049 but domain 4 does not exist.
vbd-4-2050 is VBD.
vbd-4-2049 is VBD.
vbd-3-2050 is VBD.
vbd-3-2049 is VBD.
vbd-2-2050 is VBD.
vbd-2-2049 is VBD.
vbd-1-2050 is VBD.
vbd-1-2049 is VBD.

where 4 references the domU I shut down.

Since the domU I shut down had disappeared drom xentop, I tried
starting it again with xm create. When I tried with more memory
allotted in the cfg file (my original problem was that I wanted more
than 128MB RAM) I got

Error: The privileged domain did not balloon!

(logs saying

[2008-02-01 16:56:00 xend 2254] DEBUG (balloon:133) Balloon: 131852
KiB free; 0 to scrub; need 262144; retries: 20.
[2008-02-01 16:56:00 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1372 MiB.
[2008-02-01 16:56:00 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1372 MiB.
[2008-02-01 16:56:00 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1372 MiB.
[2008-02-01 16:56:00 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1372 MiB.
[2008-02-01 16:56:06 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1373 MiB.
[2008-02-01 16:56:06 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1373 MiB.
[2008-02-01 16:56:10 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1372 MiB.
[2008-02-01 16:56:10 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1372 MiB.
[2008-02-01 16:56:15 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1372 MiB.
[2008-02-01 16:56:15 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1372 MiB.
[2008-02-01 16:56:19 xend 2254] DEBUG (balloon:148) Balloon: setting
dom0 target to 1373 MiB.
[2008-02-01 16:56:19 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1014) Setting memory target of domain Domain-0 (0) to
1373 MiB.
[2008-02-01 16:56:21 xend.XendDomainInfo 2254] ERROR
(XendDomainInfo:202) Domain construction failed
)

When I tried with the same amount RAM as previously, I got

Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

(logs saying
[2008-02-01 18:00:23 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:933) XendDomainInfo.handleShutdownWatch
[2008-02-01 18:00:23 xend 2254] DEBUG (DevController:143) Waiting for
devices vif.
[2008-02-01 18:00:23 xend 2254] DEBUG (DevController:149) Waiting for 0.
[2008-02-01 18:00:23 xend 2254] DEBUG (DevController:464)
hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status.
[2008-02-01 18:02:03 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1449) XendDomainInfo.destroy: domid=6
[2008-02-01 18:02:03 xend.XendDomainInfo 2254] DEBUG
(XendDomainInfo:1457) XendDomainInfo.destroyDomain(6)
)


I had previously upgraded the dom0 from the original etch to lenny,
which did not go so well because the tls library reappeared, and I got
scared because I couldn't find the xen kernels for lenny, so I'm still
running the etch kernels. It is possible that the xen-tools come from
lenny. Could this be the problem? If so should I try pushing forward
to lenny (does Xen even work on default lenny without recompiling Xen
from scratch?) or should I start over with a clean etch ? If that
version mismatch isn't it, then I'm at a loss how to debug further,
perl debug isn't my forte.

There does need to be a (close) match between the xen tools (not the xen-tools package), but xm, xend, etc. (i think this is in the xen-utils package typically...) need to be compatible to the dom0 and xen hypervisor version. I am not sure how close the match has to be, but it used to be the case that they had to be the same.

I am not sure which setup to recommend. It depends on what you are trying to do. If you don't need newer kernel support going with the etch packages should be fine. If you need newer kernel support then do an upgrade carefully and keep better track of what you have installed etc.

Best of luck,
Todd

 

Thanks for any help.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users