Boot errors
by Chris Jones
I installed Fedora 16 and then ran:
sudo yum install xen
Xen installed without errors and I rebooted. In the Grub2 list I selected
Xen 4.1.2 and then selected the option:
Fedora Linux, with Xen 4.1.2 and Linux 3.3.0-4.fc16.x86_64
The boot process starts (i notice that loading ramdisk is very short) and
then shortly thereafter the boot fails and the system reboots without any
error.
I tried checking the boot log but I'm not sure I'm looking at the right
log.
The only problem I see in the boot is
Started SYSV: sandbox, xguest and other apps that want to use pam_names$
Failed to start Xenstored - daemon managing xenstore file system
11 years, 11 months
DomU nat router fails when DomUs on same host
by Virgil
Hi List,
I have a strange issue someone, hopefully, can advise me on.
I have two external connections into a host: em1 is behind a firewall machine
which is connected to an internet backbone link, while em2 is an adsl all-u-
can-eat deal with a cheap router.
Both are bridged. So there's pem1 and pem2 which are connected to the em1 and
em2 bridges respectively.
There is a domU router which nats (and is connected to both bridges).
Some domU servers (a variety of fc6 to fc16 32 and 64) default route to the
domU router and go out the all-u-can-eat link.
The issue is, I recent upgraded the host from Fedora8 to Fedora16, and now the
domU machines that once happily used the all-u-can-eat link, no longer can.
However, in an act of desperation, I moved one of the domUs to a backup
machine. Nothing else changed. Bingo. That domU works. All resources are still
on the original machine (i.e. the DB servers, the router, etc. etc.).
It seems that the router does't seem to nat domUs on the same host. You move
the domU off with comms going via em1 to another host and it works.
Iptraf tracing seems to indicate that the TCP connection is setup. The first
packet goes off and is acked. Then everything stops and eventually the tcp
connection closes on the router, but the domU and the remote computer think
the link is still up (at least that's what I think is happening). The domU's
send queue ends up with lots of data in it according to 'netstat -ant'
Only nat'd tcp connections are effected. Connections to machines on the same
bridge work fine.
Does this sound familiar to anyone?
Thanks in advance
Virgil
11 years, 11 months
Fedora Core 17 Xorg can't use /dev/fb0 when using Cirrus Logic VGA or Xen PVFB driver, Was:Re: [Xen-devel] irq problem with 3.3-rc3 on guest
by Konrad Rzeszutek Wilk
On Tue, Mar 27, 2012 at 11:14:30PM +0100, M A Young wrote:
> On Mon, 26 Mar 2012, Konrad Rzeszutek Wilk wrote:
>
> >So how are you actually trying to install F17?
> >I tried:
> >virt-install --name F17 --ram 1024 --disk /dev/vg_guest/f17_32 --paravirt --location http://build/tftpboot/f17-i386/
> >
> >and it showed the text console, and then rebooted thinking it was complete.
> >When using a manual guest config:
> >kernel="/root/vmlinuz-PAE"
> >ramdisk="/root/initrd-PAE.img"
> >append="console=hvc0 loglevel=8 root=http://build/tftpboot/f17-i386"
> >memory=1024
> >maxvcpus = 2
> >vcpus = 2
> >disk = ['phy:/dev/vg_guest/f17_32,xvda,w']
> >vif = [ 'type=netfront, bridge=switch' ]
> >vfb = [ 'vnc=1, vnclisten=0.0.0.0 ,vncunused=1']
> >
> >I get this:
> > 5.680395] Broadcom NetXtreme II iSCSI Driver bnx2i v2.7.0.3 (Jun 15, 2011)
> >[ 5.681923] iscsi: registered transport (bnx2i)
> >[ 5.696419] iscsi: registered transport (be2iscsi)
> >[ 5.763271] dracut: FATAL: No or empty root= argument
> >[ 5.764158] dracut: Refusing to continue
> >[ 5.769524] dracut Warning: Signal caught!
> >[ 5.772973] dracut Warning: dracut: FATAL: No or empty root= argument
> >[ 5.776138] dracut Warning: dracut: Refusing to continue
> >[ 5.782548] init used greatest stack depth: 5480 bytes left
> >[ 5.783425] Kernel panic - not syncing: Attempted to kill init!
> >
> >so is there a new syntax for the root parameter now that is a LiveCD?
>
> Yes, the F17 install image is now a liveCD so you need to specify
> this on the boot command line. This may be as simple as replacing
> root= with root=live:
So with extra="console=hvc0 loglevel=8 root=live:http://build/tftpboot/f17-i386/LiveOS/squashfs.img"
I was able to succesfully install, but booting proved interestingly.
When trying the 'pygrub' it would complain about the 'No OS loader', but if I ran
it on the disk (pygrub /dev/vg_guest/f17_32) it would extract the payload properly.
(This is with xen-4.1.2-6.fc16). So I worked around by taking those images
directly:
kernel="/var/run/xend/boot/boot_kernel.jIsJmr"
ramdisk="/var/run/xend/boot/boot_ramdisk.I4rBjo"
extra="root=/dev/mapper/vg_f17-lv_root ro rd.md=0 rd.lvm.lv=vg_f17/lv_swap SYSFONT=True KEYTABLE=us rd.lvm.lv=vg_f17/lv_root rd.luks=0 LANG=en_US.UTF-8 rd.dm=0"
And when booting F17 either as HVM or PV, in both cases I got Xorg to
tell me:
(EE) FBDEV(0): FBIOBLANK: Invalid argument
and freeze.
The /dev/fb0 works fine thought by itslef, if do:
"exec /sbin/init 3", then login on the VNC window and
run 'fbterm' I get an nice framebuffer terminal.
@M A: Is there a BZ for this or should I open one up with Xorg?
I would think that KVM would hit the same exact problem when using the
default VGA Cirrus framebuffer.
12 years
mdadm fails to start raid in pv fc16 DomU on old host
by Virgil
I'm having a problem with mdraid running in a DomU. The issue is that mdraid
declares one leg of the raid to have failed (when there's actually nothing
wrong).
DomU is fc16 - 3.2.2-1.fc16.x86_64
Dom0 is fc14 - 2.6.32.26-174.2.xendom0.fc12.x86_64
The same DomU running on Dom0 fc16 - 3.2.7-1.fc16.x86_64 runs perfectly.
This appears to be a known issue, however the resolution (which seems to be to
disable barriers on the fly) doesn't seem to work in this case.
My question is: Is it possible to pass a parameter to the blkfront driver to
ask it not to enable barrier during initialization? or is there another work
around?
[ 1.033058] blkfront: xvda: barrier: enabled
[ 1.099153] xvda: xvda1 xvda2
[ 1.102871] blkfront: xvdb: barrier: enabled
[ 1.130876] xvdb: xvdb1 xvdb2
[ 1.292692] md: bind<xvdb1>
[ 1.413416] md: bind<xvda1>
[ 1.419411] md: raid1 personality registered for level 1
[ 1.419836] bio: create slab <bio-1> at 1
[ 1.419953] md/raid1:md127: active with 2 out of 2 mirrors
[ 1.419992] md127: detected capacity change from 0 to 7516180480
[ 1.424562] md127: unknown partition table
[ 1.547284] EXT4-fs (md127): barriers disabled
[ 1.553107] EXT4-fs (md127): mounted filesystem with ordered data mode.
Opts: (null)
[ 1.669483] dracut: Checking ext4: /dev/disk/by-label/rootfs
[ 1.669592] dracut: issuing e2fsck -a /dev/disk/by-label/rootfs
[ 1.690595] blkfront: barrier: empty write xvdb op failed
[ 1.690611] blkfront: xvdb: barrier or flush: disabled
[ 1.690628] end_request: I/O error, dev xvdb, sector 14682096
[ 1.690638] end_request: I/O error, dev xvdb, sector 14682096
[ 1.690646] md: super_written gets error=-5, uptodate=0
[ 1.690655] md/raid1:md127: Disk failure on xvdb1, disabling device.
[ 1.690657] md/raid1:md127: Operation continuing on 1 devices.
[ 1.690677] blkfront: barrier: empty write xvda op failed
[ 1.690684] blkfront: xvda: barrier or flush: disabled
[ 1.690696] end_request: I/O error, dev xvda, sector 14682096
[ 1.690705] end_request: I/O error, dev xvda, sector 14682096
[ 1.690713] md: super_written gets error=-5, uptodate=0
[ 1.692991] RAID1 conf printout:
[ 1.692997] --- wd:1 rd:2
[ 1.693002] disk 0, wo:0, o:1, dev:xvda1
[ 1.693006] disk 1, wo:1, o:0, dev:xvdb1
[ 1.693010] RAID1 conf printout:
[ 1.693013] --- wd:1 rd:2
[ 1.693016] disk 0, wo:0, o:1, dev:xvda1
[ 1.702896] dracut: rootfs: clean, 25635/454272 files, 293967/1835005 blocks
[ 1.703682] dracut: Remounting /dev/disk/by-label/rootfs with -o ro
[ 1.773347] EXT4-fs (md127): barriers disabled
[ 1.774552] EXT4-fs (md127): mounted filesystem with ordered data mode.
Opts: (null)
[ 1.797159] dracut: Mounted root filesystem /dev/md127
[ 1.937620] dracut: Switching root
12 years
Re: [Fedora-xen] Boot errors, https://bugzilla.redhat.com/show_bug.cgi?id=804347
by Konrad Rzeszutek Wilk
On Tue, Mar 27, 2012 at 11:23:41AM -0400, Josh Boyer wrote:
> On Mon, Mar 26, 2012 at 10:53:40AM -0400, Konrad Rzeszutek Wilk wrote:
> > n Sat, Mar 24, 2012 at 08:59:30PM -0400, Chris Jones wrote:
> > > Thank you both for your response.
> > >
> > > That's probably the bug. I was hoping to find more answers here as after I
> > > found that bug report.
> >
> > Ok, well, the patches should appear shortly in the FC16 kernel builds (I hope?)
> > They were Acked-by Ingo, let me attach the patches to the BZ.
> >
> > Josh, is there a specific process for those patches to appear in F16? Should
> > I email them to some kernel-backport(a)fedora.org email list?
>
> Did you CC the stable list on them? If so, we'd pick them up when Greg
> releases 3.3.1.
Not yet, waiting for Ingo to stick them in his tree first. But will surely
CC GregKH to backport them.
>
> Otherwise, I'll grab all 3 (I think there were only 3) and get them into
> F16 one way or another.
OK. Thanks.
>
> josh
12 years
F17 Kernel Badness
by Sean McNamara
Hi,
My Fedora 17 3.3-rc4.git1 kernel boots on bare metal, but it dies very
early on in the boot process when loading on top of Xen. It's got
CONFIG_XEN_DOM0=y and all the other CONFIG_XEN* options are either "y"
or "m". Linux panics with
init[1] trap invalid opcode ip:7f99a072ff15 sp:7fffbf2a5088 error :0
in libc-2.15.so[7f99a05f8000+1ac000]
init used greatest stack depth: 2392 bytes left
Kernel panic - not syncing: Attempted to kill init!
The kernel itself seems able to execute on top of Xen because I see a
very normal-looking Xen init, then the screen blanks, then Linux
initializes and starts executing early boot, stuff like the USB stack
and SATA starts to come up, and then it tries to run the init process
in userspace and it all comes crashing down.
This is on Sandy Bridge hardware with all the CPU optional instruction
sets enabled.
Any ideas?
Thanks,
Sean
12 years, 1 month
Rebélate by self-management, first project of free software by which we bet all / Rebélate por la autogestión, primer proyecto de software libre por el que apostamos todas
by Orquidea Salt mas
Inglés :
Many already we have contributed to the first project of free software
dedicated to self-management in this campaign of collective financing,
it collaborates and it spreads!/
Beginning campaign collective financing
http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion?lang=en
Login to enter with user of social networks and for would register in Goteo :
http://www.goteo.org/user/login?lang=en
Rebelaos! Publication by self-management A massive publication that
floods the public transport, the work centers, the parks, the
consumption centers, by means of distribution of 500,000 gratuitous
units, acting simultaneously in all sides and nowhere.
We announce the main tool of a vestibule Web for the management of
self-sustaining resources by means of Drupal, in addition in the
publication there will be an article dedicated to free software,
hardware, It is being prepared in inglès, the machinery You can see
more details in the index of the
publication https://n-1.cc/pg/file/read/1151902/indexresumen-de-los-contenidos-pdf
. A computer system that allows us to share resources in all the
scopes of our life so that we do not have to generate means different
for each subject nor for each territory.
A point of contact digitalis to generate projects of life outside
Capitalism and to margin of the State.
A tool to spread and to impel the social transformation through the
resources that will set out in their contents around self-management,
the autoorganización, the disobedience and the collective action.
In which the capitalist system goes to the collapse, in a while
immersed in a deep systemic crisis (ecological, political and
economic, but mainly of values), where individual and collective of
people they are being lacking of his fundamental rights, is necessary
to develop a horizontal collective process where all the human beings
we pruned to interact in equality of conditions and freedom.
To interact means to relate to us (as much human as economically), to
communicate to us, to cover our basic needs, to generate and to
protect communal properties, to know and to provide collective
solutions us problematic that our lives interfere. We want abrir a
breach within normality in the monotonous life state-capitalist, a day
anyone, that finally will not be any day.
By means of this publication we try:
- To drive a horizontal collective process where all and all we pruned
to interact in equality of conditions and freedom.
- To create communications network between the people it jeopardize
with the change and arranged to act.
- To find collective solutions to problematic that our lives interfere
- To facilitate the access to resources that make possible self-management.
- To participate in the construction of networks of mutual support,
generated horizontals, asamblearias and from the base.
- To publish all this information in an attractive format stops to
facilitate the access to all the society.
There are 15 days remaining for the upcoming March 15, the day that
will come Rebelaos!, Magazine for the selfmanagement
Today, we issue the cover of Rebelaos! (Castilian version) that can be
displayed on the following link:
https://n-1.cc/pg/file/read/1200503/portada-15-de-marzo-rebelaos
The contents of the store owners to us by 15 March. Do you? Do you
keep on 15 March?
In addition, we have over 200 distribution nodes, distributed
throughout the Spanish state. Check the map:
https://afinidadrebelde.crowdmap.com/
On the other hand, the funding campaign continues to move and still
have 12 days to collect the remaining 6,000 euros. We can all make a
bit for all the grains of sand become a great beach on March 15. You
can access the co-financing campaign:
http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion
Rebel Affinity group
www.rebelaos.net
-------------------------------------------------------------------------------
Castellano:
Muchos ya hemos aportado al primer proyecto de software libre dedicado
a la la financiación colectiva, colabora y diffunde !!!!!
Inicio campaña financiación colectiva goteo.org
www.goteo.org/project/rebelaos-publicacion-por-la-autogestion
Link para registrarse en Goteo y acceder a redes sociales para
colaborar en la difusín
http://www.goteo.org/user/login
¡Rebelaos! Publicación por la autogestión
Una publicación masiva que inunde el transporte público, los centros
de trabajo, los parques, los centros de consumo, mediante la
distribución de 500.000 ejemplares gratuitos, actuando simultáneamente
en todos lados y en ninguna parte.
Anunciamos la herramienta principal de un portal web para la gestión
de recursos autogestionados mediante Drupal, además en la publicación
habrá un artículo dedicado al software libre, el hardware, la
maquinaria... Puedes ver más detalles en el índice de la publicación
https://n-1.cc/pg/file/read/1151902/indexresumen-de-los-contenidos-pdf
Un sistema infórmatico que nos permita compartir recursos en todos los
ámbitos de nuestra vida de forma que no tengamos que generar un medio
distinto para cada tema ni para cada territorio. Un punto de encuentro
digital para generar proyectos de vida fuera del capitalismo y al
margen del Estado.
Una herramienta para difundir e impulsar la transformación social a
través de los recursos que se propondrán en sus contenidos en torno a
la autogestión, la autoorganización, la desobediencia y la acción
colectiva.
En un momento en que el sistema capitalista se dirige al colapso,
inmerso en una profunda crisis sistémica (ecológica, política y
económica, pero principalmente de valores), donde individuos y
colectivos de personas están siendo desprovistos de sus derechos
fundamentales, es necesario desarrollar un proceso colectivo
horizontal donde todos los seres humanos podamos interactuar en
igualdad de condiciones y en libertad.
Interactuar significa relacionarnos (tanto humana como
económicamente), comunicarnos, cubrir nuestras necesidades básicas,
generar y proteger bienes comunes, conocernos y dar soluciones
colectivas a problemáticas que interfieren nuestras vidas. Queremos
abrir una brecha dentro de la normalidad en la monótona vida
estatal-capitalista, un día cualquiera, que finalmente no será
cualquier día.
Mediante esta publicación pretendemos:
- Impulsar un proceso colectivo horizontal donde todos y todas podamos
interactuar en igualdad de condiciones y en libertad.
- Crear red de comunicaciones entre las personas comprometidas con el
cambio y dispuestas a actuar.
- Encontrar soluciones colectivas a problemáticas que interfieren
nuestras vidas.
- Facilitar el acceso a recursos que posibiliten la autogestión.
- Participar en la construcción de redes de apoyo mutuo, horizontales,
asamblearias y generadas desde la base.
- Publicar toda esta información en un formato atractivo para
facilitar el acceso a toda la sociedad.
Son 15 los días que restan para el próximo 15 de marzo, día en el que
verá la luz ¡Rebelaos!, publicación por la autogestión.
Hoy, hacemos pública la portada de ¡Rebelaos! (versión en castellano)
que podéis visualizar en el siguiente enlace:
https://n-1.cc/pg/file/read/1200503/portada-15-de-marzo-rebelaos
El contenido de los titulares nos los guardamos para el 15 de marzo.
¿Y tú? ¿Te guardas el 15 de marzo?
Además, ya hemos superado los 200 nodos de distribución, repartidos
por todo el estado español. Ver el mapa:
https://afinidadrebelde.crowdmap.com/
Por otro lado, la campaña de financiación continúa avanzando y todavía
quedan 12 días para reunir los 6.000 euros que restan. Todas podemos
aportar un poco para que todos los granitos de arena se conviertan en
una gran playa el 15 de marzo. Podéis acceder a la campaña de
cofinanciación en:
http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion
Colectivo Afinidad Rebelde
www.rebelaos.net
12 years, 1 month
