Kamble, Nitin A wrote:
> Hi Avi,
>I am in the middle of implementing the big real support in the KVM
> now. I am trying to boot SuseLinux 10.1 on KVM, which uses extensive big
> real mode code in the boot loader.
Ye gods, what boot loader is that?
-hpa
---
On Thu, 2007-06-07 at 15:19 +0300, Avi Kivity wrote:
> Rusty Russell wrote:
> > + sprintf(vblk->disk->disk_name, "vb%c", virtblk_index++);
> >
>
> vd%c, in keeping with hd%c and sd%c?
Should work, since iSeries' devices are /dev/iseries/vd%c. Is there
already a magic routine to take the bas
On Thu, Jun 07, 2007 at 11:25:07AM +0300, Avi Kivity wrote:
> Jon wrote:
> >Hi Avi,
> >
> >On Thu, Jun 07, 2007 at 08:15:29AM +0300, Avi Kivity wrote:
> >
> >>This was fixed in kvm.git, use the attached patch (cd kernel/, and apply
> >>with patch -p3).
> >>
> >
> >Applied, but no go. Managed
Hi Avi,
Please find a patch implementing the "ret" instruction in the
x86_emulation.
Thanks & Regards,
Nitin
Open Source Technology Center, Intel Corporation.
-
The mind is like a parachute; it works much better wh
Hi Avi,
I am in the middle of implementing the big real support in the KVM
now. I am trying to boot SuseLinux 10.1 on KVM, which uses extensive big
real mode code in the boot loader. If you have any other targeted guests
using big real mode do let me know.
I have been working on my own priva
Hi,
gcc-3.3.6
glibc-2.3.6
i686-pld-linux-gcc -I /home/areq/rpm/BUILD/kvm-27/qemu/../user -Wall
-O2 -g -fno-strict-aliasing -I
/home/areq/rpm/BUILD/kvm-27/kernel/include -fomit-frame-pointer -I.
-I.. -I/home/areq/rpm/BUILD/kvm-27/qemu/target-i386
-I/home/areq/rpm/BUILD/kvm-27/qemu -D_GNU_SOURCE
-D
On 6/5/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
> Luca Tettamanti wrote:
> > Il Mon, Jun 04, 2007 at 11:51:10PM +0300, Avi Kivity ha scritto:
> >
> >>> While doing repeated tests with the installer I ran into another
> >>> (unrelated) problem. Sometimes the guest kernel hangs at boot at:
> >>>
> >
Hello!
So here it is, im getting a kernel error when I try to go to a 1024:768
resolution or higher on my XP guest OS.
I have kvm-27
my kernel is a vanilla 2.6.21.3
im running debian sid
My cpu is a Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
So here is the nasty log from the kernel
Jun
On Thu, Jun 07, 2007 at 05:51:33PM +0300, Avi Kivity wrote:
> Joerg Roedel wrote:
> >
> >These error pointers could be read from the host userspace which has
> >normally no access to the guest FPU state. So I think they should also
> >be cleared at guest exit.
> >
> >
>
> Host userspace has acce
Bugs item #1732946, was opened at 2007-06-07 19:17
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=1732946&group_id=180599
Please note that this message will contain a full copy
Joerg Roedel wrote:
> On Thu, Jun 07, 2007 at 05:08:48PM +0300, Avi Kivity wrote:
>
>> Joerg Roedel wrote:
>>
>>> From: Joerg Roedel <[EMAIL PROTECTED]>
>>>
>>> On AMD K8 processors the fxsave/fxrstor instructions do not save and
>>> restore the x87 error pointers FIP/FOP and FDP except the
On Thu, Jun 07, 2007 at 05:08:48PM +0300, Avi Kivity wrote:
> Joerg Roedel wrote:
> >From: Joerg Roedel <[EMAIL PROTECTED]>
> >
> >On AMD K8 processors the fxsave/fxrstor instructions do not save and
> >restore the x87 error pointers FIP/FOP and FDP except the ES bit in the
> >status word is set. T
Joerg Roedel wrote:
> From: Joerg Roedel <[EMAIL PROTECTED]>
>
> On AMD K8 processors the fxsave/fxrstor instructions do not save and
> restore the x87 error pointers FIP/FOP and FDP except the ES bit in the
> status word is set. This could lead to information leakage from host to
> guest and vice
From: Joerg Roedel <[EMAIL PROTECTED]>
On AMD K8 processors the fxsave/fxrstor instructions do not save and
restore the x87 error pointers FIP/FOP and FDP except the ES bit in the
status word is set. This could lead to information leakage from host to
guest and vice versa. This patch fixes this by
Rusty Russell wrote:
> + sprintf(vblk->disk->disk_name, "vb%c", virtblk_index++);
>
vd%c, in keeping with hd%c and sd%c?
--
error compiling committee.c: too many arguments to function
-
This SF.net email is sponsore
Shahar Frank wrote:
> Milas,
>
> What host are you using, and what Vista version is it? Is it an OEM
> version or other non standard version?
>
> Vista is known to use some new ACPI features, and in fact some licensing
> options require ACPI 2.0 (not supported).
>
> Shahar
>
>
Using linux 2.6
TODO:
1) NAPI (will require way of suppressing virtio callbacks)
2) GSO.
3) Checksum options.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
---
drivers/net/Makefile |2
drivers/net/virtio_net.c | 243
include/li
The block driver uses outbufs with sg[0] being the request information
(struct virtio_blk_outhdr) with the type, sector and inbuf id. For a
write, the rest of the sg will contain the data to be written.
The first segment of the inbuf is a result code (struct
virtio_blk_inhdr). For a read, the re
>QEMU developers:
>
>I have been using QEMU off and on for some time. Recently I had a need
>for a Windows XP VM to be joined to a domain. I discovered a rather
>annoying issue in the form of the key-grab: NT-based Microsoft
>operating systems make heavy use of Ctrl-Alt-Delete, i.e. to sign on,
>
This attempts to implement a "virtual I/O" layer which should allow
common drivers to be efficiently used across most virtual I/O
mechanisms. It will no-doubt need further enhancement.
The details of probing the device are left to hypervisor-specific
code: it simple constructs the "struct virtio_
Hi again all,
It turns out that networking really wants ordered requests, which the
previous patches didn't allow. This patch changes it to a callback
mechanism; kudos to Avi.
The downside is that locking is more complicated, and after a few dead
ends I implemented the simplest s
Milas,
What host are you using, and what Vista version is it? Is it an OEM
version or other non standard version?
Vista is known to use some new ACPI features, and in fact some licensing
options require ACPI 2.0 (not supported).
Shahar
On Wed, 2007-06-06 at 09:18 +0800, Shaohua Li wrote:
> On Tue, 2007-06-05 at 22:17 +0800, Avi Kivity wrote:
> > Shaohua Li wrote:
> > > Hi,
> > > This is a updated patch set of swap out kvm guest pages.Changes are:
> > > 1. refresh against to kvm-26
> > > 2. clean up shadow page handling to make gf
Jon wrote:
> Hi Avi,
>
> On Thu, Jun 07, 2007 at 08:15:29AM +0300, Avi Kivity wrote:
>
>> This was fixed in kvm.git, use the attached patch (cd kernel/, and apply
>> with patch -p3).
>>
>
> Applied, but no go. Managed to save this before things started dying:
>
> BUG: unable to handle kerne
[EMAIL PROTECTED] wrote:
> Incorporates v8 plus the following changes:
>
> 1) Fix for hang on AMD
> 2) Fixes issue where irq-windows are inaccurately reported to
> userspace 3) Fixed issue where irq-window-exiting requests can be
> ignored in some cases
>
> Note that we no longer need the backlog
QEMU developers:
I have been using QEMU off and on for some time. Recently I had a need
for a Windows XP VM to be joined to a domain. I discovered a rather
annoying issue in the form of the key-grab: NT-based Microsoft
operating systems make heavy use of Ctrl-Alt-Delete, i.e. to sign on,
open th
26 matches
Mail list logo
