Zachary Amsden wrote:
> On Wed, 2007-11-21 at 09:13 +0200, Avi Kivity wrote:
>
>
>> Where the device is implemented is an implementation detail that should
>> be hidden from the guest, isn't that one of the strengths of
>> virtualization? Two examples: a file-based block device implemented in
The following patch complement 50096dbe4c8523d9855b0e2ee6f058a75e7942a3 to
avoid a compilation warning because of a formatting mismatch after making
"size" long to allow for allocations bigger than 4GB and as can be seen by :
kvm-53/qemu/exec.c: In function `qemu_ram_alloc':
kvm-53/qemu/exec.c:20
From: Zhang Xiantao <[EMAIL PROTECTED]>
Date: Thu, 22 Nov 2007 11:20:33 +0800
Subject: [PATCH] KVM Portability: moving unalias_gfn to arch.
Non-x86 archs don't need this mechanism. Move it to arch, and
keep its interface in common.
Signed-off-by: Zhang Xiantao <[EMAIL PROTECTED]>
---
drivers/kvm/k
Sorry to be late on reporting on kvm-53 release but I have had host hang and
BSOD when running windows xp sp2 32-bit guest. I have had to revert to
release 51 as I also have problems with release 52 (boot failure). My host
does have flexpriority and details are as follows:
Linux localhost.localdom
On Wed, 21 Nov 2007 09:36:31 pm Dan Kenigsberg wrote:
> These patches expose host CPU features (that are known to work under
> KVM) to guests. It makes a couple of benchmarks run faster, and
> generally gives kvm's user better info on its host.
>
> The kernel-space patch adds KVM_GET_SUPPORTED_CPUI
Hi,
I'm trying to install KVM using the git repos on Scientific Linux. The
error occurs when I run make.
The kvm-53 tarball works fine, but something is getting misconfigured
when I run "make -C kernel sync". This error doesn't occur on
Fedora Core. I installed kernel-headers using yu
Izik Eidus schrieb:
> Mike wrote:
>> Izik Eidus schrieb:
>>
>>> Mike wrote:
>>>
Izik Eidus schrieb:
> Mike wrote:
>
>> Izik Eidus schrieb:
>>
>>
>>> Mike wrote:
>>>
Hello,
I
Izik Eidus schrieb:
> Mike wrote:
>> Izik Eidus schrieb:
>>
>>> Mike wrote:
>>>
Izik Eidus schrieb:
> Mike wrote:
>
>> Izik Eidus schrieb:
>>
>>
>>> Mike wrote:
>>>
Hello,
I
On Nov 21, 2007, at 12:52 PM, Mike wrote:
> Hello,
> I have a problem with my virtual machines. I am using kvm53
> on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
> As distribution I use Ubuntu server 7.10.
> As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15
> GMT 2007 x86
Mike wrote:
> Izik Eidus schrieb:
>
>> Mike wrote:
>>
>>> Izik Eidus schrieb:
>>>
>>>
Mike wrote:
> Izik Eidus schrieb:
>
>
>
>> Mike wrote:
>>
>>
>>> Hello,
>>> I have a prob
Izik Eidus schrieb:
> Mike wrote:
>> Izik Eidus schrieb:
>>
>>> Mike wrote:
>>>
Izik Eidus schrieb:
> Mike wrote:
>
>> Hello,
>> I have a problem with my virtual machines. I am using kvm53
>> on an AMD Athlon(tm) 64 X2 Dual Core Processor
Mike wrote:
> Izik Eidus schrieb:
>
>> Mike wrote:
>>
>>> Izik Eidus schrieb:
>>>
>>>
Mike wrote:
> Hello,
> I have a problem with my virtual machines. I am using kvm53
> on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
> As distribu
Izik Eidus schrieb:
> Mike wrote:
>> Izik Eidus schrieb:
>>
>>> Mike wrote:
>>>
Hello,
I have a problem with my virtual machines. I am using kvm53
on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
As distribution I use Ubuntu server 7.10.
As kernel I use Linux 2.6
Mike wrote:
> Izik Eidus schrieb:
>
>> Mike wrote:
>>
>>> Hello,
>>> I have a problem with my virtual machines. I am using kvm53
>>> on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
>>> As distribution I use Ubuntu server 7.10.
>>> As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct
Izik Eidus schrieb:
> Mike wrote:
>> Hello,
>> I have a problem with my virtual machines. I am using kvm53
>> on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
>> As distribution I use Ubuntu server 7.10.
>> As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT
>> 2007 x86_64 G
Mike wrote:
> Hello,
> I have a problem with my virtual machines. I am using kvm53
> on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
> As distribution I use Ubuntu server 7.10.
> As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT
> 2007 x86_64 GNU/Linux.
>
> I have 3 diffe
Hello,
I have a problem with my virtual machines. I am using kvm53
on an AMD Athlon(tm) 64 X2 Dual Core Processor 5000+.
As distribution I use Ubuntu server 7.10.
As kernel I use Linux 2.6.22-14-server #1 SMP Sun Oct 14 22:09:15 GMT
2007 x86_64 GNU/Linux.
I have 3 different vms running. At the
> try with kvm-53! it do not even start to boot for me (actually i don't
> remember for the kvm-51 result but it may be worked with kvm-51).
>
Tried, and you're right. It crashes right from start.
Opened a bug report. We will look into this issue.
http://sourceforge.net/tracker/index.php?func=det
Alexey Eremenko wrote:
> OK, I have found that Mandrake Linux 9.0 works on Intel/x86-64 on KVM-51.
>
> Does this help you for now ?
>
> I will try to look further.
try with kvm-53! it do not even start to boot for me (actually i don't
remember for the kvm-51 result but it may be worked with kvm-
On Nov 21, 2007 11:41 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Francesc Romà i Frigolé wrote:
> > Hello,
> >
> > Sorry if the post is off-topic, but the qemu users forum has been down
> > for several days.
> >
> > Is it possible to use a wide screen resolution of 1680x1050 with kvm?
> > the gue
On Wed, 2007-11-21 at 09:13 +0200, Avi Kivity wrote:
> Where the device is implemented is an implementation detail that should
> be hidden from the guest, isn't that one of the strengths of
> virtualization? Two examples: a file-based block device implemented in
> qemu gives you fancy file for
opened a bug report about Mandrake 9.0:
http://sourceforge.net/tracker/index.php?func=detail&aid=1835911&group_id=180599&atid=893831
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio
Bugs item #1835911, was opened at 2007-11-21 19:20
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1835911&group_id=180599
Please note that this message will contain a full copy
Well, Mandrake 9.0 works on Intel/x64 KVM-51, but without SMP.
It stucks with SMP. (on init stage, when entering init 5)
-Alexey
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio
OK, I have found that Mandrake Linux 9.0 works on Intel/x86-64 on KVM-51.
Does this help you for now ?
I will try to look further.
-Alexey
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visu
Jerry Geis wrote:
> I have the old disk and I created a 10GIG image and installed the 7.3, 9
> and centos 4.
> Now I want to make sure the new image matches the physical image.
> I mounted the image as:
>
> mount -t ext3 -o loop,offset=32256 Image.redhat7.3.img /mnt/image
>
> then I executed
>
> t
[EMAIL PROTECTED] wrote:
> I have an AMD 4800+ machine with 2 GIG RAM.
>
> I have OLD machines that I want to virtualize and then TURN OFF.
> The old machines are redhat 7.3, redhat 9, centos 4 i386. I am using
> centos 5 x86_64.
>
Migrating a physical machine to a virtual environment needs add
Dan Kenigsberg wrote:
> On Wed, Nov 21, 2007 at 01:52:15PM +0200, Avi Kivity wrote:
>
>> Dan Kenigsberg wrote:
>>
>>> These patches expose host CPU features (that are known to work under
>>> KVM) to guests. It makes a couple of benchmarks run faster, and
>>> generally gives kvm's user bette
On Wed, Nov 21, 2007 at 01:52:15PM +0200, Avi Kivity wrote:
> Dan Kenigsberg wrote:
>> These patches expose host CPU features (that are known to work under
>> KVM) to guests. It makes a couple of benchmarks run faster, and
>> generally gives kvm's user better info on its host.
>>
>> The kernel-spac
Alexey Eremenko wrote:
>
> Hi Levente!
>
> Do you have a link where I can download Mandrake 9.0 ?
>
> Because I don't have this version, and don't know where to get it.
ok. just to describe why we need it. our production servers run on
mandrake-9 and mandrake-10. it's about 6-700 server runnin
I have an AMD 4800+ machine with 2 GIG RAM.
I have OLD machines that I want to virtualize and then TURN OFF.
The old machines are redhat 7.3, redhat 9, centos 4 i386. I am using
centos 5 x86_64.
I need to have the OLD machines migrated to the virtual image.
What is the BEST way to do that??? Th
Alexey Eremenko wrote:
>
> Hi Levente!
>
> Do you have a link where I can download Mandrake 9.0 ?
>
> Because I don't have this version, and don't know where to get it.
we mirror this mirror site:-):
rsync carroll.aset.psu.edu::MandrivaLinux/old/
or
ftp://carroll.aset.psu.edu/pub/linux/distrib
Hi Levente!
Do you have a link where I can download Mandrake 9.0 ?
Because I don't have this version, and don't know where to get it.
-Alexey
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R
Izik Eidus wrote:
> Farkas Levente wrote:
>> hi,
>> we made a quick try of kvm-53. in short there is no progress for us
>> (since we need the mandrake-9 i586 guest too) so switch back to kvm-36.
>> in detail:
>> - guest-1 smp guest are hang at starting udev
> i am in search for this bug
> it worked
Dan Kenigsberg wrote:
> These patches expose host CPU features (that are known to work under
> KVM) to guests. It makes a couple of benchmarks run faster, and
> generally gives kvm's user better info on its host.
>
> The kernel-space patch adds KVM_GET_SUPPORTED_CPUID ioctl to obtain the
> table of
Farkas Levente wrote:
> hi,
> we made a quick try of kvm-53. in short there is no progress for us
> (since we need the mandrake-9 i586 guest too) so switch back to kvm-36.
> in detail:
> - guest-1 smp guest are hang at starting udev
i am in search for this bug
it worked for you in kvm-36?
hi,
we made a quick try of kvm-53. in short there is no progress for us
(since we need the mandrake-9 i586 guest too) so switch back to kvm-36.
in detail:
- guest-1 smp guest are hang at starting udev
- guest-1 sinlge cpu boot.
- guest-2 both smp and single cpu guest boot.
- guest-3 neither smp nor
* Dan Kenigsberg wrote:
> These patches expose host CPU features (that are known to work under
> KVM) to guests. It makes a couple of benchmarks run faster, and
> generally gives kvm's user better info on its host.
>
> The kernel-space patch adds KVM_GET_SUPPORTED_CPUID ioctl to obtain the
> table
These patches expose host CPU features (that are known to work under
KVM) to guests. It makes a couple of benchmarks run faster, and
generally gives kvm's user better info on its host.
The kernel-space patch adds KVM_GET_SUPPORTED_CPUID ioctl to obtain the
table of cpuid functions supported by the
Francesc Romà i Frigolé wrote:
> Hello,
>
> Sorry if the post is off-topic, but the qemu users forum has been down
> for several days.
>
> Is it possible to use a wide screen resolution of 1680x1050 with kvm?
> the guest OS is windows XP. I'm using the qemu parameter -std-vga, and
> I can use re
Hello,
Sorry if the post is off-topic, but the qemu users forum has been down for
several days.
Is it possible to use a wide screen resolution of 1680x1050 with kvm? the
guest OS is windows XP. I'm using the qemu parameter -std-vga, and I can use
resolutions up to 1600x1200, but the 1680x1050 is
Zhang, Xiantao wrote:
>> IIRC a downside was mentioned that it is easier to cause a build
>> failure for another arch now.
>>
>
> I can't figure out why it can cause more build failure.
>
Nothing stops you from doing kvm->arch.blah in kvm_main.c, but blah will
not be present for all archi
Avi Kivity wrote:
> Carsten Otte wrote:
>> Hollis Blanchard wrote:
>>
>>> These patches are based on Xiantao's work to create struct kvm_x86.
>>> Patch 1 replaces his "KVM Portability split: Splitting kvm
>>> structure (V2)", and patches 2 and 3 build on it.
>>>
>> Looks like a clean approach w
Avi Kivity wrote:
> Well, I hate to say it, but the resulting code doesn't look too well
> (all the kvm_x86 variables), and it's entirely my fault as I recommended
> this approach. Not like it was difficult to predict.
>
> I'm thinking again of
>
> struct kvm {
> struct kvm_arch a;
>
* Avi Kivity wrote:
> Carsten Otte wrote:
> > Hollis Blanchard wrote:
> >> These patches are based on Xiantao's work to create struct kvm_x86.
> >> Patch 1 replaces his "KVM Portability split: Splitting kvm structure
> >> (V2)", and patches 2 and 3 build on it.
> >
> > Looks like a clean approach w
Carsten Otte wrote:
> Hollis Blanchard wrote:
>
>> These patches are based on Xiantao's work to create struct kvm_x86. Patch 1
>> replaces his "KVM Portability split: Splitting kvm structure (V2)", and
>> patches 2 and 3 build on it.
>>
> Looks like a clean approach with to to_kvm_x86 mac
Hollis Blanchard wrote:
> These patches are based on Xiantao's work to create struct kvm_x86. Patch 1
> replaces his "KVM Portability split: Splitting kvm structure (V2)", and
> patches 2 and 3 build on it.
Looks like a clean approach with to to_kvm_x86 macro. Whole series:
Acked-by: Carsten Otte
Marko Kohtala wrote:
> On Nov 21, 2007 8:56 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Marko Kohtala wrote:
>>
>>> Wait for right amount of tlb flushes. Completed can be larger than
>>> needed and therefore the loop waiting them to match never ends.
>>>
>>> Signed-off-by: Marko Kohtala
On Nov 21, 2007 8:56 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Marko Kohtala wrote:
> > Wait for right amount of tlb flushes. Completed can be larger than
> > needed and therefore the loop waiting them to match never ends.
> >
> > Signed-off-by: Marko Kohtala <[EMAIL PROTECTED]>
> >
> > ---
> >
>
49 matches
Mail list logo
