On Saturday 04 July 2009, Andre Przywara wrote:
> Paul Brook wrote:
> >> currently SMP guests happen to see vCPUs as different sockets.
> >> Some guests (Windows comes to mind) have license restrictions and refuse
> >> to run on multi-socket machines.
> >> So lets introduce a "cores=" parameter t
Andre Przywara, le Sat 04 Jul 2009 01:28:43 +0200, a écrit :
> Maybe one could describe cores, threads, sockets and nodes in -smp and
> declare the memory topology only in -numa.
Mmm, I'd rather just describe both in a -topology option.
Samuel
--
To unsubscribe from this list: send the line "uns
Andre Przywara wrote:
> So what about: "-smp 4,cores=2,threads=2[,sockets=1]" to inject 4 vCPUs
> in one package (automatically determined if omitted) with two cores and
> two threads/core? All parameters except the number of vCPUs would be
> optional,
Why is the number of vCPUs required at all
Paul Brook wrote:
currently SMP guests happen to see vCPUs as different sockets.
Some guests (Windows comes to mind) have license restrictions and refuse
to run on multi-socket machines.
So lets introduce a "cores=" parameter to the -cpu option to let the user
specify the number of _cores_ the
Samuel Thibault wrote:
Andre Przywara, le Fri 03 Jul 2009 16:41:56 +0200, a écrit :
-smp 16 -cpu host,cores=8
That means 8 cores with 2 threads each, thus 16 threads?
No, that meant: 16 vCPUs total with 8 cores per physical packages. I
don't have any notion for threads in the current code, al
On Fri, Jul 3, 2009 at 9:00 AM, Lars Ellenberg wrote:
> the elevator of the lower level block device (in this case,
> the kvm virtual block device, or the host real block device)
so, the original post (Michael) was running drbd on the KVM guests??
i thought the only sensible setup was using dbrb
Brian Jackson wrote:
Andre Przywara wrote:
currently SMP guests happen to see vCPUs as different sockets.
Some guests (Windows comes to mind) have license restrictions and refuse
to run on multi-socket machines.
So lets introduce a "cores=" parameter to the -cpu option to let the user
specify
Hi Everyone,
I am trying to use the MSR load and store areas in vmx. I did following:
1. Setting vm_entry_msr_load_count:
vmcs_write32(VM_ENTRY_MSR_LOAD_COUNT, 1);
2. Setting up vm_entry_msr_load_addr :
static struct page *vmx_msr_load;
Then in vmx_init() :
vmx_msr_load = alloc_page(GFP_KERN
> Haven't followed the thread in great detail, but has anyone tried
> putting the virtio disk back into rotational mode?
Thanks Mark.
I have not tried this yet.
To be honest, I wasn't fully understanding some of Avi's last comments and
was waiting for one of my co-workers to be available to help
G wrote:
> Hello again,
>
> I've continued my attempts to get the HASP dongle working, but with no
> success:
>
> Downloaded kvm-72.tar.gz through kvm-87.tar.gz to find out when the
> problem first appear, as kvm-72 is working. Unfortunately, kvm-72
> through kvm-82 fails to compile on my Debian
> currently SMP guests happen to see vCPUs as different sockets.
> Some guests (Windows comes to mind) have license restrictions and refuse
> to run on multi-socket machines.
> So lets introduce a "cores=" parameter to the -cpu option to let the user
> specify the number of _cores_ the guest shou
On Thu, 2009-07-02 at 12:41 +0300, Avi Kivity wrote:
> On 07/02/2009 08:48 AM, Avi Kivity wrote:
> >> HOST time (make -j12&& make -j12 modules) with no guest running
> >>
> >> real6m50.936s
> >> user29m12.051s
> >> sys5m
Andre Przywara wrote:
Hi,
currently SMP guests happen to see vCPUs as different sockets.
Some guests (Windows comes to mind) have license restrictions and refuse
to run on multi-socket machines.
So lets introduce a "cores=" parameter to the -cpu option to let the user
specify the number of _
Andre Przywara, le Fri 03 Jul 2009 16:41:56 +0200, a écrit :
> -smp 16 -cpu host,cores=8
That means 8 cores with 2 threads each, thus 16 threads? Ok, that can be
later generalized into for instance
-smp 16 -cpu host,nodes=2,sockets=2,cores=2
to define 2 NUMA nodes of 2 sockets of 2 cores, each c
Hi,
currently SMP guests happen to see vCPUs as different sockets.
Some guests (Windows comes to mind) have license restrictions and refuse
to run on multi-socket machines.
So lets introduce a "cores=" parameter to the -cpu option to let the user
specify the number of _cores_ the guest should se
Hi Everyone,
I am trying to use the MSR load and store areas in vmx. I did following:
1. Setting vm_entry_msr_load_count:
vmcs_write32(VM_ENTRY_MSR_LOAD_COUNT, 1);
2. Setting up vm_entry_msr_load_addr :
static struct page *vmx_msr_load;
Then in vmx_init() :
vmx_msr_load = alloc_page(GFP_KERN
Windows 7 tries to update the CPU's microcode on some processors,
so we ignore the MSR write here. The patchlevel register is already handled
(returning 0), because the MSR number is the same as Intel's.
Signed-off-by: Andre Przywara
---
arch/x86/kvm/x86.c |1 +
1 files changed, 1 insertions
On Fri, Jul 03, 2009 at 08:06:07AM -0500, Javier Guerra wrote:
> Lars Ellenberg wrote:
> > On Thu, Jul 02, 2009 at 11:55:05PM +0400, Michael Tokarev wrote:
> > > drbd: what's the difference in write pattern on secondary and
> > > primary nodes? Why `rotational' flag makes very big difference
> >
Lars Ellenberg wrote:
> On Thu, Jul 02, 2009 at 11:55:05PM +0400, Michael Tokarev wrote:
> > drbd: what's the difference in write pattern on secondary and
> > primary nodes? Why `rotational' flag makes very big difference
> > on secondary and no difference whatsoever on primary?
>
> not much.
On Fri, 2009-07-03 at 17:18 +0800, Yolkfull Chow wrote:
> Lucas, do we really need to find those ELFs within the whole disk if
> they are not in os.environ['PATH']? That's not testsuite's purpose I
> think.
>
> What's your opinion?
Sure it's not. My point was just to allow the user to provide
This should be no longer necessary.
Effectively reverts 143eb2bd043e82bcf353cf82d33c127f06411d82.
Signed-off-by: Andre Przywara
---
kvm/libkvm/libkvm-x86.c |9 -
qemu-kvm-x86.c |9 -
2 files changed, 0 insertions(+), 18 deletions(-)
Hi Avi,
I am not sure what c
Hi,
I'm (unsuccessfully) trying to pass-through a tape device, that is
connected to the host, to a kvm guest (Windows 2003). The tape device
is connected over SAS with a PCI card (aacraid).
First I tried to add the device with the following parameter
# ... -drive file=/dev/st0,if=scsi
This
On Sun, Jun 14, 2009 at 5:33 AM, Avi Kivity wrote:
>> I performed tests on two different systems to be sure it isn't related to
>> specific hardware.
>>
>
> What is the host cpu type? On pre-Nehalem/Barcelona processors kvm has poor
> scalability in mmu intensive workloads like kernel builds.
Hey
Hello again,
I've continued my attempts to get the HASP dongle working, but with no success:
Downloaded kvm-72.tar.gz through kvm-87.tar.gz to find out when the
problem first appear, as kvm-72 is working. Unfortunately, kvm-72
through kvm-82 fails to compile on my Debian system with kernel 2.6.30
On 07/03/2009 01:03 PM, Lucas Meneghel Rodrigues wrote:
On Thu, 2009-07-02 at 21:23 -0300, Lucas Meneghel Rodrigues wrote:
Ok, I've been trough the test and took a look at the testsuite itself.
Both look good. The testsuite requires a very current qemu-img package,
due to the use of qemu-io
On Thu, Jul 02, 2009 at 11:55:05PM +0400, Michael Tokarev wrote:
> Hello.
>
> I'm new on drbd-user@, but long-time user of kvm.
>
> [A side note: drbd-user@ appears to be subscribers-only
> list. Sad consequence of spammers activity... I doubt
> many knowlegeable people on kvm@ are subscribe
* Suresh Siddha wrote:
> On Wed, 2009-07-01 at 06:30 -0700, Gleb Natapov wrote:
> > KVM would like to provide x2APIC interface to a guest without emulating
> > interrupt remapping device. The reason KVM prefers guest to use x2APIC
> > is that x2APIC interface is better virtualizable and provides
27 matches
Mail list logo
