This bug is still present on latest git. It seems, please double check
this, that the commit you tested is related to a different issue.
The steps to reproduce the bug are attached on the case. Usually, when
there is support for ACPI operations on the guest OS, the pci_del
command triggers a
Marcos Oviedo moviedo.maill...@gmail.com writes:
This adds a way to force the removal/unplug of previously added pci
devices when ACPI-based hotplug mechanism is not present.
Signed-off-by: Marcos Oviedo movi...@gmail.com
If this makes sense for pci_del (I'm not passing judgement), then we
Amit Shah amit.s...@redhat.com writes:
On (Tue) Jun 08 2010 [18:33:00], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
The correct model type wasn't getting added when hotplugging nics with
pci_add.
Testcase: start VM with default nic type. In the qemu_monitor:
Jes Sorensen jes.soren...@redhat.com writes:
On 06/04/10 13:54, Markus Armbruster wrote:
Jes Sorensen jes.soren...@redhat.com writes:
On 06/04/10 10:21, Markus Armbruster wrote:
I like moving stuff out of vl.c in general. Your moves of entire
functions look like a win to me. I have
On 06/09/10 04:40, Anthony Liguori 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 *pdev)
+
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 pretty useless to plug in
hardware in the first place.
If your
On 06/08/10 03:56, Anthony Liguori wrote:
On 06/07/2010 08:01 PM, Paul Brook wrote:
diff --git a/hw/realview.c b/hw/realview.c
index a36bdbe..8dcef80 100644
--- a/hw/realview.c
+++ b/hw/realview.c
@@ -444,9 +444,9 @@ static QEMUMachine realview_eb_mpcore_machine = {
.init =
On 06/08/10 01:52, Anthony Liguori wrote:
max_cpus is a weird property today. On the one hand, it represents the
maximum
CPUs a board can support and is used to validate the number of vcpus requested
by the user.
On the other hand, max_cpus can be set by the user in which case it is taken
On 06/08/10 01:52, Anthony Liguori wrote:
+static QemuOptValue pc_machine_v0_11[] = {
+QOPT_VALUE(name, pc-0.11),
+QOPT_VALUE(desc, Standard PC, qemu 0.11),
+QOPT_VALUE(acpi, on),
+QOPT_VALUE(pci, on),
+QOPT_VALUE(cpu, PC_DEFAULT_CPU_MODEL),
+QOPT_VALUE(max_cpus,
jes.soren...@redhat.com writes:
From: Jes Sorensen jes.soren...@redhat.com
If a USB keyboard is unplugged, the keyboard eventhandler is never
removed, and events will continue to be passed through to the device,
causing crashes or memory corruption.
Looks good.
I wonder how many more
Peter Lieven p...@dlh.net 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.
Markus Armbruster arm...@redhat.com wrote:
Amit Shah amit.s...@redhat.com writes:
On (Tue) Jun 08 2010 [18:33:00], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
The correct model type wasn't getting added when hotplugging nics with
pci_add.
Testcase: start VM with
If you built your own qemu it may try to look for the BIOS in
/usr/local/share/qemu and not where it was originally installed on your
system. Could you please try to specify it with the -L option and see.
You don't mention what system you are running on, it would likely be -L
/usr/share/qemu-kvm
Alex Williamson alex.william...@redhat.com wrote:
On Tue, 2010-06-08 at 14:26 -0700, Chris Wright wrote:
* Alex Williamson (alex.william...@redhat.com) wrote:
extern int phys_ram_fd;
-extern uint8_t *phys_ram_dirty;
extern ram_addr_t ram_size;
-extern ram_addr_t last_ram_offset;
+
On 06/09/10 09:07, Markus Armbruster wrote:
Jes Sorensen jes.soren...@redhat.com writes:
On 06/04/10 13:54, Markus Armbruster wrote:
If there is strong feeling we should do it this way instead, I can
change the code to do it this way instead. I am not married to the
current approach, I just
Hi,
I rebased the patch series to the head of both qemu.git
(26ebe46848ecb2462cc53d4de20ac6590709643b) and qemu-kvm.git
(3f505ec990599aeb960ed7031a2bb7b233ea4927). The repository contains branches
for both tree.
git://kemari.git.sourceforge.net/gitroot/kemari/kemari
Patches for qemu.git are in
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 common to all cpus in the pool.
would that
Markus Armbruster wrote:
Peter Lieven p...@dlh.net 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 difficult to implement?
Markus Armbruster wrote:
Peter Lieven p...@dlh.net 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.
background:
with the ps/2 mouse there are always problems
This patch adds the ability to determine the build-configured
runtime config file paths from the command line. After
support for cpu model definitions were added to the default
runtime target- config file, testing of this feature has
tripped over an unintentionally mis-installed config file
Peter Lieven wrote:
background:
with the ps/2 mouse there are always problems with pointer
synchronization.
Yeah, we have that here on one of our WinNT VMs. The quick solution we
found was to install VNC Server on NT and set up everyone to connect to
that rather than to the physical
The first one results from wrong saturation judgment.
The original form is :
uint8_t sub8_usat(uint8_t a, uint8_t b) {
if (a b)
return a - b;
else
return 0;
}
it should be a b
The second problem is using op2 as op1 to tell among signed, unsigned, and half
group
**
One attachment is allowed in each comment :
for case 1
** Patch added: for case 1 problem
http://launchpadlibrarian.net/5666/0002-target-arm-fix-parallel-saturated-subtraction-error.patch
--
[ARM]: SIMD add/sub instructions are incorrect
https://bugs.launchpad.net/bugs/591320
You
Still getting BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
with -vga std-parameter on lucid.
I would suggest to set the bug-status to confirmed instead of fix-released.
---
dpkg -l |egrep -e kvm|vgabios
ii kvm
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 been
made to QEMU-kvm and libvirt. This code was developed by IBM
On Wed, Jun 02, 2010 at 05:26:54PM -0700, Richard Henderson wrote:
The tcg_out_mov patch you've seen before, but now contains a
TCG_TYPE_REG that should address the concerns you had with
the changes to the sparc port. It's also been updated to HEAD
to reflect the changes in tcg/i386.
The
On (Wed) Jun 09 2010 [09:59:50], Juan Quintela wrote:
BTW, once here, didn't default nic should be e1000? not rtl8139?
Are you looking at qemu-kvm sources? ;-)
Amit
Nicholas A. Bellinger wrote:
On Tue, 2010-06-08 at 16:15 +0200, Hannes Reinecke wrote:
This patch updates the megasas HBA emulation to version 1.01.
It fixes the following issues:
- Remove hand-crafted inquiry command
- Remove bounce-buffer for direct commands
- Implements qdev properties
On Wed, Jun 02, 2010 at 01:56:50AM +0200, Alexander Graf wrote:
Commit dd4239d6574ca41c94fc0d0f77ddc728510ffc57 broke multiboot. It replaced
the
instruction rep insb (%dx), %es:(%edi) by the binary output of
addr32 rep insb (%dx), %es:(%di).
Linuxboot calls the respective helper function
On Wed, 2010-06-09 at 03:14 -0700, Nicholas A. Bellinger wrote:
On Tue, 2010-06-08 at 16:15 +0200, Hannes Reinecke wrote:
This patch updates the megasas HBA emulation to version 1.01.
It fixes the following issues:
- Remove hand-crafted inquiry command
- Remove bounce-buffer for direct
Hi,
BUT. usb emulation is resource intensive.
Update qemu. Fixed in 0.12.4 and unstable.
cheers,
Gerd
On Wed, Jun 02, 2010 at 05:19:53PM -0300, Luiz Capitulino wrote:
This series fixes bug 573827, which is a segfault when you do:
$ qemu -usbdevice serial
All commits backported from current master, just minimally tested.
Thanks, applied.
--
Aurelien Jarno GPG:
Gerd Hoffmann wrote:
Hi,
BUT. usb emulation is resource intensive.
Update qemu. Fixed in 0.12.4 and unstable.
thanks for this update. i think my experience came from 0.12.3
i will verify this
cheers,
Gerd
On Wed, 2010-06-09 at 12:32 +0200, Hannes Reinecke wrote:
Nicholas A. Bellinger wrote:
Hi Hannes,
I applied your changes and everything looks good with the exception of
the new MEGASAS_DEFAULT_SGE=80 setting..
diff --git a/hw/megasas.c b/hw/megasas.c
index 250c3fb..19569a8 100644
Peter Lieven p...@dlh.net writes:
Markus Armbruster wrote:
Peter Lieven p...@dlh.net 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 difficult
Amit Shah amit.s...@redhat.com writes:
On (Wed) Jun 09 2010 [08:37:26], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
On (Tue) Jun 08 2010 [18:33:00], Markus Armbruster wrote:
Amit Shah amit.s...@redhat.com writes:
The correct model type wasn't getting added when
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
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 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 been
made
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:
Signed-off-by: Juan Quintela quint...@redhat.com
---
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
Signed-off-by: Juan Quintela quint...@redhat.com
---
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
They are emitted when migration starts, ends, has a failure or is canceled.
Signed-off-by: Juan Quintela quint...@redhat.com
---
QMP/qmp-events.txt | 52
monitor.c | 12
monitor.h |4
3 files
Signed-off-by: Juan Quintela quint...@redhat.com
---
migration-exec.c | 14 +-
migration-fd.c | 14 +-
migration-tcp.c | 15 ++-
migration-unix.c | 15 ++-
migration.c | 13 +
migration.h |2 ++
6 files
Signed-off-by: Juan Quintela quint...@redhat.com
---
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
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 suggest
* 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
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
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
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 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 froy...@codesourcery.com
---
target-mips/helper.h|9 +
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 representation
On Wed, Jun 9, 2010 at 4:38 AM, Gerd Hoffmann kra...@redhat.com 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
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 Tue, Jun 08, 2010 at 01:30:00PM -0700, Nathan Froyd wrote:
Signed-off-by: Nathan Froyd froy...@codesourcery.com
---
target-mips/translate_init.c | 61
++
1 files changed, 61 insertions(+), 0 deletions(-)
diff --git
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,
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
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 via -device
Hi Juan,
2010/6/9 Juan Quintela quint...@redhat.com:
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
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
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 new ones, but my plan
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 Tue, 08 Jun 2010 16:13:37 -0500
Anthony Liguori anth...@codemonkey.ws 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
On Wed, Jun 09, 2010 at 12:18:20PM -0300, Luiz Capitulino wrote:
On Tue, 08 Jun 2010 16:13:37 -0500
Anthony Liguori anth...@codemonkey.ws 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
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-bit
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
Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp 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.
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.
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
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
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/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 call
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 more release
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 this logic
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
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:
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
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 \
* Anthony Liguori anth...@codemonkey.ws [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
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
On Sun, Jun 6, 2010 at 4:28 PM, Artyom Tarasenko
atar4q...@googlemail.com wrote:
2010/6/6 Blue Swirl blauwir...@gmail.com:
On Sat, Jun 5, 2010 at 11:10 PM, Bob Breuer breu...@mc.net wrote:
Blue Swirl wrote:
but again: should we have a new machine with cg14 or
some switch to select TCX vs.
On Mon, 7 Jun 2010 15:42:14 +0100
Daniel P. Berrange berra...@redhat.com 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,
On Mon, 7 Jun 2010 15:42:16 +0100
Daniel P. Berrange berra...@redhat.com 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
On Mon, 7 Jun 2010 15:42:19 +0100
Daniel P. Berrange berra...@redhat.com 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
On Mon, 7 Jun 2010 15:42:21 +0100
Daniel P. Berrange berra...@redhat.com 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
On Sun, Jun 6, 2010 at 5:39 PM, Paolo Bonzini pbonz...@redhat.com 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
On Mon, 07 Jun 2010 10:11:28 -0500
Anthony Liguori anth...@codemonkey.ws 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
TCGv t1 needs tcg_temp_free instead of tcg_temp_free_i32.
Cc: Nathan Froyd froy...@codesourcery.com
Cc: Aurelien Jarno aurel...@aurel32.net
Signed-off-by: Stefan Weil w...@mail.berlios.de
---
target-mips/translate.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
nudge. Any comments here?
On Wed, Jun 2, 2010 at 10:58 AM, Alex Williamson
alex.william...@redhat.com 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
On Mon, Jun 7, 2010 at 4:41 PM, Cam Macdonell c...@cs.ualberta.ca wrote:
On Sat, Jun 5, 2010 at 3:44 AM, Blue Swirl blauwir...@gmail.com wrote:
On Fri, Jun 4, 2010 at 9:45 PM, Cam Macdonell c...@cs.ualberta.ca wrote:
Support an inter-vm shared memory device that maps a shared-memory object
as
On Mon, 07 Jun 2010 11:07:14 -0500
Anthony Liguori anth...@codemonkey.ws 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
On Tue, 8 Jun 2010 12:31:38 +0530
Prerna Saxena pre...@linux.vnet.ibm.com 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
On Fri, Jun 4, 2010 at 8:30 PM, Artyom Tarasenko
atar4q...@googlemail.com wrote:
2010/6/4 Blue Swirl blauwir...@gmail.com:
On Tue, Jun 1, 2010 at 8:16 PM, Artyom Tarasenko
atar4q...@googlemail.com wrote:
2010/6/1 Blue Swirl blauwir...@gmail.com:
On Tue, Jun 1, 2010 at 7:56 PM, Artyom
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 think
On Tue, 8 Jun 2010 12:34:37 +0530
Prerna Saxena pre...@linux.vnet.ibm.com wrote:
This introduces the monitor command 'trace' to read current contents of
trace buffer.
Signed-off-by: Prerna Saxena pre...@linux.vnet.ibm.com
---
configure |3 +++
monitor.c |3 +++
On Tue, 8 Jun 2010 12:38:58 +0530
Prerna Saxena pre...@linux.vnet.ibm.com wrote:
This patch adds support for dynamically enabling/disabling of tracepoints.
Monitor commands added :
1) info tracepoints : to view all available tracepoints and
their
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
On Wed, Jun 9, 2010 at 2:30 PM, Paul Brook p...@codesourcery.com 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
On Wed, 9 Jun 2010 14:10:53 +0200
Juan Quintela quint...@redhat.com 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
On 06/09/2010 03:47 PM, Blue Swirl wrote:
On Wed, Jun 9, 2010 at 2:30 PM, Paul Brookp...@codesourcery.com 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
1 - 100 of 124 matches
Mail list logo
