On Tue, Aug 09, 2011 at 12:17:50PM +0800, Zhi Yong Wu wrote:
The patch introduce one block queue for QEMU block layer.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
block/blk-queue.c | 141
+
block/blk-queue.h | 73
On Tue, Aug 09, 2011 at 12:17:51PM +0800, Zhi Yong Wu wrote:
Note:
1.) When bps/iops limits are specified to a small value such as 511
bytes/s, this VM will hang up. We are considering how to handle this senario.
2.) When dd command is issued in guest, if its option bs is set to a
On Thu, 2009-10-01 at 19:16 -0300, Marcelo Tosatti wrote:
It is possible that stale EPTP-tagged mappings are used, if a
vcpu migrates to a different pcpu.
Set KVM_REQ_TLB_FLUSH in vmx_vcpu_load, when switching pcpus, which
will invalidate both VPID and EPT mappings on the next vm-entry.
On Tue, 2009-07-21 at 14:42 +0200, Kevin Wolf wrote:
Ram Pai schrieb:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
This patch allows user
-by: Ram Pai linux...@us.ibm.com
block.c | 38 -
block/raw-posix.c | 34 +++
block/raw-win32.c | 26 --
block/vvfat.c | 97 +++-
cutils.c | 26 ++
qemu-common.h
.
Request help with testing)
Changelog w.r.t to iteration 6:
1) fixed all the issues found with win32.
a) changed the call to strnlen() to qemu_strlen() in cutils.c
b) fixed the call to CreateFile() in qemu_CreateFile()
Signed-off-by: Ram Pai linux...@us.ibm.com
On Wed, 2009-07-15 at 18:04 +0300, Blue Swirl wrote:
On 7/15/09, Ram Pai linux...@us.ibm.com wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi
.
Request help with testing)
Signed-off-by: Ram Pai linux...@us.ibm.com
block.c | 39
block/raw-posix.c | 15
block/raw-win32.c | 26 --
block/vvfat.c | 97 -
cutils.c
to upstream qemu and qemu-kvm tree
Signed-off-by: Ram Pai linux...@us.ibm.com
block.c | 30 +++-
block/raw-posix.c | 35 ++
block/raw-win32.c | 26 --
block/vvfat.c | 97
On Wed, 2009-07-15 at 11:30 +0200, Jan Kiszka wrote:
Ram Pai wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example filename scsi:0, is
interpreted as a protocol by name scsi.
This patch allows user
On Wed, 2009-07-15 at 19:20 +0100, Jamie Lokier wrote:
Ram Pai wrote:
I have verified with relative paths and it works.
After analyzing the code, i came to the conclusion that call to
realpath() adds no real value.
The logic in bdrv_open2() is something like this
bdrv_open2
On Wed, 2009-07-15 at 22:04 +0100, Jamie Lokier wrote:
Ram Pai wrote:
I have successfully verified qcow2 files. But then I may not be trying
out the exact thing that you are talking about. Can you give me a test
case that I can verify.
Commands tried with qemu-0.10.0-1ubuntu1
. Will port the patch to qemu tree
after successful test results.
Signed-off-by: Ram Pai linux...@us.ibm.com
block.c | 30 +++--
block/raw-posix.c | 35 +++
block/raw-win32.c | 26 --
block/vvfat.c | 97
it. _open() is back.
Signed-off-by: Ram Pai linux...@us.ibm.com
block.c | 10 +
block/raw-posix.c | 15
block/vvfat.c | 100 ++--
cutils.c | 40 +
qemu-common.h |2 +
5 files
changes are needed to handle commas in a filename. As
always a comma has to be escaped by a preceding comma.
Signed-off-by: Ram Pai linux...@us.ibm.com
---
block.c | 16 ++--
block/raw-posix.c | 30
to iteration 1:
1) generically handles 'file:' protocol in find_protocol
2) centralizes 'filename' pruning before the call to open().
3) fixes buffer overflow seen in fill_token()
4) adheres to codying style
5) patch against upstream qemu tree
Signed-off-by: Ram Pai linux...@us.ibm.com
On Thu, 2009-06-25 at 11:14 +0200, Kevin Wolf wrote:
Ram Pai schrieb:
Copying the qemu-devel mailing list too.
On Wed, 2009-06-24 at 09:58 -0700, Ram Pai wrote:
Problem: It is impossible to feed filenames with the character colon
because
qemu interprets such names as a protocol
be expressed as 'scsi\:0'
Here are couple of examples:
ndb:\:: is treated as a ndb protocol with a hostname ':' on port
scsi\:0\:abc is a local file scsi:0:abc
http\://myweb is a local file by name http://myweb
nbd\::localhost:2558 is a protocol by name nbd:
Signed-off-by: Ram Pai linux
On Wed, 2009-06-24 at 22:38 +0530, Balbir Singh wrote:
* Ram Pai linux...@us.ibm.com [2009-06-24 09:58:59]:
Problem: It is impossible to feed filenames with the character colon
because
qemu interprets such names as a protocol. For example a filename scsi:0,
is interpreted
Copying the qemu-devel mailing list too.
On Wed, 2009-06-24 at 09:58 -0700, Ram Pai wrote:
Problem: It is impossible to feed filenames with the character colon because
qemu interprets such names as a protocol. For example a filename scsi:0,
is interpreted as a protocol by name scsi
On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
I see this problem with a x86 sles10 guest running on x86_64 intel host.
If the guest is reset abruptly and rebooted, some where
before grub sequence it hangs and the following message
On Mon, 2009-06-22 at 11:26 +0300, Avi Kivity wrote:
On 06/22/2009 09:55 AM, Ram Pai wrote:
On Mon, 2009-06-22 at 13:12 +0800, Sheng Yang wrote:
On Saturday 20 June 2009 03:23:40 Ram Pai wrote:
I see this problem with a x86 sles10 guest running on x86_64 intel host
I see this problem with a x86 sles10 guest running on x86_64 intel host.
If the guest is reset abruptly and rebooted, some where
before grub sequence it hangs and the following message is seen in the
logs
emulation failed (pagetable) rip 7ed5 66 60 ac 20.
I located this instruction sequence in
23 matches
Mail list logo
