[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Bug#674161: xcp-xapi: 'the device disappeared from xenstore' message during vbd-plug (vm-start)

On Monday 28 May 2012 07:28 PM, George Shuklin wrote:
> On 23.05.2012 23:24, George Shuklin wrote:
>> On 23.05.2012 22:44, Dave Scott wrote:
>>> xenstore-write /local/domain/0/vm hello
>> Yes, it plugged successfully (at least no error messages).
>> I saw that code in  device.ml (where exception was raised), it seems
>> be checking that path in xenstore:
>>                 (* Sanity check: ensure the backend domain exists *)
>>                 let _ =
>>                         try
>>                                 let (_: string) = t.Xst.read (sprintf
>> "/local/domain/%d/vm" device.backend.domid) in
>>                                 ()
>>                         with Xenbus.Xb.Noent ->
>>                                 raise (Device_backend_vanished
>> device) in
>> But even I was successfull, I unable to perform any IO in guest
>> domain (I've get into initrd but I see no /dev/xvd* devices and no
>> messages in dmesg related to new device).
> I was wrong about this. Workaround 'xenstore-write /local/domain/0/vm
> something' works and new device is available in guest domain. There is
> a separate problem with networking I'll report separately.
> Now but description is looking like this:
> xcp-xapi package does not write dom0 uuid in xenstore upon startup.
> This prevents normal device initialization.
We hit the same problem in our labs.  And can confirm that the
workaround, 'xenstore-write /local/domain/0/vm something', does solve
the problem.

Are you targeting this fix for Wheezy?

Ritesh Raj Sarraf | Linux SAN Engineering | NetApp Inc.

Attachment: signature.asc
Description: OpenPGP digital signature

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.