Ciao Lynn:
I can post or email you my working config info if you really need it,
but I think you are really close to getting this working.
ok, let me trying few more times ... :-)
thank you for the answer (David Mair too)
--
Paolo Pedaletti
--
To unsubscribe from this list: send the line
Luca Bigliardi wrote:
Hi!
Please can you consider to import in kvm-userspace the native vde support
from qemu (svn revision 4896) ?
qemu-svn is merged regularly; there is no need to request this.
As it happens, I did a merge today, which of course includes the vde bits.
--
error
Marcelo Tosatti wrote:
On Sun, Jul 20, 2008 at 12:22:07PM +0300, Avi Kivity wrote:
Marcelo Tosatti wrote:
If 'g' is one then limit is 4kb granular.
Signed-off-by: Marcelo Tosatti [EMAIL PROTECTED]
Index: kvm-vmx-checks/arch/x86/kvm/x86.c
Jonathan Mezach wrote:
I've tried using the recent git tree, but the problem is still there. I did
notice though that the QEMU window no longer has the /KVM added to it. Not
sure if that has anything to do with it though.
I've installed and activated Windows Server 2008 Enterprise x64
Alexander Graf wrote:
+pr_unimpl(vcpu, %s: MSR_IA32_DEBUGCTLMSR 0x%llx, nop\n,
+__func__, data);
We can avoid the printout if data == 0, since we support that case
fully.
I was thinking a lot about that. Even though we support data == 0,
usually the kernel log
hi Avi,
* Avi Kivity [EMAIL PROTECTED] wrote:
KVM: Handle virtualization instruction #UD faults during reboot
-tip testing found a build failure on 64-bit x86, caused by this commit.
Find the fix below.
Thanks,
Ingo
commit
Ingo Molnar wrote:
hi Avi,
* Avi Kivity [EMAIL PROTECTED] wrote:
KVM: Handle virtualization instruction #UD faults during reboot
-tip testing found a build failure on 64-bit x86, caused by this commit.
Find the fix below.
Thanks. Applied this and will push to Linus
H. Peter Anvin wrote:
H. Peter Anvin wrote:
Yes, although simulating the memory pre-shadowed works just as
well; then it should be marked readonly by the BIOS immediately prior
to running INT 19h.
On top of this, getting proper DDIM support and PCI expansion ROM into
the BIOS would be a
Hi,
Following patch inserts proper spaces to fix printing of ./configure
--help output:
Before:
--disable-cpu-emulationdisables use of qemu cpu emulation code
After:
--disable-cpu-emulation disables use of qemu cpu emulation code
Cheers,
Ameya.
Signed-off-by: Ameya Palande [EMAIL PROTECTED]
Avi Kivity wrote:
H. Peter Anvin wrote:
H. Peter Anvin wrote:
Yes, although simulating the memory pre-shadowed works just as
well; then it should be marked readonly by the BIOS immediately prior
to running INT 19h.
On top of this, getting proper DDIM support and PCI expansion ROM into
The result of make headers_export should not contain CONFIG_*
conditions.
linux/kvm.h lacks __KERNEL__ around struct kvm_irqchip, I think.
Olaf
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
And also cleanup and standardize vcpu waking.
--
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
I am not sure if this is of interest to anybody, but I think there is a
bug in there somewhere :-).
I have the Squeezecenter software running in KVM. This is control software
for the dumb Squeezebox music streaming hardware. Any user action on the
Squeezebox requires a network roundtrip to the
If a vcpu has been offlined, or not initialized at all, signals
requesting userspace work to be performed will result in KVM attempting
to re-entry guest mode.
Problem is that the in-kernel irqchip emulation happily executes HALTED
state vcpu's. This breaks savevm on Windows SMP installation
Ryan Harper wrote:
* Uri Lublin [EMAIL PROTECTED] [2008-07-16 18:15]:
I think most kvm-tests will be client tests.
Agreed, the above examples will be client tests. Autotest client can do
parallel execution, or even step-wise. Between those, we should be able
to ensure we get proper
Jonathan Mezach wrote:
Avi Kivity avi at qumranet.com writes:
Jonathan Mezach wrote:
I've tried using the recent git tree, but the problem is still there. I did
notice though that the QEMU window no longer has the /KVM added to it. Not
sure if that has anything to do with it though.
The following part of commit 9ef621d3be56e1188300476a8102ff54f7b6793f
(KVM: Support mixed endian machines) changed on the size of a struct
that is exported to userspace:
include/linux/kvm.h:
@@ -318,14 +318,14 @@ struct kvm_trace_rec {
__u32 vcpu_id;
union {
[add stable]
On 7/21/08, Oleg Nesterov [EMAIL PROTECTED] wrote:
On 07/20, Roland McGrath wrote:
Yes, thanks, I see. But does it have any meaning for the user-space?
[si_sys_private]
No, it's not part of the user ABI. It's not even copied out (see
copy_siginfo_to_user).
Heh, I didn't
On Mon, Jul 21, 2008 at 11:38:56AM -0300, Marcelo Tosatti wrote:
If a vcpu has been offlined, or not initialized at all, signals
requesting userspace work to be performed will result in KVM attempting
to re-entry guest mode.
Problem is that the in-kernel irqchip emulation happily executes
Lynn Kerby wrote:
On Jul 20, 2008, at 10:07 PM, David Mair wrote:
Paolo Pedaletti wrote:
Ciao Uri:
Does using a different ifname help ?
PROXY: ifname=tap2 and dmz2
WEBAPP: ifname=tap1 and dmz1
DB: ifname=tap0 and dmz0
no, it doesn't.
always
destination host unreachable
Also check
On Mon, 21 Jul 2008 17:48:17 +0300, Avi Kivity [EMAIL PROTECTED] wrote:
Jonathan Mezach wrote:
Avi Kivity avi at qumranet.com writes:
Jonathan Mezach wrote:
I've tried using the recent git tree, but the problem is still there.
I did
notice though that the QEMU window no longer
Per subject. Etherboot comes up but is unable to get an IP address,
despite perfectly valid-looking incoming responses. Once booted, Linux
has no problem with DHCP.
Switching to the rtl8139 (while changing nothing else) works around the
issue.
--
To unsubscribe from this list: send the line
On Sun, Jul 13, 2008 at 9:23 PM, jd [EMAIL PROTECTED] wrote:
Thanks David.
I tried the cpu_set command... it exits the VM :( (kvm-70 on Fedora)
cpu_set does not have this meaning. It is just issues ACPI commands
for hot-adding/removing the cpu.
But it shouldn't exit the VM anyway. It sounds
On Thu, 2008-07-10 at 20:49 -0300, Marcelo Tosatti wrote:
diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
index b850d24..2c438a7 100644
--- a/arch/powerpc/kvm/powerpc.c
+++ b/arch/powerpc/kvm/powerpc.c
@@ -170,6 +170,11 @@ int kvm_arch_set_memory_region(struct kvm *kvm,
On Mon, Jul 21, 2008 at 04:03:27PM -0500, Hollis Blanchard wrote:
On Thu, 2008-07-10 at 20:49 -0300, Marcelo Tosatti wrote:
diff --git a/arch/powerpc/kvm/powerpc.c b/arch/powerpc/kvm/powerpc.c
index b850d24..2c438a7 100644
--- a/arch/powerpc/kvm/powerpc.c
+++ b/arch/powerpc/kvm/powerpc.c
QEMU currently supports building from a separate directory and I would like to
use this feature with kvm-userspace. The attached patch enables kvm-userspace
to be built from a separate directory. It still needs some work for non-x86
architectures (very little) and to get make install working.
On Monday 21 July 2008 16:34:40 Marcelo Tosatti wrote:
On Mon, Jul 21, 2008 at 04:03:27PM -0500, Hollis Blanchard wrote:
By the way, what is the testcase for this, i.e. how do I remove a
memslot?
The testcase I used was RH6.2 graphical install, which changes the
cirrus mode from linear
On Sat, Jul 12, 2008 at 01:28:13PM -0600, David S. Ahern wrote:
All time drift issues we were aware of are fixed in kvm-70. Can you
please provide more details on how you see the time drifting with
RHEL3/4 guests? It slowly but continually drifts or there are large
drifts at once? Are they
28 matches
Mail list logo
