t;] set_signals+0x1c/0x2e
>
> 67825e78: [<6000197d>] mount_block_root+0x246/0x264
>
> 67825ee8: [<600019eb>] mount_root+0x50/0x54
>
> 67825f08: [<60001b18>] prepare_namespace+0x129/0x14e
>
> 67825f18: [<60001424>] kernel_init+0xc7/0xd5
>
> 67825
root (ext2 filesystem) readonly.
> Mounted devfs on /dev
> INIT: version 2.78 booting
> Kernel panic: map_memory(0x467000, -1, 0x0, 4096, 0, 0, 0) failed, err = -9
That's EBADF, I'm not sure if this error is new to me, but I can't
remember them by heart (and we have no bug
RQs
>
> --
> This SF.net Dev2Dev email is sponsored by:
>
> Show off your parallel programming skills.
> Enter the Intel(R) Threading Challenge 2010.
> http://p.sf.net/sfu/intel-thread-sfd
> ___
host's entropy by reading the host's /dev/random.
Not sure about the current status of all this, though.
--
Paolo Giarrusso - Ph.D. Student
http://www.informatik.uni-marburg.de/~pgiarrusso/
--
Live Security Vir
ML version?(you forgot exactly this)
> I'm using kernel (vanillia kernel patched with:
> host-skas3-2.4.25-v3.patch)
Correct.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
--
on the host).
No clear light on this, however.
> I already asked the developer of lmbench, and he
> adviced me to ask this question to the linux kernel
> mailing list.
> I would really appreciate any inputs and advice. Thank
> you!
--
Paolo Giarrusso, aka Blaisorblade
Linux registere
me out what is the problem. Same UML binary is
> working fine on my other system.
>
> Thanks and Best Regards,
> Adil Mujeeb
Config info about the host/guest, please, to help...
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.use
ell discussed on the MLs...
I think it's this one because you don't say you've done this step.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
---
SF email is sp
> resizing/defining ONLY the COW
>
> Regards
>
> Franck
IIRC, the COW can't be bigger than the backing file + the COW header size.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
tually go
> right to zero, shortly before the guest segfaulted.
Checked the value without the cache size?
> My impression is that the guest is not using its "dedicated" ram or swap
> very efficiently.
2.6.9 kernels, on any arch, often go OOM in
uld recreate all the ubd devices like this, with a for loop... search
on :
http://user-mode-linux.sourceforge.net/compile.html
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
---
SF em
me
> on this. If you can provide a URL that will support
> your answer, I will really appreciate it. Thank you
> very much!
When you use a page (a 4k memory segment) the first time, a page fault is
performed and the page is made available.
--
Paolo Giarrusso, aka Blaisorblade
Li
/ubd1".
>
> Thanks,
> Alex Katebi
Probably ubd1 has the wrong minor - it's minor should be 16, but time ago it
was "1". And the kit is IIRC quite old.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
On Saturday 18 December 2004 16:55, [EMAIL PROTECTED] wrote:
> > -Original Message-
> > From: Paolo Giarrusso [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, December 16, 2004 2:05 PM
> > To: user-mode-linux-user@lists.sourceforge.net
> > Cc: Sala, Roger
> &
--- Jeff Dike <[EMAIL PROTECTED]> ha scritto:
> [EMAIL PROTECTED] said:
> > In the other problem case, the dstat on the host
> shows only write load
> > of good magnitude, around 16 MB/s. But it is
> writing a whole lot more
> > than what happens on the guest side. In fact, in
> one case, 15 tim
John Zavgren <[EMAIL PROTECTED]> ha scritto:
> Thanks.
> I think you are telling me that 2.6.16 has a bug that prevents UML
> from
> working and I should avoid the kernel source code with this version
> number on ftp.kernel.org... and instead I should use code that
> hasn't
> been checked in? Co
went very fast up the
> > knowledge hill so it's not a problem, you must be a smart guy).
> >
> > You're more or less claiming that if you have a hub-based
> > Ethernet LAN (multicast networking has the same properties,
> > it's a broadcast LAN
"Stephens, Allan" <[EMAIL PROTECTED]> ha scritto:
> Hi Paolo:
>
> OK, let me take one more try at explaining what I've observed.
> (And my
> apologies for making this whole issue more confusing than necessary
> ...
> I'm pretty inexperienced when it comes to detailing with the
> details of
> ne
Jeff Dike <[EMAIL PROTECTED]> ha scritto:
> On Thu, Aug 03, 2006 at 01:08:51PM -0700, Stephens, Allan wrote:
> > Where I think my confusion is arising is in the details of how
> the
> > filtering
> > controlled by the promiscuous setting is actually done. If a
> packet
> > with
> > the "wrong"
Etay Meiri <[EMAIL PROTECTED]> ha scritto:
> Not sure I understand this - what else should I use for an updated
> UML build? (vanilla kernel?)
Yes, or the -bs/-bb patchset (*when* I publish it). The skas patch is
needed to make the host support SKAS3 UML instances (without it
they'll run the sli
Sven Köhler <[EMAIL PROTECTED]> ha scritto:
> >> has anybody of you gentoo-users out there (maybe Blaisorblade?)
> tried
> >> UML with glibc 2.4 (which seems to be nptlonly!)?
> > As things stands, this should be especially tested on amd64 host
> - Antoine
> > Martin reported it works on x86 one
Nix <[EMAIL PROTECTED]> ha scritto:
> On 3 Jan 2007, [EMAIL PROTECTED] outgrape:
> > On Tuesday 26 December 2006 11:46, Stephane Bortzmeyer wrote:
> >> FATAL kernel is too old
> >>
> >> (And I cannot change the host at will, only the guest.)
> >
> > According to Nix, you're using binaries compiled
(Sorry for top-posting - this is a webmail)
/bin/bash is running with stding and stdout attached to /dev/console, and on
/dev/console ignores Ctrl-* (and that's on purpose, and not UML specific).
Possibly just the terminal emulator is noticing the press of Ctrl-C, or it's
/dev/console itself.
On Tuesday 07 August 2007, Peter Chant wrote:
> On Tuesday 07 August 2007, Blaisorblade wrote:
> >
> > I just realized the real problem - that "disk is full" message is given on
> > a tmpfs mount (with udev, /dev stays normally on tmpfs); the size limit of
> > a tmpfs mount is by default the half o
24 matches
Mail list logo
