Hi,
Is there any plan to port KVM on Itanium to utilize the VTI ? I'd like
to have a try. Is there anyone doing the work? Or Any volunteer to work
together on it?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 2007年3月19日 19:21
To: [email protected]
Subject: kvm-devel Digest, Vol 6, Issue 40
Send kvm-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/kvm-devel
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kvm-devel digest..."
Today's Topics:
1. Re: [RFC] QEMU KVM target -> Anthony (D?niel Fraga)
2. Re: [RFC] QEMU KVM target -> Anthony (D?niel Fraga)
3. Re: [RFC] QEMU KVM target -> Anthony (D?niel Fraga)
4. Re: [RFC] QEMU KVM target -> Anthony (Anthony Liguori)
5. Re: [RFC] QEMU KVM target -> Anthony (D?niel Fraga)
6. Re: kvm-16 fails to compile on Kubuntu Edgy (Avi Kivity)
7. Re: KVM Bug with Windows 2000 (Avi Kivity)
----------------------------------------------------------------------
Message: 1
Date: Sun, 18 Mar 2007 20:23:32 -0300
From: D?niel Fraga <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] [RFC] QEMU KVM target -> Anthony
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
On Sun, 18 Mar 2007 18:36:54 -0400
Jim Paris <[EMAIL PROTECTED]> wrote:
> Why not install them both? Most distributions make it quite easy.
> For Debian/Ubunty, "apt-get install gcc-3.3" and you'll have it in 60
> seconds. If you want to remove it when you're done, it's just as
> quick.
Just an analogy: it's this kind of thing that allow companies
like Sun and Adobe to take forever to release a 64bit plugin, for
example. Just because people can run the plugin on 32bit... I disagree
with this. I think that if we have a 64 bit machine, we should be able
to use it in pure 64bit mode and the software should follow the
hardware evolution.
The same applies for gcc. If I have a better gcc, I should be
able to compile qemu with it, instead of using the old gcc3.
gcc is the second most important piece of software in Linux
world, so all the software should follow gcc evolution, since there
isn't another viable compiler (icc isn't a free option).
> I don't think it's appropriate to tell the qemu authors what they
> should be doing. Perhaps the problems are more complicated than you
> believe and they thought their time was better spent elsewhere.
Ok, but at least I think that if someone wants to do something
right, it should put all his/her effort so it will be done right,
otherwise it will result in problems like these. And Anthony's patch
would suffice for kvm's purpose.
But you're correct. i can't blame qemu author if he doesn't
want to support gcc4. I'm just on his hands... At the same time, those
who don't want to use gcc3 will be unable to use kvm because kvm
depends on qemu...
I just think that if KVM uses a patched qemu, it does not mind
if we have patches for the qemu distributed in the kvm tarball, since
it will just be used together with KVM. And as far as I know, the
official qemu won't support kvm, right? So you'll have to maintain your
own qemu version separately.
> GCC 4.x also introduced many new bugs. For a list of just the known
> regressions, see: http://preview.tinyurl.com/ywvpxv
Ok, but when qemu will fully support gcc4? Does it mean we will
have to use gcc3 forever?
Thanks.
--
http://u-br.net
Linux 2.6.20: Homicidal Dwarf Hamster
gcc (GCC) 4.1.2
------------------------------
Message: 2
Date: Sun, 18 Mar 2007 19:50:12 -0300
From: D?niel Fraga <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] [RFC] QEMU KVM target -> Anthony
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
On Sun, 18 Mar 2007 18:42:48 -0400
"Gregory Haskins" <[EMAIL PROTECTED]>
wrote:
> This is what I do and it works fine. Hope this helps.
Ok Greg, thanks for the message, but I really would like to be
able to compile qemu using gcc 4.1.2. But thanks anyway.
--
http://u-br.net
Linux 2.6.20: Homicidal Dwarf Hamster
gcc (GCC) 4.1.2
------------------------------
Message: 3
Date: Sun, 18 Mar 2007 21:08:38 -0300
From: D?niel Fraga <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] [RFC] QEMU KVM target -> Anthony
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
On Sun, 18 Mar 2007 16:08:21 -0700
"Ed Swierk" <[EMAIL PROTECTED]> wrote:
> Please read this email thread if you want to know why your assumption
> is incorrect:
> http://lists.gnu.org/archive/html/qemu-devel/2006-10/msg00175.html
I read everything. The last message by Paul Brook:
"- qemu makes assumptions about the layout of the code gcc generates.
This works by chance on older gcc. This effects all hosts, and is not a gcc bug.
- qemu reserves several registers for its own use. On architecturally crippled
hosts (ie. x86) this means we hit really obscure gcc bugs on x86 because gcc
runs out of registers. This is a gcc bug, but is also relatively easy to
workaround".
He even proposes a solution:
https://nowt.dyndns.org/
And even this way, nobody agreed with each other...
So I ask: if Paul Brook could fix this, why it isn't merged? A
solution should be applied. What we can't do is keep discussing forever
this and the previous message is realy annoying:
"Basically, gcc changed in a way that broke qemu. There's been an open
bug report in gcc ever since, but the GCC developers really aren't interested
in
backwards compatability. (Heck, gcc 4.0 breaks building bash 2.05b). The
qemu developers aren't interested in applying ugly patches to support gcc 4.x
until gcc 3.x becomes so obsolete nobody ships it anymore. (And considering
that there are still some niche embedded boards that have hacked up versions
of gcc 2.95 targeting them and nothing else, I wouldn't be surprised if in
five years we have your main compiler and the compiler to build qemu, ala
kgcc under Red Hat 7. *shrug*)"
It's like saying: "we don't care. Keep using gcc3". :(
--
http://u-br.net
Linux 2.6.20: Homicidal Dwarf Hamster
gcc (GCC) 4.1.2
------------------------------
Message: 4
Date: Sun, 18 Mar 2007 20:39:33 -0500
From: Anthony Liguori <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] [RFC] QEMU KVM target -> Anthony
To: D?niel Fraga <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
D?niel Fraga wrote:
> On Sun, 18 Mar 2007 16:08:21 -0700
> "Ed Swierk" <[EMAIL PROTECTED]> wrote:
>
>
>> Please read this email thread if you want to know why your assumption
>> is incorrect:
>> http://lists.gnu.org/archive/html/qemu-devel/2006-10/msg00175.html
>>
>
> I read everything. The last message by Paul Brook:
>
> "- qemu makes assumptions about the layout of the code gcc generates.
> This works by chance on older gcc. This effects all hosts, and is not a gcc
> bug.
>
> - qemu reserves several registers for its own use. On architecturally
> crippled
> hosts (ie. x86) this means we hit really obscure gcc bugs on x86 because gcc
> runs out of registers. This is a gcc bug, but is also relatively easy to
> workaround".
>
> He even proposes a solution:
>
> https://nowt.dyndns.org/
>
> And even this way, nobody agreed with each other...
>
> So I ask: if Paul Brook could fix this, why it isn't merged? A
> solution should be applied. What we can't do is keep discussing forever
> this and the previous message is realy annoying:
>
This is qops which is why I said "qops is the right solution" in my
previous note. It's a huge, fundamental change to QEMU so it needs some
time being developed outside of the main tree.
I understand that it's frustrating to depend on gcc3. Please realize
though that if it was simple to fix than it would be fixed and more
importantly, that the work is being done to fix the situation.
Regards,
Anthony Liguori
> "Basically, gcc changed in a way that broke qemu. There's been an open
> bug report in gcc ever since, but the GCC developers really aren't interested
> in
> backwards compatability. (Heck, gcc 4.0 breaks building bash 2.05b). The
> qemu developers aren't interested in applying ugly patches to support gcc 4.x
> until gcc 3.x becomes so obsolete nobody ships it anymore. (And considering
> that there are still some niche embedded boards that have hacked up versions
> of gcc 2.95 targeting them and nothing else, I wouldn't be surprised if in
> five years we have your main compiler and the compiler to build qemu, ala
> kgcc under Red Hat 7. *shrug*)"
>
> It's like saying: "we don't care. Keep using gcc3". :(
>
>
------------------------------
Message: 5
Date: Sun, 18 Mar 2007 23:01:37 -0300
From: D?niel Fraga <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] [RFC] QEMU KVM target -> Anthony
To: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII
On Sun, 18 Mar 2007 20:39:33 -0500
Anthony Liguori <[EMAIL PROTECTED]> wrote:
> This is qops which is why I said "qops is the right solution" in my
> previous note. It's a huge, fundamental change to QEMU so it needs
> some time being developed outside of the main tree.
>
> I understand that it's frustrating to depend on gcc3. Please realize
> though that if it was simple to fix than it would be fixed and more
> importantly, that the work is being done to fix the situation.
Ok. I'll wait for the fix.
Thank you and everybody who answered!
--
http://u-br.net
Linux 2.6.20: Homicidal Dwarf Hamster
gcc (GCC) 4.1.2
------------------------------
Message: 6
Date: Mon, 19 Mar 2007 08:43:43 +0200
From: Avi Kivity <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] kvm-16 fails to compile on Kubuntu Edgy
To: Anthony Liguori <[EMAIL PROTECTED]>
Cc: [email protected], Martin Kaufmann
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Anthony Liguori wrote:
>
> The definition of struct file_system_type.get_sb for 2.6.17 is:
>
> struct super_block *(*get_sb) (struct file_system_type *, int,
> const char *, void *);
>
> So a slightly modified kvmfs_get_sb() is needed. I'm not sure how to
> cope with this though since this #if guard isn't in
> external-module-compat.h. I was under the impression that per-kernel
> version defined were frowned upon in mainline code.
>
> What's the correct solution to this?
>
See the 'sync' target in kernel/Makefile. It looks like all that is
necessary is to add the 2.6.17 case to external-module-compat.h.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
------------------------------
Message: 7
Date: Mon, 19 Mar 2007 13:20:42 +0200
From: Avi Kivity <[EMAIL PROTECTED]>
Subject: Re: [kvm-devel] KVM Bug with Windows 2000
To: Daniel Hecken <[EMAIL PROTECTED]>
Cc: [email protected]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-15"
Daniel Hecken wrote:
> Hello!
>
> I have installed Windows 2000 on KVM SVN snapshot 4539 and the module
> from the git master branch. My Computer has an Intel Core 2 Duo and runs
> an x86 distribution (Ubuntu Feisty with Kernel 2.6.20).
>
> After the installation without kvm I tried to start the image with kvm
> and get the exception in the appendix.
>
>
Let me know if the attached patch fixes this.
--
error compiling committee.c: too many arguments to function
-------------- next part --------------
A non-text attachment was scrubbed...
Name: win-acpi-boot.patch
Type: text/x-patch
Size: 533 bytes
Desc: not available
------------------------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------
_______________________________________________
kvm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel
End of kvm-devel Digest, Vol 6, Issue 40
****************************************
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
kvm-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel
