Re: device/udev problem

Re: device/udev problem

[Stephan Böni]

> Does anyone know the problem with missing device nodes (like /dev/hda1) in domU?
> 
> Must the device nodes used in domU exist in the dom0?
> 
> What i have to do, when some device nodes are missing in domU?
> 

OK, no answer - other question: Has anyone created a domU with Xen3 successfully?

Stephan

Re: device/udev problem

[stoeni]

Stephan Böni schrieb:
> OK, no answer - other question: Has anyone created a domU with Xen3 successfully?

sometimes :) i'm waiting for some fixes an will try the unstable sources
the next days.

on sunday i got three domU's up and running, one did the whole night
kernel compile (and delete afterwards), the other two domU's did rsync
themselves the whole night. simple load test. all domains on a workload
of five but not probs. then i tried the sources from monday ... erhm .. ;-)

-- 
Tschaw/2,
Stoeni!

++ Please remember: rm -rf means "read mail -really fast" ++

Re: device/udev problem

[Kurt Garloff]

[-- Attachment #1.1: Type: text/plain, Size: 889 bytes --]

Hi Stephan,

On Wed, Oct 19, 2005 at 01:44:23PM +0200, Stephan Böni wrote:
> > Does anyone know the problem with missing device nodes (like /dev/hda1) in domU?

I still guess missing hotplug events in dom0, see my other mail.

> > Must the device nodes used in domU exist in the dom0?

No. They are unrelated.

> > What i have to do, when some device nodes are missing in domU?
> 
> OK, no answer - other question: Has anyone created a domU with Xen3 successfully?

I do it very often.
After some time, xenbus seems to get stuck however, and then the hotplug
events don't seem to get through any longer.
Rebooting helps against this.

Best,
-- 
Kurt Garloff                   <kurt@garloff.de>             [Koeln, DE]
Physics:Plasma modeling <garloff@plasimo.phys.tue.nl> [TU Eindhoven, NL]
Linux: SUSE Labs (Director)    <garloff@suse.de>            [Novell Inc]

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: device/udev problem

[Ewan Mellor]

On Wed, Oct 19, 2005 at 02:20:09PM +0200, Kurt Garloff wrote:

> After some time, xenbus seems to get stuck however, and then the hotplug
> events don't seem to get through any longer.
> Rebooting helps against this.

Do you issue xm block-detach commands?  There is a known bug here that would
cause such behaviour.  If you are not doing this, I would be interested to
know, because that would be an unknown bug, and would be worth tracking down.

Cheers,

Ewan.

Re: device/udev problem

[Gerd Knorr]

Ewan Mellor wrote:
> On Wed, Oct 19, 2005 at 02:20:09PM +0200, Kurt Garloff wrote:
> 
>> After some time, xenbus seems to get stuck however, and then the hotplug
>> events don't seem to get through any longer.
>> Rebooting helps against this.
> 
> Do you issue xm block-detach commands?  There is a known bug here that would
> cause such behaviour.  If you are not doing this, I would be interested to
> know, because that would be an unknown bug, and would be worth tracking down.

I see that behavior as well, after some time setting up block devices 
stops working (maybe network too, can't test that due to vbd not working 
and my domU's not booting any more).  Restarting xend doesn't help.  I 
don't use "xm block-*" commands.

cheers,

   Gerd

Re: device/udev problem

[Kurt Garloff]

[-- Attachment #1.1: Type: text/plain, Size: 689 bytes --]

Hi Gerd, Ewan,

On Wed, Oct 19, 2005 at 03:43:38PM +0200, Gerd Knorr wrote:
> Ewan Mellor wrote:
> >Do you issue xm block-detach commands?  There is a known bug here that would
> >cause such behaviour.  If you are not doing this, I would be interested to
> >know, because that would be an unknown bug, and would be worth tracking 
> >down.
> 
> I see that behavior as well, after some time setting up block devices 
> stops working (maybe network too, can't test that due to vbd not working 
> and my domU's not booting any more).  Restarting xend doesn't help.  I 
> don't use "xm block-*" commands.

Same here.

Best,
-- 
Kurt Garloff, Director SUSE Labs, Novell Inc.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: device/udev problem

[Matt Ayres]

Gerd Knorr wrote:
> Ewan Mellor wrote:
>> On Wed, Oct 19, 2005 at 02:20:09PM +0200, Kurt Garloff wrote:
>>
>>> After some time, xenbus seems to get stuck however, and then the hotplug
>>> events don't seem to get through any longer.
>>> Rebooting helps against this.
>>
>> Do you issue xm block-detach commands?  There is a known bug here that 
>> would
>> cause such behaviour.  If you are not doing this, I would be 
>> interested to
>> know, because that would be an unknown bug, and would be worth 
>> tracking down.
> 
> I see that behavior as well, after some time setting up block devices 
> stops working (maybe network too, can't test that due to vbd not working 
> and my domU's not booting any more).  Restarting xend doesn't help.  I 
> don't use "xm block-*" commands.
> 

Was this using udev or hotplug for dom0 device manipulation?

Re: device/udev problem

[Gerd Hoffmann]

> 
> Gerd Knorr wrote:
>> Ewan Mellor wrote:
>>> On Wed, Oct 19, 2005 at 02:20:09PM +0200, Kurt Garloff wrote:
>>>
>>>> After some time, xenbus seems to get stuck however, and then the
>>>> hotplug
>>>> events don't seem to get through any longer.
>>>> Rebooting helps against this.
>>>
>>> Do you issue xm block-detach commands?  There is a known bug here
>>> that would
>>> cause such behaviour.  If you are not doing this, I would be
>>> interested to
>>> know, because that would be an unknown bug, and would be worth
>>> tracking down.
>>
>> I see that behavior as well, after some time setting up block devices
>> stops working (maybe network too, can't test that due to vbd not
>> working and my domU's not booting any more).  Restarting xend doesn't
>> help.  I don't use "xm block-*" commands.
>>
> 
> Was this using udev or hotplug for dom0 device manipulation?

udev IIRC, but I think that one has been fixed months ago ...

cheers,

  Gerd

-- 
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg

device/udev problem

[Stephan Böni]

[-- Attachment #1.1: Type: text/plain, Size: 222 bytes --]

Does anyone know the problem with missing device nodes (like /dev/hda1) in domU?
 
Must the device nodes used in domU exist in the dom0?
 
What i have to do, when some device nodes are missing in domU?
 
Stephan
 

[-- Attachment #1.2: Type: text/html, Size: 1126 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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