Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
>
> On Oct 19 2007 15:44, Carsten Otte wrote:
> > Carsten Otte wrote:
> >> First thing we do, is figure whether or not 2.6.23.1 as released breaks our
> >> system too. This way, we can either focus on differences between Linus and
> >> Avi, or t
On Oct 19 2007 15:44, Carsten Otte wrote:
> Carsten Otte wrote:
>> First thing we do, is figure whether or not 2.6.23.1 as released breaks our
>> system too. This way, we can either focus on differences between Linus and
>> Avi, or turn on the big red warning sign saying "regression".
>
> Looks li
On Fri, 2007-10-19 at 11:57 -0500, Hollis Blanchard wrote:
> > @@ -669,11 +670,13 @@ __init void kvm_arch_init(void);
> >
> > static inline void kvm_guest_enter(void)
> > {
> > + account_system_vtime(current);
> > current->flags |= PF_VCPU;
> > }
> >
> > static inline void kvm_guest_exi
On Thu, 2007-10-18 at 17:04 -0500, Anthony Liguori wrote:
> Hollis Blanchard wrote:
> >
> > I must be misunderstanding, because this seems completely backwards to
> > me. With your nesting, any time architecture code wants to access
> > architecture state (which is almost all the time), you'd *need
I am running 2.6.23.1 with kvm built from that tree as a module. My
system is running Debian/testing on a Tyan board with two dual-core
Opteron 2216 processors; each socket has 4G of RAM. I have attached the
serial console dump including a bunch of output from SysRq (gzipped,
because it was 300k
Hollis Blanchard wrote:
> This patch can now execute guest userspace (I'm not saying it's complete
> or stable or anything though). I need to put together a more
> full-featured ramdisk to test userspace more completely.
>
> That reminds me, what is the status of KVM VirtIO work? If I can put a
> v
* Bart Trojanowski <[EMAIL PROTECTED]> [071019 17:00]:
>
> Once the system is booted, I attached using vnc, then I ssh in and ran
> 'svn update'... and the host machine froze.
>
> The last messages I on my serial console are:
>
> kvm: unhandled rdmsr: 0x417
> kvm: unhandled rdmsr: 0xc400
>
On Sat, 2007-10-20 at 00:15 +0200, Dor Laor wrote:
> Hollis Blanchard wrote:
> > This patch can now execute guest userspace (I'm not saying it's
> complete
> > or stable or anything though). I need to put together a more
> > full-featured ramdisk to test userspace more completely.
> >
> > That remi
On Fri, Oct 19, 2007 at 11:55:03PM +0200, Dor Laor wrote:
> Can you also give a shot with the -no-kvm-irqchip flag? Maybe this is the
> source for the failures.
Sorry, I forgot to mention this, but I have tested it
earlier and got the same result: crash at boot loader and dump
registers.
Some m
Vladimir Stavrinov wrote:
> Microsoft.Windows.Vista.Ultimate.X86.OEM guest successfully
> installed but after that kvm crash immediately after startup on
> vista boot loader and dump registers into linux console:
>
> unhandled vm exit: 0x8021 vcpu_id 0
> rax 6010 rbx 008
Am Freitag, 19. Oktober 2007 schrieb Luca Tettamanti:
> linus-git has at least one bug with SG chaining, but usually it just
> hangs the machine. Patch is here:
>
> http://lkml.org/lkml/2007/10/17/269
Looks promising.
I pulled this fix by pulling the latest Linus-git into the kvm.git. I also
ena
Microsoft.Windows.Vista.Ultimate.X86.OEM guest successfully
installed but after that kvm crash immediately after startup on
vista boot loader and dump registers into linux console:
unhandled vm exit: 0x8021 vcpu_id 0
rax 6010 rbx 0080 rcx rdx
On 10/19/07, Christian Borntraeger <[EMAIL PROTECTED]> wrote:
> Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> > Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
> > linux-2.6.23.1.tar.bz2 ?
> >
> > 2.6.23.1 corrects nothing except sata_mv...
>
> Yes I know. The question we
On Fri, 2007-10-19 at 16:17 +0200, Back, Michael (ext) wrote:
> >Are you referring to the -rt patch?
>
> Yes, I take the patch from
> http://www.kernel.org/pub/linux/kernel/projects/rt/
>
Ah, yes. There were problems in the past with running KVM on -rt if you
have the full kit enabled. Its po
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> Did you patch kvm.git with patch-2.6.23.1.bz2 or did you download
> linux-2.6.23.1.tar.bz2 ?
>
> 2.6.23.1 corrects nothing except sata_mv...
Yes I know. The question we tried to answer was: is the bug in 2.6.23 or was
it introduced after 2.6
The following patch Implement a configure passthrough for qemu and
migrate all current qemu specific configuration flags (enable-alsa,
disable-vnc-tls and disable-gcc-check) to use it.
It leaves a description of the current flags (as used in kvm's configure)
as a reference but I'm not sure if th
Carsten Otte wrote:
> Hi list,
>
> we've experienced a severe bug in current kvm.git, that may have been
> introduced to the git tree quite recently around last weekend. 2.6.23
> is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
> kvm test machine shredders its hard disk conten
Hi Gregory,
>Hi Michael,
>On Fri, 2007-10-19 at 15:32 +0200, Back, Michael (ext) wrote:
>>
>>
>> 2.6.31.1 should be 2.6.23.1 - sorry
>>
>> _
>> Von:Back, Michael (ext)
>> Gesendet: Friday, October 19, 2007 3:16 PM
>> An: 'kvm-de
Christian Borntraeger a écrit :
> Am Freitag, 19. Oktober 2007 schrieb Jan Engelhardt:
>> On Oct 19 2007 15:44, Carsten Otte wrote:
>>> Carsten Otte wrote:
First thing we do, is figure whether or not 2.6.23.1 as released breaks our
system too. This way, we can either focus on differences
Farkas Levente wrote:
> Laurent Vivier wrote:
>> Farkas Levente a écrit :
>>> Farkas Levente wrote:
Avi Kivity wrote:
> kvm-47 had a host memory corruption bug when setting the guest pte
> dirty bit, so here's kvm-48 with a fix.
>
> Note that guest time accounting, below, will
Hollis Blanchard wrote:
> I must be misunderstanding, because this seems completely backwards to
> me. With your nesting, any time architecture code wants to access
> architecture state (which is almost all the time), you'd *need*
> container_of:
>
> void arch_func(struct kvm_vcpu *vcpu) {
2.6.31.1 should be 2.6.23.1 - sorry
> _
> Von: Back, Michael (ext)
> Gesendet: Friday, October 19, 2007 3:16 PM
> An: 'kvm-devel@lists.sourceforge.net'
> Betreff: KVM and Prempt?
>
>
> Hallo,
> I tried to run Windows XP with KVM on Lin
Certified MDs in the US
788,703 in total 17,607 emails
Coverage in many different areas of medicine such as Endocrinology, Pathology,
Urology, Neurology, Plastic Surgery, Psychiatry, Cardiology and much more
Can easily be sorted by 16 different fields
Lowered Price - $328
*** Recie
Ok, I will try it without rtl8139, and let you know the result.
Thanks
Yunfeng
>-Original Message-
>From: Izik Eidus [mailto:[EMAIL PROTECTED]
>Sent: 2007年10月19日 20:56
>To: Zhao, Yunfeng
>Cc: kvm-devel
>Subject: Re: [kvm-devel] Test for KVM , kernel bb1d1fe..., userspace 332650e...
>
>Zha
Zhao, Yunfeng wrote:
> Three Linux guest issues:
> 5. segfault while booting 64bit linux with 4GB mem
> https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1812050&gro
> up_id=180599
probably there is another bug there, beacuse the patch that was inserted
from kvm-47 fixed this issue to m
Mike Lampard wrote:
> There was a commit ab9c232286c2b77be78441c2d8396500b045777e regarding libata
> on linus's master tree that happened on Friday, that was pulled into kvm git
> over the weekend.. I dont know if that may be affecting you.. there is/was
> also chatter on LKML regarding some pro
On Fri, 19 Oct 2007 09:07:42 pm Carsten Otte wrote:
> Aurelien Jarno wrote:
> > Could you please precise what is corrupted? The guest disk image?
>
> As stated, we actually did not run any guests and did not load the kvm
> kernel modules.
> The host root file system gets corrupted to an extend not
Am Freitag, 19. Oktober 2007 schrieb Laurent Vivier:
> Carsten Otte a écrit :
> > Laurent Vivier wrote:
> >> How do you know the problem has been introduced by kvm ?
> > I don't. In fact I think it has not been introduced by kvm. All I
> > stated, is that we experienced the problem when running th
Carsten Otte a écrit :
> Laurent Vivier wrote:
>> How do you know the problem has been introduced by kvm ?
> I don't. In fact I think it has not been introduced by kvm. All I
> stated, is that we experienced the problem when running the kvm.git
> kernel after the 2.6.23 update that has not been p
Laurent Vivier wrote:
> How do you know the problem has been introduced by kvm ?
I don't. In fact I think it has not been introduced by kvm. All I
stated, is that we experienced the problem when running the kvm.git
kernel after the 2.6.23 update that has not been present in the
kvm.git -rc8 as o
Hi,
Here is the testing result for latest KVM commits, kernel
bb1d1fee77d97efba72dccec85d857378e3abea5, userspace,
332650e859f19aac2e941f1e31693a99e0484820.
One issue has been fixed:
1. 64bit guest with 2.6.16 kernel crashes when start up nic
https://sourceforge.net/tracker/index.php?func=detail&a
Hi list,
we've experienced a severe bug in current kvm.git, that may have been
introduced to the git tree quite recently around last weekend. 2.6.23
is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
kvm test machine shredders its hard disk content to a state that is
not corre
Aurelien Jarno wrote:
> Could you please precise what is corrupted? The guest disk image?
As stated, we actually did not run any guests and did not load the kvm
kernel modules.
The host root file system gets corrupted to an extend not correctable
by the file system checker (we gave it 24h to repa
Bugs item #1816417, was opened at 2007-10-19 10:33
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=1816417&group_id=180599
Please note that this message will contain a full copy
Farkas Levente a écrit :
> Farkas Levente wrote:
>> Avi Kivity wrote:
>>> kvm-47 had a host memory corruption bug when setting the guest pte dirty
>>> bit, so here's kvm-48 with a fix.
>>>
>>> Note that guest time accounting, below, will only work with Linux 2.6.24+.
>> smp guests still not workin
Farkas Levente wrote:
> Avi Kivity wrote:
>> kvm-47 had a host memory corruption bug when setting the guest pte dirty
>> bit, so here's kvm-48 with a fix.
>>
>> Note that guest time accounting, below, will only work with Linux 2.6.24+.
>
> smp guests still not working with kvm-48:-( i can't image
Bugs item #1816339, was opened at 2007-10-19 16:21
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=1816339&group_id=180599
Please note that this message will contain a full copy
On Thu, 2007-10-18 at 14:39 +0200, Christian Borntraeger wrote:
> Avi,
>
> ppc and s390 offer the possibility to track process times precisely
> by looking at cpu timer on every context switch, irq, softirq etc.
> We can use that infrastructure as well for guest time accounting.
> We need to accou
Carsten Otte wrote:
> First thing we do, is figure whether or not 2.6.23.1 as released breaks
> our system too. This way, we can either focus on differences between
> Linus and Avi, or turn on the big red warning sign saying "regression".
Looks like 2.6.23.1 works fine on that box. We'll leave it
Laurent Vivier wrote:
> Farkas Levente a écrit :
>> Farkas Levente wrote:
>>> Avi Kivity wrote:
kvm-47 had a host memory corruption bug when setting the guest pte
dirty bit, so here's kvm-48 with a fix.
Note that guest time accounting, below, will only work with Linux
2.6.2
Bugs item #1816460, was opened at 2007-10-19 19:36
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=1816460&group_id=180599
Please note that this message will contain a full copy
Carsten Otte a écrit :
> Hi list,
>
> we've experienced a severe bug in current kvm.git, that may have been
> introduced to the git tree quite recently around last weekend. 2.6.23
> is broken, 2.6.23-rc8 works for us. The symptom is, that our operon
> kvm test machine shredders its hard disk co
Hi,
Nice to meet you, all.
I recently got understanding kvm started,
and I found some worning at compiling kvm.
This patch is for cleanup of kvmctl.c.
I tested Booting Linux guest on x86_32.
Signed-off-by: Akio Takebe <[EMAIL PROTECTED]>
--- kvm-48.orig/user/kvmctl.c 2007-10-19 01:42:58.0
Hi Michael,
On Fri, 2007-10-19 at 15:32 +0200, Back, Michael (ext) wrote:
>
>
> 2.6.31.1 should be 2.6.23.1 - sorry
>
> _
> Von:Back, Michael (ext)
> Gesendet: Friday, October 19, 2007 3:16 PM
> An: 'kvm-devel@lists.sourceforge.net
Hallo,
I tried to run Windows XP with KVM on Linux 2.6.31.1 on a AMD Opteron and on a
Intel Xeon, on both it works fine!
After this test I patch the kernel with the current prempt-patch and on both it
doesn't works!
-> After a very short time - I could see the windows startup screen - the
comp
Carsten Otte wrote:
> 2.6.23 is broken, 2.6.23-rc8 works for us.
Actually, the working version was 2.6.23-rc6, git-head of kvm.git as
of October 11.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log
Carsten Otte a écrit :
> Aurelien Jarno wrote:
>> Could you please precise what is corrupted? The guest disk image?
> As stated, we actually did not run any guests and did not load the kvm
> kernel modules.
> The host root file system gets corrupted to an extend not correctable
> by the file syst
Hi,
Please CC me, I'm not a subscriber to the list.
Also, please note this could very well be a guest-os problem, but I've
never experienced anything like this before.
I have a Debian unstable 64bit host on an intel S3000 quad core xeon
X3210. Kernel 2.6.22-2-amd64 (debian flavour) KVM46.
My g
Joris wrote:
> I have a Debian unstable 64bit host on an intel S3000 quad core xeon
> X3210. Kernel 2.6.22-2-amd64 (debian flavour) KVM46.
> My guests are debian32 with 1 cpu and 1GB ram, connected via '-net
> nic,macaddr=52:54:00:00:00:xx -net tap' and linux bridging. I'm
> running 3 guests at the
49 matches
Mail list logo
