Public bug reported:
When running RTEMS test psxndbm01.exe built for AArch64-ilp32 (this code is not
yet publically available), the test generates a spurious data abort (the MMU
and alignment checks should be disabled according to bits 1, 0 of SCTLR_EL1).
The abort information is as follows:
Ta
** Description changed:
When running RTEMS test psxndbm01.exe built for AArch64-ilp32 (this code is
not yet publically available), the test generates a spurious data abort (the
MMU and alignment checks should be disabled according to bits 1, 0 of
SCTLR_EL1). The abort information is as follow
I would have thought that TLB considerations would not apply when the
MMU is disabled (RTEMS runs in a completely flat memory space). I'll try
to reproduce on more modern QEMU today. Thanks for taking a look at
this.
--
You received this bug notification because you are a member of qemu-
devel-ml
Ok, thanks for rooting this out. I could swear that I checked that
address several times and I clearly remember 0x4010ca28, but I don't
remember ever seeing 0x10 ahead of it. I'll dig into it a bit and
hopefully find the root cause in my code.
** Changed in: qemu
Status: New => Invalid
--
An update for anyone interested: I didn't remember seeing the leading
0x10 because the values are correct when retrieved from memory. They get
packed into a structure that gets returned in a single register, so the
0x10 second element ends up in the upper 4 bytes of x0 which is provided
as the firs
Hi,
I need to trace all data loads/stores of a guest OS running under qemu (for
now, both guest and host are x86-64, and virtual addresses should be
sufficient). Looking into qemu-devel archive I see that this subject is
brought up not very frequently, but regularly. I know, there is a general
trac
> -Original Message-
> From: Yan Vugenfirer [mailto:yvuge...@redhat.com]
> Sent: Wednesday, May 21, 2014 5:01 PM
> To: Michael Roth
> Cc: Luiz Capitulino; Wangrui (K); Gonglei (Arei); qemu-devel@nongnu.org;
> arm...@redhat.com
> Subject: Re: [Qemu-devel] [PATCH] qg
Hi All,
I am looking for a way to emulate avoton processor. Is there
any pre-defined configuration to simulate an avoton based board with qemu?
At this point of time, I am trying to experiment with the various i2c
SoC, LPC of the processor.
Any pointers to jump start with this would be
Hi All,
I am looking for a way to emulate avoton processor. Is there
any pre-defined configuration to simulate an avoton based board with qemu?
At this point of time, I am trying to experiment with the various i2c
SoC, LPC of the processor.
Any pointers to jump start with this would be
Any ideas about the issue ?
Regards.
> -Original Message-
> From: Gonglei (Arei)
> Sent: Wednesday, April 16, 2014 10:05 AM
> To: qemu-devel@nongnu.org
> Cc: mdr...@linux.vnet.ibm.com; Wangrui (K)
> Subject: qemu-ga: How to static compilation qemu-ga.exe for wind
I am trying to prevent write from DomU for particular sector of hardisk
which is passed through QEMU device.
I am putting an error condition in ide.c using API
ide_handle_write_error(s, -ret, BM_STATUS_ERROR) called from
ide_write_dma_cb, however DomU is still going ahead and writing to those
se
I am trying to prevent write from DomU for particular sector of hardisk
which is passed through QEMU device.
I am putting an error condition in ide.c using API
ide_handle_write_error(s, -ret, BM_STATUS_ERROR) called from
ide_write_dma_cb, however DomU is still going ahead and writing to those
se
On Tue, Oct 29, 2013 at 7:51 AM, Shakil k wrote:
> I am trying to prevent write from DomU for particular sector of hardisk
> which is passed through QEMU device.
>
> I am putting an error condition in ide.c using API
> ide_handle_write_error(s, -ret, BM_STATUS_ERR
Hi, all
I used switch and vhost-user to receive packets from vm to host, or to send
packets to vm .
When switch process was restarted by any time, it was not communicated with
each other from vm to host.
How to deal with the problem about communicating from vm to host or vm to vm
when switch p
Yes, this patch is only reconnect socket.
The "Is_reconnect" field is used by next patch.
-Original Message-
From: Zhang Haoyu [mailto:zhhy.zhangha...@gmail.com]
Sent: Monday, December 22, 2014 3:20 PM
To: Zhangkun (K); qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATC
Hi,
I am experimenting with VHOST-BLK with the codes I got from:
QEMU - git://github.com/asias/qemu.git
KERNEL - git://github.com/asias/linux.git
The VM I am booting is compiled with MSIX config options.
I am seeing a failure in the QEMU function msix_enabled during the
initialization of the bloc
Hi
This is my first post here. Am not sure if this is right forum. I am
trying to get KVM/qemu running on linux. I compiled 2.6.27.10 by
enabling "KVM", "KVM for intel" options at configure time. My box is
running with KVM enabled inside kernel. I also built
qemu-kvm-0.12.2 using above kernel head
Hi
I'm trying to run kvm/qemu on a linux host built from scratch ie., no x
windows, no window manager etc. bare minimum libraries etc. when i try to spawn
a VM with "-curses", I see "VGA Blank Mode" and nothing else. i'm attached to
serial console for this host. what could be the issue?
thanks
Hi
I built 2.6.27.10 kernel with KVM configured as built-in.
CONFIG_HAVE_KVM=y
CONFIG_VIRTUALIZATION=y
CONFIG_KVM=y
CONFIG_KVM_INTEL=y
I built qemu-kvm 0.12.2 from sources pointing to above kernel. When I spawn a
VM, it hangs at boot. Pl see below. I copied qemu-kvm binary and bios, vga etc
bi
Hi
I am able to boot my custom kernel off of bare hardware, but when I try to boot
this with qemu it hangs after first two lines of print about BIOS. i tried
booting through qemu image and also via '-kernel' arg. same result in both
cases. i verified that with same qeumu-system-x86_64 i could b
Hello
I'm trying to connect gdb to qemu and it seems not to
work correctly.
I mean it does not wait for gdb to connect.
I perform the following command to do that:
qemu -s -kernel arch/i386/boot/bzImage -hda
root-2.4.20.img -append "root=/dev/hda"
It just runs like this option hasn't been specif
Hello
Look at the following monitor's memory dump commands:
(qemu) x/1xw 0
: 0xb7d00694
(qemu) x/1xw 1
0001: 0xb7d00694
(qemu) x/2xw 0
: 0xb7d00694 0x081459a6
It looks like the single 4-byte dumps always show the
first memory location.
Is it a bug ?
I use qemu-0.9.0 under
: K. Lange
---
ui/gtk.c | 4
1 file changed, 4 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index a8567b9ddc..8675ae76fa 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -958,6 +958,10 @@ static gboolean gd_button_event(GtkWidget *widget,
GdkEventButton *button,
return TRUE
I have made a bare metal "Hello World" program for the Netduino2. I have
pushed it here:
https://github.com/skintigh/baremetal_netduino2
It should output "Test 1/4" to USART 1, "Test 2/4" to USART 2, "Test 3/4"
to USART 3 and "Test 4/4" to UART 4.
What actually happens in QEMU is only the first
T4 to /tmp/uart4. 2 and 3
still disappear but that seems to be a bug and I have reported it. Now to
test this on a chip with 8 UARTS...
Thanks again!
On Wed, Oct 5, 2016 at 5:21 PM, Alistair Francis
wrote:
> On Wed, Oct 5, 2016 at 10:45 AM, Seth K wrote:
> > Thanks for that link.
> &
The only machine I saw listed in the help output is "netduino2." I pulled
QEMU from github, was that the right thing to do?
I found the specifications for the stm32f2xx and some similar chips and
verified the addresses and interrupts are correct.
The stm32f205 should support 6 UARTs, and the 6 ad
ote:
> > On Fri, Oct 7, 2016 at 8:59 AM, Seth K wrote:
> >> The only machine I saw listed in the help output is "netduino2." I
> pulled
> >> QEMU from github, was that the right thing to do?
> >>
> >> I found the specifications for the st
zy?
I don't understand Qemu enough to know what should be calling the functions
that handle UART read/write. Is there something I should look at in Qemu
and try to intercept?
On Fri, Oct 7, 2016 at 6:27 PM, Alistair Francis
wrote:
> On Fri, Oct 7, 2016 at 1:04 PM, Seth K wrote:
> >
of 3804 which means
nothing.
On Wed, Oct 12, 2016 at 6:25 PM, Seth K wrote:
> It's a bare metal program so I don't really have anywhere to print to,
> other than my custom function to output to the uart. I did double check all
> the address to make sure they agreed with the
ault is 60
video codec is always h264
The patch uses ffmpeg so you will need to install these packages:
ffmpeg libavformat-dev libavcodec-dev libavutil-dev libswscale-dev
This is my first time posting here, so please correct me if I'm doing
something wrong
Signed-off-by: Alex K
Thank you all for help with my last patch. I found one more entry in my
notes that could be a bug, or could be a misunderstanding on my part.
The memory map in DocID15818 (Rev 15) datasheet says:
ADC1 - ADC2 - ADC3: 0x40012000-0x400123FF
That suggests a size of 0x400 (they share that range?)
I corrected these 2 memory regions based on specifications from the chip
manufacturer. The existing ranges seem to overlap and and cause odd
behavior and/or crashes when trying to set up multiple UARTs,
I also played with changing MAX_SERIAL_PORTS to 8 to match the hardware,
but I did not include t
On Thu, Nov 15, 2018 at 7:05 AM Peter Maydell
wrote:
> On 4 November 2018 at 07:42, Seth K wrote:
> > I corrected these 2 memory regions based on specifications from the chip
> > manufacturer. The existing ranges seem to overlap and and cause odd
> > behavior and/or cra
19 November 2018 at 10:43, Philippe Mathieu-Daudé
> wrote:
> > > > Hi Seth,
> > > >
> > > > On Mon, Nov 19, 2018 at 4:17 AM Seth K wrote:
> > > >>
> > > >> From: Seth Kintigh
> > > >>
> > > >> I corre
I need to simulate 3 chips that are on one board and that talk to each
other through UART, SPI and GPIO. The chips verify each other's work, and I
need to be able to observe this communication for debugging. Can something
like this be done in QEMU?
My first thought was to create the chip then crea
ault is 60
video codec is always h264
The patch uses ffmpeg so you will need to install these packages:
ffmpeg libavformat-dev libavcodec-dev libavutil-dev libswscale-dev
This is my first time posting here, so please correct me if I'm doing
something wrong
Signed-off-by: Alex K
It's still an issue using qemu-6.0.0-rc4. If you remove the environment
variable ENV GOPROXY="https://proxy.golang.org|direct" you get a
different error:
=> ERROR [6/6] RUN go build .
Public bug reported:
After updating to 5.2 I am getting following assertion error:
qemu-aarch64: ../tcg/tcg-op-gvec.c:54: check_size_align: Assertion `(maxsz &
max_align) == 0' failed.
I think it was introduced by commit:
e2e7168a214b0ed98dc357bba96816486a289762
Becasue before this change, in f
Public bug reported:
I try to pass-through nvidia 1060 6gb card, which is connected via
ExpressCard (EXP-GDC converter).
I can successfully run my virtual machine without pass-through, but when
I try to add the devices, qemu crashes.
The coredump contains:
Stack trace of thread 3289311:
#0 0x0
dmesg:
[0.00] microcode: microcode updated early to revision 0x21, date =
2019-02-13
[0.00] Linux version 5.8.6-1-MANJARO (builder@db927223e331) (gcc (GCC)
10.2.0, GNU ld (GNU Binutils) 2.35) #1 SMP PREEMPT Thu Sep 3 14:19:36 UTC 2020
[0.00] Command line: BOOT_IMAGE=/boot
Thank you Alex for answering me.
It seems, I've got it working, if I boot the host with the connected GPU from
the very beginning.
Previously, I tried hotplug and it crashes.
So previously I had:
1. enable the host
2. enable GPU
3. connect the cable
And this time I tried:
1. enable GP
What's more interesting, it doesn't crash if I hotplug GPU after it was boot
with it. So if I do
1. enable GPU
2. connect the cord
3. enable the host
4. run qemu (I'm not sure, if it's mandatory)
5. disable cord
6. disable GPU
7. enable GPU
8. enable cord
9. run qemu again
qe
Can confirm that it does not crash after applying that patch. I've added
the `fprintf` statement there:
if (vdev->bars[i].size) {
vfio_bar_quirk_setup(vdev, i);
} else {
fprintf(stderr, "%04x:%04x bars for %d are empty\n",
vdev->vendor_id, vdev->device_id, i)
I recorded both lspci - and lspci - for the following
connections:
- hotplug: when GPU is connected after the host was loaded
- fresh: when GPU is connected before the host was started
The main difference is the following:
1c1
< # hotplug
---
> # fresh
6c6
< Control: I/O+ Mem-
Hello
Can I run code compiled for ARM920T core in QEMU?
I am learning Embedded Linux for ARM processor. This is very crucial for my
studies. In future will have to work on AT91RM9200 atmel board with ARM920T
cpu.
Embedded Linux version that I am working on is 2.6.17.
I am struggling to set up an
Qemu Dev's,
I have been reading through many mail archives about the issues with threading
in qemu-i386 user mode.
I am writing now because here at One Laptop per Child we have a deployment
looking to run simple Windows x86 executables using WINE on our new ARM
platform.
We are interested to
On 12/26/2011 07:37 PM, Avi Kivity wrote:
On 12/19/2011 04:11 PM, Jan Kiszka wrote:
Backwards compatibility
If we want backwards compatibility, we need more than just a simple feature
check, no? Oh, you feed that into CPUID? That's nifty. Ok, so you behave like
VMX/SVM do on real hardware -
From: Raghavendra K T
The patch, extends KVM-hypervisor and Linux guest running on
KVM-hypervisor to support pv-ticket spinlocks.
PV ticket spinlock helps to solve Lock Holder Preemption problem discussed in
http://www.amd64.org/fileadmin/user_upload/pub/LHP-commented_slides.pdf.
When spinlock
script.
---
Changes in V3:
rename PVLOCK_KICK --> PV_UNHALT
add MSR related changes to aid migration
Changes in V2:
Drop the syncing kernel header changes. (Alex)
rename KICK_VCPU --> PVLOCK_KICK.
Raghavendra K T(2):
add PV_UNHALT feature support.
add support to get/set vcpu unhalt
From: Raghavendra K T
Extend the KVM Hypervisor to enable PVLOCK_KICK feature that allows
a vcpu to kick the halted vcpu to continue with execution in PV ticket
spinlock.
Signed-off-by: Srivatsa Vaddagiri
Signed-off-by: Raghavendra K T
---
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
From: Raghavendra K T
MSR_KVM_PV_UNHALT tells whether vcpu is unhalted, which needs to be
used during migration.
Signed-off-by: Raghavendra K T
---
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index a1ed3e7..10286a5 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -697,6 +697,7
On 03/23/2012 02:27 PM, Jan Kiszka wrote:
On 2012-03-23 09:23, Raghavendra K T wrote:
From: Raghavendra K T
MSR_KVM_PV_UNHALT tells whether vcpu is unhalted, which needs to be
used during migration.
Err, and where is it actually saved to/restored from the vmstate? You
are lacking an
On 03/23/2012 02:27 PM, Jan Kiszka wrote:
On 2012-03-23 09:23, Raghavendra K T wrote:
From: Raghavendra K T
MSR_KVM_PV_UNHALT tells whether vcpu is unhalted, which needs to be
used during migration.
Err, and where is it actually saved to/restored from the vmstate? You
are lacking an
It was tested with v9fs in the guest by using: sudo mount -t 9p -o
trans=virtio,version=9p2000 v_boot /pmnt
Signed-off-by: William K. Bittner
diff --git a/hw/9pfs/virtio-9p.c b/hw/9pfs/virtio-9p.c
index b5fc52b..febfba2 100644
--- a/hw/9pfs/virtio-9p.c
+++ b/hw/9pfs/virtio-9p.c
@@ -1186,6
generates. This patch uses the qemu
Notifier system to tell the guest it is about to be stopped.
Signed-off-by: Eric B Munson
Signed-off-by: Raghavendra K T
Cc: Eric B Munson
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc: Anthony Liguori
Cc: Jan Kiszka
Cc: "Andreas Färber"
---
Chang
On 04/06/2012 02:29 PM, Andreas Färber wrote:
Am 06.04.2012 09:21, schrieb Raghavendra K T:
From: Eric B Munson
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the
On 04/06/2012 03:19 PM, Raghavendra K T wrote:
On 04/06/2012 02:29 PM, Andreas Färber wrote:
Am 06.04.2012 09:21, schrieb Raghavendra K T:
From: Eric B Munson
Often when a guest is stopped from the qemu console, it will report
spurious
soft lockup warnings on resume. There are kernel patches
On 04/07/2012 02:39 AM, Andreas Färber wrote:
Am 06.04.2012 15:01, schrieb Raghavendra K T:
On 04/06/2012 03:19 PM, Raghavendra K T wrote:
On 04/06/2012 02:29 PM, Andreas Färber wrote:
Am 06.04.2012 09:21, schrieb Raghavendra K T:
From: Eric B Munson
Often when a guest is stopped from the
generates. This patch uses the qemu
Notifier system to tell the guest it is about to be stopped.
Signed-off-by: Eric B Munson
Signed-off-by: Raghavendra K T
Cc: Eric B Munson
Cc: Avi Kivity
Cc: Marcelo Tosatti
Cc: Anthony Liguori
Cc: Jan Kiszka
Cc: Andreas Färber
---
Changes from V8
Hi
I have been trying to setup a qemu session for qemu-system-s390x (on
x86_64) using a kernel (with initramfs built-in the kernel) without a
disk image. The kernel was built with s390 defconfig + disabled loadable
modules (just to keep everything inside the kernel).
$ qemu-system-s390x -M s390
On 01/15/2013 04:39 PM, Alexander Graf wrote:
On 15.01.2013, at 12:05, Suzuki K. Poulose wrote:
Hi
I have been trying to setup a qemu session for qemu-system-s390x (on
x86_64) using a kernel (with initramfs built-in the kernel) without a
disk image. The kernel was built with s390 defconfig
Update the kvm kernel headers to the 3.2.0-rc1 post using
scripts/update-linux-headers.sh script.
Signed-off-by: Raghavendra K T
---
diff --git a/linux-headers/asm-powerpc/kvm.h b/linux-headers/asm-powerpc/kvm.h
index fb3fddc..08fe69e 100644
--- a/linux-headers/asm-powerpc/kvm.h
+++ b/linux
From: Raghavendra K T
Three patch series following this, extends KVM-hypervisor
and Linux guest running on KVM-hypervisor to support pv-ticket spinlocks.
PV ticket spinlock helps to solve Lock Holder Preemption problem discussed in
http://www.amd64.org/fileadmin/user_upload/pub/LHP
Extend the KVM Hypervisor to enable KICK_VCPU feature that allows
a vcpu to kick the halted vcpu to continue with execution in PV ticket
spinlock.
Signed-off-by: Srivatsa Vaddagiri
Signed-off-by: Raghavendra K T
---
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 5bfc21f..69bce21
Update the kernel header that adds a hypercall to support pv-ticketlocks.
Signed-off-by: Raghavendra K T
---
diff --git a/linux-headers/asm-x86/kvm_para.h b/linux-headers/asm-x86/kvm_para.h
index f2ac46a..03d3a36 100644
--- a/linux-headers/asm-x86/kvm_para.h
+++ b/linux-headers/asm-x86
On 11/04/16 07:52, Vijay Kilari wrote:
Adding Suzuki Poulose.
Hi Suzuki,
On Fri, Apr 8, 2016 at 3:13 PM, Peter Maydell wrote:
On 8 April 2016 at 07:21, Vijay Kilari wrote:
On Thu, Apr 7, 2016 at 5:15 PM, Peter Maydell wrote:
I'm told there are kernel patches in progress to get this sort
o
On 13/04/16 10:54, Vijay Kilari wrote:
On Mon, Apr 11, 2016 at 3:07 PM, Suzuki K Poulose
wrote:
On 11/04/16 07:52, Vijay Kilari wrote:
Hi Suzuki,
The last 5 patches are not compiling on v4.4. Looks like your patch
series is not merged completely. Can you please
rebase your patches and
On 09/05/16 04:30, Vijay Kilari wrote:
Hi Suzuki,
The last 5 patches are not compiling on v4.4. Looks like your patch
series is not merged completely. Can you please
rebase your patches and let me know.
Could you please give the tree below a try ?
git://linux-arm.org/linux-skp.git cpu-ftr
I am curious to know why you'd want to do it?
On Mon, Aug 9, 2010 at 2:03 AM, Dennis wrote:
> Hi,
>
> I've been looking at the qemu source code but couldn't find anything
> that would suit my needs.
> Basically I'm looking for a way to use a file on disk as physical
> memory inside Qemu.
>
> Bef
Hi,
I've built qemu on my mac osx using this config -
./configure --prefix=/Users/ckk/local/ --target-list="i386-softmmu
x86_64-softmmu" --enable-linux-user
Now, I have a simple a.out built on linux - how can I run it using qemu on
my mac box?
--
Regards,
Kashyap
Let me see if I understand this right -
qemu loads the a.out and begins to interpret the x86 instructions in the
a.out and when a system call happens, it makes the call the host system
is that right?
On Wed, Aug 11, 2010 at 2:12 PM, Stefan Weil wrote:
> Am 11.08.2010 10:31, schrieb
ilar on mac (as far
as writing to stdout is concerned) Would it be possible/easy to give it
a shot?
On Wed, Aug 11, 2010 at 2:48 PM, Stefan Weil wrote:
> Am 11.08.2010 11:06, schrieb C K Kashyap:
>
> Let me see if I understand this right -
>
> qemu loads the a.out a
Thanks Stefan for the explanation ... It does not look like a pleasant thing
to do though :)
On Wed, Aug 11, 2010 at 3:33 PM, Stefan Weil wrote:
> Am 11.08.2010 11:33, schrieb C K Kashyap:
>
> I was wondering if it would be easy to force build the user-emulation on
> mac - as in,
> That should be portable to use Mac OS X as host instead of NetBSD, and to
> run thru QEMU (running x86 Linux software on PowerPC Darwin)
>
> Regards,
> Natalia Portillo
>
> El 11/08/2010, a las 10:33, C K Kashyap escribió:
>
> I was wondering if it would be easy to for
Hi,
This is not strictly qemu related but I think people who have a good idea
about it must be on this list.
I was wondering if I had an app that requires a fixed quantity of memory -
sufficiently less than the available physical memory. Would it benefit from
getting rid of the paging mechanism in
Thanks Malc .. I'll check out the video ... and perhaps ping you off the
list.
On Fri, Aug 13, 2010 at 10:15 AM, malc wrote:
> On Fri, 13 Aug 2010, C K Kashyap wrote:
>
> > Hi,
> > This is not strictly qemu related but I think people who have a good idea
> >
Hi
I was wondering if qemu's user mode emulation could be tweaked to generate
callgraph.
Today was the first time I tried the user mode emulation - I ran into the
below issue
[u...@kashyap lab]$ qemu-x86_64 -cpu qemu64 ./a.out
ERROR: ioctl(SNDCTL_DSP_MAPINBUF): target=0x80085013 host=0x80105013
E
Hi,
I tried to build qemu's user mode linux emulation on RHEL 4.8 x86_64 -
but I run into this issue -
ARi386-linux-user/libqemu.a
LINK i386-linux-user/qemu-i386
/usr/bin/ld:/home/ckk/lab/qemu-0.12.5/x86_64.ld:41: syntax error
collect2: ld returned 1 exit status
make[1]: *** [qemu-i386] Er
Given below is the debug o/p from usb-uhci,strangely it seems to
skip the frames after 118 it jumps to 145 .. similar is the
case with frame 0 , it doesn't load frame 0 rather jumps to
frame 1.The guest is minix 3.1.5 and the o/p was generated
from the driver under development,i have notice the s
uired libs installed. Patching and compiling qemu-kvm went
flawless.
- Original Message -
From: "MORITA Kazutaka"
To: k...@vger.kernel.org, qemu-devel@nongnu.org, linux-fsde...@vger.kernel.org
Sent: Wednesday, October 21, 2009 8:13:47 AM
Subject: [ANNOUNCE] Sheepdog: Distribu
or sheepdog compiles fine.
- Original Message -
From: "MORITA Kazutaka"
To: k...@vger.kernel.org, qemu-devel@nongnu.org, linux-fsde...@vger.kernel.org
Sent: Wednesday, October 21, 2009 8:13:47 AM
Subject: [ANNOUNCE] Sheepdog: Distributed Storage System for KVM
Hi everyone,
Can anyone tell me if there's any work going on to support eabi for arm?
--rich
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Jeremy Katz wrote:
The bochs rombios has supported attempting to boot from more than one
device for a while. It seems like it would make sense to be able to
specify "-boot acd" as an argument for qemu to try booting first from
the floppy, then the cd and finally the hard drive to make things mo
Are the new arm targets, versatile[ap]b expected to be working?
On ubuntu-5, building 0.8.2 yields a binary which can run the other two
targets, but which hangs after printing the monitor prompt on either of
these.
--rich
___
Qemu-devel mailing li
Are the new arm targets, versatile[ap]b expected to be working?
On ubuntu-5, building 0.8.2 yields a binary which can run the other two
targets, but which hangs after printing the monitor prompt on either of
these.
--rich
(apologies if you see this twice. I thought I sent it yesterday, but I
d
Are the new arm targets, versatile[ap]b expected to be working?
On ubuntu-5, building 0.8.2 yields a binary which can run the other two
targets, but which hangs after printing the monitor prompt on either of
these.
--rich
(apologies if you see this twice. I thought I sent it last week, but I
di
Are the new arm targets, versatile[ap]b expected to be working?
On ubuntu-5, building 0.8.2 yields a binary which can run the other two
targets, but which hangs after printing the monitor prompt on either of
these.
--rich
(apologies if you see this multiple times. I thought I sent it
previousl
I have at least one 450Mhz k6 in my spare bedroom. I'll by happy to
sell it to you as a platform for running debian and qemu. I'm sure it's
performance would be lower than most of the current amd processors,
though it might not be slower than some of the current intel chips,
(*grin*).
--ric
Does anyone have qemu running in user emulation with arm eabi, (armel),
traps?
I can get qemu-system booting an armel system. And I can get qemu-user
running with the codesourcery gcc-3 eabi libc's, (ie, the ones with the
codesourcery kernel call "shims"), but I haven't gotten it working yet
Ok, then I'm confused because I'm seeing dumps just trying to run a null
program. Unless there's NPTL setup stuff in crt0, I can't guess what
might be going on yet. This same null binary runs on a qemu-system with
suitable rootfs & kernel.
--rich
[EMAIL PROTECTED]> ./qemu-arm --version
qemu
Paul Brook wrote:
On Tuesday 26 September 2006 23:14, K. Richard Pixley wrote:
Ok, then I'm confused because I'm seeing dumps just trying to run a null
program. Unless there's NPTL setup stuff in crt0, I can't guess what
might be going on yet. This same n
Paul Brook wrote:
Do you know why 2.6.16 would be required? (I'll see if I can't
find/build a 2.6.16 system on which to try it today.)
Because arm-linux didn't get EABI support until 2.6.16 (though our toolchains
may accept 2.6.14). glibc has santity checks stop applications
When I build qemu-0.8.2, qemu-arm is a shared library rather than being
an executable. This seems highly suspicious and makes it particularly
difficult to debug. What's the rationale behind this?
--rich
___
Qemu-devel mailing list
Qemu-devel@nongn
I have now managed to run a null program and a helloworld, (both eabi,
linked statically, and without any thread calls), using the qemu-arm
user mode, both inside and outside of scratchbox. To do this with
qemu-0.8.2 I needed the following:
1) Paul's patch for NLS.
http://lists.gnu.org/arch
Paul Brook wrote:
1) Paul's patch for NLS.
You mean TLS and/or NPTL. NLS is something completely different :-)
Bah. Of course you're right. And I'm sure you can explain your patch
better than I can.
--rich
___
Qemu-devel mailing list
Qemu-d
Ishwar Rattan wrote:
Is it possible to boot the iso image
debian-31r3-sparc-netinst.iso
in qemu-system-sparc? What about other
Linux distributions?
I haven't tried it. But I'd be curious to hear how it works for you.
--rich
___
Qemu-devel maili
Blue Swirl wrote:
BTW, we could easily design and implement an ideal CPU just for Qemu
purposes. It could be unlike any existing hardware, for example with
zero or thousands of registers. The problem would be making a compiler
for the CPU, also porting some OS to it. Any GCC and Linux guru
vol
Johannes Schindelin wrote:
This s reminds me of Java.
Or lisp.
:-).
--rich
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Could someone please explain the issue with gcc4, please? Or point me
to an existing explanation?
I mean, I understand that qemu is believed to be building incorrectly
with gcc4. But what is the failure mode folks have been seeing? And
what's being done about it or what needs to be done abo
Martin Guy wrote:
Now, gcc4 can produce code with several return instructions (with no
option to turn that of, as far as I understand). You cannot cut them
out,
and therefore you cannot chain the simple functions.
...unless you also map return instructions within the generated
functions into
1 - 100 of 373 matches
Mail list logo
