I had upgraded to latest hg version of xen unstable and my arch linux guest can''t find /dev/xvda1. My server 2008R2 boot and work just fine.
Hi,
see, if one could have a look at your domU config file, or peek into the
output of your
booting domU, it would be possible to give a reliable answer.
That way, I''ld take a look into my crystal ball (which is quite
scratched these days ...) and guess, your
domU''s /boot/grub/menu.lst gives a wrong root=... to your kernel.
sorry for sarcasm, but a little more information would be really
helpful.
cheeers,
--
Stephan Seitz
Senior System Administrator
netz-haut GmbH
multimediale kommunikation
Friedrich-Bergius-Ring 12
97076 Würzburg
Telefon: 0931 - 780 11 780
Telefax: 0931 - 780 11 799
Web: www.netzhaut.de
Amtsgericht Würzburg – HRB 10764
Geschäftsführer: Michael Daut, Kai Neugebauer
Am Dienstag, den 24.07.2012, 09:51 -0600 schrieb jacek burghardt:
> I had upgraded to latest hg version of xen unstable and my arch linux
> guest can''t find /dev/xvda1. My server 2008R2 boot and work just
fine.
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xen.org
> http://lists.xen.org/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users
Well is very strange my configuration worked witth fine before I had installed latest xen unstable there and no logs created for linux guest at all. And I had one version of xen compiled that had stated that creation failed and my guess stoped looking fro xvda1 root drive that always had worked before. I have root specified in my config file Any tips fro trouble shooting this ? On 7/24/12, Stephan Seitz <s.seitz@netzhaut.de> wrote:> Hi, > > see, if one could have a look at your domU config file, or peek into the > output of your > booting domU, it would be possible to give a reliable answer. > > That way, I''ld take a look into my crystal ball (which is quite > scratched these days ...) and guess, your > domU''s /boot/grub/menu.lst gives a wrong root=... to your kernel. > > sorry for sarcasm, but a little more information would be really > helpful. > > cheeers, > > > -- > > > Stephan Seitz > Senior System Administrator > > netz-haut GmbH > multimediale kommunikation > > Friedrich-Bergius-Ring 12 > 97076 Würzburg > > Telefon: 0931 - 780 11 780 > Telefax: 0931 - 780 11 799 > > Web: www.netzhaut.de > > > Amtsgericht Würzburg – HRB 10764 > > Geschäftsführer: Michael Daut, Kai Neugebauer > > > > Am Dienstag, den 24.07.2012, 09:51 -0600 schrieb jacek burghardt: > >> I had upgraded to latest hg version of xen unstable and my arch linux >> guest can''t find /dev/xvda1. My server 2008R2 boot and work just fine. >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >
Hello. El 24/07/12 13:12, jacek burghardt escribió:> Any tips fro trouble shooting this ?I would start by a careful inspection of DomU config file, it''s bootloader configuration and the content of the root image. Often it helps to ask other people to take a look on them, it''s easy to miss something if you are too familiar with the text you are looking at. (as it was mentioned before, the crystal ball is on it''s maintenance window, so you will probably have to use the fallback method and post your configs) -- Alexandre Kouznetsov
The line listed bellow was causing all the issues. vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0, keymap=it''] On Tue, Jul 24, 2012 at 12:55 PM, Alexandre Kouznetsov <alk@ondore.com>wrote:> Hello. > > El 24/07/12 13:12, jacek burghardt escribió: > > Any tips fro trouble shooting this ? >> > I would start by a careful inspection of DomU config file, it''s bootloader > configuration and the content of the root image. > > Often it helps to ask other people to take a look on them, it''s easy to > miss something if you are too familiar with the text you are looking at. > > (as it was mentioned before, the crystal ball is on it''s maintenance > window, so you will probably have to use the fallback method and post your > configs) > > -- > Alexandre Kouznetsov > > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
> I had upgraded to latest hg version of xen unstable and my arch linux > guest can''t find /dev/xvda1. My server 2008R2 boot and work just > fine. > (..) >The line listed bellow was causing all the issues. >vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0, keymap=it'']Please don''t top post. If this is actually the case we definitely need some logs, because that should never happen. -- Stay in touch, Mark van Dijk. ,-------------------------------- ----------------------------'' Wed Aug 01 00:26 UTC 2012 Today is Pungenday, the 67th day of Confusion in the YOLD 3178
El 31/07/12 19:27, Mark van Dijk escribió:>> The line listed bellow was causing all the issues. >> vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0, keymap=it''] > > If this is actually the case we definitely need some logs, because that > should never happen.And configs, then console output example... -- Alexandre Kouznetsov
There was no logs ins /var/log/xen After looking over my config file vnc was refereed again so i guess there was conflict _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Am Mittwoch, den 01.08.2012, 02:27 +0200 schrieb Mark van Dijk:> > I had upgraded to latest hg version of xen unstable and my arch linux > > guest can''t find /dev/xvda1. My server 2008R2 boot and work just > > fine. > > (..) > >The line listed bellow was causing all the issues. > >vfb=[''vnc=1,vncunused=1,vnclisten=0.0.0.0, keymap=it''] > > Please don''t top post. > > If this is actually the case we definitely need some logs, because that > should never happen. >I''m currently upgrading a xen cluster from xen 3.2 to xen 4.1 and also found that issue. Log''s are really quiet about it. It''s just that starting a domU connect''s all devices. pvgrub and pygrub menu are working. then xentop / xl top / xm top shows high cpu load for the particular domU, but nothings going to happen. I think that has been discussed already, but I assume it''s not solved finally. Playing around with the console= parameter of domUs kernel didn''t change anything. That misbehaviour has been introduced somewhere at the 4.1 version. 4.0 was one step in the evaluation of my upgrade path and only 4.1 needs vfb removed from config. I''m currently stuck at the xm toolstack, as I started adding some own settings to domU configs a long while ago which can''t be parsed by the xl stack... So, my tests with xl about that issue weren''t too excessive. _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users