Tried that too.
Same output.
On Thu, Apr 1, 2010 at 8:41 PM, Mulyadi Santosa
wrote:
> Hi Arpit...
>
> On Thu, Apr 1, 2010 at 10:04, Arpit Patel wrote:
> > Here is the command I issued
> >
> > "qemu -initrd initramfs.img -kernel vmlinux-2.6.24 /dev/zero -append
> "noapic
> > rw root=/dev/ram"
>
>
Hi Arpit...
On Thu, Apr 1, 2010 at 10:04, Arpit Patel wrote:
> Here is the command I issued
>
> "qemu -initrd initramfs.img -kernel vmlinux-2.6.24 /dev/zero -append "noapic
> rw root=/dev/ram"
IIRC, you need to pass the bzImage as the argument of -kernel
parameter, not the vmlinux one. Please tr
On 01.04.2010, at 15:49, Andreas Färber wrote:
>
> Am 26.03.2010 um 03:44 schrieb Rob Landley:
>
>> According to "qemu-system-ppc -M ?", g3beige is still the default. The mac99
>> machine is the default for ppc64. (Are there newworlds that run a 32 bit ppc
>> instead of a 64 bit ppc?)
>
> Th
Am 01.04.2010 um 23:18 schrieb Bastian Blank :
On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
This patch adds a firmware blob to the S390 target. The blob is a
simple
implementation of a virtio client that tries to read the second stage
bootloader from sectors described as o
On Wed, Mar 24, 2010 at 03:34:00PM -0500, Rob Landley wrote:
> I have a native build under qemu that gets killed if it doesn't produce a
> line
> of output for 60 seconds (hang detection enforced by the host monitoring
> qemu's stdout with --nographic, not from within qemu).
>
> In the most rec
On 04/01/2010 04:56 PM, Stefan Weil wrote:
u_int64_t raises compiler error messages:
CClibhw32/virtio.o
/qemu/ar7/hw/virtio.c: In function ‘virtio_queue_get_avail_size’:
/qemu/ar7/hw/virtio.c:776: error: ‘u_int64_t’ undeclared (first use in this
function)
/qemu/ar7/hw/virtio.c:776: error
u_int64_t raises compiler error messages:
CClibhw32/virtio.o
/qemu/ar7/hw/virtio.c: In function ‘virtio_queue_get_avail_size’:
/qemu/ar7/hw/virtio.c:776: error: ‘u_int64_t’ undeclared (first use in this
function)
/qemu/ar7/hw/virtio.c:776: error: (Each undeclared identifier is reported only
Signed-off-by: Adam Lackorzynski
---
target-i386/op_helper.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/target-i386/op_helper.c b/target-i386/op_helper.c
index 22259df..dcbdfe7 100644
--- a/target-i386/op_helper.c
+++ b/target-i386/op_helper.c
@@ -1231,7 +1231,7 @@
Signed-off-by: Adam Lackorzynski
---
hw/debugcon.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/debugcon.c b/hw/debugcon.c
index d549091..5ee6821 100644
--- a/hw/debugcon.c
+++ b/hw/debugcon.c
@@ -60,7 +60,7 @@ static uint32_t debugcon_ioport_read(void *opaque, uin
On Thu, Apr 01, 2010 at 06:42:41PM +0200, Alexander Graf wrote:
> This patch adds a firmware blob to the S390 target. The blob is a simple
> implementation of a virtio client that tries to read the second stage
> bootloader from sectors described as of offset 0x20 in the MBR.
How do you intend to
In the previous patch which introduced fprintf_function to
allow parameter checking by gcc some compiler warnings
remained unfixed.
These warnings are fixed here.
Signed-off-by: Stefan Weil
---
target-mips/translate.c | 34 --
1 files changed, 20 insertions(+),
On Thu, 01 Apr 2010 21:14:30 +0200
Kevin Wolf wrote:
> Am 01.04.2010 20:22, schrieb Luiz Capitulino:
> > On Thu, 1 Apr 2010 15:15:51 -0300
> > Luiz Capitulino wrote:
> >
> >> On Thu, 25 Mar 2010 09:32:58 -0500
> >> Ryan Harper wrote:
> >>
> >>> Currently when using the change command to switch
When two requests of the same multiwrite batch fail, the callback of all
requests in that batch were called twice. This could have any kind of nasty
effects, in my case it lead to use after free and eventually a segfault.
Signed-off-by: Kevin Wolf
---
block.c |2 +-
1 files changed, 1 insert
On 4/1/10, Artyom Tarasenko wrote:
> 2010/4/1 Blue Swirl :
> > Which list?
>
> This mailing list?
>
>
> > On 4/1/10, Artyom Tarasenko wrote:
> >> and looks wrong or incomplete to me:
> >>
> >> >According to Sun4M System Architecture Manual chapter 5.3.2, a limit
> >> >of 0 will not gener
On 4/1/10, Anthony Liguori wrote:
> On 04/01/2010 03:07 PM, Blue Swirl wrote:
>
> > Remove dependency of vl.c to KVM, then we can partially revert
> > b33612d03540fda7fa67485f1c20395beb7a2bf0.
> >
> > Signed-off-by: Blue Swirl
> > ---
> > Makefile.objs |2 +-
> > Makefile.target |2 +-
>
On 04/01/2010 10:07 PM, Blue Swirl wrote:
Remove dependency of vl.c to KVM, then we can partially revert
b33612d03540fda7fa67485f1c20395beb7a2bf0.
This is ugly...
Michael Tsirkin said in commit ca821806:
Comment on kvm usage: rather than require users to do if(kvm_enabled())
and/or ifdefs,
2010/4/1 Blue Swirl :
> Which list?
This mailing list?
> On 4/1/10, Artyom Tarasenko wrote:
>> and looks wrong or incomplete to me:
>>
>> >According to Sun4M System Architecture Manual chapter 5.3.2, a limit
>> >of 0 will not generate interrupts.
>>
>> This is indeed correct, but the chapter
On 04/01/2010 03:07 PM, Blue Swirl wrote:
Remove dependency of vl.c to KVM, then we can partially revert
b33612d03540fda7fa67485f1c20395beb7a2bf0.
Signed-off-by: Blue Swirl
---
Makefile.objs |2 +-
Makefile.target |2 +-
arch_init.c | 20
arch_init.h
Signed-off-by: Blue Swirl
---
I'm not sure this patch is worth applying. Anyway, it proves that no
non-target devices use kvm.h.
hw/acpi.c | 10 +-
hw/pc.h |2 +-
hw/poison.h |3 +++
3 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/hw/acpi.c b/hw/acpi.c
inde
Remove dependency of vl.c to KVM, then we can partially revert
b33612d03540fda7fa67485f1c20395beb7a2bf0.
Signed-off-by: Blue Swirl
---
Makefile.objs |2 +-
Makefile.target |2 +-
arch_init.c | 20
arch_init.h |2 ++
vl.c| 14 ++--
Which list?
On 4/1/10, Artyom Tarasenko wrote:
> and looks wrong or incomplete to me:
>
> >According to Sun4M System Architecture Manual chapter 5.3.2, a limit
> >of 0 will not generate interrupts.
>
> This is indeed correct, but the chapter 5.3.2 also explains why:
>
> "Setting the limit reg
On Wed, 31 Mar 2010, Gerd Hoffmann wrote:
I'm also interested in a backport to the 0.12.x version that I can test.
Can this be easily done?
http://git.savannah.gnu.org/cgit/qemu.git/log/hw/lsi53c895a.c
Pick the five most recent patches (committed jan 11th) and apply the patch
posted in this
On Sun, Mar 28, 2010 at 11:44:41AM +0200, Stefan Weil wrote:
> Commit c05c7a7306a23a4b01d1606172b142c45caffc92
> breaks cross compilation for mips (and other
> compilations without CONFIG_INOTIFY1):
>
> make[1]: Entering directory `/qemu/bin/mips'
> CCi386-linux-user/syscall.o
> cc1: warning
and looks wrong or incomplete to me:
>According to Sun4M System Architecture Manual chapter 5.3.2, a limit
>of 0 will not generate interrupts.
This is indeed correct, but the chapter 5.3.2 also explains why:
"Setting the limit register to 0 allows the counter to free run. Since the
timer alway
Does current qemu-kvm (qemu v0.12.3) use the irqchip, pit of KVM? I
cannot find any KVM_CREATE_IRQCHIP and KVM_CREATE_PIT in the qemu
code.
Concerning the interface between qemu and kvm, I have the following confusion:
1. How irqchip and pit of KVM collaborating with the irq and pit
emulation of Q
On 03/17/2010 06:07 AM, Michael S. Tsirkin wrote:
Will be used by vhost to attach/detach to backend.
Signed-off-by: Michael S. Tsirkin
Applied. Thanks.
Regards,
Anthony Liguori
---
net/tap.c |7 +++
net/tap.h |2 ++
2 files changed, 9 insertions(+), 0 deletions(-)
dif
Am 01.04.2010 20:22, schrieb Luiz Capitulino:
> On Thu, 1 Apr 2010 15:15:51 -0300
> Luiz Capitulino wrote:
>
>> On Thu, 25 Mar 2010 09:32:58 -0500
>> Ryan Harper wrote:
>>
>>> Currently when using the change command to switch the file in the cd drive
>>> the command doesn't complain if the file
On 4/1/10, Nigel Horne wrote:
>
>
> > just for the record: a build of QEMU from HEAD with
> > '--enable-io-thread' fails. In "vl.c" "qemu_system_ready" is used but
> > not declared any longer.
> >
> >
> I noticed this yesterday evening. The thing is that qemu_system_ready is
> defined in cpus.c,
On Thu, 1 Apr 2010 13:23:44 -0500
Ryan Harper wrote:
> * Luiz Capitulino [2010-04-01 13:17]:
> > On Thu, 25 Mar 2010 09:32:58 -0500
> > Ryan Harper wrote:
> >
> > > Currently when using the change command to switch the file in the cd drive
> > > the command doesn't complain if the file doesn't
* Luiz Capitulino [2010-04-01 13:17]:
> On Thu, 25 Mar 2010 09:32:58 -0500
> Ryan Harper wrote:
>
> > Currently when using the change command to switch the file in the cd drive
> > the command doesn't complain if the file doesn't exit or can't be opened
> > and the drive keeps the existing image
On Thu, 1 Apr 2010 15:15:51 -0300
Luiz Capitulino wrote:
> On Thu, 25 Mar 2010 09:32:58 -0500
> Ryan Harper wrote:
>
> > Currently when using the change command to switch the file in the cd drive
> > the command doesn't complain if the file doesn't exit or can't be opened
> > and the drive keep
On Thu, 25 Mar 2010 09:32:58 -0500
Ryan Harper wrote:
> Currently when using the change command to switch the file in the cd drive
> the command doesn't complain if the file doesn't exit or can't be opened
> and the drive keeps the existing image. This patch adds a qerror_report
> call to print
With argument checking for cpu_fprintf, gcc throws this warning:
CCi386-softmmu/helper.o
cc1: warnings being treated as errors
/qemu/ar7/target-i386/helper.c: In function ‘cpu_x86_dump_seg_cache’:
/qemu/ar7/target-i386/helper.c:220: error: format not a string literal and no
format arguments
Signed-off-by: Paolo Bonzini
---
Makefile.target |2 +-
balloon.c | 146 +++
balloon.h |7 +++
monitor.c | 85
vl.c| 34 -
5 files changed, 154 insertions(+)
Signed-off-by: Paolo Bonzini
---
kvm.h |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/kvm.h b/kvm.h
index 4f77188..8bbd127 100644
--- a/kvm.h
+++ b/kvm.h
@@ -31,6 +31,10 @@ struct kvm_run;
int kvm_init(int smp_cpus);
+int kvm_has_sync_mmu(void);
+int kvm_has_
With more files from outside the hw/ directory being placed into
libhw, avoid the need to include hw/hw.h for the sake of targ_phys_addr_t.
Signed-off-by: Paolo Bonzini
---
cpu-common.h|8
hw/hw.h |2 --
hw/poison.h => poison.h |0
3 files changed
Signed-off-by: Paolo Bonzini
---
hw/i8259.c |1 +
hw/isa-bus.c |1 +
vl.c |4
3 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/hw/i8259.c b/hw/i8259.c
index 3de22e3..37ef04e 100644
--- a/hw/i8259.c
+++ b/hw/i8259.c
@@ -68,6 +68,7 @@ static int irq_level[16
Signed-off-by: Paolo Bonzini
---
qemu-sockets.c | 24
qemu_socket.h |1 +
vl.c | 24
3 files changed, 25 insertions(+), 24 deletions(-)
diff --git a/qemu-sockets.c b/qemu-sockets.c
index 23c3def..a7399aa 100644
--- a/qemu-socke
v2->v3
- re-rebased
- salvage some cleanups made while trying to compile balloon.c once,
but do not do it because it breaks (I have patches to do it also for
vl.o, but they are ugly!)
Paolo Bonzini (5):
move socket_init to qemu-sockets.c
move two variable declarations out of vl.c
move targph
On Thu, Apr 01, 2010 at 11:59:11AM +, Paul Brook wrote:
> > Oh this is happening with x86_64-bsd-user on the same arch so I'd say
> > (abi_ulong)-1 would be the same as ~0ul (and still cause the assert.)
>
> No. These two are different when sizeof(abi_ulong) < sizeof(long).
Yeah sorry I meant
Virtio-Console can only process one character at a time. Using it on S390
gave me strage "lags" where I got the character I pressed before when
pressing one. So I typed in "abc" and only received "a", then pressed "d"
but the guest received "b" and so on.
While the stdio driver calls a poll functi
This patch adds a firmware blob to the S390 target. The blob is a simple
implementation of a virtio client that tries to read the second stage
bootloader from sectors described as of offset 0x20 in the MBR.
In combination with an updated zipl this allows for booting from virtio
block devices. This
The KVM kernel module on S390 refuses to create a VM when the switch_amode
kernel parameter is not used.
Since that is not exactly obvious, let's give the user a nice warning.
Signed-off-by: Alexander Graf
---
kvm-all.c |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --gi
While improving KVM on S390x I stumbled across some more issues. The most
annoying ones were in the character layer, where -nographic would just fail
on most users. This set fixes these issues.
The set also adds support for my new zipl bootloader. Using this firmware
and a patches version of zipl
When using virtio-console on s390, the input doesn't work.
The root of the problem is rather simple. What happens is the following:
1) create character device for stdio
2) char device is done creating, sends OPENED event
3) virtio-console adds handlers
4) no event comes because the char devic
The guest may issue a RESET command for virtio. So far we didn't bother
to implement it, but with my new bootloader we actually need it for Linux
to get back to a safe state.
Signed-off-by: Alexander Graf
---
hw/s390-virtio-bus.c |3 +--
hw/s390-virtio-bus.h |1 +
hw/s390-virtio.c |
We don't implement any virtual memory in the S390 target so far, so let's
add a stub for this now mandatory function.
Fixes building of S390 target.
Signed-off-by: Alexander Graf
---
target-s390x/helper.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/target-s390x/
Aurelien Jarno wrote:
> On Thu, Mar 25, 2010 at 02:58:59PM +0100, Alexander Graf wrote:
>
>> We're in a bad situation with the S390 qemu target. It only works with KVM,
>> so people can't test it when they don't have access to a real S390 machine.
>>
>> While trying to build and use s390x-softmm
On 4/1/10, Aurelien Jarno wrote:
> On Wed, Mar 31, 2010 at 02:24:51PM -0500, Anthony Liguori wrote:
> > On 03/31/2010 02:07 PM, Michael S. Tsirkin wrote:
> >> On Wed, Mar 31, 2010 at 03:38:05PM -0300, Luiz Capitulino wrote:
> >>
> >>> On Wed, 31 Mar 2010 13:26:23 -0500
> >>> Anthony Liguori
On 04/01/2010 10:54 AM, Blue Swirl wrote:
On 4/1/10, Anthony Liguori wrote:
On 03/31/2010 05:45 PM, Aurelien Jarno wrote:
While it probably make sense to achieve this goal, it doesn't mean it
should be done the dirty way.
For example it is known for a lot of time that the solution
On 4/1/10, Anthony Liguori wrote:
> On 03/31/2010 05:45 PM, Aurelien Jarno wrote:
>
> > While it probably make sense to achieve this goal, it doesn't mean it
> > should be done the dirty way.
> >
> > For example it is known for a lot of time that the solution for the
> > bswap in the device code i
> On 04/01/2010 04:14 PM, Paul Brook wrote:
> >>> On a philosophical note, threads may be easier to model complex
> >>> hardware that includes a processor, for example our scsi card (and how
> >>> about using tcg as a jit to boost it :)
> >>
> >> Yeah, it's hard to argue that script evaluation shou
On Wed, Mar 31, 2010 at 10:38:47PM +0300, Blue Swirl wrote:
> > Maybe it makes sense to revert the compile once patches, and discuss
> > these issues before re-commit?
>
> Maybe I'll try to remember this as your favourite problem solving
> approach if I happen to dislike the changes your patches
On 04/01/2010 04:14 PM, Paul Brook wrote:
On a philosophical note, threads may be easier to model complex
hardware that includes a processor, for example our scsi card (and how
about using tcg as a jit to boost it :)
Yeah, it's hard to argue that script evaluation shouldn't be done in
configure adds the macro WIN32_LEAN_AND_MEAN to
QEMU_CFLAGS, and SDL_syswm.h defines it, too.
This results in a compiler warning (redefinition of
WIN32_LEAN_AND_MEAN in SDL_syswm.h. That warning prevents
compilations for win32 with warning = error).
Fix this by removing the definition of WIN32_LE
>> >This patch adds support for virtio-rng. Data is read from a
>> > chardev and can be either raw entropy or received via the EGD protocol.
>>
>> I still don't get why you need this at all. It seems like
>> virtio-serial would already provides everything you need.
>
>I guess when virtio-rn
Am 26.03.2010 um 03:44 schrieb Rob Landley:
According to "qemu-system-ppc -M ?", g3beige is still the default.
The mac99
machine is the default for ppc64. (Are there newworlds that run a
32 bit ppc
instead of a 64 bit ppc?)
There are. All G3 and G4 PowerMacs, iMacs, iBooks were ppc32 AF
>CPU #0CPU #1
>
>x <- load-locked(A)
>y <- load(B)
> x+1 -> store(A)
> y+1 -> store(B)
> x -> store(A)
>f(x,y) -> store-cond(A)
>
> Unless I made a mistake, the above cannot store f(x,y+1)
>>> 1) state machines with a thread pool to make blocking functions
>>> asynchronous (what we have today)
>>>
>>> 2) co-operative threading
>>>
>>> 3) pre-emptive threading
> > On a philosophical note, threads may be easier to model complex
> > hardware that includes a processor, for example our s
> > One example is the openpic page size pointed out downthread.
> >
> > What about something like this (doesn't change all the places affected
> > by your series, compile-tested only)?
>
> In general (with vmport and maybe virtio as the only exceptions), the
> devices have no business knowing
Paul Brook wrote:
> >This patch adds support for virtio-rng. Data is read from a chardev
> > and can be either raw entropy or received via the EGD protocol.
>
> I still don't get why you need this at all. It seems like
> virtio-serial would already provides everything you need.
I guess wh
> Wenhao Xu wrote:
> > Hi, Juan,
> >I am fresh to both QEMU and KVM. But so far, I notice that QEMU
> > uses "KVM_SET_USER_MEMORY_REGION" to set memory region that KVM can
> > use and uses cpu_register_physical_memory_offset to register the same
> > memory to QEMU emulator, which means QEMU an
>This patch adds support for virtio-rng. Data is read from a chardev
> and can be either raw entropy or received via the EGD protocol.
I still don't get why you need this at all. It seems like virtio-serial would
already provides everything you need.
> +qemu_gettimeofday(&now);
> But this makes kvm_enabled() check dynamic and code that was
> eliminated by compiler for !CONFIG_KVM will now be generated.
>
> Wouldn't adding CONFIG_KVM to config-host.h also solve the problem?
CONFIG_KVM is (and should be) a per-target decision.
Paul
> I'm wondering take part on GSoC with QEMU, I really liked the "IOMMU
> emulation project". However I only know basically how an IOMMU works,
> but that is not a big a deal, I can learn about it and implement.
> Besides read the code and learn how a IOMMU works what else more do I
> need to do? Al
> Oh this is happening with x86_64-bsd-user on the same arch so I'd say
> (abi_ulong)-1 would be the same as ~0ul (and still cause the assert.)
No. These two are different when sizeof(abi_ulong) < sizeof(long).
Paul
> I will contact jai soon about the S3 Trio. I'll also skim through the
> documentation so that I can set reasonable goals in my timeline.
TBH I'm less convinced about the utility of emulating an S3 graphics card.
You'd want to make sure you know what you're expecting from it.
While it may have
On 04/01/2010 01:59 PM, Michael S. Tsirkin wrote:
On Thu, Apr 01, 2010 at 11:58:29AM +0300, Avi Kivity wrote:
On 03/31/2010 12:12 PM, Michael S. Tsirkin wrote:
$ echo 4> /sys/.../msix/allocate
$ # subdirectories 0 1 2 3 magically appear
$ # bind fd 13 to msix
On Thu, Apr 01, 2010 at 11:58:29AM +0300, Avi Kivity wrote:
> On 03/31/2010 12:12 PM, Michael S. Tsirkin wrote:
>>
>>
>>>$ echo 4> /sys/.../msix/allocate
>>>$ # subdirectories 0 1 2 3 magically appear
>>>$ # bind fd 13 to msix
>>>
>> There's no way to know, when qemu starts, how
On 03/30/2010 05:52 PM, Cam Macdonell wrote:
Ah, the usual "ioctls are ugly, go away".
It could be done via sysfs:
$ cat /sys/.../msix/max-interrupts
256
$ echo 4> /sys/.../msix/allocate
$ # subdirectories 0 1 2 3 magically appear
$ # bind fd 13 to msix
$ echo 13> /sys/.../msix/
On 03/31/2010 12:12 PM, Michael S. Tsirkin wrote:
$ echo 4> /sys/.../msix/allocate
$ # subdirectories 0 1 2 3 magically appear
$ # bind fd 13 to msix
There's no way to know, when qemu starts, how many vectors will be used
by driver. So I think we can just go ahead and allocat
Luiz Capitulino writes:
> Trivial, as it never fails, doesn't have output nor return
> any data.
>
> Note that it's also available under QMP, as kvm-autotest
> needs this.
>
> Signed-off-by: Luiz Capitulino
Looks good.
Aside: screen dump fails silently, but that's outside the scope of QMP
conv
just for the record: a build of QEMU from HEAD with
'--enable-io-thread' fails. In "vl.c" "qemu_system_ready" is used but
not declared any longer.
I noticed this yesterday evening. The thing is that qemu_system_ready
is defined in cpus.c, but it's a static variable.
Dirk
-Nigel
On 03/31/2010 02:31 PM, Juan Quintela wrote:
Wenhao Xu wrote:
Hi, Juan,
I am fresh to both QEMU and KVM. But so far, I notice that QEMU
uses "KVM_SET_USER_MEMORY_REGION" to set memory region that KVM can
use and uses cpu_register_physical_memory_offset to register the same
memory to QEM
On 03/31/2010 09:27 PM, Anthony Liguori wrote:
On 03/31/2010 02:19 PM, Blue Swirl wrote:
On 3/31/10, Anthony Liguori wrote:
On 03/27/2010 05:11 PM, Blue Swirl wrote:
Move target specific functions and RAM handling to arch_init.c.
Add a flag to QEMUOptions structure to indicate for which
arch
On 03/31/2010 05:25 PM, Paolo Bonzini wrote:
balloon.c contained some code from monitor.c, so it was compiled
once per target. Fix this.
This patch is wrong just like Blue Swirl's vl.c patch. The other 4 are
fine though.
Paolo
On 03/31/10 09:33, Amit Shah wrote:
Hello,
These patches rework the way ports are announced to the guests. A
control message is used to let the guest know a new port is
added. Initial port discovery and port hot-plug work via this way now.
This was done to have the host and guest port numbering
77 matches
Mail list logo
