On 10.05.2011, at 08:06, David Gibson wrote:
The pSeries machine uses two tables to look up guest hcalls for emulation.
One of these is exactly one entry too small to hold all the hcalls it needs
to, leading to memory corruption.
This patch fixes the bug, and while we're at it, make both
The pSeries machine uses two tables to look up guest hcalls for emulation.
One of these is exactly one entry too small to hold all the hcalls it needs
to, leading to memory corruption.
This patch fixes the bug, and while we're at it, make both tables 'static'
since they're never used from other
Hi
On Tue, May 10, 2011 at 05:24, Adnan Khaleel ad...@khaleel.us wrote:
Can somebody give me some pointers on what the best way to debug the boot
process in Qemu and seabios?
At first, I guess -s a.k.a qemu gdb stub of Qemu could help
you...but uhm, on a second thought, I think it is the
Until recently, -net options used to add interfaces to linux in the same
order they went on the command line, so the first one you listed on the
qemu command line would become eth0, the second -net became eth1, and so
on. Now they're added in _reverse_ order, so the _last_ one on the
command line
From: BrillyWu brill...@viatech.com.cn
When KVM is running on VIA CPU with host cpu's model, the
feautures of VIA CPU will be passed into kvm guest by calling
the CPUID instruction for Centaur.
Signed-off-by: BrillyWubrill...@viatech.com.cn
Signed-off-by: KaryJinkary...@viatech.com.cn
---
Gerd Hoffmann kra...@redhat.com writes:
Hi,
+#define DEFINE_IDE_DEV_PROPERTIES() \
+DEFINE_PROP_UINT32(unit, IDEDrive, dev.unit, -1), \
+DEFINE_BLOCK_PROPERTIES(IDEDrive, dev.conf),\
+DEFINE_PROP_STRING(ver, IDEDrive, dev.version), \
+
hi jan,
Thank you for your help.I choose to use gmail sending emails,and have send a
new version of the patch,please check it. thank.
brilly
-Original Message-
From: jan.kis...@web.de [mailto:jan.kis...@web.de]
Sent: Monday, May 09, 2011 2:14 PM
To: Brilly Wu
Cc: a...@redhat.com;
Hi,
This is the usb storage fix cherry-picked into the stable branch.
please pull,
Gerd
The following changes since commit 56a60dd6d619877e9957ba06b92d2f276e3c229d:
Version 0.14.1 (2011-05-04 13:50:56 -0500)
are available in the git repository at:
git://git.kraxel.org/qemu
Initialize scsi_len with zero when starting a new request, so any
stuff leftover from the previous request is cleared out. This may
happen in case the data returned by the scsi command doesn't fit
into the buffer provided by the guest.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
(cherry
Am 09.05.2011 17:32, schrieb jes.soren...@redhat.com:
From: Jes Sorensen jes.soren...@redhat.com
Signed-off-by: Jes Sorensen jes.soren...@redhat.com
Thanks, applied to the block branch.
Kevin
Am 09.05.2011 17:48, schrieb Jan Kiszka:
If ahci_dma_set_inactive is called a while there is still a pending BH
from a previous run, we will crash on the second run of
ahci_check_cmd_bh as it overwrites AHCIDevice::check_bh. Avoid this
broken and redundant duplicate registration.
Am 09.05.2011 17:45, schrieb Stefan Hajnoczi:
This patch marks QED images as clean periodically when it is safe to do so.
This reduces the chance of having to perform a consistency check at startup.
Previously we left the image dirty even when it was consistent, therefore
risking an
Hi,
These patches fix and improve the physical port handling in the usb host
driver. Passthrough of devices connected via usb hub should work better
now. Also you can specify usb devices for passthrough by physical port
(on the host) now.
please review,
Gerd
Gerd Hoffmann (2):
The device path isn't just a number. It specifies the physical port
the device is connected to and in case the device is connected via
usb hub you'll have two numbers there, like this: 5.1. The first
specifies the root port where the hub is plugged into, the second
specifies the port number of
This patch adds a hostport property which allows to specify the host usb
devices to pass through by bus number and physical port. This means you
can basically hand over one (or more) of the usb plugs on your host to
the guest and whatever device is plugged in there will show up in the
guest.
On 05/10/2011 12:07 AM, Serge E. Hallyn wrote:
To get this to compile on top of qemu-kvm, I needed the following
patch to force CONFIG_THREAD on so as to define things like
qemu_mutex_lock:
Index: qemu-kvm-tpm/configure
===
---
Am 09.05.2011 11:51, schrieb Markus Armbruster:
This patch series is about purging the type hint from the block
layer. My previous series cleaned up improper uses it. Remaining
uses are info block and qdevs ide-drive, scsi-disk.
ide-drive and scsi-disk can either act as disk or as CD
I've volunteered for the task of fixing virt-clone[0]. There are a
number of bugs which need to be addressed. Unfortunately the current
virt-clone is broken-by-design since it cannot make changes inside the
guest.
[0] http://linux.die.net/man/1/virt-clone
The bugs boil down to what Microsoft
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
On 05/10/2011 12:07 AM, Serge E. Hallyn wrote:
To get this to compile on top of qemu-kvm, I needed the following
patch to force CONFIG_THREAD on so as to define things like
qemu_mutex_lock:
Index: qemu-kvm-tpm/configure
On 05/10/2011 07:59 AM, Serge E. Hallyn wrote:
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
On 05/10/2011 12:07 AM, Serge E. Hallyn wrote:
To get this to compile on top of qemu-kvm, I needed the following
patch to force CONFIG_THREAD on so as to define things like
qemu_mutex_lock:
On 05/10/11 - 12:56:30PM, Richard W.M. Jones wrote:
Sysprepping Windows
---
This is a complex, manual process. We do some steps to automate it in
RHEV. It's best to read Microsoft's online documentation at
[2][3][4].
[3] http://support.microsoft.com/kb/302577
[4]
On 10 May 2011 13:56, Richard W.M. Jones rjo...@redhat.com wrote:
So I'd like feedback from virt-clone next generation users:
(a) Is cloning guests useful for you or not? Often or infrequently?
I clone guests quite often.
(b) Do you currently use virt-clone to clone guests?
no
(c) Do
Alex,
the current s390x qemu memory layout is
0x100: guest start
0x8000: qemu binary
which limits the amount of available memory to 2GB.
This patch moves the guest pages to 32GB to not collide with the binary
and to leave some space for the program break of qemu.
Signed-off-by:
Alex,
the s390 memory detection has a 16bit field that specifies the amount of
increments. This patch adopts the memory size to always fit into that
scheme. This also fixes virtio detection for these guests, since the
descriptor page is located after the main memory.
Signed-off-by: Christian
(a) Is cloning guests useful for you or not? Often or infrequently?
I clone VMs once os twice a month. It's usefull for creating test
environments for the applications this company runs, and to safely backup a
VM before doing some change of update.
(b) Do you currently use virt-clone to
On 05/09/11 13:50, Juan Quintela wrote:
Please send in any agenda items you are interested in covering.
From last week, we have already:
- import kvm headers into qemu, drop #ifdef maze (Jan)
Thanks, Juan.
Since we haven't received any further agenda items. In addition Anthony
is
(a) Is cloning guests useful for you or not? Often or infrequently?
Our end-users are quite virtualization aware, they have demanded that we
support a number of features in our virtual infrastructure, this
included. It will be used frequently and often, maybe 100s of times a
day across our
On Mon, May 09, 2011 at 04:40:00PM +0300, Dor Laor wrote:
No patch here (sorry) but collection of thoughts about these
features and their potential building blocks. Please review (also on
http://wiki.qemu.org/Features/LiveBlockMigration)
Future qemu is expected to support these features
Quoting Stefan Berger (stef...@linux.vnet.ibm.com):
What is your plan regarding libtpms? Will you be making actual
releases at sf.net at some point?
I was going to wait for a review of all the patches here on the ml
and see the code checked in -- until that hasn't happened anything
could
On Tuesday 10 May 2011 12:30:41 Gerd Hoffmann wrote:
Hi,
These patches fix and improve the physical port handling in the usb host
driver. Passthrough of devices connected via usb hub should work better
now. Also you can specify usb devices for passthrough by physical port
(on the host)
Given a couple of questions I have gotten in response to my survey
responses... let me clarify, although I imply we do a significant volume
of V2V, which we do as well, the responses below are targeted and
applicable to cloning. Especially the need to re-personalize clones
beyond the OS scope to
Hi,
(a) Is cloning guests useful for you or not? Often or infrequently?
I'm almost never do that.
Usually I use qcow2 copy-on-write images for testing, so I can easily
rollback stuff by just zapping and re-creating the copy-on-write image.
When I need a fresh VM I install one. Have
I found one problem in the bios config that was preventing the BIOS from seeing
the MBR.
The AHCI support was not enabled. To fix this
change seabios/.config
CONFIG_AHCI=y
The system now loads the boot loader and does some device initialization.
However, the boot gets stuck when the OS
man qemu...
hostname=name Specifies the client hostname reported by the builtin
DHCP server.
I would like to add a technically similar option: search
It would be sent along the same path that the above hostname parameter takes.
This would allow the guest OS to reference other boxes on my LAN
We're currently very strict in requiring that DMA unmaps are done
using the exact same regions as used for the original mapping.
In a VM environment, we may want to change sub-areas of a previous
mapping without tearing down the entire region. This might also
also us to support ballooning or
Message: 3
Date: Sun, 08 May 2011 21:41:15 +0200
From: Llu?s xscr...@gmx.net
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Binary translation (of code)
Message-ID: 87ei49ugis@ginnungagap.bsc.es
Content-Type: text/plain; charset=utf-8
Tarmo Pikaro writes:
Hi !
I think
I meant what is the best way to debug the qemu and seabios interaction, I don't
necessarily want to inspect instructions but rather just the function calls and
trace the process so I can compare it for another case that isn't working.
AK
_
From: Mulyadi Santosa
On 05/10/2011 11:13 AM, Tarmo Pikaro wrote:
It would be much easier to ship an executable containing both the guest
application and qemu, so that executing it starts qemu with a
pre-defined configuration and runs the guest binary.
- Binary recompilation would allow faster execution than
Tarmo Pikaro writes:
It would be much easier to ship an executable containing both the guest
application and qemu, so that executing it starts qemu with a
pre-defined configuration and runs the guest binary.
- Binary recompilation would allow faster execution than emulated code
QEMU does
Hi,
TCG uses a fixed global register (AREG0) to which points to currently
used CPUState, also known as 'env'. Using a fixed register has the
downsides that the register must be reserved by TCG for generated code
and by the compiler for compiling a few critical files (op_helper.c
etc.). The latter
TCG uses a fixed global register (AREG0) to which points to currently
used CPUState, also known as 'env'. Using a fixed register has the
downsides that the register must be reserved by TCG for generated code
and by the compiler for compiling a few critical files (op_helper.c
etc.). The latter
Am 10.05.2011 22:54, schrieb Blue Swirl:
Hi,
TCG uses a fixed global register (AREG0) to which points to currently
used CPUState, also known as 'env'. Using a fixed register has the
downsides that the register must be reserved by TCG for generated code
and by the compiler for compiling a few
Since virtio devices intentionally access memory directly, we
are not actually dependant on the iommu patches in order to
make progress. Merely fixing the PCI interrupt setup was
enough to get the virtio-pci interface working.
There should be nothing special about virtio-pci. These devices
On 05/10/2011 01:54 PM, Blue Swirl wrote:
TCG the generator backend
-AREG0 is used for qemu_ld/st ops for TLB access. It should be
possible for the translators to pass instead a pointer to either
CPUState or directly to the TLB.
I believe that AREG0 should continue to be present in the
On 05/10/2011 02:33 PM, Paul Brook wrote:
There should be nothing special about virtio-pci. These devices should access
memory in exactly the same way as any other PCI device. Bypassing the normal
PCI iommu is IMO a serious bug.
I suspect that the argument is that virtio is implemented on
On 05/10/2011 02:33 PM, Paul Brook wrote:
There should be nothing special about virtio-pci. These devices should
access memory in exactly the same way as any other PCI device. Bypassing
the normal PCI iommu is IMO a serious bug.
I suspect that the argument is that virtio is implemented
While we're at it, let us change things a bit further to allow guest
byte-swap load/store insns to be implemented more efficiently. For
instance, currently a sparc load_asr (little-endian), as emulated on
an x86 host, does the byte swap twice.
FWIW this also ends up interacting with the
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Versatile/PB test build:
linux-2.6.38.5
buildroot-2010.11
alsa-lib-1.0.22
alsa-utils-1.0.22
mpg123-0.66
Qemu host: Ubuntu 10.04 in Vmware/OS
On Tue, 10 May 2011, Mathieu Sonet wrote:
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Versatile/PB test build:
linux-2.6.38.5
buildroot-2010.11
alsa-lib-1.0.22
On 05/10/2011 12:13 AM, Alexander Graf wrote:
On 10.05.2011, at 06:58, Rob Landley wrote:
On 05/09/2011 09:11 AM, Alexander Graf wrote:
C) requires more research, because I have to make sure the
entry point is either doing the 16-32 (or 64) bit startup
dance or that it's being launched in
50 matches
Mail list logo
