On Mon, Mar 18, 2013 at 7:10 PM, Stefan Hajnoczi wrote:
[...]
> read/write/flush should be either .bdrv_co_* or .bdrv_aio_*.
>
> The current code pauses the guest while I/O is in progress! Try running
> disk I/O benchmarks inside the guest and you'll see that performance and
> interactivity are p
On Wed, Mar 20, 2013 at 6:04 PM, Stefan Hajnoczi wrote:
> On Wed, Mar 20, 2013 at 04:43:17PM +0800, harryxiyou wrote:
>> On Mon, Mar 18, 2013 at 11:16 PM, Stefan Hajnoczi wrote:
>> [...]
>> > I looked at the Google Code project before, it looks like a repo that
>>
On Mon, Mar 18, 2013 at 11:16 PM, Stefan Hajnoczi wrote:
[...]
> I looked at the Google Code project before, it looks like a repo that
> a few people are hacking on. The site is developer-focussed and there
> is no evidence of users. This is why I asked about the background of
> the community.
>
On Mon, Mar 18, 2013 at 7:10 PM, Stefan Hajnoczi wrote:
Hi Stefan,
> Is HLFS making releases that distros can package? I don't see packages
> in Debian or Fedora.
We will make packages for Debian and Fedora.
>
> Block drivers in qemu.git should have active and sustainable communities
> behind
From: Harry Wei
HLFS is HDFS-based(Hadoop Distributed File System) Log-Structured File
System. Actually, HLFS, currently, is not a FS but a block-storage system,
which we simplify LFS to fit block-level storage. So you could also call HLFS
as HLBS (HDFS-based Log-Structured Block-storage System).
From: Harry Wei
HLFS is HDFS-based(Hadoop Distributed File System) Log-Structured File
System. Actually, HLFS, currently, is not a FS but a block-storage system,
which we simplify LFS to fit block-level storage. So you could also call HLFS
as HLBS (HDFS-based Log-Structured Block-storage System).
From: Harry Wei
HLFS is HDFS-based(Hadoop Distributed File System) Log-Structured File
System. Actually, HLFS, currently, is not a FS but a block-storage system,
which we simplify LFS to fit block-level storage. So you could also call HLFS
as HLBS (HDFS-based Log-Structured Block-storage System).
On Tue, Mar 12, 2013 at 11:16 PM, Stefan Hajnoczi wrote:
> On Tue, Mar 12, 2013 at 09:47:57PM +0800, harryxiyou wrote:
>> Could anyone give me some suggestions to submit HLFS driver patches for
>> QEMU to our QEMU community. Thanks a lot in advance ;-)
>
> http://wik
On Thu, Feb 14, 2013 at 11:15 PM, Stefan Hajnoczi wrote:
[...]
> Hi Harry,
Hi Stefan,
> Thanks for your interest. You can begin thinking about ideas but
> please keep in mind that we are still in the very early stages of GSoC
> preparation.
>
> Google will publish the list of accepted organizati
On Tue, Feb 12, 2013 at 5:21 AM, Stefan Hajnoczi wrote:
> On Thu, Feb 7, 2013 at 4:19 PM, Stefan Hajnoczi wrote:
>> I believe Google will announce GSoC again this year (there is
>> no guarantee though) and I have created the wiki page so we can begin
>> organizing project ideas that students can
On Fri, Feb 8, 2013 at 12:11 AM, Peter Maydell wrote:
> On 7 February 2013 16:08, Stefan Hajnoczi wrote:
>> On Thu, Feb 7, 2013 at 3:12 PM, harryxiyou wrote:
>>> The above debug info show jni will be used in coroutine. I do not
>>> familay with coroutine, however I g
HI all :
I write a new block driver based on hdfs of hadoop, it need to
connect to hdfs when create step (called by bdrv_create in block.c) by
use libhdfs ( hdfs c++ api) 。
libhdfs use jni api to will create jvm . The problem is —— it
will cause sigsegv error when create jvm .
#0 0x000
On Sat, Feb 2, 2013 at 5:02 AM, Brian Jackson wrote:
[...]
> It probably gets stripped during the install process. Check 'file'
> output on both and see.
This is a stupid mistake, which the latter one is *NOT* installed by
the first one. Jackson, thanks for your suggestions ;-)
--
Thanks
Harry
Hi all,
I did following operations to install QEMU to my PC.
1. git clone git://git.qemu.org/qemu.git
2. cd qemu
3, git reset --hard v1.3.0
4, ./configure
5, make
6, sudo make install
After step 6, i did following jobs.
a: see size of qemu-img bin in qemu package
jiawei@jiawei-laptop:~/workshop
On Tue, Jan 29, 2013 at 8:55 PM, harryxiyou wrote:
> On Tue, Jan 29, 2013 at 12:05 AM, MORITA Kazutaka
> wrote:
>> At Mon, 28 Jan 2013 23:43:04 +0800,
>> harryxiyou wrote:
>>>
>>> Following test is Libvirt v0.8.6, which you just add Sheepdog volume
>>>
On Tue, Jan 29, 2013 at 12:05 AM, MORITA Kazutaka
wrote:
> At Mon, 28 Jan 2013 23:43:04 +0800,
> harryxiyou wrote:
>>
>> Following test is Libvirt v0.8.6, which you just add Sheepdog volume
>> patch to Libvirt.
>
> The version doesn't support Sheepdog storage p
On Mon, Jan 28, 2013 at 11:23 PM, harryxiyou wrote:
> On Mon, Jan 28, 2013 at 11:06 PM, harryxiyou wrote:
>> On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
>> wrote:
>> [...]
>>> I'm not familiar with HLFS at all. Sheepdog examples I explained to
>>
On Mon, Jan 28, 2013 at 11:06 PM, harryxiyou wrote:
> On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
> wrote:
> [...]
>> I'm not familiar with HLFS at all. Sheepdog examples I explained to
>> you in another mail may help you, but I cannot give you any other
On Mon, Jan 28, 2013 at 10:44 PM, MORITA Kazutaka
wrote:
[...]
> I'm not familiar with HLFS at all. Sheepdog examples I explained to
> you in another mail may help you, but I cannot give you any other
> suggestions about HLFS.
>
Thanks for your reminder, i have found this email.
Therefore, could
Hi Daniel and other developers,
We have programed a HLFS(HDFS based Log-Structured FileSystem)
driver for QEMU, which you can see it here.
http://cloudxy.googlecode.com/svn/trunk/hlfs/patches/hlfs_driver_for_qemu_1.3.0.patch
And i have tested in QEMU environment, which works well for us.
Now, we
On Sat, Jan 19, 2013 at 10:04 PM, MORITA Kazutaka
wrote:
[...]
> If you do the above work, I think you can use your file system with
> OpenStack.
>
> But I suggest doing them step by step. If your file system is not
> supported in QEMU, I think libvirt won't support it. If libvirt
> doesn't supp
Hi all,
We wanna add a block storage driver named HLFS to QEMU, which
now have to configure qemu/configure file to add following stuffs.
[...]
2828 ##
2829 # hlfs probe
2830 echo "Entering HLFS probe...";
2831 sleep 2;
2832 if test "$hlfs" != "no" ; then
28
On Wed, Jan 23, 2013 at 2:12 AM, Brendan Dolan-Gavitt
wrote:
> These are runtime options to QEMU. For example: "qemu-system-x86_64 -D
> ~/qemu_debug.log -d in_asm".
Ok, i will have a try. Thanks very much.
>
> Or are you trying to add *new* debugging statements to QEMU? If so,
> look at the funct
On Wed, Jan 23, 2013 at 12:58 AM, Brendan Dolan-Gavitt
wrote:
> Assuming you're using one of the -d options to qemu, they will by
> default go into /tmp/qemu.log.
How to add -d options to qemu.(Configure qemu/configure or Makefile?)
> You can also specify where to put the debug log using the -D
Hi all,
When i debug our block driver in QEMU source codes, i cannot
find the debug logs for QEMU. I have searched /var/log/messages
and /var/log/dmesg but i cannot find debug logs.
Could anyone tell me how to find debug logs? Thanks in advance ;-)
--
Thanks
Harry Wei
On Tue, Jan 22, 2013 at 4:43 PM, harryxiyou wrote:
> Hi all,
>
> We add new entries for qemu/configure(QEMU v1.3.0), which
> can locate our libraries and header files to compile our driver
> for QEMU. The new entries in qemu/configure are like following.
&
On Tue, Jan 22, 2013 at 6:14 PM, Stefan Hajnoczi wrote:
[...]
> The fix is now in qemu.git/master.
Ok, thanks for your job.
--
Thanks
Harry Wei
Hi all,
We add new entries for qemu/configure(QEMU v1.3.0), which
can locate our libraries and header files to compile our driver
for QEMU. The new entries in qemu/configure are like following.
[...]
2828 ##
2829 # hlfs probe
2830 echo "Entering HLFS probe.
On Tue, Jan 22, 2013 at 1:14 AM, harryxiyou wrote:
> On Tue, Jan 22, 2013 at 12:49 AM, Stefan Hajnoczi wrote:
> [...]
>> qemu-devel is not the appropriate place to ask for help with hlfs. The
>> hlfs patch is not part of qemu.git. Try emailing Kang Hua and Wang Sen
>
On Tue, Jan 22, 2013 at 12:49 AM, Stefan Hajnoczi wrote:
[...]
> qemu-devel is not the appropriate place to ask for help with hlfs. The
> hlfs patch is not part of qemu.git. Try emailing Kang Hua and Wang Sen
> directly.
Hmmm..., you are right.
>
> The error message indicates that you are apply
On Mon, Jan 21, 2013 at 5:07 PM, Andreas Färber wrote:
> Hi,
Hi Andreas,
>
> There's a patch queued on qemu-trivial:
> http://patchwork.ozlabs.org/patch/213610/
>
> Would be nice to get this applied soon, it looks annoying but is not to
> worry about.
>
I see, thanks for your help ;-)
--
Thank
Hi all,
We programmed a block storage(HLFS) patch for QEMU. Therefore,
when i patched this driver for QEMU, it happened to me some errors.
Could anyone give me some suggestions, thanks in advance ;-)
You can see this issue i described in details from
http://code.google.com/p/cloudxy/issues/detail
On Sat, Jan 19, 2013 at 10:04 PM, MORITA Kazutaka
wrote:
> At Sat, 19 Jan 2013 16:47:37 +0800,
[...]
> If you do the above work, I think you can use your file system with
> OpenStack.
>
Thanks for your review ;-)
> But I suggest doing them step by step. If your file system is not
> supported in
Hi all,
I wanna add a new block storage driver by Libvirt/Qemu way for Openstack, which
is as same as Sheepdog driver for Openstack. So i think the theories
are like this.
1, In the Openstack Nova branch, Openstck driver call libvirt client
and send parameters
to libvirt client.(From this point,
34 matches
Mail list logo
