Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. My config files says sda7 maps to /dev/sda7 eg: disk = [ ''phy:sda7,sda7,w'' ] root = "/dev/sda7 ro" My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. Can anyone confirm/deny this? thanks James
> Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. > > My config files says sda7 maps to /dev/sda7 eg: > > disk = [ ''phy:sda7,sda7,w'' ] > root = "/dev/sda7 ro" > > My only thought is that maybe devfs is confusing the > issue... eg there are no scsi devices so sda7 doesn''t appear in > /dev.I think you are the first person to try using devfs, so it might take a bit of debugging, but should be possible to make work. Are you using devfs in both dom0 and guest domains? If dom0 hasn''t got a /dev/sda7 I''m surprised the tools are letting you proceed as they need to lookup /dev/sda7 to discover the major,minor (8,7). I believe devfs creates links for the old /dev/sdXX names though, right? Within the new guest, it will have had a block device plumbed through to it appearing as major,minor = 8,7. When it parses it''s root= command line, it will lookup the name ''sda'' in the grim table appearing in init/do_mounts.c, and associate that with 8,7 hence everything should work from a kernel POV. When the startup scripts go through your fstab and remount root that''s a different matter, and it''s possible that the 8,7 device hasn''t been properly registered with devfs. Does it the guest get this far? Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. > > My config files says sda7 maps to /dev/sda7 eg: > > disk = [ ''phy:sda7,sda7,w'' ] > root = "/dev/sda7 ro" > > My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. > > Can anyone confirm/deny this?We make no effort to make ''logical'' devices appear in devfs --- if it doesn''t happen automatically then code needs to be added to do it manually. Is devfs still alive in 2.6, or have they moved to some other scheme? -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink? After my next reboot i''ll try making /dev/sda7 a proper device node. After dom1 crashes and burns, I don''t seem to be able to kill it (xm destroy 1), or create it again, so I have to reboot. doh. Also, make menuconfig for xenU flashes an error on the screen but otherwise works unless I try to look in SCSI where I get this message: Menuconfig has encountered a possible error in one of the kernel''s configuration files and is unable to continue. Here is the error report: Q> scripts/Menuconfig: line 832: MCmenu53: command not found Please report this to the maintainer <mec@shout.net>. You may also send a problem report to <linux-kernel@vger.kernel.org>. Please indicate the kernel version you are trying to configure and which menu you were trying to enter when this error occurred. James From: Keir Fraser Sent: Wed 30/06/2004 4:43 PM To: James Harper Cc: xen-devel@lists.sourceforge.net Subject: Re: [Xen-devel] can''t mount root... devfs???> Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. > > My config files says sda7 maps to /dev/sda7 eg: > > disk = [ ''phy:sda7,sda7,w'' ] > root = "/dev/sda7 ro" > > My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. > > Can anyone confirm/deny this?We make no effort to make ''logical'' devices appear in devfs --- if it doesn''t happen automatically then code needs to be added to do it manually. Is devfs still alive in 2.6, or have they moved to some other scheme? -- Keir
Turns out devfs is obsolete in 2.6 to be replaced by udev, which is supposed to be rather nicer to work with. I don''t think I''ll be trying to emulate /dev/scsi/host0/bus0/target5/lun0/part7 style names with the Xen backend driver. As for your DOM0 issue, what do you get if you run ''/sbin/sfdisk -d /dev/sda'' ? You should get lines of the form: /dev/sda3 : start= 16948575, size=16836120, Id=83, bootable Perhaps you are getting the primary devfs names, in which case we can fix by modifying our matching regexp. -- Keir> devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! > > it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink? > > After my next reboot i''ll try making /dev/sda7 a proper device node. After dom1 crashes and burns, I don''t seem to be able to kill it (xm destroy 1), or create it again, so I have to reboot. doh. > > Also, make menuconfig for xenU flashes an error on the screen but otherwise works unless I try to look in SCSI where I get this message: > > Menuconfig has encountered a possible error in one of the kernel''s > configuration files and is unable to continue. Here is the error > report: > Q> scripts/Menuconfig: line 832: MCmenu53: command not found > Please report this to the maintainer <mec@shout.net>. You may also > send a problem report to <linux-kernel@vger.kernel.org>. > Please indicate the kernel version you are trying to configure and > which menu you were trying to enter when this error occurred. > > James > > > > > > From: Keir Fraser > Sent: Wed 30/06/2004 4:43 PM > To: James Harper > Cc: xen-devel@lists.sourceforge.net > Subject: Re: [Xen-devel] can''t mount root... devfs??? > > > > Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. > > > > My config files says sda7 maps to /dev/sda7 eg: > > > > disk = [ ''phy:sda7,sda7,w'' ] > > root = "/dev/sda7 ro" > > > > My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. > > > > Can anyone confirm/deny this? > > We make no effort to make ''logical'' devices appear in devfs --- if > it doesn''t happen automatically then code needs to be added to do it > manually. > > Is devfs still alive in 2.6, or have they moved to some other scheme? > > -- Keir-=- MIME -=- --_03EC8C21-3324-4C90-85C6-3C4D454655EF_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink? After my next reboot i''ll try making /dev/sda7 a proper device node. After dom1 crashes and burns, I don''t seem to be able to kill it (xm destroy 1), or create it again, so I have to reboot. doh. Also, make menuconfig for xenU flashes an error on the screen but otherwise works unless I try to look in SCSI where I get this message: Menuconfig has encountered a possible error in one of the kernel''s configuration files and is unable to continue. Here is the error report: Q> scripts/Menuconfig: line 832: MCmenu53: command not found Please report this to the maintainer <mec@shout.net>. You may also send a problem report to <linux-kernel@vger.kernel.org>. Please indicate the kernel version you are trying to configure and which menu you were trying to enter when this error occurred. James From: Keir Fraser Sent: Wed 30/06/2004 4:43 PM To: James Harper Cc: xen-devel@lists.sourceforge.net Subject: Re: [Xen-devel] can''t mount root... devfs???> Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. >=20 > My config files says sda7 maps to /dev/sda7 eg: >=20 > disk =3D [ ''phy:sda7,sda7,w'' ] > root =3D "/dev/sda7 ro" >=20 > My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. >=20 > Can anyone confirm/deny this?We make no effort to make ''logical'' devices appear in devfs --- if it doesn''t happen automatically then code needs to be added to do it manually. Is devfs still alive in 2.6, or have they moved to some other scheme? -- Keir --_03EC8C21-3324-4C90-85C6-3C4D454655EF_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <HTML><HEAD></HEAD> <BODY> <DIV id=3DidOWAReplyText89384 dir=3Dltr> <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!!</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2>it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink?</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2>After my next reboot i''ll try making /dev/sda7 a proper device node. After dom1 crashes and burns, I don''t seem to be able to kill it (xm destroy 1), or create it again, so I have to reboot. doh.</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2>Also, make menuconfig for xenU flashes an error on the screen but otherwise works unless I try to look in SCSI where I get this message:</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2><BR>Menuconfig has encountered a possible error in one of the kernel''s<BR>configuration files and is unable to continue. Here is the error<BR>report:</DIV> <DIV dir=3Dltr> Q> scripts/Menuconfig: line 832: MCmenu53: command not found</DIV> <DIV dir=3Dltr>Please report this to the maintainer <<A href=3D"mailto:mec@shout.net" target=3D_blank>mec@shout.net</A>>. You may also<BR>send a problem report to <<A href=3D"mailto:linux-kernel@vger.kernel.org" target=3D_blank>linux-kernel@vger.kernel.org</A>>.</DIV> <DIV dir=3Dltr>Please indicate the kernel version you are trying to configure and<BR>which menu you were trying to enter when this error occurred.</DIV> <DIV dir=3Dltr></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2>James</FONT></DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV> <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT> </DIV></DIV> <DIV dir=3Dltr><BR> <HR tabIndex=3D-1> <FONT face=3DTahoma size=3D2><B>From:</B> Keir Fraser<BR><B>Sent:</B> Wed 30/06/2004 4:43 PM<BR><B>To:</B> James Harper<BR><B>Cc:</B> xen-devel@lists.sourceforge.net<BR><B>Subject:</B> Re: [Xen-devel] can''t mount root... devfs???<BR></FONT><BR></DIV> <DIV><PRE style=3D"WORD-WRAP: break-word">> Domain1 is now not booting anymore, and the boot console tells me it''s because it can''t mount /dev/sda7. >=20 > My config files says sda7 maps to /dev/sda7 eg: >=20 > disk =3D [ ''phy:sda7,sda7,w'' ] > root =3D "/dev/sda7 ro" >=20 > My only thought is that maybe devfs is confusing the issue... eg there are no scsi devices so sda7 doesn''t appear in /dev. >=20 > Can anyone confirm/deny this? We make no effort to make ''logical'' devices appear in devfs --- if it doesn''t happen automatically then code needs to be added to do it manually. Is devfs still alive in 2.6, or have they moved to some other scheme? -- Keir </PRE></DIV></BODY></HTML> --_03EC8C21-3324-4C90-85C6-3C4D454655EF_-- ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! > > it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink?Possibly, though we always used to look through links; don''t know about the new tools, but this could be the issue. Could you try a devfs dom0 and standard dom1?> After my next reboot i''ll try making /dev/sda7 a proper device node. After dom1 crashes and burns, I don''t seem to be able to kill it (xm destroy 1), or create it again, so I have to reboot. doh.Is this with the latest repo? I think some changes that went in last night finally got this functionality working again.> Also, make menuconfig for xenU flashes an error on the screen but otherwise works unless I try to look in SCSI where I get this message: > Menuconfig has encountered a possible error in one of the kernel''s > configuration files and is unable to continue. Here is the > errorThere''s something broken with the arch/xen/config.in but I just can''t spot it. The error messages from the Linux config system are so spectacularly unhelpful that it''s impossible to debug. Fortunately, the error message doesn''t actually seem to obviously break anything, though I have noticed xconfig do strange things if you ever visit the SCSI config pages. I think we need to revert to the standard i386 one, and then just add back in the Xen specific options. Anyone fancy a really boring but important job? ;-) Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I believe DevFS is officially deprecated in 2.6. They''re looking to replace it with udev, which is a userspace daemon that creates device nodes on your existing filesystem when it detects and identifies devices using mechanisms including the new sysfs. Amongst other things, this allows for more flexible naming policy for device nodes. It is still in 2.6 but I think they want to get rid of it eventually. Cheers, Mark ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I believe DevFS is officially deprecated in 2.6. They''re looking to replace > it with udev, which is a userspace daemon that creates device nodes on your > existing filesystem when it detects and identifies devices using mechanisms > including the new sysfs. Amongst other things, this allows for more flexible > naming policy for device nodes. > > It is still in 2.6 but I think they want to get rid of it eventually.It turns out that most kernel developers hate devfs. And fortunately it''s rabid naming schemes (e.g., /dev/scsi/host/bus/lun/target/....) are going with it. :-) udev appears to default to using traditional /dev names [hopefully distros will stick to this too]. -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! > > it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink?I''ve just done a simple test where I created a normal symlink pointing to a device node and the control tools followed it fine. I forget how devfs works, but is the major:minor of /dev/scsi/host0/bus0/target5/lun0/part7 08:07 ? If so, I''d have thought it would just work... Could you do an experiment with a non devfs dom1 kernel just to ascertain that the problem is actually with the tools or backend driver in dom0 (or vice versa)? Thanks, Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I''m now recompiling both xen0 and xenU with devfs not compiled in (I had tried booting xenU with devfs=nomount and it didn''t make a difference). One thing I did just notice is now that the xenU config is fixed for SCSI (make menuconfig would crash if you tried to access SCSI), I can actually go in there and enable or disable scsi in the kernel. I assume that even though xen0 is using the scsi device directly, and that i''m exporting /dev/sda7 to xenU, xenU shouldn''t need any scsi block devices at all, is that correct? SCSI was enabled, i''m now trying it with SCSI not selected at all. thanks James From: Ian Pratt Sent: Thu 1/07/2004 9:14 AM To: James Harper Cc: Keir Fraser; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] can''t mount root... devfs???> devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! > > it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink?I''ve just done a simple test where I created a normal symlink pointing to a device node and the control tools followed it fine. I forget how devfs works, but is the major:minor of /dev/scsi/host0/bus0/target5/lun0/part7 08:07 ? If so, I''d have thought it would just work... Could you do an experiment with a non devfs dom1 kernel just to ascertain that the problem is actually with the tools or backend driver in dom0 (or vice versa)? Thanks, Ian
> I''m now recompiling both xen0 and xenU with devfs not compiled in (I had tried booting xenU with devfs=nomount and it didn''t make a difference). > > One thing I did just notice is now that the xenU config is fixed for SCSI (make menuconfig would crash if you tried to access SCSI), I can actually go in there and enable or disable scsi in the kernel. I assume that even though xen0 is using the scsi device directly, and that i''m exporting /dev/sda7 to xenU, xenU shouldn''t need any scsi block devices at all, is that correct? SCSI was enabled, i''m now trying it with SCSI not selected at all. > > thanks > > JamesCorrect --- you don''t need low-level device drivers in xenU. If we were prepared to modify the drivers/scsi/config, we''d remove the low-level driver options when configuring a non-privileged kernel. -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > One thing I did just notice is now that the xenU config is fixed for SCSI (make menuconfig would crash if you tried to access SCSI), I can actually go in there and enable or disable scsi in the kernel. I assume that even though xen0 is using the scsi device directly, and that i''m exporting /dev/sda7 to xenU, xenU shouldn''t need any scsi block devices at all, is that correct? SCSI was enabled, i''m now trying it with SCSI not selected at all. > > Correct --- you don''t need low-level device drivers in xenU. If we > were prepared to modify the drivers/scsi/config, we''d remove the > low-level driver options when configuring a non-privileged kernel.Just to follow up, although you never need SCSI low-level drivers in an unprivileged kernel, there are still occasions where you might want the SCSI core and disk code, for instance when using iSCSI within the domain. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I am once again able to boot a xenU kernel after removing all traces of devfs. *yay* can''t say for sure if it was devfs though as i did a bk pull just before I sent my last email... having booted my new domain, ''xm list'' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though. halting the new domain from the console causes it to disappear from ''xm list'' correctly, but it won''t restart properly, and then ''xm destroy, won''t remove it from ''xm list''. lastly, is there a plan to be able to export a filesystem rather than just block devices, like ''hostfs'' under uml? It would make copying modules over a bit easier! keep up the good work! james From: James Harper Sent: Fri 2/07/2004 12:58 PM To: Ian Pratt Cc: Keir Fraser; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: RE: [Xen-devel] can''t mount root... devfs??? I''m now recompiling both xen0 and xenU with devfs not compiled in (I had tried booting xenU with devfs=nomount and it didn''t make a difference). One thing I did just notice is now that the xenU config is fixed for SCSI (make menuconfig would crash if you tried to access SCSI), I can actually go in there and enable or disable scsi in the kernel. I assume that even though xen0 is using the scsi device directly, and that i''m exporting /dev/sda7 to xenU, xenU shouldn''t need any scsi block devices at all, is that correct? SCSI was enabled, i''m now trying it with SCSI not selected at all. thanks James From: Ian Pratt Sent: Thu 1/07/2004 9:14 AM To: James Harper Cc: Keir Fraser; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] can''t mount root... devfs???> devfs is alive and well in 2.6. there is a udev(?) scheme i think which accomplishes the same sort of thing via a different mechanism, but that is about the extent of my knowledge on it and is probably wrong anyway!!! > > it is the kernel failing to mount /dev/sda7, not userspace. It also fails if I specify root as 0807, so I guess it isn''t a devfs issue on dom1. Dom0 also is using devfs, /dev/sda7 is a symlink to /dev/scsi/host0/bus0/target5/lun0/part7, which is in turn of the right major and minor number. Would xen be failing to work out the device numbers because of the symlink?I''ve just done a simple test where I created a normal symlink pointing to a device node and the control tools followed it fine. I forget how devfs works, but is the major:minor of /dev/scsi/host0/bus0/target5/lun0/part7 08:07 ? If so, I''d have thought it would just work... Could you do an experiment with a non devfs dom1 kernel just to ascertain that the problem is actually with the tools or backend driver in dom0 (or vice versa)? Thanks, Ian
> I am once again able to boot a xenU kernel after removing all traces of devfs. *yay*Excellent. Success stories are good to hear.> can''t say for sure if it was devfs though as i did a bk pull just before I sent my last email...I suspect adding devfs support wouldn''t be too hard, but its probably not high on the list of priorities for us. Do any common distros use it by default?> having booted my new domain, ''xm list'' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though.Not good. I think xend is getting more robust over time.> halting the new domain from the console causes it to disappear from ''xm list'' correctly, but it won''t restart properly, and then ''xm destroy, won''t remove it from ''xm list''.So: you started a domain, halted it, and it correctly disappeared. You then issued the same xm create command to recreate it and it failed to come up. Odd. Any error output from xend or xm?> lastly, is there a plan to be able to export a filesystem rather than just block devices, like ''hostfs'' under uml? It would make copying modules over a bit easier!How about using NFS for the moment? It would be nice to add a super-fast page flipping filesystem interface, but its on the todo list. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I suspect adding devfs support wouldn''t be too hard, but its > probably not high on the list of priorities for us. Do any > common distros use it by default? > > > having booted my new domain, ''xm list'' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though. > > Not good. I think xend is getting more robust over time. >I have seen a number of ''''heisenbugs" with xend. They especially occur when I stop xend and start it again. Every now and then a ''xend start'' does nothing and sends no output to console. Commands such as ''xm list'' will give a ''Connection refused'' error. A ''xend stop'' followed by a ''xend start'' usually fixes this but there have been a few times where I have had to repeat the cycle a couple of times. Also, sometimes after a reboot, a domain creation just fails and the ''xm create'' command does not return. There are no error messages from xend. Even though I suspect that things are hosed at this point in time, a ''xend stop'' works. However xend will not startup again and gives a ''IOError: [Errno 16] Device or resource busy'' error. The problem cannot be reproduced as the same create command works after another reboot. Niraj ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > I suspect adding devfs support wouldn''t be too hard, but its > > probably not high on the list of priorities for us. Do any > > common distros use it by default? > > > > > having booted my new domain, ''xm list'' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though. > > > > Not good. I think xend is getting more robust over time. > > > > I have seen a number of ''''heisenbugs" with xend. They especially occur > when I stop xend and start it again. Every now and then a ''xend start'' > does nothing and sends no output to console. Commands such as ''xm > list'' will give a ''Connection refused'' error. A ''xend stop'' followed > by a ''xend start'' usually fixes this but there have been a few times > where I have had to repeat the cycle a couple of times.Could you try running xend with "xend start_trace". It might give a clue as to what is going wrong if you compare traces. It would be nice to get this nailed. Thanks, Ian> Also, sometimes after a reboot, a domain creation just fails and the > ''xm create'' command does not return. There are no error messages from > xend. Even though I suspect that things are hosed at this point in > time, a ''xend stop'' works. However xend will not startup again and > gives a ''IOError: [Errno 16] Device or resource busy'' error. The > problem cannot be reproduced as the same create command works after > another reboot. > > Niraj > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
If devfs is indeed disappearing in 2.6 then there''s probably not a lot of point adding support for it. Debian can use it, but I don''t think it''s enabled by default. I like the way devfs works but obviously most people don''t. What are the meanings of ''state''? I see dom0 as ''r----'', and dom1 (when it works) appears as ''-b---'', and when it doesn''t it appears with a ''p'' somewhere in there. I would have thought that ''b'' means booting, and it should then progress to ''r'' meaning running. I was thinking about a hostfs option for automatically copying in the modules in at boot time. My network configuration doesn''t actually enable networking until it has started the firewall, which it can''t because the modules aren''t loaded. Being on the todo list sounds promising! James From: Ian Pratt Sent: Sat 3/07/2004 1:21 AM To: James Harper Cc: Ian Pratt; Keir Fraser; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: [Xen-devel] Re: almost working> I am once again able to boot a xenU kernel after removing all traces of devfs. *yay*Excellent. Success stories are good to hear.> can''t say for sure if it was devfs though as i did a bk pull just before I sent my last email...I suspect adding devfs support wouldn''t be too hard, but its probably not high on the list of priorities for us. Do any common distros use it by default?> having booted my new domain, ''xm list'' in dom0 hung for ages with 100% cpu time until I hit ctrl-C. trying it again worked fine though.Not good. I think xend is getting more robust over time.> halting the new domain from the console causes it to disappear from ''xm list'' correctly, but it won''t restart properly, and then ''xm destroy, won''t remove it from ''xm list''.So: you started a domain, halted it, and it correctly disappeared. You then issued the same xm create command to recreate it and it failed to come up. Odd. Any error output from xend or xm?> lastly, is there a plan to be able to export a filesystem rather than just block devices, like ''hostfs'' under uml? It would make copying modules over a bit easier!How about using NFS for the moment? It would be nice to add a super-fast page flipping filesystem interface, but its on the todo list. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> What are the meanings of ''state''? I see dom0 as ''r----'', and dom1 (when it works) appears as ''-b---'', and when it doesn''t it appears with a ''p'' somewhere in there. I would have thought that ''b'' means booting, and it should then progress to ''r'' meaning running. I have some better state-output code that I''ll check in for the ''xm'' tool. Currently, the flag array is ''rbpsc'', where: r: Running b: Blocked (e.g., waiting for I/O) p: Paused DOM0 by control software s: Domain has shut itself down (probably awaiting cleanup by xend) c: Domain crashed inside Xen -- shutdown pending postmortem by xend I have code that actually gives a useful phrase describing the state of the domain in plain English, which might be more useful. :-) -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Sat, Jul 03, 2004 at 08:24:54PM +1000, James Harper wrote:> If devfs is indeed disappearing in 2.6 then there''s probably not a lot of point adding support for it. Debian can use it, but I don''t think it''s enabled by default. I like the way devfs works but obviously most people don''t.Just a note, I believe Andrew Morton confirmed that devfs definitely won''t be disappearing in 2.6. The earliest it would be removed is 2.7, and even that''s not certain. ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, Jul 02, 2004 at 04:21:32PM +0100, Ian Pratt wrote:> So: you started a domain, halted it, and it correctly > disappeared. You then issued the same xm create command to > recreate it and it failed to come up. > > Odd. Any error output from xend or xm?Having just upgraded to r1056 i''m getting this now myself. I''m including screenlogs from the xend tracing, and the operations that caused it. It happens every time, without fail. -- Jody Belka knew (at) pimb (dot) org
On Sat, 3 Jul 2004, James Harper wrote:> If devfs is indeed disappearing in 2.6 then there''s probably not a lot > of point adding support for it. Debian can use it, but I don''t think > it''s enabled by default. I like the way devfs works but obviously most > people don''t.yes, on point in fooling with devfs. It''s dead. ron ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > Not good. I think xend is getting more robust over time. > > I have seen a number of ''''heisenbugs" with xend. They especially occur > when I stop xend and start it again. Every now and then a ''xend start'' > does nothing and sends no output to console. Commands such as ''xm > list'' will give a ''Connection refused'' error. A ''xend stop'' followed > by a ''xend start'' usually fixes this but there have been a few times > where I have had to repeat the cycle a couple of times. > > Also, sometimes after a reboot, a domain creation just fails and the > ''xm create'' command does not return. There are no error messages from > xend. Even though I suspect that things are hosed at this point in > time, a ''xend stop'' works. However xend will not startup again and > gives a ''IOError: [Errno 16] Device or resource busy'' error. The > problem cannot be reproduced as the same create command works after > another reboot.I think many people had been seeing problems of this ilk, so you will probably be delighted to hear that these bugs have been squashed by today''s checkins. It was a combination of a simple stupid bug in the device-driver code, coupled with faulty error handling in xend. -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, Jul 06, 2004 at 05:11:04PM +0100, Keir Fraser wrote:> I think many people had been seeing problems of this ilk, so you will > probably be delighted to hear that these bugs have been squashed by > today''s checkins. > > It was a combination of a simple stupid bug in the device-driver code, > coupled with faulty error handling in xend.Seeing this msg i cloned down the latest (at the time) rev from bk. After rebuilding xen, my dom0 and domU kernels, and all the tools, I tried it out. Unfortunately i couldn''t even start an unpriveleged domain any more. Logs of xend tracing and the relevant command window are attached; hope they''re helpful in tracking down the problem. For reference, this was using rev 40eae953qXVB0VAXac-t2uDXq-tS9Q -- Jody Belka (knew) at (pimb) dot (org)
> Seeing this msg i cloned down the latest (at the time) rev from bk. After > rebuilding xen, my dom0 and domU kernels, and all the tools, I tried it > out. Unfortunately i couldn''t even start an unpriveleged domain any more. > Logs of xend tracing and the relevant command window are attached; hope > they''re helpful in tracking down the problem.Oops. I can confirm I get the same error. And it was all working so well earlier this afternoon... It looks like a timeout talking to the blk device backend driver, which is a bug that was believed fixed earlier today -- sorry folks. Not withstanding this bug, the good news is that we''re beginning to get the first inklings of warm fuzzy feelings about new xend''s stability. I''m afraid a fix will have to wait until tomorrow, though. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > > Seeing this msg i cloned down the latest (at the time) rev from bk. After > > rebuilding xen, my dom0 and domU kernels, and all the tools, I tried it > > out. Unfortunately i couldn''t even start an unpriveleged domain any more. > > Logs of xend tracing and the relevant command window are attached; hope > > they''re helpful in tracking down the problem. > > Oops. > > I can confirm I get the same error. > > And it was all working so well earlier this afternoon... > > It looks like a timeout talking to the blk device backend driver, > which is a bug that was believed fixed earlier today -- sorry > folks. > > Not withstanding this bug, the good news is that we''re beginning > to get the first inklings of warm fuzzy feelings about new xend''s > stability. I''m afraid a fix will have to wait until tomorrow, > though.Somehow related to specifying more than one VBD when creating a new guest. If you specify just one then it works. Hopefully not hard to track down. -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Hi, after booting Xen i am trying to start some domains with the domain control tools. When i type "xend start" File "usr/bin/xend", line 23, in ? from xen.xend.server import SrvDaemon ImportError: no module named xen.xend.server I guess the files are installed in the wrong place, but the "make world" should to this, right? I have manually tried to move the files under /install/ to their right places. Whar can be the error? Regards Rune A ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
You should go to xeno.bk/tools/ and type make install. That will ensure file go in their correct place. Cheers Tom On 7 Jul 2004, at 15:56, Rune Johan Andresen wrote:> Hi, after booting Xen i am trying to start some domains with the > domain control tools. > When i type "xend start" > > File "usr/bin/xend", line 23, in ? > from xen.xend.server import SrvDaemon > ImportError: no module named xen.xend.server > > I guess the files are installed in the wrong place, but the "make > world" should to this, right? I have manually tried to move the files > under /install/ to their right places. Whar can be the error? > > Regards > Rune A > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel >------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Hi, after booting Xen i am trying to start some domains with the domain > control tools. > When i type "xend start" > > File "usr/bin/xend", line 23, in ? > from xen.xend.server import SrvDaemon > ImportError: no module named xen.xend.server > > I guess the files are installed in the wrong place, but the "make > world" should to this, right? I have manually tried to move the files > under /install/ to their right places. Whar can be the error?Please try ''make world'' followed by ''make install''. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Thanks! I must have missed this in the howtos. Sorry, the information is a little distributed :) Do you have any howtos or docs on the new features for the domain control tools? Rune On Jul 7, 2004, at 5:06 PM, Tom Wilkie wrote:> You should go to xeno.bk/tools/ and type make install. That will > ensure file go in their correct place. > > Cheers > > Tom > > On 7 Jul 2004, at 15:56, Rune Johan Andresen wrote: > >> Hi, after booting Xen i am trying to start some domains with the >> domain control tools. >> When i type "xend start" >> >> File "usr/bin/xend", line 23, in ? >> from xen.xend.server import SrvDaemon >> ImportError: no module named xen.xend.server >> >> I guess the files are installed in the wrong place, but the "make >> world" should to this, right? I have manually tried to move the files >> under /install/ to their right places. Whar can be the error? >> >> Regards >> Rune A >> >> >> ------------------------------------------------------- >> This SF.Net email sponsored by Black Hat Briefings & Training. >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital >> self defense, top technical experts, no vendor pitches, unmatched >> networking opportunities. Visit www.blackhat.com >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xen-devel >> > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Tue, 06 Jul 2004 17:11:04 +0100, Keir Fraser <keir.fraser@cl.cam.ac.uk> wrote:> > > Not good. I think xend is getting more robust over time. > > > > I have seen a number of ''''heisenbugs" with xend. They especially occur > > when I stop xend and start it again. Every now and then a ''xend start'' > > does nothing and sends no output to console. Commands such as ''xm > > list'' will give a ''Connection refused'' error. A ''xend stop'' followed > > by a ''xend start'' usually fixes this but there have been a few times > > where I have had to repeat the cycle a couple of times. > > > > Also, sometimes after a reboot, a domain creation just fails and the > > ''xm create'' command does not return. There are no error messages from > > xend. Even though I suspect that things are hosed at this point in > > time, a ''xend stop'' works. However xend will not startup again and > > gives a ''IOError: [Errno 16] Device or resource busy'' error. The > > problem cannot be reproduced as the same create command works after > > another reboot. > > I think many people had been seeing problems of this ilk, so you will > probably be delighted to hear that these bugs have been squashed by > today''s checkins. > > It was a combination of a simple stupid bug in the device-driver code, > coupled with faulty error handling in xend. >Just FYI, I still see most of the above bugs. Running the latest and greatest. BTW what has the start_trace option for xend been replaced by? Niraj> -- Keir >------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > > I have seen a number of ''''heisenbugs" with xend. They especially occur > > > when I stop xend and start it again. Every now and then a ''xend start'' > > > does nothing and sends no output to console. Commands such as ''xm > > > list'' will give a ''Connection refused'' error. A ''xend stop'' followed > > > by a ''xend start'' usually fixes this but there have been a few times > > > where I have had to repeat the cycle a couple of times. > > > > > > Also, sometimes after a reboot, a domain creation just fails and the > > > ''xm create'' command does not return. There are no error messages from > > > xend. Even though I suspect that things are hosed at this point in > > > time, a ''xend stop'' works. However xend will not startup again and > > > gives a ''IOError: [Errno 16] Device or resource busy'' error. The > > > problem cannot be reproduced as the same create command works after > > > another reboot.> Just FYI, I still see most of the above bugs. Running the latest and greatest.I''ve actually found that xend has been very stable for me for the last few days. How are other people finding it? I think there''s real merit in cleaning out old installations before doing a new install e.g.: rm -rf "/etc/xen /usr/lib/python2.2/site-packages/xen* /usr/lib/libxc* /usr/lib/python2.2/site-packages/Xc*" If you still get problems, please post any output. I know of two outstanding Xen bugs, both of which Keir understands and is about to vanquish: * instability after shutting a domain down on a CPU other than CPU 0. * dom0 oops when hitting local block devices hard from within dom0 while doing block io from other domains. Let''s get these two fixed then see where we are. Ian ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I know of two outstanding Xen bugs, both of which Keir > understands and is about to vanquish: > > * instability after shutting a domain down on a CPU other than CPU 0. > > * dom0 oops when hitting local block devices hard from within > dom0 while doing block io from other domains. > > Let''s get these two fixed then see where we are.Both of these are now fixed. Both of them were both nasty and fairly difficult to hit --- but when you hit them they would take out the machine by crashing either Xen or DOM0. Hopefully occasional machine reboots will be rather more occasional now. :-) -- Keir ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Just for feedback''s sake - I''ve been running an unprivileged xen domain which has been happily processing spam for over 24 hours. It is configured as a backup mail server and because the primary server is up, it only really gets spam (spammers love to hit MX records other than the lowest as they often aren''t configured for spam filtering). It get''s a message every few minutes or so. It''s running on an SMP machine with two virtual interfaces mapped to two physical interfaces in dom0. my xen tree is probably 36 hours old or so and therefore probably doesn''t have any of the recent fixes in it which from what i''ve read fix quite a few issues - none of which are affecting me thus far except for a reboot problem I saw a few days ago. just a suggestion, could you put those rm''s which you mention in a make option, eg make installflush. Maybe exclude /etc/xen from that though or only remove specific files from there though, i''ve modified at least one config file in there. James From: Ian Pratt Sent: Wed 14/07/2004 1:13 AM To: Niraj Tolia Cc: Keir Fraser; Ian Pratt; James Harper; xen-devel@lists.sourceforge.net; Ian.Pratt@cl.cam.ac.uk Subject: Re: [Xen-devel] Re: almost working> > > I have seen a number of ''''heisenbugs" with xend. They especially occur > > > when I stop xend and start it again. Every now and then a ''xend start'' > > > does nothing and sends no output to console. Commands such as ''xm > > > list'' will give a ''Connection refused'' error. A ''xend stop'' followed > > > by a ''xend start'' usually fixes this but there have been a few times > > > where I have had to repeat the cycle a couple of times. > > > > > > Also, sometimes after a reboot, a domain creation just fails and the > > > ''xm create'' command does not return. There are no error messages from > > > xend. Even though I suspect that things are hosed at this point in > > > time, a ''xend stop'' works. However xend will not startup again and > > > gives a ''IOError: [Errno 16] Device or resource busy'' error. The > > > problem cannot be reproduced as the same create command works after > > > another reboot.> Just FYI, I still see most of the above bugs. Running the latest and greatest.I''ve actually found that xend has been very stable for me for the last few days. How are other people finding it? I think there''s real merit in cleaning out old installations before doing a new install e.g.: rm -rf "/etc/xen /usr/lib/python2.2/site-packages/xen* /usr/lib/libxc* /usr/lib/python2.2/site-packages/Xc*" If you still get problems, please post any output. I know of two outstanding Xen bugs, both of which Keir understands and is about to vanquish: * instability after shutting a domain down on a CPU other than CPU 0. * dom0 oops when hitting local block devices hard from within dom0 while doing block io from other domains. Let''s get these two fixed then see where we are. Ian