date:20070815

Farkas Levente wrote:
> Avi Kivity wrote:
>   
>> There are two answers to this:
>>
>> - balloon driver (like in Xen) which allows the host to move memory from
>> one guest to another (or from host to guest)
>> - swapping, which allows the host to move guest memory to disk and
>> allocate it to another guest
>>
>> Unfortunately the balloon driver has not been publicly released yet, and
>> swapping is still in early development, so for now you will have to use
>> static allocation.
>> 
>
> which will be available sooner? and an estimate when?
>   

We already have a balloon driver, however it is not yet ready for 
inclusion.  Perhaps Dor will comment.   Swapping is some way off; there 
is a fairly complete patch from Shaohua Li that does this, but it 
requires kernel changes and we are investigating other approaches.

> this rise another question if swapping will be used the it moves the
> guest memory to the guest's swap or the host's swap? if to the host's
> swap then this implies i should have to allocate large enough swap for
> the host. ie. even if i give only 256mb to the host still have to gives
> 6-8GB swap partition to the host.
>   

Yes, when swapping is implemented then guest memory will be swapped to 
the host swap.  Of course, if the guest has its own swap file, then it 
will swap to the guest's swap independently.

> still believe that these memory, swap, and other disk partitions should
> have to be explain in the faq.
>   

Yes.

-- 
error compiling committee.c: too many arguments to function

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] [ANNOUNCE] kvm-35 release

kvm-35 refuses to load on Intel Core (not Core 2) processors, so this 
release is mainly to fix that unhappy regression.

Changes since kvm-34:
- fix kvm refusing to load on Core processors (Glauber de Oliveira Costa)
- improve qemu monitor handling CR/LF sequences (Jim Paris)
- fix compile warning in qemu (Luca Tettamanti)

Notes:
If you use the modules from kvm-35, you can use any version of Linux
from 2.6.9 upwards.
If you use the modules from Linux 2.6.20, you need to use kvm-12.
If you use the modules from Linux 2.6.21, you need to use kvm-17.
Modules from Linux 2.6.22 and up will work with any kvm version from
kvm-22.  Some features may only be available in newer releases.
For best performance, use Linux 2.6.23-rc2 or later as the host.

http://kvm.qumranet.com



-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [ANNOUNCE] kvm-35 release

Avi Kivity wrote:
> kvm-35 refuses to load on Intel Core (not Core 2) processors, so this 
> release is mainly to fix that unhappy regression.
>
> Changes since kvm-34:
> - fix kvm refusing to load on Core processors (Glauber de Oliveira Costa)
> - improve qemu monitor handling CR/LF sequences (Jim Paris)
> - fix compile warning in qemu (Luca Tettamanti)

Oh, and the smp live migration fix that escaped kvm-34 is in there too.

-- 
error compiling committee.c: too many arguments to function

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Slohm Gadaburi

hi ppl,

I am grateful for the help and tips I've been given here on the earlier
thread.
I just want to summarize the bits I've collected,
please confirm :)

On an up-to-date Ubuntu 7.04 machine:
- install kvm+qemu packages
- install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x ?)
- download kvm-35
- configure it without the --patched flag (will it automatically find
the gcc-3 ?)
- insmod the just-build kvm-(amd|intel) module
- make sure i run the qemu binaries supplied from the kvm35 package

that should do the trick ?

thank you all i am already anxious to see now whether
installing RH9 will take less than 3 hours :)

slohm

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Koen de Jonge (ProcoliX)

Slohm Gadaburi wrote:
> hi ppl,
>
> I am grateful for the help and tips I've been given here on the earlier
> thread.
> I just want to summarize the bits I've collected,
> please confirm :)
>
> On an up-to-date Ubuntu 7.04 machine:
> - install kvm+qemu packages
> - install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x ?)
> - download kvm-35
> - configure it without the --patched flag (will it automatically find
> the gcc-3 ?)
> - insmod the just-build kvm-(amd|intel) module
> - make sure i run the qemu binaries supplied from the kvm35 package
>
> that should do the trick ?
>   
You'll need the rest of the required libs also, but this pretty much 
sums it up.

Koen
> thank you all i am already anxious to see now whether
> installing RH9 will take less than 3 hours :)
>   
Please let us know the results.

Koen

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] adding support for above 2giga to kvm (include patchs)

2007-08-15 Thread Izik Eidus

On Tue, 2007-08-14 at 17:21 -0500, Ryan Harper wrote:
> So, I don't think passing the structure as a pointer works.  The 16-bit
> compiler bcc has a number of quirks.  I don't pretend to understand what
> the issue is here, but, changing the signature of set_e820_range() to:
> 
> void set_e820_range(ES, DI, start, end, extra_start, extra_end, type)
>  Bit16u ES;
>  Bit16u DI;
>  Bit32u start;
>  Bit32u end;
>  Bit16u extra_start;
>  Bit8u  extra_end;
>  Bit16u type;
> {
> 
> and the callers accordingly, fixes the issue with memtest iso.  I can
> still boot guests with more than 4G, and memtest sees the correct
> amount, above and below 4G.
> 

can you send the the diff and the compiled bios?
i am getting some sort of stack overflow if i try to pass many
arguments, and this was the reason i used pointer to struck from the
beginning.

thanks, and good work!

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] a few may be wiki question

On Wed, 2007-08-15 at 11:07 +0300, Avi Kivity wrote:
> Farkas Levente wrote:
> > this rise another question if swapping will be used the it moves the
> > guest memory to the guest's swap or the host's swap? if to the host's
> > swap then this implies i should have to allocate large enough swap for
> > the host. ie. even if i give only 256mb to the host still have to gives
> > 6-8GB swap partition to the host.
> >   
> 
> Yes, when swapping is implemented then guest memory will be swapped to 
> the host swap.  Of course, if the guest has its own swap file, then it 
> will swap to the guest's swap independently.

And to clarify: FYI, I believe the guest-swap option should actually
work today.  If you assign a partition as a swap device in the guest it
should use it.  kvm-host will simply see it as disk io as any other.
This is in contrast to the host-swap and/or balloon driver which is
still a work-in-progress.

On thing that is interesting about this (to me) is that, in a way it
kind of is a "poor mans" swap for the guests memory on the host.  E.g.
you could give your guests a really small amount of "physical" ram (say,
I dunno, 64MB/ea) and a large swap file (say several gigs).  Since the
disk-io emanating from the guest would likely be mediated by the hosts
buffercache, its kind of like you just gave the guest a large chunk of
(indirectly accessible) pageable ram.

OTOH, virtualized disk-io is pretty slow compared to bare-metal io.  As
I said, this is a "poor mans" solution ;)  What it really comes down to
is: does having emulated disk-io to a buffercache offer adequate
performance for your applications running in the guest?  If so, this may
be a good interim solution to get a larger number of guests running on a
given host with "dynamic ram".

Regards,
-Greg

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] [patch] Renaming kvm_arch in view of upcoming architecture ports

2007-08-15 Thread Christian Ehrhardt


Hi,
in view of the upcoming architecture ports, this is a little cleanup 
patch that renames the current "_arch" to "_x86"

e.g. kvm_arch_ops -> kvm_x86_ops

I discussed with some people about names like kvm_x86_arch_ops or 
kvm_subarch_ops, ... but at the end we thought that "arch" has a special 
meaning in linux and so it should be freed for the real architecture 
ports of kvm that show up slowly on the horizon (look at Tucson).
I want to invite everyone to comment about what may be a more 
appropriate name in order to find out what naming scheme the community 
wants.


I attached the patch to keep the usual form, but actually it is just 
what comes out executing the following:

 perl -p -i -e "s/_arch/_x86/g" drivers/kvm/*

--

Grüsse / regards, 
Christian Ehrhardt


IBM Linux Technology Center, Open Virtualization
+49 7031/16-3385
[EMAIL PROTECTED]
[EMAIL PROTECTED]

IBM Deutschland Entwicklung GmbH
Vorsitzender des Aufsichtsrats: Johann Weihen 
Geschäftsführung: Herbert Kircher 
Sitz der Gesellschaft: Böblingen

Registergericht: Amtsgericht Stuttgart, HRB 243294

diff --git a/drivers/kvm/kvm.h b/drivers/kvm/kvm.h
index 70231f3..a3dcc96 100644
--- a/drivers/kvm/kvm.h
+++ b/drivers/kvm/kvm.h
@@ -415,7 +415,7 @@ struct descriptor_table {
unsigned long base;
 } __attribute__((packed));
 
-struct kvm_arch_ops {
+struct kvm_x86_ops {
int (*cpu_has_kvm_support)(void);  /* __init */
int (*disabled_by_bios)(void); /* __init */
void (*hardware_enable)(void *dummy);  /* __init */
@@ -472,7 +472,7 @@ struct kvm_arch_ops {
unsigned char *hypercall_addr);
 };
 
-extern struct kvm_arch_ops *kvm_arch_ops;
+extern struct kvm_x86_ops *kvm_x86_ops;
 
 /* The guest did something we don't support. */
 #define pr_unimpl(vcpu, fmt, ...)  \
@@ -488,9 +488,9 @@ extern struct kvm_arch_ops *kvm_arch_ops;
 int kvm_vcpu_init(struct kvm_vcpu *vcpu, struct kvm *kvm, unsigned id);
 void kvm_vcpu_uninit(struct kvm_vcpu *vcpu);
 
-int kvm_init_arch(struct kvm_arch_ops *ops, unsigned int vcpu_size,
+int kvm_init_x86(struct kvm_x86_ops *ops, unsigned int vcpu_size,
  struct module *module);
-void kvm_exit_arch(void);
+void kvm_exit_x86(void);
 
 int kvm_mmu_module_init(void);
 void kvm_mmu_module_exit(void);
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index f7ff231..64c2cc4 100644
--- a/drivers/kvm/kvm_main.c
+++ b/drivers/kvm/kvm_main.c
@@ -52,7 +52,7 @@ static LIST_HEAD(vm_list);
 
 static cpumask_t cpus_hardware_enabled;
 
-struct kvm_arch_ops *kvm_arch_ops;
+struct kvm_x86_ops *kvm_x86_ops;
 struct kmem_cache *kvm_vcpu_cache;
 EXPORT_SYMBOL_GPL(kvm_vcpu_cache);
 
@@ -180,14 +180,14 @@ static void vcpu_load(struct kvm_vcpu *vcpu)
mutex_lock(&vcpu->mutex);
cpu = get_cpu();
preempt_notifier_register(&vcpu->preempt_notifier);
-   kvm_arch_ops->vcpu_load(vcpu, cpu);
+   kvm_x86_ops->vcpu_load(vcpu, cpu);
put_cpu();
 }
 
 static void vcpu_put(struct kvm_vcpu *vcpu)
 {
preempt_disable();
-   kvm_arch_ops->vcpu_put(vcpu);
+   kvm_x86_ops->vcpu_put(vcpu);
preempt_notifier_unregister(&vcpu->preempt_notifier);
preempt_enable();
mutex_unlock(&vcpu->mutex);
@@ -364,7 +364,7 @@ static void kvm_free_vcpus(struct kvm *kvm)
kvm_unload_vcpu_mmu(kvm->vcpus[i]);
for (i = 0; i < KVM_MAX_VCPUS; ++i) {
if (kvm->vcpus[i]) {
-   kvm_arch_ops->vcpu_free(kvm->vcpus[i]);
+   kvm_x86_ops->vcpu_free(kvm->vcpus[i]);
kvm->vcpus[i] = NULL;
}
}
@@ -393,7 +393,7 @@ static int kvm_vm_release(struct inode *inode, struct file 
*filp)
 
 static void inject_gp(struct kvm_vcpu *vcpu)
 {
-   kvm_arch_ops->inject_gp(vcpu, 0);
+   kvm_x86_ops->inject_gp(vcpu, 0);
 }
 
 /*
@@ -468,7 +468,7 @@ void set_cr0(struct kvm_vcpu *vcpu, unsigned long cr0)
inject_gp(vcpu);
return;
}
-   kvm_arch_ops->get_cs_db_l_bits(vcpu, &cs_db, &cs_l);
+   kvm_x86_ops->get_cs_db_l_bits(vcpu, &cs_db, &cs_l);
if (cs_l) {
printk(KERN_DEBUG "set_cr0: #GP, start paging "
   "in long mode while CS.L == 1\n");
@@ -487,7 +487,7 @@ void set_cr0(struct kvm_vcpu *vcpu, unsigned long cr0)
 
}
 
-   kvm_arch_ops->set_cr0(vcpu, cr0);
+   kvm_x86_ops->set_cr0(vcpu, cr0);
vcpu->cr0 = cr0;
 
mutex_lock(&vcpu->kvm->lock);
@@ -530,7 +530,7 @@ void set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4)
inject_gp(vcpu);
return;
}
-   kvm_arch_ops->set_cr4(vcpu, cr4);
+   kvm_x86_ops->set_cr4(vcpu, cr4);
mutex_lock(&vcpu->kvm->lock);
kvm_mmu_

Re: [kvm-devel] a (bad) kvm story from a plain user

2007-08-15 Thread Daniel P. Berrange

On Wed, Aug 15, 2007 at 01:43:58AM -0300, Jorge Luc?ngeli Obes wrote:
> On 8/15/07, Daniel P. Berrange <[EMAIL PROTECTED]> wrote:
> > On Tue, Aug 14, 2007 at 10:26:24PM -0500, Anthony Liguori wrote:
> > >
> > > On Wed, 2007-08-15 at 05:44 +0300, Avi Kivity wrote:
> > > > Slohm Gadaburi wrote:
> > > > > How can I know if the qemu I ran took advantage of the kvm module ?
> > > > >
> > > >
> > > > No one mentioned my favorite: when kvm is in control, the title bar of
> > > > the guest console window changes to "QEMU/KVM".
> > > >
> > > > > I ran /usr/bin/qemu as I didn't have /usr/local/kvm/bin/qemu like the 
> > > > > HOWTO
> > > > > mentioned (as I didn't compiled the kvm bundle myself...).
> > > > >
> > > >
> > > > Well, the HOWTO assumes you did all the previous steps.  We should have
> > > > a HOWTO/Ubuntu for distro users (but really, Ubuntu should have a gui
> > > > for this).
> > >
> > > virt-manager isn't currently packaged for Ubuntu (even in Gutsy).  If
> > > there any Ubuntu devs out there, please consider packaging it!
> >
> > There are virt-manager packages for Debian so it shouldn't be hard to port
> > them.
> 
> Just today I was trying virt-manager and libvirt. I got this error
> when creating a VM:
> 
> Unable to complete install: 'virDomainCreateLinux() failed Cannot find
> QEMU binary /usr/bin/qemu: No such file or directory'

The KVM support in libvirt is just an extension to the generic QEMU
support. So you have to have a plain QEMU installed, as well as the
KVM-ified version. To avoid filename clashes it expects the KVM version
of QEMU to be named /usr/bin/qemu-kvm.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-   Perl modules: http://search.cpan.org/~danberr/  -=|
|=-   Projects: http://freshmeat.net/~danielpb/   -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [patch] Renaming kvm_arch in view of upcoming architecture ports

Christian Ehrhardt wrote:
> Hi,
> in view of the upcoming architecture ports, this is a little cleanup 
> patch that renames the current "_arch" to "_x86"
> e.g. kvm_arch_ops -> kvm_x86_ops
>
> I discussed with some people about names like kvm_x86_arch_ops or 
> kvm_subarch_ops, ... but at the end we thought that "arch" has a 
> special meaning in linux and so it should be freed for the real 
> architecture ports of kvm that show up slowly on the horizon (look at 
> Tucson).
> I want to invite everyone to comment about what may be a more 
> appropriate name in order to find out what naming scheme the community 
> wants.
>
> I attached the patch to keep the usual form, but actually it is just 
> what comes out executing the following:
>  perl -p -i -e "s/_arch/_x86/g" drivers/kvm/*
>

Seems a sensible name.  I thought of subarch at first, but x86 is more 
explicit.

I'll apply this after the lapic merge.

-- 
error compiling committee.c: too many arguments to function

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [RFC PATCH 0/9] PV device infrastructure v2

On Wed, 2007-08-15 at 00:52 -0700, Dor Laor wrote:

> If the above is followed, any enhancement will be appriciated.

Since I am close, I will probably make at least one more v3 drop "as is"
with the new lguest_bus inspired pvbus (with hotplug, etc).  From there,
we can (virtually) get together and figure out what can be used
directly, what can be used in spirit, and what should be thrown away.

Dor, I know you mentioned you wanted to go stepwise, but note that I
*did* break it up into a series.  I just delivered it all at once ;)

But the fact is, I really need to do this stuff in-kernel so I am very
much interested in getting the solution designed with that in mind from
the get-go.  So note that you will continue to see a series that is
oriented to support both your userspace approach and my current
in-kernel direction.  (Note that my current series doesn't deal with the
userspace side yet).

Please point me to your current branch when it is available for me to
look at.  I'm looking forward to helping out here!

Regards,
-Greg   


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [RFC PATCH 0/9] PV device infrastructure v2

On Wed, 2007-08-15 at 00:13 -0400, Gregory Haskins wrote:
> On Wed, 2007-08-15 at 06:58 +0300, Avi Kivity wrote:

> > since it wants to be hypervisor agnostic, it cannot specify an ABI (as
> > some already have ABIs, for example Xen).
> 
> I see, and that is a good point.  By only being an API, virtio can work
> over XenBus or any other ABI it wants.  IOQ is an API *and* an ABI.
> While this doesnt preclude it from ever working on Xen, it does imply
> that you would need to add the IOQ ABI to the Xen infrastructure if you
> wanted to use it (at least, if you wanted to use it directly instead of
> doing some kind of funky queue-in-queue with IOQ on XenBus..yuk). 

I think I misspoke when I said this (it was up way to late for coherent
thought ;)

While what you said is true (virtio = API, IOQ = API+ABI) note that I
believe both can be considered hypervisor agnostic.  (That was a primary
design goal of mine).  All the hypervisor would need to do is write an
ioq_mgr layer.  Xen for instance, could use either hypercalls/interrupts
directly like I do for the KVM implementation.  Or it could use XenBus
as a signaling transport.

I am only bringing this up as a correction to my statement, not to try
to sway someone in some kind of IOQ vs VirtIO debate.  :)

Regards,
-Greg

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] a few may be wiki question

2007-08-15 Thread Farkas Levente

Gregory Haskins wrote:
> On Wed, 2007-08-15 at 11:07 +0300, Avi Kivity wrote:
>> Farkas Levente wrote:
>>> this rise another question if swapping will be used the it moves the
>>> guest memory to the guest's swap or the host's swap? if to the host's
>>> swap then this implies i should have to allocate large enough swap for
>>> the host. ie. even if i give only 256mb to the host still have to gives
>>> 6-8GB swap partition to the host.
>>>   
>> Yes, when swapping is implemented then guest memory will be swapped to 
>> the host swap.  Of course, if the guest has its own swap file, then it 
>> will swap to the guest's swap independently.
> 
> And to clarify: FYI, I believe the guest-swap option should actually
> work today.  If you assign a partition as a swap device in the guest it
> should use it.  kvm-host will simply see it as disk io as any other.
> This is in contrast to the host-swap and/or balloon driver which is
> still a work-in-progress.
> 
> On thing that is interesting about this (to me) is that, in a way it
> kind of is a "poor mans" swap for the guests memory on the host.  E.g.
> you could give your guests a really small amount of "physical" ram (say,
> I dunno, 64MB/ea) and a large swap file (say several gigs).  Since the
> disk-io emanating from the guest would likely be mediated by the hosts
> buffercache, its kind of like you just gave the guest a large chunk of
> (indirectly accessible) pageable ram.

i just imagine th opposite setup. suppose i've got 4 guest and 4gb ram.
most of the time guest are idle they just used as a compile server for
different platforms (centos, mandrake, fedora, windows etc). i can
schedule the compiles (ie. 1:00 guest1, 2:00 guest 2 etc). in this case
i gives the host 1-2gb and all guest 2-3gb logical ram. which is in sum
9-14gb ram even i have only 4gb physical ram.
_BUT_ as i know that the guests are usually idle _and_ they have high
resource requirement at different time, probably all of them can use
2-3gb real ram as memory. and in this setup if all other time most of
the guest's ram are swapped out it's not really bother me since they are
idle.
or did is something misunderstood?

-- 
  Levente   "Si vis pacem para bellum!"

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] Again the rtc: lost some interrupts at 1024Hz

2007-08-15 Thread Daniel Paquet

Well im still playing with this darn error, and in fact I am even starting
to think that this is my cause of kicker crash. Im getting my logs filled
with
rtc: lost some interrupts at 1024Hz when I sed the max freq to 1024 as per
request of kvm when I start it.

Im running debian Lenny and a vanilla kernel 2.6.23-rc3 with no patch.

I may miss some information since im not a dev, so let me know if you need
more information, or maybe if I should RTFM ;) but I alread did alot of
search on google for this, and it has not been very successfull...

Thanks!

-- 
Ubuntu est un ancien mot africain qui veut dire "Je ne peux pas configurer
Debian"
--
Daniel Paquet
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] a few may be wiki question

On Wed, 2007-08-15 at 15:52 +0200, Farkas Levente wrote:
> Gregory Haskins wrote:
> > 
> > On thing that is interesting about this (to me) is that, in a way it
> > kind of is a "poor mans" swap for the guests memory on the host.  E.g.
> > you could give your guests a really small amount of "physical" ram (say,
> > I dunno, 64MB/ea) and a large swap file (say several gigs).  Since the
> > disk-io emanating from the guest would likely be mediated by the hosts
> > buffercache, its kind of like you just gave the guest a large chunk of
> > (indirectly accessible) pageable ram.
> 
> i just imagine th opposite setup. suppose i've got 4 guest and 4gb ram.
> most of the time guest are idle they just used as a compile server for
> different platforms (centos, mandrake, fedora, windows etc). i can
> schedule the compiles (ie. 1:00 guest1, 2:00 guest 2 etc). in this case
> i gives the host 1-2gb and all guest 2-3gb logical ram. which is in sum
> 9-14gb ram even i have only 4gb physical ram.
> _BUT_ as i know that the guests are usually idle _and_ they have high
> resource requirement at different time, probably all of them can use
> 2-3gb real ram as memory. and in this setup if all other time most of
> the guest's ram are swapped out it's not really bother me since they are
> idle.
> or did is something misunderstood?

I think you are just misunderstanding me.  We are saying the same thing
(I think) :)

What it sounds like you are talking about is oversubscribing your ram.
IIUC this is not possible today unless you employ a guest-swap scheme
like I mentioned.  Until the balloon/swap support is in, the guest "ram"
allocation aggregated across all VMs cannot exceed host-physical ram (in
your case, 4GB).  In fact, it has to be a little less of course so the
host still has some to play with ;)

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] [PATCH 1/2]Fix CR8 support in kvm

2007-08-15 Thread Yang, Sheng

These two patches fix CR8 support for x64 Windows. Now when writing to
CR8 in the guest OS, we exit to userspace and update tpr in qemu apic
emulation.
We can boot x64 Windows XP with these patches now.

Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
 drivers/kvm/vmx.c   |3 ++-
 include/linux/kvm.h |1 +
 2 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/drivers/kvm/vmx.c b/drivers/kvm/vmx.c
index 906d4fa..8f9a0bb 100644
--- a/drivers/kvm/vmx.c
+++ b/drivers/kvm/vmx.c
@@ -1831,7 +1831,8 @@ static int handle_cr(struct kvm_vcpu *vcpu, struct
kvm_run *kvm_run)
vcpu_load_rsp_rip(vcpu);
set_cr8(vcpu, vcpu->regs[reg]);
skip_emulated_instruction(vcpu);
-   return 1;
+   kvm_run->exit_reason = KVM_EXIT_SET_TPR;
+   return 0;
};
break;
case 2: /* clts */
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index 91a446f..1d5a49c 100644
--- a/include/linux/kvm.h
+++ b/include/linux/kvm.h
@@ -46,6 +46,7 @@ enum kvm_exit_reason {
KVM_EXIT_SHUTDOWN = 8,
KVM_EXIT_FAIL_ENTRY   = 9,
KVM_EXIT_INTR = 10,
+   KVM_EXIT_SET_TPR  = 11
 };
 
 /* for KVM_RUN, returned by mmap(vcpu_fd, offset=0) */
-- 
1.5.2



Fix-CR8-support-in-kvm.patch
Description: Fix-CR8-support-in-kvm.patch
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] [PATCH 2/2]Fix CR8 support in kvm-userspace

2007-08-15 Thread Yang, Sheng

Signed-off-by: Sheng Yang <[EMAIL PROTECTED]>
---
 qemu/qemu-kvm.c |3 ++-
 user/kvmctl.c   |7 +++
 user/kvmctl.h   |   11 +++
 3 files changed, 20 insertions(+), 1 deletions(-)

diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
index e23f477..59cba64 100644
--- a/qemu/qemu-kvm.c
+++ b/qemu/qemu-kvm.c
@@ -497,7 +497,8 @@ static void post_kvm_run(void *opaque, int vcpu)
? env->eflags | IF_MASK : env->eflags & ~IF_MASK;
 env->ready_for_interrupt_injection
= kvm_is_ready_for_interrupt_injection(kvm_context, vcpu);
-//cpu_set_apic_tpr(env, kvm_run->cr8);
+
+cpu_set_apic_tpr(env, kvm_get_cr8(kvm_context, vcpu));
 cpu_set_apic_base(env, kvm_get_apic_base(kvm_context, vcpu));
 }
 
diff --git a/user/kvmctl.c b/user/kvmctl.c
index 43b374d..e211626 100644
--- a/user/kvmctl.c
+++ b/user/kvmctl.c
@@ -868,6 +868,11 @@ void kvm_set_cr8(kvm_context_t kvm, int vcpu,
uint64_t cr8)
run->cr8 = cr8;
 }
 
+__u64 kvm_get_cr8(kvm_context_t kvm, int vcpu)
+{
+   return kvm->run[vcpu]->cr8;
+}
+
 static int kvm_run_abi10(kvm_context_t kvm, int vcpu)
 {
int r;
@@ -1007,6 +1012,8 @@ again:
case KVM_EXIT_SHUTDOWN:
r = handle_shutdown(kvm, vcpu);
break;
+   case KVM_EXIT_SET_TPR:
+   break;
default:
fprintf(stderr, "unhandled vm exit: 0x%x\n",
run->exit_reason);
kvm_show_regs(kvm, vcpu);
diff --git a/user/kvmctl.h b/user/kvmctl.h
index f3f807e..b7af128 100644
--- a/user/kvmctl.h
+++ b/user/kvmctl.h
@@ -191,6 +191,17 @@ int
kvm_is_ready_for_interrupt_injection(kvm_context_t kvm, int vcpu);
 void kvm_set_cr8(kvm_context_t kvm, int vcpu, uint64_t cr8);
 
 /*!
+ * \brief Get cr8 for sync tpr in qemu apic emulation
+ *
+ * This is a getter for cr8, which used to sync with the tpr in qemu
+ * apic emualtion.
+ *
+ * \param kvm Pointer to the current kvm_context
+ * \param vcpu Which virtual CPU should get dumped
+ */
+__u64 kvm_get_cr8(kvm_context_t kvm, int vcpu);
+
+/*!
  * \brief Read VCPU registers
  *
  * This gets the GP registers from the VCPU and outputs them
-- 
1.5.2



Fix-CR8-support-in-kvm-userspace.patch
Description: Fix-CR8-support-in-kvm-userspace.patch
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] a (bad) kvm story from a plain user

On 8/15/07, Daniel P. Berrange <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 15, 2007 at 01:43:58AM -0300, Jorge Luc?ngeli Obes wrote:
> > On 8/15/07, Daniel P. Berrange <[EMAIL PROTECTED]> wrote:
> > Just today I was trying virt-manager and libvirt. I got this error
> > when creating a VM:
> >
> > Unable to complete install: 'virDomainCreateLinux() failed Cannot find
> > QEMU binary /usr/bin/qemu: No such file or directory'
>
> The KVM support in libvirt is just an extension to the generic QEMU
> support. So you have to have a plain QEMU installed, as well as the
> KVM-ified version. To avoid filename clashes it expects the KVM version
> of QEMU to be named /usr/bin/qemu-kvm.

Thanks. I had reached more or less that conclusion after looking at
'src/qemu_driver.c', but it's good to have confirmation.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [PATCH] Dynamic ticks

2007-08-15 Thread Dan Kenigsberg

Thank you (Luca and Thiemo) for your prompt review and comments!

On Tue, Aug 14, 2007 at 12:06:20AM +0100, Thiemo Seufer wrote:
> Luca Tettamanti wrote:
> [snip]
> > I've implemented some of my suggestions in the following patch - rebased
> > to kvm-userspace current git since it's easier to test (...ok, I'm lazy -
> > but you get the idea):
> > 
> > 
> > diff --git a/qemu/configure b/qemu/configure
> > index 365b7fb..38373db 100755
> > --- a/qemu/configure
> > +++ b/qemu/configure
> > @@ -262,6 +262,8 @@ for opt do
> >;;
> >--enable-uname-release=*) uname_release="$optarg"
> >;;
> > +  --disable-dynamic-ticks) dynamic_ticks="no"
> > +  ;;
> 
> Is there a situation where the attempt to use dynticks is harmful?
> 

Well, I cannot really say when and how much, but rearming the timer
every shot has its price (especially when the guest is not idling).
I thought that even just uselessly checking use_dynamic_ticks in every
signal handler call would be frowned upon.

Maybe you are right, and for the sake of code and build simplisity I
should drop that ifdef altogether.

Thanks,

Dan.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [PATCH] Dynamic ticks

2007-08-15 Thread Dan Kenigsberg

On Mon, Aug 13, 2007 at 10:37:41PM +0200, Luca Tettamanti wrote:
> 
> I like it ;) I have some comments (and a reworked patch at the end):
> 

And thanks a lot for that.

> 
> Plus, in this way you change the behaviour from "always try RTC under
> Linux" to "don't use RTC is dynticks is enabled".
> Is this what you really want?

I don't know whether this is what should be done, but it's what I wanted.
I was not looking for a dynamic-ticks solution for every available time
source, and considered the system's POSIX timer as a good enough source.
Am I wrong here?

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] [PATCH] hint your using kvm

2007-08-15 Thread Matthew Kent

Signed-off-by: Matthew Kent <[EMAIL PROTECTED]>
---
 qemu/vnc.c |   12 ++--
 1 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/qemu/vnc.c b/qemu/vnc.c
index 37d5e35..4430651 100644
--- a/qemu/vnc.c
+++ b/qemu/vnc.c
@@ -1109,8 +1109,16 @@ static int protocol_client_init(VncState *vs, char 
*data, size_t len)

 vnc_write(vs, pad, 3);   /* padding */
 
-vnc_write_u32(vs, 4);
-vnc_write(vs, "QEMU", 4);
+#if USE_KVM
+if (kvm_allowed) {
+vnc_write_u32(vs, 8);
+vnc_write(vs, "QEMU/KVM", 8);
+} else
+#endif
+{
+vnc_write_u32(vs, 4);
+vnc_write(vs, "QEMU", 4); 
+}
 vnc_flush(vs);
 
 vnc_read_when(vs, protocol_client_msg, 1);
-- 
1.5.2.2


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [PATCH] Dynamic ticks

2007-08-15 Thread Dor Laor

>> I like it ;) I have some comments (and a reworked patch at the end):
>>
>
>And thanks a lot for that.
>
>>
>> Plus, in this way you change the behaviour from "always try RTC under
>> Linux" to "don't use RTC is dynticks is enabled".
>> Is this what you really want?
>
>I don't know whether this is what should be done, but it's what I
>wanted.
>I was not looking for a dynamic-ticks solution for every available time
>source, and considered the system's POSIX timer as a good enough
source.
>Am I wrong here?

Using dyn-tick should be the default option. Not only it saves ticks for
guests
with HZ < 1000, it improves the accurency and responsiveness of the
system.
There are also issues with [EMAIL PROTECTED] because of HPET inteference.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] Error while inserting kvm-intel.ko from kvm-34

2007-08-15 Thread Glauber de Oliveira Costa

> > commit 2863174b39dd8768cd7922832e45ea00d5c6442c
> > Author: Glauber de Oliveira Costa <[EMAIL PROTECTED]>
> > Date:   Tue Aug 14 15:51:22 2007 -0300
>
> Author email is misconfigured...
>
>
Thanks for noting, Avi. I didn't wrote this patch in my usual test
machine, but in my t60. (you could tell).

-- 
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net

"The less confident you are, the more serious you have to act."

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images

2007-08-15 Thread Segher Boessenkool

>>> When I read Avi's TODO, I basically thought about getting rid of the
>>> long command lines I had to store in scripts. I wanted to write that
>>> command line once, and then forgetting about it, until I needed to
>>> change it.
>>
>> Instead of inventing great and wonderfully complicated schemes, the
>> most sensible way I can think of is to recycle a feature which is now
>> implemented in the GNU toolchain, and apparently stems from Windows:
>>
>>   qemu @qemu.cfg
>>
>> where qemu.cfg is a file which contains the command line arguments.
>> (This is also low-maintenance, as it allows to re-use the existing
>
> IMHO, it should be implemented at the shell level, not qemu level, 
> like "*" is.

The shell _does_ implement it:  qemu `cat qemu.cfg`  :-)

If you want "@" anyway, you can pick up the code from libiberty
(or just build with libiberty).


Segher


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Cam Macdonell

Koen de Jonge (ProcoliX) wrote:
> Slohm Gadaburi wrote:
>> hi ppl,
>>
>> I am grateful for the help and tips I've been given here on the earlier
>> thread.
>> I just want to summarize the bits I've collected,
>> please confirm :)
>>
>> On an up-to-date Ubuntu 7.04 machine:
>> - install kvm+qemu packages
>> - install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x ?)
>> - download kvm-35
>> - configure it without the --patched flag (will it automatically find
>> the gcc-3 ?)
>> - insmod the just-build kvm-(amd|intel) module
>> - make sure i run the qemu binaries supplied from the kvm35 package
>>
>> that should do the trick ?
>>   

I'm trying to compile kvm-35 (from the git repository) on Ubuntu Feisty 
(all up to date) and I get the following error:

[EMAIL PROTECTED]:~/src/KVM/kvm-userspace$ sudo make
make -C kernel
make[1]: Entering directory `/home/cam/src/KVM/kvm-userspace/kernel'
make -C /lib/modules/2.6.20-15-generic/build M=`pwd` "$@"
make[2]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
make[3]: *** No rule to make target 
`/home/cam/src/KVM/kvm-userspace/kernel/svm.o', needed by 
`/home/cam/src/KVM/kvm-userspace/kernel/kvm.o'.  Stop.
make[2]: *** [_module_/home/cam/src/KVM/kvm-userspace/kernel] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/cam/src/KVM/kvm-userspace/kernel'
make: *** [kernel] Error 2

I have to admit that I'm a little fuzzy on the modules that are needed 
to build a particular kvm release (and where to get them from).

Initially, I used Ubuntu's apt install and then moved on to buidling 
kvm-33 from source tar ball which built fine.  But, the kvm-33 tarball 
had the svm source files in the the kernel directory.  I notice those 
files are not in the kvm-35 kernel directory (and are causing the 
failure above).  Is there some other repo svm files are part of?

Thanks,
Cam

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

On 8/15/07, Cam Macdonell <[EMAIL PROTECTED]> wrote:
> Koen de Jonge (ProcoliX) wrote:
> > Slohm Gadaburi wrote:
> >> hi ppl,
> >>
> >> I am grateful for the help and tips I've been given here on the earlier
> >> thread.
> >> I just want to summarize the bits I've collected,
> >> please confirm :)
> >>
> >> On an up-to-date Ubuntu 7.04 machine:
> >> - install kvm+qemu packages
> >> - install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x 
> >> ?)
> >> - download kvm-35
> >> - configure it without the --patched flag (will it automatically find
> >> the gcc-3 ?)
> >> - insmod the just-build kvm-(amd|intel) module
> >> - make sure i run the qemu binaries supplied from the kvm35 package
> >>
> >> that should do the trick ?
> >>
>
> I'm trying to compile kvm-35 (from the git repository) on Ubuntu Feisty
> (all up to date) and I get the following error:
>
> [EMAIL PROTECTED]:~/src/KVM/kvm-userspace$ sudo make
> make -C kernel
> make[1]: Entering directory `/home/cam/src/KVM/kvm-userspace/kernel'
> make -C /lib/modules/2.6.20-15-generic/build M=`pwd` "$@"
> make[2]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
> make[3]: *** No rule to make target
> `/home/cam/src/KVM/kvm-userspace/kernel/svm.o', needed by
> `/home/cam/src/KVM/kvm-userspace/kernel/kvm.o'.  Stop.
> make[2]: *** [_module_/home/cam/src/KVM/kvm-userspace/kernel] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/cam/src/KVM/kvm-userspace/kernel'
> make: *** [kernel] Error 2
>
> I have to admit that I'm a little fuzzy on the modules that are needed
> to build a particular kvm release (and where to get them from).
>
> Initially, I used Ubuntu's apt install and then moved on to buidling
> kvm-33 from source tar ball which built fine.  But, the kvm-33 tarball
> had the svm source files in the the kernel directory.  I notice those
> files are not in the kvm-35 kernel directory (and are causing the
> failure above).  Is there some other repo svm files are part of?

When I compile from GIT, I use both kvm-userspace.git and kvm.git
(kernel). The files that are missing are the kernel part of KVM. You
could clone kvm.git too:

git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git

and use the following line:

./configure --with-patched-kernel --kerneldir=

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [RFC PATCH 0/9] PV device infrastructure v2

2007-08-15 Thread Dor Laor

>Since I am close, I will probably make at least one more v3 drop "as
is"
>with the new lguest_bus inspired pvbus (with hotplug, etc).  From
there,
>we can (virtually) get together and figure out what can be used
>directly, what can be used in spirit, and what should be thrown away.

Sure thing. 
>
>Dor, I know you mentioned you wanted to go stepwise, but note that I
>*did* break it up into a series.  I just delivered it all at once ;)

The series is good, though personally I prefer to test each stage using
live packets. Well, I recon the IOQ already tested and only the other
mechanisms
are new.

>
>But the fact is, I really need to do this stuff in-kernel so I am very
>much interested in getting the solution designed with that in mind from
>the get-go.  So note that you will continue to see a series that is
>oriented to support both your userspace approach and my current
>in-kernel direction.  (Note that my current series doesn't deal with
the
>userspace side yet).
>
>Please point me to your current branch when it is available for me to
>look at.  I'm looking forward to helping out here!

Currently things at my end are a bit broken since I replaced the dma
backend with a generic dma based on Rusty's code. Hope that it will work
tomorrow.

If you'll be quick enough you can rip the lguest_bus into a very light
weight
virtio_bus. Please keep it thin as possible, Rusty's code is 217 lines
long, half
of it comments. I'm planing to have a flexible use of this bus while one
can either choose virtio_bus or pci bus.

>
>Regards,
>-Greg


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

> Thanks for the help, that compiled the userspace part.   I need the new
> kernel module (kvm-intel.ko), can I take it from the kernel tree some
> way or do I have to use the whole KVM kernel?

You should be able to compile it without having to compile the whole
kernel. That's what one does with release versions, so it has to be
possible. However, I've been working with the userspace part, so I've
not yet tried it. Maybe someone else can comment? It's probably just
Makefile dark magic.

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Luca

On 8/16/07, Cam Macdonell <[EMAIL PROTECTED]> wrote:
> Koen de Jonge (ProcoliX) wrote:
> > Slohm Gadaburi wrote:
> >> hi ppl,
> >>
> >> I am grateful for the help and tips I've been given here on the earlier
> >> thread.
> >> I just want to summarize the bits I've collected,
> >> please confirm :)
> >>
> >> On an up-to-date Ubuntu 7.04 machine:
> >> - install kvm+qemu packages
> >> - install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x 
> >> ?)
> >> - download kvm-35
> >> - configure it without the --patched flag (will it automatically find
> >> the gcc-3 ?)
> >> - insmod the just-build kvm-(amd|intel) module
> >> - make sure i run the qemu binaries supplied from the kvm35 package
> >>
> >> that should do the trick ?
> >>
>
> I'm trying to compile kvm-35 (from the git repository) on Ubuntu Feisty
> (all up to date) and I get the following error:
>
> [EMAIL PROTECTED]:~/src/KVM/kvm-userspace$ sudo make
> make -C kernel
> make[1]: Entering directory `/home/cam/src/KVM/kvm-userspace/kernel'
> make -C /lib/modules/2.6.20-15-generic/build M=`pwd` "$@"
> make[2]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
> make[3]: *** No rule to make target
> `/home/cam/src/KVM/kvm-userspace/kernel/svm.o', needed by
> `/home/cam/src/KVM/kvm-userspace/kernel/kvm.o'.  Stop.
> make[2]: *** [_module_/home/cam/src/KVM/kvm-userspace/kernel] Error 2
> make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/cam/src/KVM/kvm-userspace/kernel'
> make: *** [kernel] Error 2
>
> I have to admit that I'm a little fuzzy on the modules that are needed
> to build a particular kvm release (and where to get them from).
>
> Initially, I used Ubuntu's apt install and then moved on to buidling
> kvm-33 from source tar ball which built fine.  But, the kvm-33 tarball
> had the svm source files in the the kernel directory.  I notice those
> files are not in the kvm-35 kernel directory (and are causing the
> failure above).  Is there some other repo svm files are part of?

That is not kvm-35 tarball, it's the git repository for the userspace
component (which -as the name suggests - does not contain the kernel
space part).
Download kvm-35 tarball, you'll find both pieces.

Luca

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] Making qemu images executable (and store command line arguments in them =P)

I've been giving some thought to Anthony's idea:

http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage

However, maybe I'm just too much on vacations, but I don't seem to
come up with a nice way of doing this. Everything keeps coming back to
creating a new 'container' image format and then implementing block
layer functions that only add the number of sectors occupied by the
command-line to the read and write calls made by QEMU, and then just
relay those calls to the image-specific functions. That doesn't sound
very efficient.

The '#!' trick works nice with scripts, but I don't see it playing
very well with images. ¿Comments? ¿Pointers?

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Cam Macdonell

Jorge Lucángeli Obes wrote:
> On 8/15/07, Cam Macdonell <[EMAIL PROTECTED]> wrote:
>> Koen de Jonge (ProcoliX) wrote:
>>> Slohm Gadaburi wrote:
 hi ppl,

 I am grateful for the help and tips I've been given here on the earlier
 thread.
 I just want to summarize the bits I've collected,
 please confirm :)

 On an up-to-date Ubuntu 7.04 machine:
 - install kvm+qemu packages
 - install the gcc-3.4 package (hopefully it will not overwrite my gcc 4.x 
 ?)
 - download kvm-35
 - configure it without the --patched flag (will it automatically find
 the gcc-3 ?)
 - insmod the just-build kvm-(amd|intel) module
 - make sure i run the qemu binaries supplied from the kvm35 package

 that should do the trick ?

>> I'm trying to compile kvm-35 (from the git repository) on Ubuntu Feisty
>> (all up to date) and I get the following error:
>>
>> [EMAIL PROTECTED]:~/src/KVM/kvm-userspace$ sudo make
>> make -C kernel
>> make[1]: Entering directory `/home/cam/src/KVM/kvm-userspace/kernel'
>> make -C /lib/modules/2.6.20-15-generic/build M=`pwd` "$@"
>> make[2]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
>> make[3]: *** No rule to make target
>> `/home/cam/src/KVM/kvm-userspace/kernel/svm.o', needed by
>> `/home/cam/src/KVM/kvm-userspace/kernel/kvm.o'.  Stop.
>> make[2]: *** [_module_/home/cam/src/KVM/kvm-userspace/kernel] Error 2
>> make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/home/cam/src/KVM/kvm-userspace/kernel'
>> make: *** [kernel] Error 2
>>
>> I have to admit that I'm a little fuzzy on the modules that are needed
>> to build a particular kvm release (and where to get them from).
>>
>> Initially, I used Ubuntu's apt install and then moved on to buidling
>> kvm-33 from source tar ball which built fine.  But, the kvm-33 tarball
>> had the svm source files in the the kernel directory.  I notice those
>> files are not in the kvm-35 kernel directory (and are causing the
>> failure above).  Is there some other repo svm files are part of?
> 
> When I compile from GIT, I use both kvm-userspace.git and kvm.git
> (kernel). The files that are missing are the kernel part of KVM. You
> could clone kvm.git too:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
> 
> and use the following line:
> 
> ./configure --with-patched-kernel --kerneldir=
> 

Thanks for the help, that compiled the userspace part.   I need the new 
kernel module (kvm-intel.ko), can I take it from the kernel tree some 
way or do I have to use the whole KVM kernel?

Thanks,
Cam

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [RFC PATCH 0/9] PV device infrastructure v2

On Wed, 2007-08-15 at 15:37 -0700, Dor Laor wrote:

> 
> If you'll be quick enough you can rip the lguest_bus into a very light
> weight
> virtio_bus. Please keep it thin as possible, Rusty's code is 217 lines
> long, half
> of it comments. I'm planing to have a flexible use of this bus while one
> can either choose virtio_bus or pci bus.

Already done ;)

Its not quite polished yet.  I will send tomorrow.  Currently it looks
like this:

 arch/x86_64/Kconfig  |2
 drivers/Makefile |1
 drivers/pvbus/Kconfig|7 +++
 drivers/pvbus/Makefile   |6 ++
 drivers/pvbus/pvbus-driver.c |   89
+++
 include/linux/pvbus.h|   55 ++
 6 files changed, 160 insertions(+)

Of course its still IOQ oriented currently, but we can reconcile that
when we get together.

-Greg

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [Qemu-devel] Making qemu images executable (and store command line arguments in them =P)

2007-08-15 Thread Mark Williamson

> I've been giving some thought to Anthony's idea:
>
> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>
> However, maybe I'm just too much on vacations, but I don't seem to
> come up with a nice way of doing this. Everything keeps coming back to
> creating a new 'container' image format and then implementing block
> layer functions that only add the number of sectors occupied by the
> command-line to the read and write calls made by QEMU, and then just
> relay those calls to the image-specific functions. That doesn't sound
> very efficient.

It's not necessarily that pretty, but I wouldn't have thought that adding a 
simple offset to block operations will have a measurable performance impact 
(given the latencies involved in block accesses anyhow, and the amount of 
data transferred each time).

> The '#!' trick works nice with scripts, but I don't see it playing
> very well with images. ¿Comments? ¿Pointers?

Well, it's not really necessary, but it would be darn cool :-)  Another cool 
(but admittedly twisted - get the brain soap ready!) thing to do would be to 
statically link a qemu, and then include a virtual machine config and disks 
in a section of the elf file (inspired by glick: 
http://blogs.gnome.org/alexl/2007/08/07/experiments-with-runtime-less-app-bundles/).
  
So then you'd have an "executable" VM image which doesn't need a Qemu runtime 
to be available.  There are various variations you could do on this basic 
premise in order to make the file you carry around less terrifyingly huge!

Anyhow, enough of my random ideas...  I was thinking about container formats.

I've missed some of the discussion, but wouldn't tar be an obvious choice?  It 
can expand easily out to a directory hierarchy containing config file and 
multiple virtual disk files, there are standard tools that can manipulate it 
and standard libraries that can be used by Qemu in order to get at the 
contents.  Only problem I see with this approach is that sparse file handling 
might get a bit strange (using real sparse files vs using tar's 
represesntation of sparse files vs compatibility with tars that don't support 
them!).

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [RFC PATCH 0/9] PV device infrastructure v2

2007-08-15 Thread Rusty Russell

On Wed, 2007-08-15 at 00:52 -0700, Dor Laor wrote:
> btw: Rusty, I tried to apply the new-io-lguest* patches and they failed
> to apply cleanly.
> What base repo do you use for that?

Sorry, with all the movement of getting lguest in tree, those patches
have rotted slightly (particularly the new-io-lguest-readwrite.patch
which needs a complete rework).

I've restored them now (well, they apply and compile again...)

Cheers,
Rusty.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [Patch] (big) real mode emulation - jmp rel

2007-08-15 Thread Nitin A Kamble

Hi Avi,
  I modified the patch as per your suggestions. Attached is the update
patch for the "jmp rel" instruction. Also the "jmp rel short" patch
would go on top of it.

Thanks & Regards,
Nitin
Open Source Technology Center, Intel Corporation
-
The mind is like a parachute; it works much better when it's open.
On Mon, 2007-08-13 at 01:49 -0700, Avi Kivity wrote:
> Please use an inline function instead of a macro.  That will help when
> we later make large scale changes (for example, splitting the emulator
> into a decoder and executor).
> 
> (and, when defining the macro, indent the contents)
> 
> --
> error compiling committee.c: too many arguments to function
> 
> 

commit dd675f122c14adac40c9ac1eb5864de60330cc8c
Author: Nitin A Kamble <[EMAIL PROTECTED]>
Date:   Wed Aug 15 20:52:41 2007 -0700

Implement instruction "jmp rel" opcode 0xe9

Signed-off-by: Nitin A Kamble <[EMAIL PROTECTED]>

diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index b4f439c..9130fd5 100644
--- a/drivers/kvm/x86_emulate.c
+++ b/drivers/kvm/x86_emulate.c
@@ -145,8 +145,10 @@ static u8 opcode_table[256] = {
 	0, 0, 0, 0,
 	/* 0xD8 - 0xDF */
 	0, 0, 0, 0, 0, 0, 0, 0,
-	/* 0xE0 - 0xEF */
-	0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
+	/* 0xE0 - 0xE7 */
+	0, 0, 0, 0, 0, 0, 0, 0,
+	/* 0xE8 - 0xEF */
+	0, SrcImm|ImplicitOps, 0, 0, 0, 0, 0, 0,
 	/* 0xF0 - 0xF7 */
 	0, 0, 0, 0,
 	ImplicitOps, 0,
@@ -504,6 +506,12 @@ x86_emulate_memop(struct x86_emulate_ctxt *ctxt, struct x86_emulate_ops *ops)
 	unsigned long _eip = ctxt->vcpu->rip, _eflags = ctxt->eflags;
 	unsigned long modrm_val = 0;
 
+	inline void jmp_rel(int rel)
+	{
+		_eip += (int)(rel);
+		_eip = ((op_bytes == 2) ? (uint16_t)_eip : (uint32_t)_eip);
+	};
+
 	memcpy(_regs, ctxt->vcpu->regs, sizeof _regs);
 
 	switch (mode) {
@@ -1200,6 +1208,10 @@ special_insn:
 	case 0xae ... 0xaf:	/* scas */
 		DPRINTF("Urk! I don't handle SCAS.\n");
 		goto cannot_emulate;
+	case 0xe9: /* jmp rel */
+		jmp_rel(src.val);
+		no_wb = 1; /* Disable writeback. */
+		break;
 	case 0xf4:  /* hlt */
 		ctxt->vcpu->halt_request = 1;
 		goto done;
commit 38f7db6830c862cd0470aaa07cabe616ff741d69
Author: Nitin A Kamble <[EMAIL PROTECTED]>
Date:   Fri Aug 10 18:48:05 2007 -0700

Implement "jmp rel short" opcode: 0xeb

Signed-off-by: Nitin A Kamble <[EMAIL PROTECTED]>

diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index 40fb6ee..16ea385 100644
--- a/drivers/kvm/x86_emulate.c
+++ b/drivers/kvm/x86_emulate.c
@@ -148,7 +148,7 @@ static u8 opcode_table[256] = {
 	/* 0xE0 - 0xE7 */
 	0, 0, 0, 0, 0, 0, 0, 0,
 	/* 0xE8 - 0xEF */
-	0, SrcImm|ImplicitOps, 0, 0, 0, 0, 0, 0,
+	0, SrcImm|ImplicitOps, 0, SrcImmByte|ImplicitOps, 0, 0, 0, 0,
 	/* 0xF0 - 0xF7 */
 	0, 0, 0, 0,
 	ImplicitOps, 0,
@@ -1208,6 +1208,7 @@ special_insn:
 	case 0xae ... 0xaf:	/* scas */
 		DPRINTF("Urk! I don't handle SCAS.\n");
 		goto cannot_emulate;
+	case 0xeb: /* jmp rel short */
 	case 0xe9: /* jmp rel */
 		jmp_rel(src.val);
 		no_wb = 1; /* Disable writeback. */


signature.asc
Description: This is a digitally signed message part
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] KVM Test result, kernel 83aecfbf.. , userspace 108ccc34.

2007-08-15 Thread Zhao, Yunfeng

Hi, all,

This is today's KVM test result against kvm.git
83aecfbf44f3ba92abde47957a3c9175f1ec7165 and kvm-userspace.git
108ccc346fa8fc226a8fcdba91387554d7b35709.

##What's working:
Can boot most ia32/ia32e SMP/UP Linux guests with either acpi enabled or acpi
disabled.
Can boot ia32 SMP/UP Windows 2k, Windows XP, and Windows 2k3 guests with
either acpi enabled or acpi disabled.
Can boot Vista RTM with acpi, but network doesn't work. A workaround is
installing a win2k ne2000 driver.
Save/Restore works on both ia32 and IA32e
Live migration works on ia32 and ia32e
ia32 guest can be migrated from ia32 host to ia32e host
Keybord, mouse, ide disk, vga, and nic work well.

##What's not working:
Can NOT boot guest with > 2GB mem
Can NOT boot ia32e UP/SMP Windows guests
Can NOT boot ia32e rhel4u3 with -no-acpi
Can NOT boot 2.6.22 kernel if not disable nmi_watchdog
Timer is not accurate
Booting multiple guests likely fails
Booting windows guest is very slow

Issue list in ABAT Testing:

1. Could not create kvm guest with memory >=2040
https://sourceforge.net/tracker/index.php?func=detail&aid=1736307&group_id=180599&atid=893831
2. Create multiple guests simultaneously or create one guest many times may fail
https://sourceforge.net/tracker/index.php?func=detail&aid=1741312&group_id=180599&atid=893831
3. Can not boot IA32e RHEL 4u3 guest with -no-acpi
https://sourceforge.net/tracker/index.php?func=detail&aid=1741314&group_id=180599&atid=893831
4. Can not boot 64 bits windows
https://sourceforge.net/tracker/index.php?func=detail&aid=1741318&group_id=180599&atid=893831
5. Some ltp test cases fail
https://sourceforge.net/tracker/index.php?func=detail&aid=1741316&group_id=180599&atid=893831
6. Booting windows guest is very slow
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1768187&group_id=180599
7. Fails to boot linux guests with 2.6.22 kernel
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1769884&group_id=180599

Test environment

Platform Paxville-Harwich
CPU 16
Memory size 8G'

Details

PAE:

1. boot guest with 256M memory PASS

2. boot two windows xp guestPASS

3. boot 4 same guest in parallelPASS

4. boot linux and windows guest in parallel PASS

5. boot 4G linux guest FAIL

6. boot guest with 1500M memory PASS

7. boot windows 2003 with ACPI enabled PASS

8. boot 32 bit vista with win2000 ne2000 driverFAIL

9. boot Windows xp with ACPI enabledFAIL

10. boot Windows 2000 without ACPI PASS

11. kernel build on SMP linux guestPASS

12. LTP on SMP linux guest PASS

13. boot base kernel linux FAIL

14. save/restore 32-bit HVM guestsPASS

15. boot SMP Windows xp with ACPI enabledPASS

16. boot SMP windows 2003 with ACPI enabled PASS

17. boot SMP Windows 2000 with ACPI enabled PASS

IA32e:

1. boot four 32-bit guest in parallel PASS

2. boot four 64-bit guest in parallel PASS

3. boot 4G 64-bit guest FAIL

4. boot 4G pae guest FAIL

5. boot 32-bit linux and 32 bit windows guest in parallel PASS

6. boot 32-bit guest with 1500M memory PASS

7. boot 32-bit guest with 256M memory PASS

8. boot 64-bit guest with 1500M memory PASS

9. boot 64-bit guest with 256M memory PASS

10. boot two 32-bit windows xp in parallel PASS

11. boot four 32-bit different guest in parallel PASS

12. save/restore 64-bit linux guests PASS

13. save/restore 32-bit linux guests PASS

14. boot 32-bit SMP windows 2003 with ACPI enabled PASS

15. boot 32-bit SMP Windows xp with ACPI enabled PASS

16. boot 32-bit Windows 2000 without ACPI PASS

17. boot 64-bit windows 2003 without ACPI FAIL

18. boot 64-bit Windows xp without ACPIFAIL

19. boot 32-bit Windows xp without ACPIPASS

20. boot 64-bit vista FAIL

21. kernel build in 32-bit linux guest OS PASS

22. kernel build in 64-bit linux guest OS PASS

23. LTP on SMP 32-bit linux guest OS P

Re: [kvm-devel] CPU consumption for SMP windows guests.

On 8/14/07, Igor Lvovsky <[EMAIL PROTECTED]> wrote:
> I attached the patch for BOCHS bios and compiled bios.bin.

Good work! I'm getting considerably less load on my Windows XP SMP guest.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] It uses the functionality of the associated, but independent, DCDSERVE.

2007-08-15 Thread master Altshuler

T h'i's g'e+m is reall,y mo*vabl.e!!
T.h-i_s o n.e is reall y p_rofi,table!!!




H_a_v_e y+o.u b.e_e+n watc__hing t.h,i*s f-o-r t+h e l,a+s-t w+e,e.k_?


T.a-k-e a l o+o_k at it:

rec'ent n e*w's rel -eases s-e,n_t g,en.erating gr_owing inter_*est in C,Y.T+V



Com,pan.y: CHI+NA YO_UTV C'O*R.P ('O*T-C BB:CYT'V,.OB)

S t o c k:  C*Y T'V
C+urrent Pric-e: $_._4_9

4.t*h Stra,,ight d,a+y-s we h-a.v'e s_e-e'n t-h.i*s climb+. (_S e_e Yah-oo 
Chart-'Ne.w N.e,w's releas e)





T+h+i_s o,n'e h-a,s h+a'd n*i+c'e ret-urns f-o'r inve'st+ors o'v-e.r t_h*e 
su'mmer, and

n'o-w s hows prom ise to begi n a secon d w,a_v'e of ret,urns.


K-e_e,p a e-y-e o-u t agai.n on We-dnesd-ay A-u'g 15.*...



B.u-t I w,e n't a+head a.n+d d_i.d it j*u s,t t+h e s+a'm'e .

F+o.r t*h+i_s purpos-e a p.u,s.h f+unc+tion is define*d.

Echo-es of thun der ro lled acr.oss t h'e s_k_y befo-re t'hey, t_o_o , fa-ded 
a.w_a'y+.
He real*,ized o,n+c_e he h'a_d a h+a-n d on t+h e f+lute c'ase, a+n'd f+irmly 
pushe*d it a'round to h'i+s b'a c_k*.

Tab'les a_r.e u_s.e-d in sev eral pla ces in t.h*i s d-ocumen*t to p_lace ite 
ms s i.d,e by s+i+d_e*.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] Making qemu images executable (and store command line arguments in them =P)

2007-08-15 Thread H. Peter Anvin

Jorge Lucángeli Obes wrote:
> 
> The '#!' trick works nice with scripts, but I don't see it playing
> very well with images. ¿Comments? ¿Pointers?
> 

Well, you can make it work with a header (you just have to pad it out to
a fixed length or use a variable-offset format), but binfmt_misc might
be a better choice.

-hpa

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

Jorge Lucángeli Obes wrote:
>> Thanks for the help, that compiled the userspace part.   I need the new
>> kernel module (kvm-intel.ko), can I take it from the kernel tree some
>> way or do I have to use the whole KVM kernel?
>> 
>
> You should be able to compile it without having to compile the whole
> kernel. That's what one does with release versions, so it has to be
> possible. However, I've been working with the userspace part, so I've
> not yet tried it. Maybe someone else can comment? It's probably just
> Makefile dark magic.
>
>   

make -C kernel sync LINUX=/path/to/your/linux/repo

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [Qemu-devel] Re: Making qemu images executable (and store command line arguments in them =P)

H. Peter Anvin wrote:
> Jorge Lucángeli Obes wrote:
>   
>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>>
>> 
>
> Well, you can make it work with a header (you just have to pad it out to
> a fixed length or use a variable-offset format), but binfmt_misc might
> be a better choice.
>
>   

binfmt_misc is Linux specific.  And while kvm is a Linux thing now, qemu
isn't.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

[kvm-devel] Makefiles (was: kvm for Ubuntu 7.04)

On 8/16/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Jorge Lucángeli Obes wrote:
> >> Thanks for the help, that compiled the userspace part.   I need the new
> >> kernel module (kvm-intel.ko), can I take it from the kernel tree some
> >> way or do I have to use the whole KVM kernel?
> >>
> >
> > You should be able to compile it without having to compile the whole
> > kernel. That's what one does with release versions, so it has to be
> > possible. However, I've been working with the userspace part, so I've
> > not yet tried it. Maybe someone else can comment? It's probably just
> > Makefile dark magic.
> >
> >
>
> make -C kernel sync LINUX=/path/to/your/linux/repo

Speaking of makefiles, this shows in 'qemu/config-host.mak' on kvm-35:

CFLAGS=-I /home/tamsyn/local/kvm-35/qemu/../user -Wall -O2 *-g*

¿Are we keeping that '-g' on purpose?

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] Makefiles (was: kvm for Ubuntu 7.04)

Jorge Lucángeli Obes wrote:
> On 8/16/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>   
>> Jorge Lucángeli Obes wrote:
>> 
 Thanks for the help, that compiled the userspace part.   I need the new
 kernel module (kvm-intel.ko), can I take it from the kernel tree some
 way or do I have to use the whole KVM kernel?

 
>>> You should be able to compile it without having to compile the whole
>>> kernel. That's what one does with release versions, so it has to be
>>> possible. However, I've been working with the userspace part, so I've
>>> not yet tried it. Maybe someone else can comment? It's probably just
>>> Makefile dark magic.
>>>
>>>
>>>   
>> make -C kernel sync LINUX=/path/to/your/linux/repo
>> 
>
> Speaking of makefiles, this shows in 'qemu/config-host.mak' on kvm-35:
>
> CFLAGS=-I /home/tamsyn/local/kvm-35/qemu/../user -Wall -O2 *-g*
>
> ¿Are we keeping that '-g' on purpose?
>   

What's wrong with -g?


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

2007-08-15 Thread Slohm Gadaburi

hi..

so I've compiled kvm-35 on Ubuntu 7.04.
i really had NO troubles, thanks to Koen and his great apt-get list.
and indeed now when I was running, I had the "QEMU\KVM" banner.

so I reinstalled RH9.0.

On 8/15/07, Koen de Jonge (ProcoliX) <[EMAIL PROTECTED]> wrote:
> Please let us know the results.

Estimated time of installation dropped from about 2.5 hours to... 15 minutes !!!

that's remarkable !

thank you all for the help !

maybe if i could slip in a last question - can I share a folder between the host
and the guest ?

thanks
slohm

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] Makefiles (was: kvm for Ubuntu 7.04)

On 8/16/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> What's wrong with -g?

Code/executable size... never mind. Thinking about it, it's probably
better to have those debugging symbols there anyways.

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] [Qemu-devel] Making qemu images executable (and store command line arguments in them =P)

Mark Williamson wrote:
>> I've been giving some thought to Anthony's idea:
>>
>> http://kvm.qumranet.com/kvmwiki/Specs/StoringCommandLineInImage
>>
>> However, maybe I'm just too much on vacations, but I don't seem to
>> come up with a nice way of doing this. Everything keeps coming back to
>> creating a new 'container' image format and then implementing block
>> layer functions that only add the number of sectors occupied by the
>> command-line to the read and write calls made by QEMU, and then just
>> relay those calls to the image-specific functions. That doesn't sound
>> very efficient.
>> 
>
> It's not necessarily that pretty, but I wouldn't have thought that adding a 
> simple offset to block operations will have a measurable performance impact 
> (given the latencies involved in block accesses anyhow, and the amount of 
> data transferred each time).
>
>   

Right.

>> The '#!' trick works nice with scripts, but I don't see it playing
>> very well with images. ¿Comments? ¿Pointers?
>> 
>
> Well, it's not really necessary, but it would be darn cool :-)  Another cool 
> (but admittedly twisted - get the brain soap ready!) thing to do would be to 
> statically link a qemu, and then include a virtual machine config and disks 
> in a section of the elf file (inspired by glick: 
> http://blogs.gnome.org/alexl/2007/08/07/experiments-with-runtime-less-app-bundles/).
>   
> So then you'd have an "executable" VM image which doesn't need a Qemu runtime 
> to be available.  There are various variations you could do on this basic 
> premise in order to make the file you carry around less terrifyingly huge!
>   

That would make the VM not transportable (think moving from an x86_64
host to an i386 host) and would tie it to a particular version of kvm
userspace.

> Anyhow, enough of my random ideas...  I was thinking about container formats.
>
> I've missed some of the discussion, but wouldn't tar be an obvious choice?  
> It 
> can expand easily out to a directory hierarchy containing config file and 
> multiple virtual disk files, there are standard tools that can manipulate it 
> and standard libraries that can be used by Qemu in order to get at the 
> contents.  Only problem I see with this approach is that sparse file handling 
> might get a bit strange (using real sparse files vs using tar's 
> represesntation of sparse files vs compatibility with tars that don't support 
> them!).
>   

Also it can't be used in-place, like Anthony's header or the
metadata-in-snapshot idea.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)

> maybe if i could slip in a last question - can I share a folder between the 
> host
> and the guest ?

If you use -net user (which is the default) and you have Samba
installed in the host, you can use -smb 
and see that folder in:

\\10.0.2.4\qemu

Check QEMU command line options:

-tftp prefixallow tftp access to files starting with prefix [-net user]
-smb dirallow SMB access to files in 'dir' [-net user]
-redir [tcp|udp]:host-port:[guest-host]:guest-port
redirect TCP or UDP connections from host to guest [-net user]

Those are the ones I use. If you use tftp access, the tftp server is
on 10.0.2.2.

Cheers,
Jorge

-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
___
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: [kvm-devel] kvm for Ubuntu 7.04 (was Re: a (bad) kvm story from a plain user)