On Thu, Nov 26, 2009 at 03:14:04PM +0800, Liang YANG wrote:
I think Kurt have a clear view on interrupt deliver routine.
Maybe when a outer physical interrupt yield durning the guest running
on cpu, this interrupt cause the guest exit
and eventually delived to the host to be disposed. Is that
Hello Dor,
Thank you for your review. I have few questions about your comments:
--- snip ---
+ stat += Guests memsh = {
+ for vm in lvms:
+ if vm.is_dead():
+ logging.info(Trying to get informations of death VM: %s
+ % vm.name)
+ continue
You can fail the entire test.
On 11/26/2009 03:35 AM, Andrew Theurer wrote:
NMI backtrace for cpu 9
CPU 9:
Modules linked in: tun sunrpc af_packet bridge stp ipv6 binfmt_misc
dm_mirror dm_region_hash dm_log dm_multipath scsi_dh dm_mod kvm_intel
kvm uinput sr_mod cdrom ata_generic pata_acpi ata_piix joydev libata
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
This patch exports enough of the MMU segment state to
On 11/26/2009 01:16 PM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
This
Bugs item #2902983, was opened at 2009-11-24 10:17
Message generated for change (Comment added) made by glebn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2902983group_id=180599
Please note that this message will contain a full copy of the comment
Avi Kivity wrote:
On 11/26/2009 02:46 PM, Alexander Graf wrote:
Please avoid unnamed unions in user-visible headers - they're a gcc
extension.
Yes, we have them elsewhere, but let's not add to the pile.
I'm open to scalable suggestions that don't break existing userspace
code.
If I
On 11/26/2009 03:16 PM, Alexander Graf wrote:
You can keep pvr out of the (named) union.
So we'd have
sregs.padded.ppc64.slb?
or sregs.u.ppc64.slb.
I don't see how that is an improvement.
Buildability takes precedence.
(an alternative is to drop the union, and add a
On 11/21/2009 12:34 AM, Kevin O'Connor wrote:
On Thu, Nov 19, 2009 at 04:02:06PM +0200, Avi Kivity wrote:
On 11/19/2009 03:39 PM, Kevin O'Connor wrote:
Long story short - this is the result of gcc's -combine being
fragile. It's possible to avoid by compiling seabios with make
On 11/21/2009 12:36 AM, Kevin O'Connor wrote:
It looks like I spoke too soon. It appears the SeaBIOS init can leave
the ATA controller in an interrupts disabled state. This appears to
confuse Vista. So, this is a SeaBIOS bug - I'll implement a fix.
I've committed a fix to SeaBIOS -
On 26.11.2009, at 17:06, Adrian Terranova wrote:
Hello,
Looking for a pointer to a working setup of kvm nesting kvm with svm
extensions working thruout.
I'm working with proxmox - and trying to get a proxmox in a proxmox
working. KVM is called as follows from the proxmox host.
31515
Am 26.11.2009 um 16:24 schrieb Alexander Graf ag...@suse.de:
Currently userspace has no chance to find out which virtual address
space we're
in and resolve addresses. While that is a big problem for migration,
it's also
unpleasent when debugging, as gdb and the monitor don't work on
The new pci_dev-dev.config is a uint_8 pointer, but get_real_device()
still using sizeof(pci_dev-dev.config) to fill the configuration space,
which lost most of information.
Spot the issue when INTx cannot work again after previous fix...
Signed-off-by: Sheng Yang sh...@linux.intel.com
---
Folks,
Any comments on the patch below ?
On Wed, Nov 25, 2009 at 11:35 AM, sudhir kumar smalik...@gmail.com wrote:
This patch adds a test for verifying whether the number of cpus and amount
of memory as seen inside a guest is same as allocated to it on the qemu
command line.
Signed-off-by:
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
This patch exports enough of the MMU segment state to
Avi Kivity wrote:
On 11/26/2009 01:16 PM, Alexander Graf wrote:
Currently userspace has no chance to find out which virtual address
space we're
in and resolve addresses. While that is a big problem for migration,
it's also
unpleasent when debugging, as gdb and the monitor don't work on
On 11/26/2009 02:46 PM, Alexander Graf wrote:
Please avoid unnamed unions in user-visible headers - they're a gcc
extension.
Yes, we have them elsewhere, but let's not add to the pile.
I'm open to scalable suggestions that don't break existing userspace code.
If I name the union now,
Avi Kivity wrote:
On 11/26/2009 02:46 PM, Alexander Graf wrote:
Please avoid unnamed unions in user-visible headers - they're a gcc
extension.
Yes, we have them elsewhere, but let's not add to the pile.
I'm open to scalable suggestions that don't break existing userspace
code.
If I
On 11/26/2009 03:16 PM, Alexander Graf wrote:
You can keep pvr out of the (named) union.
So we'd have
sregs.padded.ppc64.slb?
or sregs.u.ppc64.slb.
I don't see how that is an improvement.
Buildability takes precedence.
(an alternative is to drop the union, and add a
Currently userspace has no chance to find out which virtual address space we're
in and resolve addresses. While that is a big problem for migration, it's also
unpleasent when debugging, as gdb and the monitor don't work on virtual
addresses.
This patch exports enough of the MMU segment state to
Am 26.11.2009 um 16:24 schrieb Alexander Graf ag...@suse.de:
Currently userspace has no chance to find out which virtual address
space we're
in and resolve addresses. While that is a big problem for migration,
it's also
unpleasent when debugging, as gdb and the monitor don't work on
21 matches
Mail list logo
