Re: [Qemu-devel] Guest moved used index from 0 to 1796

[Rick Vernam]

On Wednesday 15 September 2010 10:57:10 Gleb Natapov wrote:
> On Wed, Sep 15, 2010 at 10:50:15AM -0500, Rick Vernam wrote:
> > On Wednesday 15 September 2010 10:32:51 Gleb Natapov wrote:
> > > On Wed, Sep 15, 2010 at 10:30:38AM -0500, Rick Vernam wrote:
> > > > On Wednesday 15 September 2010 10:24:29 Gleb Natapov wrote:
> > > > > On Wed, Sep 15, 2010 at 10:16:29AM -0500, Rick Vernam wrote:
> > > > > > I don't have nearly enough info to file a proper bug report.
> > > > > > 
> > > > > > I am running qemu-kvm-0.13.0 rc1
> > > > > > starting qemu like so:
> > > > > > /root/qemu/bin/qemu-system-x86_64 -cpu host -enable-kvm -drive
> > > > > > file=/root/qemu/w2k3_server.raw,if=virtio,aio=native -net
> > > > > > nic,model=virtio,macaddr=52:54:00:12:34:56 -net tap,ifname=tap0
> > > > > > -localtime - usb -usbdevice tablet -vga std -vnc :25581 -monitor
> > > > > > stdio -m 512 -runas rick
> > > > > > 
> > > > > > When I reboot the guest OS, Qemu will quit during guest POST with
> > > > > > the
> > > > > 
> > > > > > following message:
> > > > > How do you reboot it? From inside the guest or by system_reset in
> > > > > monitor?
> > > > 
> > > > From inside the guest.
> > > 
> > > And if you do system_reset?
> > 
> > Same failure.
> > 
> > > > Also forgot to mention that this only happens when using -vnc
> > > 
> > > You mean with SDL it works? Doesn't make sense to me :(
> > 
> > I have not encountered any such error with SDL.
> > Note that where I run Qemu and encounter this error, SDL support is not
> > even enabled (headless server).
> 
> So how do you know it works with SDL? Also does the same happens with
> linux guest + virtio disk?
okay, linux guest started like so, this time on my laptop:
qemu-system-x86_64 -cpu host -enable-kvm -drive 
file=/home/rick/qemu/hds/linux.raw,if=virtio,media=disk,aio=native -m 1368 -net 
nic,model=virtio -net user -localtime -usb -name "32-bit Linux" -vnc :25581

Fails just like other, both during guest initiated and system_reset:
Guest moved used index from 0 to 147

If I run with -drive file=...,if=ide,... I do not experience the failure.

I typically run my linux guest with -vga vmware & -drive if=virtio, but 
without vnc...and I have never experienced this failure.

my laptop is
Linux 2.6.33.5 SMP x86_64 Intel(R) Core(TM) i7 CPU Q 820 @ 1.73GHz 
GenuineIntel GNU/Linux

qemu-kvm-0.13.0-rc1 on my laptop is configured like so:
./configure --prefix=/usr --target-list=x86_64-softmmu --extra-cflags="-
march=native -O2 -pipe" --extra-ldflags="-march=native -O2 -pipe" --audio-drv-
list=alsa --disable-curses --disable-curl --disable-vnc-tls --disable-vnc-sasl 
--enable-vnc-jpeg --enable-vnc-png --enable-vnc-thread
Install prefix    /usr
BIOS directory    /usr/share/qemu
binary directory  /usr/bin
config directory  /usr/etc
Manual directory  /usr/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path       /home/rick/qemu/src/qemu-kvm-0.13.0-rc1
C compiler        gcc
Host C compiler   gcc
CFLAGS            -O2 -g 
QEMU_CFLAGS       -m64 -fstack-protector-all -Wold-style-definition -Wold-
style-declaration -I. -I$(SRC_PATH) -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -
D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-
decls -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes -fno-
strict-aliasing -march=native -O2 -pipe 
LDFLAGS           -Wl,--warn-common -m64 -g -march=native -O2 -pipe 
make              make
install           install
host CPU          x86_64
host big endian   no
target list       x86_64-softmmu
tcg debug enabled no
Mon debug enabled no
gprof enabled     no
sparse enabled    no
strip binaries    yes
profiler          no
static build      no
-Werror enabled   no
SDL support       yes
curses support    no
curl support      no
check support     no
mingw32 support   no
Audio drivers     alsa
Extra audio cards ac97 es1370 sb16
Block whitelist   
Mixer emulation   no
VNC TLS support   no
VNC SASL support  no
VNC JPEG support  yes
VNC PNG support   yes
VNC thread        yes
xen support       no
CPU emulation     yes
brlapi support    no
bluez  support    yes
Documentation     yes
NPTL support      yes
GUEST_BASE        yes
PIE user targets  no
vde support       no
IO thread         no
Linux AIO support yes
ATTR/XATTR support yes
Install blobs     yes
KVM support       yes
KVM PIT support   yes
KVM device assig. yes
fdt support       no
preadv support    yes
fdatasync         yes
uuid support      yes
vhost-net support yes


> And can you reproduce the problem without virtio-net + your windows guest.
without virtio-net (ie, just -net nic) it continues to fail.
however, without virtio-scsi (ie, -drive file=...,if=ide,...) it does not fail.


So with both windows & linux guests, it fails only with -file ...,if=virtio,... 
and -vnc


Thanks Gleb,
-Rick
> 
> --
>                       Gleb.