Hi, I''m trying to setup a xen environment. I download xen-2.0-src.tgz, follow the steps from the Xen user''s manual, and got a new kernel that i put in my machine. I have made a reboot and every thing goes well. Then i have try to configure a new domain like this in /etc/xen/xmdefconfig kernel = "/boot/vmlinuz-2.6.8.1-xenU" disk = [ ''phy:hda5,xda5,r'' ] root = "/dev/xda5 ro" then i run "xm create -c vmid=1" and i''m getting this kernel panic VFS: Cannot open root device "xda5" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0) Someone can point me what i''m doing wrong ? I''m using Scientific Linux CERN release 3.0.2 (SL), this distribution is based on Redhat Enterprise 3. Thank''s ND -- Nuno Dias <ndias@lip.pt> LIP ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
xda device no longer exists, so change xda5 -> hda5. -- Keir> Hi, > > I''m trying to setup a xen environment. > I download xen-2.0-src.tgz, follow the steps from the Xen user''s manual, > and got a new kernel that i put in my machine. > > I have made a reboot and every thing goes well. > > Then i have try to configure a new domain like this > in /etc/xen/xmdefconfig > > kernel = "/boot/vmlinuz-2.6.8.1-xenU" > disk = [ ''phy:hda5,xda5,r'' ] > root = "/dev/xda5 ro" > > then i run "xm create -c vmid=1" and i''m getting this kernel panic > > VFS: Cannot open root device "xda5" or unknown-block(2,0) > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0) > > Someone can point me what i''m doing wrong ? > I''m using Scientific Linux CERN release 3.0.2 (SL), this distribution is > based on Redhat Enterprise 3. > > Thank''s > > ND > -- > Nuno Dias <ndias@lip.pt> > LIP > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
I''ve seen this error a few times recently: "Kernel panic: Unable to reduce memory reservation In interrupt handler - not syncing" And quite a few of these: "Received packet needs 52 bytes more headroom." The first one is obviously a bit of a problem. Does the second one matter? James ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I''ve seen this error a few times recently: > "Kernel panic: Unable to reduce memory reservation > In interrupt handler - not syncing"Yes, there seems to be a nasty bug that possibly involves writable page tables (noone has reported the bug with writable page tables disabled in the kernel configuration).> And quite a few of these: > "Received packet needs 52 bytes more headroom." > > The first one is obviously a bit of a problem. Does the second one > matter?I''ve increased the headroom allocated for received packets in teh frontend driver. It should get rid of the messages. -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Yes, there seems to be a nasty bug that possibly involves writable > page tables (noone has reported the bug with writable page tables > disabled in the kernel configuration).I''m building now with wpt disabled. I''ll let you know how it goes. In addition, trying to clean up the crashed domain with ''xm destroy <name>'' caused dom0 and therefore the whole machine to reboot.> I''ve increased the headroom allocated for received packets in teh > frontend driver. It should get rid of the messages.Is it just an informative message or is it telling me that something is wrong? Thanks James ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > Yes, there seems to be a nasty bug that possibly involves writable > > page tables (noone has reported the bug with writable page tables > > disabled in the kernel configuration). > > I''m building now with wpt disabled. I''ll let you know how it goes. In > addition, trying to clean up the crashed domain with ''xm destroy <name>'' > caused dom0 and therefore the whole machine to reboot.Yes, there is definitely a reference-counting bug in Xen. Once a guest prints out that particular message, it really is time to reboot the machine!> > I''ve increased the headroom allocated for received packets in teh > > frontend driver. It should get rid of the messages. > > Is it just an informative message or is it telling me that something is > wrong?Informative, as the packet gets copied into a buffer that is big enough. I just wanted to know how large the buffers should be that I allocate for received packets -- I want to make it small enough that buffer accounting in the sockets layer isn''t thrown off, but large enough that packets don''t have to be copied to fit. The message tells me that my chosen size was a bit too small. -- Keir ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > Yes, there seems to be a nasty bug that possibly involves writable > > page tables (noone has reported the bug with writable page tables > > disabled in the kernel configuration). > > I''m building now with wpt disabled. I''ll let you know how it goes. In > addition, trying to clean up the crashed domain with ''xm destroy <name>'' > caused dom0 and therefore the whole machine to reboot.Have you got a serial line on the machine? If so, if you have a debug build we should be getting interesting debugging. Also, before trying to destroy the domain, hit ctrl-A three times and then ''q'' and ''o''. This will do an audit of all the domain''s remaining memory, and might give us a clue as to what is broken. Even more informative might be to add a call to audit_domains() in the "Bad page free for domain" error path in xen/common/dom_mem_ops.c What are you doing in the domains that''s causing this bug? We''ve tried to reproduce but can''t so far. Thanks, Ian ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> > Have you got a serial line on the machine? If so, if you have a > debug build we should be getting interesting debugging. > > Also, before trying to destroy the domain, hit ctrl-A three times > and then ''q'' and ''o''. > > This will do an audit of all the domain''s remaining memory, and > might give us a clue as to what is broken. > > Even more informative might be to add a call to audit_domains() > in the "Bad page free for domain" error path inxen/common/dom_mem_ops.c Unfortunately I don''t have any time to maintain this machine currently - it''s in the office and I''m not. So I''ve disabled wpt and am testing without. Would it be possible to have xen hook into the syslog facility of dom0, which could then be relayed to another server? Most likely dom0 would be too broken by this point to be able to function in this way though.> What are you doing in the domains that''s causing this bug? We''ve > tried to reproduce but can''t so far.The domain that is crashing is a mail server. It''s running exim4 + cyrus + mailscanner (+ sendmail + razor + clamav), so it works reasonably hard but is still just doing disk and network io, nothing really special. Would that error be caused by it running out of memory? I''ve not seen it even get close to that though, but if a lot of large emails came in in one hit it could happen... James ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel