Hidetoshi Seto | 1 Jul 2010 05:32
Favicon

[PATCH] Makefile: add qemu-options.def to distclean

Remove generated qemu-options.def at "make distclean".

Signed-off-by: Hidetoshi Seto <seto.hidetoshi <at> jp.fujitsu.com>
---
 Makefile |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/Makefile b/Makefile
index 221fbd8..560eac6 100644
--- a/Makefile
+++ b/Makefile
 <at>  <at>  -168,6 +168,7  <at>  <at>  clean:

 distclean: clean
 	rm -f config-host.mak config-host.h* config-host.ld $(DOCS) qemu-options.texi qemu-img-cmds.texi qemu-monitor.texi
+	rm -f qemu-options.def
 	rm -f config-all-devices.mak
 	rm -f roms/seabios/config.mak roms/vgabios/config.mak
 	rm -f qemu-{doc,tech}.{info,aux,cp,dvi,fn,info,ky,log,pdf,pg,toc,tp,vr}
--

-- 
1.7.0

Hidetoshi Seto | 1 Jul 2010 05:32
Favicon

[PATCH] Makefile: add fsdev/*.{o,d} to clean

There were fsdev/qemu-fsdev.{o,d} not removed at "make clean".

Signed-off-by: Hidetoshi Seto <seto.hidetoshi <at> jp.fujitsu.com>
---
 Makefile |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/Makefile b/Makefile
index 560eac6..ce5f0e6 100644
--- a/Makefile
+++ b/Makefile
 <at>  <at>  -159,7 +159,7  <at>  <at>  clean:
 # avoid old build problems by removing potentially incorrect old files
 	rm -f config.mak op-i386.h opc-i386.h gen-op-i386.h op-arm.h opc-arm.h gen-op-arm.h
 	rm -f *.o *.d *.a $(TOOLS) TAGS cscope.* *.pod *~ */*~
-	rm -f slirp/*.o slirp/*.d audio/*.o audio/*.d block/*.o block/*.d net/*.o net/*.d
+	rm -f {slirp,audio,block,net,fsdev}/*.{o,d}
 	rm -f qemu-img-cmds.h
 	$(MAKE) -C tests clean
 	for d in $(ALL_SUBDIRS) libhw32 libhw64 libuser libdis libdis-user; do \
--

-- 
1.7.0

Aneesh Kumar K. V | 1 Jul 2010 07:31
Picon
Gravatar

Re: [V9fs-developer] [PATCH] virtio-9p: getattr server implementation for 9P2000.L protocol.

On Fri, 28 May 2010 16:08:43 +0530, Sripathi Kodi <sripathik <at> in.ibm.com> wrote:
> From: M. Mohan Kumar <mohan <at> in.ibm.com>
> 
> SYNOPSIS
> 
>       size[4] Tgetattr tag[2] fid[4]
> 
>       size[4] Rgetattr tag[2] lstat[n]
> 
>    DESCRIPTION
> 
>       The getattr transaction inquires about the file identified by fid.
>       The reply will contain a machine-independent directory entry,
>       laid out as follows:
> 
>          qid.type[1]
>             the type of the file (directory, etc.), represented as a bit
>             vector corresponding to the high 8 bits of the file's mode
>             word.
> 
>          qid.vers[4]
>             version number for given path
> 
>          qid.path[8]
>             the file server's unique identification for the file
> 
>          st_mode[4]
>             Permission and flags
> 
>          st_nlink[8]
(Continue reading)

Jes Sorensen | 1 Jul 2010 08:13
Picon
Favicon

[Bug 595438] Re: KVM segmentation fault, using SCSI+writeback and linux 2.4 guest

Could you try and run this in GDB and get the backtrace when it crashes?
Just do:

gdb /usr/bin/kvm
(gdb) set args -M pc-0.12 -enable-kvm -m 256 -smp 1 -name spamsender -uuid
b9cacd5e-08f7-41fd-78c8-89cec59af881 -chardev
socket,id=monitor,path=/var/lib/libvirt/qemu/spamsender.monitor,server,nowait -monitor
chardev:monitor -boot d -drive
file=/mnt/megadiff/cdiso_400_130.iso,if=ide,media=cdrom,index=2 -drive
file=/home/mmarkk/spamsender2.img,if=scsi,index=0,format=qcow2,cache=writeback -net
nic,macaddr=00:00:00:00:00:00,vlan=0,name=nic.0 -net tap,vlan=0,name=tap.0 -chardev
pty,id=serial0 -serial chardev:serial0 -parallel none -usb -vnc 127.0.0.1:0 -vga cirrus
(gdb) run
<after crash>
(gdb) bt

Make sure to have all the debug packages installed, otherwise the
backtrace isn't really useful.

Unfortunately the core file you posted isn't of use to anyone who
doesn't have Ubuntu installed with the exact packages you have
installed. It just shows some random addresses in gdb.

Thanks,
Jes

--

-- 
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
https://bugs.launchpad.net/bugs/595438
You received this bug notification because you are a member of qemu-
(Continue reading)

Markus Armbruster | 1 Jul 2010 08:47
Picon
Favicon

Re: [PATCH 2/3] blkdebug: Free QemuOpts after having read the config

Kevin Wolf <kwolf <at> redhat.com> writes:

> Forgetting to free them means that the next instance inherits all rules and
> gets its own rules only additionally.

I also found a use for freeing a complete QemuOptsList, here's my
solution.  The code that needs it isn't ready, yet.  If you'd like to
use it, I can push it to my repo.

diff --git a/qemu-option.c b/qemu-option.c
index 7f70d0f..30327d4 100644
--- a/qemu-option.c
+++ b/qemu-option.c
 <at>  <at>  -719,6 +719,15  <at>  <at>  QemuOpts *qemu_opts_create(QemuOptsList *list, const char *id, int fail_if_exist
     return opts;
 }

+void qemu_opts_reset(QemuOptsList *list)
+{
+    QemuOpts *opts, *next_opts;
+
+    QTAILQ_FOREACH_SAFE(opts, &list->head, next, next_opts) {
+        qemu_opts_del(opts);
+    }
+}
+
 int qemu_opts_set(QemuOptsList *list, const char *id,
                   const char *name, const char *value)
 {
diff --git a/qemu-option.h b/qemu-option.h
(Continue reading)

Markus Armbruster | 1 Jul 2010 08:50
Picon
Favicon

Re: [PATCH 0/3] blkdebug: Fix config with multiple states

Kevin Wolf <kwolf <at> redhat.com> writes:

> Turns out that using more than one state doesn't really work well. I'm trying
> to reproduce a bug for which I need states, so now is the time to fix it.

I'm not familiar with blkdebug, but these look like obvious bug fixes.

Jan Kiszka | 1 Jul 2010 09:04
Picon

Re: [Bug 494500] Re: QEMU 0.12.0 does not support KVM with Kernel < 2.6.29, bug in ./configure and kvm-all.c

rowa wrote:
> Does the _lastest_ kvm-kmod's install the right headers for the used
> kernel, for example kernel 2.6.28-11?

It installs the headers required to build kvm support into the qemu that
allows full-featured kernel or kvm-kmod usage up to the version kvm-kmod
carries.

> 
> As I wrote in this bug I had problems with a  kernel 2.6.28-11 and the
> _latest_ version of kvm-kmod. It works only with the right (not the
> latest) version of kvm-kmod.

Once you properly installed the kernel headers that kvm-kmod delivers,
qemu should detect their presence during configure and succeed with this
step. Of course, you also have to install the kvm-kmod modules which
will disable those that come with 2.6.28 to actually run qemu in kvm
mode later on.

Jan

Jan Kiszka | 1 Jul 2010 09:13
Picon

Re: [Bug 599958] Re: Timedrift problems with Win7: hpet missing time drift fixups

Anthony Liguori wrote:
> -no-hpet works in every version of qemu/qemu-kvm that has included HPET
> support.  RHEL disables HPET support by default unlike qemu and qemu-
> kvm.
> 
> I've updated the bug priority and title to reflect what the issue is.
> 
> We only support edge triggered interrupts with HPET which seems to be
> what most OSes use anyway.

qemu.git now also supports level triggering.

>  We could potentially use the
> reset_irq_delivered/get_irq_delivered APIC functions to implement
> interrupt catch-up but I think it would be better to try to merge Jan's
> generic IRQ delivered API first.

Which one? I'm a bit tired of rebasing versions that will only be
rejected again. :)

> 
> ** Summary changed:
> 
> - Timedrift problems with Win7 + qemu-kvm
> + Timedrift problems with Win7: hpet missing time drift fixups
> 
> ** Changed in: qemu
>    Importance: Undecided => Wishlist
> 
> ** Changed in: qemu
(Continue reading)

Markus Armbruster | 1 Jul 2010 09:30
Picon
Favicon

[PATCH v3 03/13] blockdev: Remove drive_get_serial()

Unused since commit 6ced55a5.

Signed-off-by: Markus Armbruster <armbru <at> redhat.com>
---
 blockdev.c |   12 ------------
 blockdev.h |    1 -
 2 files changed, 0 insertions(+), 13 deletions(-)

diff --git a/blockdev.c b/blockdev.c
index 3b8c606..e0495e5 100644
--- a/blockdev.c
+++ b/blockdev.c
 <at>  <at>  -78,18 +78,6  <at>  <at>  int drive_get_max_bus(BlockInterfaceType type)
     return max_bus;
 }

-const char *drive_get_serial(BlockDriverState *bdrv)
-{
-    DriveInfo *dinfo;
-
-    QTAILQ_FOREACH(dinfo, &drives, next) {
-        if (dinfo->bdrv == bdrv)
-            return dinfo->serial;
-    }
-
-    return "\0";
-}
-
 static void bdrv_format_print(void *opaque, const char *name)
 {
(Continue reading)

Markus Armbruster | 1 Jul 2010 09:30
Picon
Favicon

[PATCH v3 01/13] scsi: scsi_bus_legacy_handle_cmdline() can fail, fix callers

None of its callers checks for failure.  scsi_hot_add() can crash
because of that:

(qemu) drive_add 4 if=scsi,format=host_device,file=/dev/sg1
scsi-generic: scsi generic interface too old
Segmentation fault (core dumped)

Fix all callers, not just scsi_hot_add().

Signed-off-by: Markus Armbruster <armbru <at> redhat.com>
---
 hw/esp.c         |    3 +--
 hw/lsi53c895a.c  |    2 +-
 hw/pci-hotplug.c |    3 +++
 hw/scsi-bus.c    |   11 +++++++----
 hw/scsi.h        |    2 +-
 hw/usb-msd.c     |    3 +++
 6 files changed, 16 insertions(+), 8 deletions(-)

diff --git a/hw/esp.c b/hw/esp.c
index 7740879..349052a 100644
--- a/hw/esp.c
+++ b/hw/esp.c
 <at>  <at>  -679,8 +679,7  <at>  <at>  static int esp_init1(SysBusDevice *dev)
     qdev_init_gpio_in(&dev->qdev, parent_esp_reset, 1);

     scsi_bus_new(&s->bus, &dev->qdev, 0, ESP_MAX_DEVS, esp_command_complete);
-    scsi_bus_legacy_handle_cmdline(&s->bus);
-    return 0;
+    return scsi_bus_legacy_handle_cmdline(&s->bus);
(Continue reading)


Gmane