From: David F Barrera <dfbp@us.ibm.com>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Ewan Mellor <ewan@xensource.com>
Subject: RE: Hotplug scripts not working... xen/ia64 domU stopped working
Date: Fri, 02 Dec 2005 15:22:20 -0600 [thread overview]
Message-ID: <1133558540.25147.1.camel@dbarrera_tp> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD587600D@cacexc12.americas.cpqcorp.net>
I wonder if what I am seeing is the same problem described in this
thread. I am unable to create domUs on an x86_64 box, something which I
had been able to do even this morning:
VmError: Device 2070 (vbd) could not be connected. Backend device not
found.
[2005-12-02 15:11:25 xend] DEBUG (DevController:119) Waiting for devices
vif.
[2005-12-02 15:11:25 xend] DEBUG (DevController:125) Waiting for 0.
[2005-12-02 15:11:25 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2005-12-02 15:11:25 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status.
[2005-12-02 15:11:25 xend] DEBUG (DevController:415)
hotplugStatusCallback 1.
[2005-12-02 15:11:25 xend] DEBUG (DevController:119) Waiting for devices
usb.
[2005-12-02 15:11:25 xend] DEBUG (DevController:119) Waiting for devices
vbd.
[2005-12-02 15:11:25 xend] DEBUG (DevController:125) Waiting for 2070.
[2005-12-02 15:11:25 xend] DEBUG (DevController:398)
hotplugStatusCallback /local/domain/0/backend/vbd/1/2070/hotplug-
status.[2005-12-02 15:11:25 xend] DEBUG (DevController:415)
hotplugStatusCallback 3.
[2005-12-02 15:11:25 xend] ERROR (SrvBase:87) Request wait_for_devices
failed.
Traceback (most recent call last):
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/web/SrvBase.py", line 85,
in perform
return op_method(op, req)
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/xend/server/SrvDomain.py",
line 72, in op_wait_for_devices
return self.dom.waitForDevices()
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py",
line 1276, in waitForDevices
self.waitForDevices_(c)
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/xend/XendDomainInfo.py",
line 923, in waitForDevices_
return self.getDeviceController(deviceClass).waitForDevices()
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/xend/server/DevController.py", line 121, in waitForDevices
return map(self.waitForDevice, self.deviceIDs())
File "/tmp/xen-
unstable.hg/dist/install/usr/lib64/python/xen/xend/server/DevController.py", line 137, in waitForDevice
raise VmError("Device %s (%s) could not be connected. "
VmError: Device 2070 (vbd) could not be connected. Backend device not
found.
On Fri, 2005-12-02 at 12:40 -0800, Magenheimer, Dan (HP Labs Fort
Collins) wrote:
> > Anyway, I'd be inclined to try the new changesets (not yet
> > pushed to the public
> > tree) and see if that improves things.
>
> Same problem and same workaround on tip (8169). Please
> email when your new changesets get pushed and I will
> try them.
>
> > > My /etc/xen/xmdefconfig is very short:
> > > kernel = "/tmp/xenlinux"
> > > memory = 256
> > > nics=0
> > > disk = ['phy:loop0,hda1,w'] # <-change to w!
> > >
> > > and after a fresh boot, I am simply doing:
> > >
> > > # lomount -t ext2 -diskimage /var/xen/hda /mnt
> > > # xend start
> > > # xm create
> > >
> > > I can see how it could be interpreted that loop0 is
> > > being used both by domain0 and the newly created domain,
> > > but isn't this a common use model?
> >
> > Only if you want to corrupt your filesystem! Writing to that
> > file via /mnt
> > in dom0 and via /dev/hda1 in the guest ought to corrupt your
> > fs nicely.
>
> Not as long as the image is only used from domU, correct?
>
> What is the proper use model? As I noted previously,
> disk = ['file:/var/xen/hda,hda1,w'] results in a Linux
> error message ("UDF-fs: No VRS found"... and, no, I do
> not have any CD's in /etc/fstab!). Am I spelling
> this xmdefconfig entry incorrectly? Or is there
> a better way to use a disk-in-a-file as root disk for
> a guest domain?
>
> Thanks,
> Dan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
next prev parent reply other threads:[~2005-12-02 21:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 20:40 Hotplug scripts not working... xen/ia64 domU stopped working Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 21:22 ` David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-03 20:31 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 17:41 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 20:17 ` Ewan Mellor
2005-12-02 0:54 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 0:39 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-02 0:51 ` Ewan Mellor
2005-12-01 21:54 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01 23:31 ` Ewan Mellor
2005-12-01 20:49 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01 23:38 ` Ewan Mellor
2005-12-02 0:53 ` Adam Heath
2005-12-02 1:44 ` Ewan Mellor
2005-12-02 2:16 ` Adam Heath
2005-11-30 21:13 Magenheimer, Dan (HP Labs Fort Collins)
2005-12-01 1:01 ` Ewan Mellor
2005-11-30 16:56 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 18:10 ` Himanshu Raj
2005-11-30 16:48 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 16:53 ` Ryan Harper
2005-11-30 17:16 ` Ewan Mellor
2005-11-30 17:22 ` Ewan Mellor
2005-11-30 14:26 Petersson, Mats
2005-12-01 0:26 ` Hotplug scripts not working... xen/ia64 domU?stopped working Horms
2005-11-30 14:17 Hotplug scripts not working... xen/ia64 domU stopped working Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 5:50 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 4:43 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-30 11:52 ` Ewan Mellor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133558540.25147.1.camel@dbarrera_tp \
--to=dfbp@us.ibm.com \
--cc=dan.magenheimer@hp.com \
--cc=ewan@xensource.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.