Public bug reported:
Hello,
I try to execute on linux machine sparc binary (simple hello word application)
using qemu-sparc32plus
and get segfault.Before test I copy all libraries and headers
(/usr/lib, /lib/, /usr/local/lib /usr/include /usr/local/include)
from original solaris workstation t
Implement a threaded VNC server using the producer-consumer model.
The main thread will push encoding jobs (a list a rectangles to update)
in a queue, and the VNC worker thread will consume that queue and send
framebuffer updates to the output buffer.
The threaded VNC server can be enabled with ./
Hi,
This series add a threaded VNC server and should be applied on top on my
previous patch set (adding tight encoding).
The first patch add some functions to qemu-thread. The last oneis the threaded
VNC server.
Thanks
Since v1:
* Moved locks from VncState to VncDisplay because it's only used i
Add some missing functions in qemu-thread. Currently qemu-thread
is only used for io-thread but it will used by the vnc server soon
and we need those functions instead of calling pthread directly.
Signed-off-by: Corentin Chary
---
qemu-thread.c | 22 ++
qemu-thread.h |4
Thanks to IRC, the correct syntax is: -netdev
tap,id=asa1_eth0_tap,ifname=asa1_eth0_tap -device
e1000,netdev=asa1_eth0_tap,mac=00:aa:cd:dd:01:01
(noted, fd=h option doesn't work on -netdev)
--
QEMU netdev tap type id name is not used on linux host
https://bugs.launchpad.net/bugs/589827
You recei
Apologies if I'm spamming this venue - truly just trying to be of assistance.
Just got done installing the new updates to packages
qemu bochsbios qemu-kvm seabios vgabios - still did not fix the failure to
recognize the mouse.
--
Windows 98 doesn't detect mouse on qemu and SeaBIOS.
https://b
Signed-off-by: Sheng Yang
---
qemu-kvm-x86.c| 114
qemu-kvm.c| 24 ++
qemu-kvm.h| 28
target-i386/cpu.h |6 +++
target-i386/machine.c | 21 +
5 files changed, 174 insertio
We can support it in KVM now. The 0xd leaf is queried from KVM.
Signed-off-by: Sheng Yang
---
target-i386/cpuid.c | 21 +
1 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/target-i386/cpuid.c b/target-i386/cpuid.c
index fb78061..26e4054 100644
--- a/target-i38
Would use it later for XSAVE related CPUID.
Signed-off-by: Sheng Yang
---
kvm.h |2 +-
target-i386/kvm.c | 19 +++
2 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/kvm.h b/kvm.h
index aab5118..16b06a4 100644
--- a/kvm.h
+++ b/kvm.h
@@ -152,7 +152,
On 06/10/2010 05:37 AM, Dong, Eddie wrote:
Avi Kivity wrote:
On 06/09/2010 06:59 PM, Dong, Eddie wrote:
Besides VF IO interrupt and timer interrupt introduced performance
overhead risk,
VF usually uses MSI
Typo, I mean PV IO.
That also uses MSI these days.
A VF
Avi Kivity wrote:
> On 06/09/2010 06:59 PM, Dong, Eddie wrote:
>>
>> Besides VF IO interrupt and timer interrupt introduced performance
>> overhead risk,
>
> VF usually uses MSI
Typo, I mean PV IO.
A VF interrupt usually happens in 4-8KHZ. How about the virtio?
I assume virtio will be widely u
On Fri, Jun 04, 2010 at 12:14:13PM -0700, Richard Henderson wrote:
> Before gcc 4.2, __builtin___clear_cache doesn't exist, and
> afterward the gcc s390 backend implements it as nothing.
Does it means that instruction and data caches are coherent on s390?
> Signed-off-by: Richard Henderson
> ---
On Fri, Jun 04, 2010 at 12:14:11PM -0700, Richard Henderson wrote:
> The default placement of the application at 0x8000 is fine,
> and will avoid the default placement for most other guests.
>
> Signed-off-by: Richard Henderson
> ---
> configure |3 +++
> 1 files changed, 3 insertions(+)
On Fri, Jun 04, 2010 at 12:14:14PM -0700, Richard Henderson wrote:
> This allows the use of direct calls to the helpers,
> and a direct branch back to the epilogue.
>
> Signed-off-by: Richard Henderson
> ---
> exec.c |7 +++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --
On Fri, Jun 04, 2010 at 12:14:12PM -0700, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> cpu-exec.c | 42 +++---
> 1 files changed, 39 insertions(+), 3 deletions(-)
Thanks, applied.
> diff --git a/cpu-exec.c b/cpu-exec.c
> index c776605
On Fri, Jun 04, 2010 at 12:14:10PM -0700, Richard Henderson wrote:
> There's no _llseek on s390x either. Replace the existing
> test for __x86_64__ with a functional test for __NR_llseek.
>
> Signed-off-by: Richard Henderson
> ---
> linux-user/syscall.c |4 ++--
> 1 files changed, 2 inserti
On Fri, Jun 04, 2010 at 12:14:09PM -0700, Richard Henderson wrote:
> Force -m31/-m64 based on s390/s390x target.
>
> Force -march=z990. The TCG backend will always require the
> long-displacement facility, so the compiler may as well make
> use of that as well.
>
> Signed-off-by: Richard Henders
On Fri, Jun 04, 2010 at 12:14:17PM -0700, Richard Henderson wrote:
> The full general-instruction-extension facility was added to binutils
> after the change to GPLv3. This is not the entire extension, just
> what we're using in TCG.
>
> Signed-off-by: Richard Henderson
> ---
> s390-dis.c | 8
On Fri, Jun 04, 2010 at 12:14:16PM -0700, Richard Henderson wrote:
> Signed-off-by: Richard Henderson
> ---
> s390-dis.c | 81
> +---
> 1 files changed, 50 insertions(+), 31 deletions(-)
Thanks, applied.
> diff --git a/s390-dis.c b/s390
> >> AFAICS the current commandline options only result in simple addition of
> >> devices. They might add slightly different devices in slightly different
> >> places, but that's easy to accommodate by having the machine define a
> >> few standard device/bus IDs.
> >>
> >> IMO it's even more lame
On Wed, May 26, 2010 at 04:08:15PM +0200, Paolo Bonzini wrote:
> This series cleans up the handling of --xyzdir options and
> improves the customizability of the directory layout.
>
> Patches 1/2/3/14 are somewhat unrelated to the main purpose
> of the patch, but they conflict with other patches i
2010/6/10 Juan Quintela :
> Yoshiaki Tamura wrote:
>> Hi Juan,
>>
>
>> I don't know I have addressed the problem correctly, but here is my
>> try to get "info migrate" on incoming side.
>>
>> http://lists.gnu.org/archive/html/qemu-devel/2010-06/msg00417.html
>
> I saw it, haven't had the time to l
This patch fixes the following error report. When changing
migration-tcp.c to call migrate_fd_error() instead of close() and
free() by itself, monitor is resumed, and returns allocated mig_state
is set to current_migration in migration.c allows us to print "info
migrate".
Reported-by: Cole Robins
On Wed, Jun 09, 2010 at 10:09:40PM +0200, Stefan Weil wrote:
> TCGv t1 needs tcg_temp_free instead of tcg_temp_free_i32.
>
> Cc: Nathan Froyd
> Cc: Aurelien Jarno
> Signed-off-by: Stefan Weil
> ---
> target-mips/translate.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Thanks
** Changed in: qemu
Status: Confirmed => In Progress
--
qemu: Improve error reporting when migration can't connect
https://bugs.launchpad.net/bugs/589315
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: In Progress
2010/6/10 Luiz Capitulino :
> On Wed, 9 Jun 2010 14:10:53 +0200
> Juan Quintela wrote:
>
>> This is a resent with what we agreed on yesterday call.
>> Migration events would be there for 0.13 until we get proper
>> async command support.
>
> Something which is not clear to me is the set of event
2010/6/10 Alex Williamson :
> On Wed, 2010-06-09 at 14:11 -0600, Cam Macdonell wrote:
>> On Tue, Jun 8, 2010 at 1:15 PM, Alex Williamson
>> > diff --git a/cpu-all.h b/cpu-all.h
>> > index 77eaf85..458cb4b 100644
>> > --- a/cpu-all.h
>> > +++ b/cpu-all.h
>> > @@ -859,9 +859,21 @@ target_phys_addr_t
Hi all,
I was wondering if anybody had success in running eCos and RedBoot in
qemu, specifically on Integrator or Versatile boards.
I can see that eCos has Integrator port, but for ARM7TDMI and
ARM966E-S variants, and qemu emulated Integrator does not have these.
I am specially interested in this
On Wed, Jun 9, 2010 at 8:52 PM, Anthony Liguori wrote:
> On 06/09/2010 03:47 PM, Blue Swirl wrote:
>>
>> On Wed, Jun 9, 2010 at 2:30 PM, Paul Brook wrote:
>>
>>
>> Because at some point the base tree will have to be written in C.
>>
>
> No. You can start with a completely empt
Perhaps you have found an endianness bug as well, but my issue is with
word size (my host is a 64-bit Intel). I manually applied the patch to
a 0.12.3 build, and I am still seeing the problem with the curses
console.
It seems that the console_ch_t type is used in a number of different
contexts.
On Wed, 2010-06-09 at 14:11 -0600, Cam Macdonell wrote:
> On Tue, Jun 8, 2010 at 1:15 PM, Alex Williamson
> > diff --git a/cpu-all.h b/cpu-all.h
> > index 77eaf85..458cb4b 100644
> > --- a/cpu-all.h
> > +++ b/cpu-all.h
> > @@ -859,9 +859,21 @@ target_phys_addr_t cpu_get_phys_page_debug(CPUState
>
On Wed, 9 Jun 2010 14:10:56 +0200
Juan Quintela wrote:
> They are emitted when migration starts, ends, has a failure or is canceled.
>
> Signed-off-by: Juan Quintela
> ---
> QMP/qmp-events.txt | 52
>
> monitor.c | 12
On 06/09/2010 03:47 PM, Blue Swirl wrote:
On Wed, Jun 9, 2010 at 2:30 PM, Paul Brook wrote:
Because at some point the base tree will have to be written in C.
No. You can start with a completely empty machine.
We don't/shouldn't need any machine specific C code.
I thi
On Wed, 9 Jun 2010 14:10:53 +0200
Juan Quintela wrote:
> This is a resent with what we agreed on yesterday call.
> Migration events would be there for 0.13 until we get proper
> async command support.
Something which is not clear to me is the set of events we'd have if migrate
was an async com
On Wed, Jun 9, 2010 at 2:30 PM, Paul Brook wrote:
>> >> Because at some point the base tree will have to be written in C.
>> >
>> > No. You can start with a completely empty machine.
>> > We don't/shouldn't need any machine specific C code.
>>
>> I think you're missing the argument. I should be p
It sounds like this is an existing image that you can't boot from. I
can create a new 2k3 VM with upstream qemu and boot it again after
install with no issues. So I'm wondering if you can also do this. If
so, then something happened to your existing image (maybe some sort of
corruption of the bo
On Tue, 8 Jun 2010 12:38:58 +0530
Prerna Saxena wrote:
> This patch adds support for dynamically enabling/disabling of tracepoints.
> Monitor commands added :
> 1) info tracepoints : to view all available tracepoints and
> their state.
> 2) tracepoint NA
On Tue, 8 Jun 2010 12:34:37 +0530
Prerna Saxena wrote:
> This introduces the monitor command 'trace' to read current contents of
> trace buffer.
>
>
> Signed-off-by: Prerna Saxena
> ---
> configure |3 +++
> monitor.c |3 +++
> qemu-monitor.hx | 16
>
> > Not really. This identifier is device and bus independent, which is why
> > I suggested passing the device to qemu_ram_alloc. This can then figure
> > out how to the identify the device. It should probably do this the same
> > way that we identify the saved state for the device. Currently I
On Fri, Jun 4, 2010 at 8:30 PM, Artyom Tarasenko
wrote:
> 2010/6/4 Blue Swirl :
>> On Tue, Jun 1, 2010 at 8:16 PM, Artyom Tarasenko
>> wrote:
>>> 2010/6/1 Blue Swirl :
On Tue, Jun 1, 2010 at 7:56 PM, Artyom Tarasenko
wrote:
> 2010/6/1 Blue Swirl :
>> On Sun, May 30, 2010 at 10:
On Tue, 8 Jun 2010 12:31:38 +0530
Prerna Saxena wrote:
> This exports tdb_hash() for use by tracing framework.
Suggest to rename it (eg. qemu_hash()) and move it to a better location, qdict
is not the best module to export such service.
>
> Signed-off-by: Prerna Saxena
> ---
> qdict.c |
On Mon, 07 Jun 2010 11:07:14 -0500
Anthony Liguori wrote:
> Hi Daniel,
>
> On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
> > As everyone here agrees, having management apps parse -help output
> > to determine the QEMU capabilities is not at all nice, because it
> > is an ill-defined& fragil
On Mon, Jun 7, 2010 at 4:41 PM, Cam Macdonell wrote:
> On Sat, Jun 5, 2010 at 3:44 AM, Blue Swirl wrote:
>> On Fri, Jun 4, 2010 at 9:45 PM, Cam Macdonell wrote:
>>> Support an inter-vm shared memory device that maps a shared-memory object
>>> as a
>>> PCI device in the guest. This patch also s
nudge. Any comments here?
On Wed, Jun 2, 2010 at 10:58 AM, Alex Williamson
wrote:
>
> PCI hotplug currently doesn't work after a migration because
> we don't migrate the enable bits of the GPE state. Pull hotplug
> structs into vmstate.
>
> Signed-off-by: Alex Williamson
> ---
>
> hw/acpi_pii
On Tue, Jun 8, 2010 at 1:15 PM, Alex Williamson
wrote:
> This makes the RAM block list easier to manipulate. Also incorporate
> relevant variables into the RAMList struct.
>
> Signed-off-by: Alex Williamson
> ---
>
> arch_init.c | 14 ++-
> cpu-all.h | 28 ---
>
TCGv t1 needs tcg_temp_free instead of tcg_temp_free_i32.
Cc: Nathan Froyd
Cc: Aurelien Jarno
Signed-off-by: Stefan Weil
---
target-mips/translate.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index 3473281..940f57
On Mon, 07 Jun 2010 12:07:56 -0500
Anthony Liguori wrote:
> On 06/07/2010 11:44 AM, Daniel P. Berrange wrote:
> > On Mon, Jun 07, 2010 at 10:13:27AM -0500, Anthony Liguori wrote:
> >
> >> On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
> >>
> >>> Add a new QMP monitor command 'query-m
On Mon, 07 Jun 2010 10:11:28 -0500
Anthony Liguori wrote:
> On 06/07/2010 09:42 AM, Daniel P. Berrange wrote:
> > A previous discussion brought up the fact that clients should
> > not have to parse version string from QMP, it should be given
> > to them pre-split.
> >
> > Change query-version out
On Sun, Jun 6, 2010 at 5:39 PM, Paolo Bonzini wrote:
> On 06/05/2010 11:31 PM, Blue Swirl wrote:
>>
>> Use only an opaque CPUState pointer and move the actual CPUState
>> contents handling to cpu.h and cpuid.c.
>>
>> Set env->halted in pc.c and add a function to get the local APIC state
>> of the
On Mon, 7 Jun 2010 15:42:21 +0100
"Daniel P. Berrange" wrote:
> Convert the rtc clock and driftfix parameters to use enums for
> configuration. This ensures strict validation at time of config
> parsing.
>
> Also fixes a bug in qemu-config.c where 'driftfix' was never
> enabled because this is
On Mon, 7 Jun 2010 15:42:19 +0100
"Daniel P. Berrange" wrote:
> This converts the drive options if, trans, media, cache, aio,
> rerror and werror to use the QEMU_OPT_ENUM datatype. This
> standardizes the string parsing and error reporting
>
> $ qemu -drive file=foo,werror=stop3
> qemu: -d
On Mon, 7 Jun 2010 15:42:16 +0100
"Daniel P. Berrange" wrote:
> There is quite alot of code using an enumeration of possible
> values, which also needs todo conversions to/from a string
> representation of enum values. These string <-> int conversions
> have been repeated in an adhoc manner thro
On Mon, 7 Jun 2010 15:42:14 +0100
"Daniel P. Berrange" wrote:
> The monitor does not pretty-print JSON output, so that everything
> will be on a single line reply. When JSON docs get large this is
> quite unpleasant to read. For the future command line capabilities
> query ability, huge JSON doc
On Sun, Jun 6, 2010 at 4:28 PM, Artyom Tarasenko
wrote:
> 2010/6/6 Blue Swirl :
>> On Sat, Jun 5, 2010 at 11:10 PM, Bob Breuer wrote:
>>> Blue Swirl wrote:
but again: should we have a new machine with cg14 or
some switch to select TCX vs. cg14?
>
> Why not just probe for both devi
I did find a workaround - I removed the BOCH BIOS package and QEMU
package from my Lucid Install, and instead used the respective QEMU
packages from 8.04 - this worked for me. I don't know if the most
recent updates to the BIOS and QEMU packages will fix this or not - I
might not try until I get c
* Anthony Liguori [2010-06-09 14:36]:
> On 06/09/2010 02:28 PM, Ryan Harper wrote:
> >When configure qemu with --block-drv-whitelist we don't report when we are
> >blocked by the white list and the resulting error message is misleading:
> >
> >./configure --target-list=x86_64-softmmu \
> >
On 06/09/2010 02:28 PM, Ryan Harper wrote:
When configure qemu with --block-drv-whitelist we don't report when we are
blocked by the white list and the resulting error message is misleading:
./configure --target-list=x86_64-softmmu \
--block-drv-whitelist=qcow2,raw,host_device,host_
When configure qemu with --block-drv-whitelist we don't report when we are
blocked by the white list and the resulting error message is misleading:
./configure --target-list=x86_64-softmmu \
--block-drv-whitelist=qcow2,raw,host_device,host_cdrom
x86_64-softmmu/qemu-system-x86_64 -L pc
Do you mean, I should try to install and boot Win2k3 without libvirt?
If I install Windows through libvirt and boot it with a simple command line like
> qemu-kvm -hda /someimage.img -enable-kvm
it doesn't boot.
It's in fact this bug, just like Cole meant:
https://bugzilla.redhat.com/show_bug.cgi?
I wrote already which system I use (see the third reply).
It's Gentoo on AMD64 with the hardened no-multilib profile with qemu-kvm 0.12.4
and SeaBIOS 0.5.1.
It isn't really my own build. Since I use Gentoo, it was compiled on my own
computer and it's installed in /usr, not in /usr/local.
Qemu on
On Wed, 2010-06-09 at 13:18 +0100, Paul Brook wrote:
> > > > Not all ram is associated with a device.
> > >
> > > Maybe not, but where it is we should be using that information.
> > > Absolute minimum we should be using the existing qdev address rather than
> > > inventing a new one. Duplicating
On Wed, Jun 09, 2010 at 11:22:55AM -0500, Anthony Liguori wrote:
> On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
> >> However, libvirt was counting on this feature and on the snapshot
> >> commands
> >>to switch from the text Monitor. We have two options:
> >>
> >> 1. Ask them to wait one m
On 06/03/2010 05:41 PM, Yoshiaki Tamura wrote:
>
> Hi,
>
> Does the following patch fix the problem?
>
> Thanks,
>
> Yoshi
>
> [PATCH] migration-tcp: call migrate_fd_error() instead of close() and free().
>
> This patch fixes the following error report. When changing
> migration-tcp.c to cal
On Fri, May 28, 2010 at 08:01:26PM +0200, Kevin Wolf wrote:
> The following changes since commit 0c459361a1117a6c434c7b2b008a4c6c035eb4bf:
> Rabin Vincent (1):
> arm_timer: fix oneshot mode
>
> are available in the git repository at:
>
> git://repo.or.cz/qemu/kevin.git for-stable-0.12
On 06/09/2010 10:18 AM, Luiz Capitulino wrote:
The big problem is things like the block io error events. I don't see
how we can support that given what we have in 0.13. Putting errno on
the wire is a bad idea. We need to marshal a QError object using the
__class__ memory to identify it as QErr
On 06/09/2010 10:31 AM, Daniel P. Berrange wrote:
However, libvirt was counting on this feature and on the snapshot commands
to switch from the text Monitor. We have two options:
1. Ask them to wait one more release (not so good for us)
2. Try to find a way to have those features in for 0.
Avi Kivity wrote:
> I am currently investigating a problem with the a guest running Linux
> malfunctioning in the NMI watchdog code. The problem is that we don't
> handle NMI delivery mode for the local APIC LINT0 pin; instead we
> expect ExtInt deliver mode or that the line is disabled completely
Yoshiaki Tamura wrote:
> Hi Juan,
>
> I don't know I have addressed the problem correctly, but here is my
> try to get "info migrate" on incoming side.
>
> http://lists.gnu.org/archive/html/qemu-devel/2010-06/msg00417.html
I saw it, haven't had the time to look at it yet.
> Apart from that I ha
On 06/09/2010 06:59 PM, Dong, Eddie wrote:
Besides VF IO interrupt and timer interrupt introduced performance overhead
risk,
VF usually uses MSI
EOI message deliver from lapic to ioapic,
Only for non-MSI
which becomes in user land now, may have potential scalability issue. For
exam
On Wed, Jun 09, 2010 at 04:10:25PM +0200, Aurelien Jarno wrote:
> On Tue, Jun 08, 2010 at 01:29:55PM -0700, Nathan Froyd wrote:
> > This patch series adds support for the microMIPS ASE. microMIPS is a
> > new ASE similar to MIPS16, but re-encodes the entire instruction set
> > into 16-bit and 32-b
On Wed, Jun 09, 2010 at 12:18:20PM -0300, Luiz Capitulino wrote:
> On Tue, 08 Jun 2010 16:13:37 -0500
> Anthony Liguori wrote:
>
> > On 06/08/2010 03:59 PM, Luiz Capitulino wrote:
> > > Now, QError.
> > >
> > > This is something I think we should fix for 0.13. However, I still don't
> > > kno
On Tue, 08 Jun 2010 16:13:37 -0500
Anthony Liguori wrote:
> On 06/08/2010 03:59 PM, Luiz Capitulino wrote:
> > Now, QError.
> >
> > This is something I think we should fix for 0.13. However, I still don't
> > know how to get it right: most of what you say in the wiki page has already
> > been
On 06/09/2010 06:12 PM, Gleb Natapov wrote:
a) i remember that there (have been) are instructions that have a
high virtualization penalty.
are there flags that should better not be offered to a VM?
Not that I know of.
rdtscp? I think it's always emulated.
No, it executes
On Wed, Jun 09, 2010 at 06:08:23PM +0300, Avi Kivity wrote:
> On 06/09/2010 11:29 AM, Peter Lieven wrote:
> >Avi Kivity wrote:
> >>On 06/08/2010 04:44 PM, Peter Lieven wrote:
> -cpu host is good if you have identical machines and don't
> plan to add new ones.
> >>>
> >>>i will likely add ne
On 06/09/2010 11:29 AM, Peter Lieven wrote:
Avi Kivity wrote:
On 06/08/2010 04:44 PM, Peter Lieven wrote:
-cpu host is good if you have identical machines and don't plan to
add new ones.
i will likely add new ones, but my plan would be to use qemu64 and
then add all flags manually that
are
Hi Juan,
2010/6/9 Juan Quintela :
> This is a resent with what we agreed on yesterday call.
> Migration events would be there for 0.13 until we get proper
> async command support.
>
> Later, Juan.
>
> v3:
> - Add comment that MIGRATION_FAILURE will add a QError for 0.14
> (when we get internal su
> >> Because at some point the base tree will have to be written in C.
> >
> > No. You can start with a completely empty machine.
> > We don't/shouldn't need any machine specific C code.
>
> I think you're missing the argument. I should be possible to create a
> machine entirely from a FDT or vi
Hi,
with 0.12.4 it is still the case that a total idle vm takes about 6-8%
of a 2.4GHz Xeon Core.
I see that order of magitude too, no matter whenever usb is on or off.
With older qemu and usbtablet it used to be up to 25%.
cheers,
Gerd
Hi,
This make sense when you mistakenly add a pci device on a -s -S
scenario, like the scenario described on the following bug:
https://bugs.launchpad.net/qemu/+bug/544367.
It doesn't IMHO.
When ACPI-based hotplug support is present on the guest and we run
pci_del with the force option, th
On Tue, Jun 08, 2010 at 01:30:00PM -0700, Nathan Froyd wrote:
>
> Signed-off-by: Nathan Froyd
> ---
> target-mips/translate_init.c | 61
> ++
> 1 files changed, 61 insertions(+), 0 deletions(-)
>
> diff --git a/target-mips/translate_init.c b/target-mip
On Tue, Jun 08, 2010 at 01:29:55PM -0700, Nathan Froyd wrote:
> This patch series adds support for the microMIPS ASE. microMIPS is a
> new ASE similar to MIPS16, but re-encodes the entire instruction set
> into 16-bit and 32-bit instructions--in contrast to MIPS16, which
> re-encodes only integer
On Wed, Jun 9, 2010 at 4:38 AM, Gerd Hoffmann wrote:
> On 06/09/10 07:37, Marcos Oviedo wrote:
>
>> This adds a way to force the removal/unplug of previously added pci
>> devices when ACPI-based hotplug mechanism is not present.
>>
>
> Point being?
>
> If your guest can't handle pci hotplug it is
> Keep in mind, this has to be a stable string across versions of qemu
> since this is savevm/migration. Are we absolutely confident that the
> full qdev path isn't going to change? I'm more confident that a unique
> device name is going to be static across qemu versions.
The actual representati
On Tue, Jun 08, 2010 at 01:29:59PM -0700, Nathan Froyd wrote:
> Add instruction decoding for the microMIPS ASE. All we do is decode and
> then forward to the existing gen_* routines.
>
> Signed-off-by: Nathan Froyd
> ---
> target-mips/helper.h|9 +
> target-mips/mips-defs.h |1 +
>
On 06/09/2010 06:58 AM, Avi Kivity wrote:
On 06/09/2010 05:54 AM, Paul Brook wrote:
On 06/08/2010 09:30 PM, Paul Brook wrote:
The offset given to a block created via qemu_ram_alloc/map() is
arbitrary, let the caller specify a name so we can make a positive
match.
@@ -1924,7 +1925,9 @@ static
On 06/08/2010 09:11 PM, Paul Brook wrote:
Because at some point the base tree will have to be written in C.
No. You can start with a completely empty machine.
We don't/shouldn't need any machine specific C code.
I think you're missing the argument. I should be possible to create a
Gerd Hoffmann wrote:
Hi,
BUT. usb emulation is resource intensive.
Update qemu. Fixed in 0.12.4 and unstable.
hi gerd,
with 0.12.4 it is still the case that a total idle vm takes about 6-8%
of a 2.4GHz Xeon Core.
see: http://dev.cs1.dlh.net/usb-on-off.png
until approx 13.00 cet its w
> * Alex Williamson (alex.william...@redhat.com) wrote:
> > +// XXX check duplicates
>
> Yes, definitely. You created a notion of a hierarchical namespace,
> can this be formalized any more?
We already have one: The qdev tree.
Paul
> > > Not all ram is associated with a device.
> >
> > Maybe not, but where it is we should be using that information.
> > Absolute minimum we should be using the existing qdev address rather than
> > inventing a new one. Duplicating this logic inside every device seems
> > like a bad idea so I s
Signed-off-by: Juan Quintela
---
migration-exec.c |3 ++-
migration-fd.c |1 +
migration-tcp.c |2 ++
migration-unix.c |2 ++
migration.c |5 +
5 files changed, 12 insertions(+), 1 deletions(-)
diff --git a/migration-exec.c b/migration-exec.c
index 14718dd..9052c
Signed-off-by: Juan Quintela
---
migration-exec.c | 14 +-
migration-fd.c | 14 +-
migration-tcp.c | 15 ++-
migration-unix.c | 15 ++-
migration.c | 13 +
migration.h |2 ++
6 files changed, 21 insertions(+),
They are emitted when migration starts, ends, has a failure or is canceled.
Signed-off-by: Juan Quintela
---
QMP/qmp-events.txt | 52
monitor.c | 12
monitor.h |4
3 files changed, 68 insertions(+),
Signed-off-by: Juan Quintela
---
migration.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/migration.c b/migration.c
index 4ce19ff..2a44b46 100644
--- a/migration.c
+++ b/migration.c
@@ -60,10 +60,13 @@ int qemu_start_incoming_migration(const char *uri)
void proces
Signed-off-by: Juan Quintela
---
migration.c | 16 ++--
migration.h |2 +-
vl.c|7 ++-
3 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/migration.c b/migration.c
index fbf2339..ecc67f1 100644
--- a/migration.c
+++ b/migration.c
@@ -36,22 +36,26 @@
This is a resent with what we agreed on yesterday call.
Migration events would be there for 0.13 until we get proper
async command support.
Later, Juan.
v3:
- Add comment that MIGRATION_FAILURE will add a QError for 0.14
(when we get internal support for that)
rebase against today tree
v2:
-
On Jun 9, 2010, at 5:39 AM, Harder, Stefan wrote:
> Hi,
>
> I've read in a Reservoir paper[1] the following passage:
>
> "2.2.8 VEE-MIG: Migration of VMs between hosts that do not share storage
> This code supports migraton of VMs between hosts that do not share storage.
> Modifications have bee
On 06/09/2010 12:41 AM, Chris Wright wrote:
pci.
D.F. (B:D.F?)
D:B:D.F
bar
rom
bar.n
--
error compiling committee.c: too many arguments to function
On 06/09/2010 05:54 AM, Paul Brook wrote:
On 06/08/2010 09:30 PM, Paul Brook wrote:
The offset given to a block created via qemu_ram_alloc/map() is
arbitrary, let the caller specify a name so we can make a positive
match.
@@ -1924,7 +1925,9 @@ static int pci_add_option_rom(PCIDevice *pde
Amit Shah writes:
> On (Wed) Jun 09 2010 [08:37:26], Markus Armbruster wrote:
>> Amit Shah writes:
>>
>> > On (Tue) Jun 08 2010 [18:33:00], Markus Armbruster wrote:
>> >> Amit Shah writes:
>> >>
>> >> > The correct model type wasn't getting added when hotplugging nics with
>> >> > pci_add.
>>
Peter Lieven writes:
> Markus Armbruster wrote:
>> Peter Lieven writes:
>>
>>
>>> Hi,
>>>
>>> is there any way to disable the PS/2 mouse emulation from command line?
>>>
>>
>> Judging from pc_basic_device_init() and i8042_initfn(): I don't think
>> so, sorry.
>>
>>
> would it be diffi
1 - 100 of 137 matches
Mail list logo
