On Tue, Mar 19, 2019 at 09:51:19AM +0530, Sarah Abraham wrote:
> Hey all!
> I am Sarah Abraham and I'm an Outreachy applicant for May '19-Aug '19
> round.I'm really interested to work on the project "Improve GNOME boxes
> express-installations by adding support to tree-based installations" .
>
On 10/01/19 21:58, Eduardo Habkost wrote:
> On Mon, Dec 10, 2018 at 05:09:42PM -0200, Eduardo Habkost wrote:
>> On Mon, Dec 10, 2018 at 03:34:27PM -0200, Eduardo Habkost wrote:
>>> On Mon, Dec 10, 2018 at 12:07:20PM -0500, Emilio G. Cota wrote:
On Mon, Dec 10, 2018 at 14:36:01 -0200, Eduardo H
On Mon, Dec 10, 2018 at 05:09:42PM -0200, Eduardo Habkost wrote:
> On Mon, Dec 10, 2018 at 03:34:27PM -0200, Eduardo Habkost wrote:
> > On Mon, Dec 10, 2018 at 12:07:20PM -0500, Emilio G. Cota wrote:
> > > On Mon, Dec 10, 2018 at 14:36:01 -0200, Eduardo Habkost wrote:
> > > > On Sun, Dec 09, 2018 a
On Mon, Dec 10, 2018 at 15:47:15 -0200, Eduardo Habkost wrote:
> On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> > On Fri, Dec 07, 2018 at 18:41:07 -0200, Eduardo Habkost wrote:
> > > I've noticed QEMU Travis builds are failing recently, and they
> > > seem to happen only on the -
On Mon, Dec 10, 2018 at 03:34:27PM -0200, Eduardo Habkost wrote:
> On Mon, Dec 10, 2018 at 12:07:20PM -0500, Emilio G. Cota wrote:
> > On Mon, Dec 10, 2018 at 14:36:01 -0200, Eduardo Habkost wrote:
> > > On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> > > > Can you try re-running
On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> On Fri, Dec 07, 2018 at 18:41:07 -0200, Eduardo Habkost wrote:
> > I've noticed QEMU Travis builds are failing recently, and they
> > seem to happen only on the --enable-gprof jobs. I have enabled
> > V=1 and noticed that the jobs a
On Mon, Dec 10, 2018 at 12:07:20PM -0500, Emilio G. Cota wrote:
> On Mon, Dec 10, 2018 at 14:36:01 -0200, Eduardo Habkost wrote:
> > On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> > > Can you try re-running the test, after applying the appended patch?
> > > (It disables the "resi
On Mon, Dec 10, 2018 at 14:36:01 -0200, Eduardo Habkost wrote:
> On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> > Can you try re-running the test, after applying the appended patch?
> > (It disables the "resize" thread.)
>
> It is running right now, here:
> https://travis-ci.org
On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> On Fri, Dec 07, 2018 at 18:41:07 -0200, Eduardo Habkost wrote:
> > I've noticed QEMU Travis builds are failing recently, and they
> > seem to happen only on the --enable-gprof jobs. I have enabled
> > V=1 and noticed that the jobs a
On Fri, Dec 07, 2018 at 18:41:07 -0200, Eduardo Habkost wrote:
> I've noticed QEMU Travis builds are failing recently, and they
> seem to happen only on the --enable-gprof jobs. I have enabled
> V=1 and noticed that the jobs are hanging inside test-qht-par.
>
> Example here (look for "/qht/parall
> On Sep 17, 2018, at 2:51 PM, Peter Maydell wrote:
>
> On 17 September 2018 at 18:56, Programmingkid
> wrote:
>>
>>> On Sep 17, 2018, at 1:52 PM, Peter Maydell wrote:
>>>
>>> On 17 September 2018 at 18:48, Programmingkid
>>> wrote:
What I hope to do is implement a PowerPC CPU flag
On 17 September 2018 at 18:56, Programmingkid wrote:
>
>> On Sep 17, 2018, at 1:52 PM, Peter Maydell wrote:
>>
>> On 17 September 2018 at 18:48, Programmingkid
>> wrote:
>>> What I hope to do is implement a PowerPC CPU flag that indicates if an
>>> rounded result is inexact.
>>
>> How is this
On 17 September 2018 at 18:48, Programmingkid wrote:
> What I hope to do is implement a PowerPC CPU flag that indicates if an
> rounded result is inexact.
How is this different from the float_flag_inexact flag that softfloat already
supports ?
thanks
-- PMM
> On Sep 17, 2018, at 1:52 PM, Peter Maydell wrote:
>
> On 17 September 2018 at 18:48, Programmingkid
> wrote:
>> What I hope to do is implement a PowerPC CPU flag that indicates if an
>> rounded result is inexact.
>
> How is this different from the float_flag_inexact flag that softfloat al
On Sat, Mar 17, 2018 at 8:37 PM, Projat Banerjee
wrote:
> What is the type of proposal should I submit here ? What kind or on what
> basis should I build my proposal so that I may get easily selected or chances
> for my selection is high ?
Are you referring to Google Summer of Code? Outreachy?
On Tue, Jan 16, 2018 at 02:47:41PM +0530, sagart wrote:
> Hello,
> I am trying to configure qemu with ptnet. But it seems like, now there is
> no 'ptnet' branch to checkout,
> so I am unable to configure using '--enable-ptnetmap' option.
> please help in this regard.
Please ask the author of the
> -Original Message-
> From: Vadim Rozenfeld [mailto:vroze...@redhat.com]
> Sent: Tuesday, September 05, 2017 2:33 PM
> To: Gonglei (Arei); Paolo Bonzini
> Cc: Hangaohuai; Yan Vugenfirer; qemu-devel@nongnu.org;
> k...@vger.kernel.org; Radim Krcmar
> Subject: R
On 21/02/17 00:18, Gonglei (Arei) wrote:
On 20/02/2017 12:54, Gonglei (Arei) wrote:
On 20/02/2017 10:19, Gonglei (Arei) wrote:
Hi Paolo,
On 16/02/2017 02:31, Gonglei (Arei) wrote:
And the below patch works for me, I can support max 255 vcpus for
WS2012
with hyper-v enlightenments.
dif
> On Aug 14, 2017, at 3:18 AM, Mark Cave-Ayland
> wrote:
>
> On 14/08/17 07:51, Paolo Bonzini wrote:
>
>> On 13/08/2017 21:13, Programmingkid wrote:
>>> Lately I found out that Windows NT 4.0 seems to work well with the
>>> 486 and pentium processors. Using "-cpu 486" made installing it
>>> ac
> On Aug 18, 2017, at 3:23 PM, John Snow wrote:
>
>
>
> On 08/18/2017 09:36 AM, Programmingkid wrote:
>>
>>> On Aug 18, 2017, at 4:46 AM, Artyom Tarasenko wrote:
>>>
>>> On Fri, Aug 18, 2017 at 6:31 AM, Programmingkid
>>> wrote:
> On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote
On 08/18/2017 09:36 AM, Programmingkid wrote:
>
>> On Aug 18, 2017, at 4:46 AM, Artyom Tarasenko wrote:
>>
>> On Fri, Aug 18, 2017 at 6:31 AM, Programmingkid
>> wrote:
>>>
On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
On 15/08/2017 20:46, Programmingkid wrote:
>
>>
> On Aug 18, 2017, at 4:46 AM, Artyom Tarasenko wrote:
>
> On Fri, Aug 18, 2017 at 6:31 AM, Programmingkid
> wrote:
>>
>>> On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
>>>
>>> On 15/08/2017 20:46, Programmingkid wrote:
> On Aug 14, 2017, at 2:51 AM, Paolo Bonzini wrote:
>
On Fri, Aug 18, 2017 at 6:31 AM, Programmingkid
wrote:
>
>> On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
>>
>> On 15/08/2017 20:46, Programmingkid wrote:
>>>
On Aug 14, 2017, at 2:51 AM, Paolo Bonzini wrote:
On 13/08/2017 21:13, Programmingkid wrote:
> Lately I found out
> On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
>
> On 15/08/2017 20:46, Programmingkid wrote:
>>
>>> On Aug 14, 2017, at 2:51 AM, Paolo Bonzini wrote:
>>>
>>> On 13/08/2017 21:13, Programmingkid wrote:
Lately I found out that Windows NT 4.0 seems to work well with the
486 and p
On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
On 15/08/2017 20:46, Programmingkid wrote:
On Aug 14, 2017, at 2:51 AM, Paolo Bonzini
wrote:
On 13/08/2017 21:13, Programmingkid wrote:
Lately I found out that Windows NT 4.0 seems to work well with the
486 and pentium processors. Using
On Aug 15, 2017, at 6:27 PM, Paolo Bonzini wrote:
On 15/08/2017 20:46, Programmingkid wrote:
On Aug 14, 2017, at 2:51 AM, Paolo Bonzini
wrote:
On 13/08/2017 21:13, Programmingkid wrote:
Lately I found out that Windows NT 4.0 seems to work well with the
486 and pentium processors. Using
On 15/08/2017 20:46, Programmingkid wrote:
>
>> On Aug 14, 2017, at 2:51 AM, Paolo Bonzini wrote:
>>
>> On 13/08/2017 21:13, Programmingkid wrote:
>>> Lately I found out that Windows NT 4.0 seems to work well with the
>>> 486 and pentium processors. Using "-cpu 486" made installing it
>>> actuall
> On Aug 14, 2017, at 3:18 AM, Mark Cave-Ayland
> wrote:
>
> On 14/08/17 07:51, Paolo Bonzini wrote:
>
>> On 13/08/2017 21:13, Programmingkid wrote:
>>> Lately I found out that Windows NT 4.0 seems to work well with the
>>> 486 and pentium processors. Using "-cpu 486" made installing it
>>> ac
> On Aug 14, 2017, at 2:51 AM, Paolo Bonzini wrote:
>
> On 13/08/2017 21:13, Programmingkid wrote:
>> Lately I found out that Windows NT 4.0 seems to work well with the
>> 486 and pentium processors. Using "-cpu 486" made installing it
>> actually work. Now I am seeing another issue. When I boot
On 14/08/17 07:51, Paolo Bonzini wrote:
> On 13/08/2017 21:13, Programmingkid wrote:
>> Lately I found out that Windows NT 4.0 seems to work well with the
>> 486 and pentium processors. Using "-cpu 486" made installing it
>> actually work. Now I am seeing another issue. When I boot Windows NT
>> 4
On 13/08/2017 21:13, Programmingkid wrote:
> Lately I found out that Windows NT 4.0 seems to work well with the
> 486 and pentium processors. Using "-cpu 486" made installing it
> actually work. Now I am seeing another issue. When I boot Windows NT
> 4.0 I see this error message:
>
> *** STOP: 0x0
On Jul 14, 2017, at 11:25 AM, Peter Maydell wrote:
> On 14 July 2017 at 16:01, Programmingkid wrote:
>> How do I build the tilegx target? I have tried "./configure
>> --target-list=tilegx" and "./configure --target-list=tilegx-softmmu". They
>> both fail with this message: "ERROR: Unknown targ
On 14 July 2017 at 16:01, Programmingkid wrote:
> How do I build the tilegx target? I have tried "./configure
> --target-list=tilegx" and "./configure --target-list=tilegx-softmmu". They
> both fail with this message: "ERROR: Unknown target name".
tilegx at the moment only supports linux-user,
Thanks a lot.
I really appreciate this.
From: Mark Cave-Ayland
Sent: Monday, May 1, 2017 9:06 PM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
On 23/04/17 00:42, Ajallooiean Hossein wrote
On 23/04/17 00:42, Ajallooiean Hossein wrote:
Hi Ajallooiean,
> Hi Mark,
>
> Thanks a lot for this. - it did work!
>
> So, now im wondering how did you install the iso on disk?
>
> would you mind sharing your command line for the install please? and hacks if
> any
I simply went for somethin
-devel@nongnu.org
Cc: Mark Cave-Ayland
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
Hi Mark,
Thanks a lot for this. - it did work!
So, now im wondering how did you install the iso on disk?
would you mind sharing your command line for the install please? and hacks if
any
i am now
t image...
Loaded 7680 bytes
entry point is 0x4000
SILO Version 1.4.14
boot:
Thanks a lot in advance for your help.
Cheers
Hoss
From: Mark Cave-Ayland
Sent: Saturday, April 22, 2017 11:12 AM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Q
On 21/04/17 16:12, Ajallooiean Hossein wrote:
> Thanks for the files and the notes.
>
> I am attaching my config-host file for you. I'm on x86_64, running Linux 64,
> Ubuntu 16.04.2 LTS
>
> so, i can also boot like you do - this worked before as well. btw, if you try
> to install that to a dis
My mistake.
Yes I Already tried qemu-2.9.0.rc5. Same error happens.
Regards,
Siavash.
> On Apr 21, 2017, at 19:36, Mark Cave-Ayland
> wrote:
>
> On 21/04/17 15:56, Siavash Katebzadeh wrote:
>
>> My command line is:
>>
>> ./qemu-system-sparc64 \
>> -L pc-bios -m 720 \
>> -kernel ${KERNEL_PAT
Hoss
From: Mark Cave-Ayland
Sent: Friday, April 21, 2017 2:03 PM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
On 20/04/17 10:29, Ajallooiean Hossein wrote:
> Thanks for getting back
On 21/04/17 15:56, Siavash Katebzadeh wrote:
> My command line is:
>
> ./qemu-system-sparc64 \
> -L pc-bios -m 720 \
> -kernel ${KERNEL_PATH}/${KERNEL} \
> -initrd ${KERNEL_PATH}/${INITRD} \
> -drive file=${QCOW2_PATH}/${QCOW2},if=virtio,index=0 \
> -rtc base='2006-06-17T16:01:21',clock=vm \
> -n
On 20/04/17 10:29, Ajallooiean Hossein wrote:
> Thanks for getting back to me so quickly.
>
> I can boot Sparc64 -- ONLY when using the qemu from package manager.
> supposedly version 2.5
>
> but when building it myself (as i have some additions) - im getting this
> kernel error:
>
> https:/
On 21/04/17 12:37, Siavash Katebzadeh wrote:
> Hi,
>
> I can reproduce this panic using debian-7.8.0 image. I’m getting this
> segmentation fault:
>
> [ 24.846406] busybox[1]: segfault at f78a000c ip f77ab0ac (rpc
> f77ab090) sp ffd95a50 error 30001 in
> libc.so.6[f7
n Hossein
Sent: Thursday, April 20, 2017 3:08 PM
To: Peter Maydell
Cc: Mark Cave-Ayland; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
Ive downloaded the rc4 link you posted for 2.9 and am using that. - vanilla qemu
And am getting the error with that version.
Ive downloaded the rc4 link you posted for 2.9 and am using that. - vanilla qemu
And am getting the error with that version.
Kindest regards
Hoss
On 20 Apr 2017, 14:40 +0200, Peter Maydell , wrote:
On 20 April 2017 at 10:29, Ajallooiean Hossein
wrote:
Thanks for getting back to me so quickly.
On 20 April 2017 at 10:29, Ajallooiean Hossein
wrote:
> Thanks for getting back to me so quickly.
>
> I can boot Sparc64 -- ONLY when using the qemu from package manager.
> supposedly version 2.5
>
> but when building it myself (as i have some additions) - im getting this
> kernel error:
Sanit
me your kernel/image for testing?
Thanks a lot
Hoss
From: Mark Cave-Ayland
Sent: Thursday, April 20, 2017 9:26 AM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
On 20/04/17 06:25, Ajallooiean
send me your kernel/image for testing?
Thanks a lot
Hoss
From: Mark Cave-Ayland
Sent: Thursday, April 20, 2017 9:26 AM
To: Ajallooiean Hossein; qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: Sparc 64, kernel panic
On 20/04/17 06:25
On 20/04/17 10:29, Ajallooiean Hossein wrote:
> Thanks for getting back to me so quickly.
>
> I can boot Sparc64 -- ONLY when using the qemu from package manager.
> supposedly version 2.5
>
> but when building it myself (as i have some additions) - im getting this
> kernel error:
>
> https:/
On 20/04/17 06:25, Ajallooiean Hossein wrote:
> Hi All
>
> Has anyone experienced any kernel panics with the Sparc64 in 2.9-rc4? I dont
> seem to be able to run it right out of the box.
>
> Ill appreciate any kind of help
>
> Regards
> -H
I have a range of test images that I boot on a regular
On Wed, Apr 12, 2017 at 04:36:58PM +0430, ali saeedi wrote:
> I am new in qemu vm live migration. why we have this condition
> "current_time >= initial_time + BUFFER_DELAY" in qemu?
BUFFER_DELAY is used for rate-limiting. The maximum network throughput
can be set by the user so that QEMU doesn't
On 04/03/2017 10:24 AM, Alberto Garcia wrote:
> On Mon, Apr 03, 2017 at 09:07:02AM -0500, Eric Blake wrote:
>
>> At this point, it looks like no one is calling
>> throttle_group_unregister_blk() as a result of the 'device_del',
>> which leaves stale memory around
>
> I see, I can also reproduce t
On Mon, Apr 03, 2017 at 09:07:02AM -0500, Eric Blake wrote:
> At this point, it looks like no one is calling
> throttle_group_unregister_blk() as a result of the 'device_del',
> which leaves stale memory around
I see, I can also reproduce this very easily.
I wonder if it's not enough to simply d
Richard Odell writes:
> step by step instructions please
https://qemu.weilnetz.de/doc/qemu-doc.html
--
Alex Bennée
>
>
> On 20/02/2017 12:54, Gonglei (Arei) wrote:
> >>
> >> On 20/02/2017 10:19, Gonglei (Arei) wrote:
> >>> Hi Paolo,
> >>>
>
>
> On 16/02/2017 02:31, Gonglei (Arei) wrote:
> > And the below patch works for me, I can support max 255 vcpus for
> >> WS2012
> > with hyper-v en
On 20/02/2017 12:54, Gonglei (Arei) wrote:
>>
>> On 20/02/2017 10:19, Gonglei (Arei) wrote:
>>> Hi Paolo,
>>>
On 16/02/2017 02:31, Gonglei (Arei) wrote:
> And the below patch works for me, I can support max 255 vcpus for
>> WS2012
> with hyper-v enlightenments.
>
>
>
> On 20/02/2017 10:19, Gonglei (Arei) wrote:
> > Hi Paolo,
> >
> >>
> >>
> >> On 16/02/2017 02:31, Gonglei (Arei) wrote:
> >>> And the below patch works for me, I can support max 255 vcpus for
> WS2012
> >>> with hyper-v enlightenments.
> >>>
> >>> diff --git a/target/i386/kvm.c b/target/i386/kv
On 20/02/2017 10:19, Gonglei (Arei) wrote:
> Hi Paolo,
>
>>
>>
>> On 16/02/2017 02:31, Gonglei (Arei) wrote:
>>> And the below patch works for me, I can support max 255 vcpus for WS2012
>>> with hyper-v enlightenments.
>>>
>>> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
>>> index 27fd050.
Hi Paolo,
>
>
> On 16/02/2017 02:31, Gonglei (Arei) wrote:
> > And the below patch works for me, I can support max 255 vcpus for WS2012
> > with hyper-v enlightenments.
> >
> > diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> > index 27fd050..efe3cbc 100644
> > --- a/target/i386/kvm.c
> > ++
On 16/02/2017 02:31, Gonglei (Arei) wrote:
> And the below patch works for me, I can support max 255 vcpus for WS2012
> with hyper-v enlightenments.
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 27fd050..efe3cbc 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -77
On Thu, 2017-02-16 at 01:31 +, Gonglei (Arei) wrote:
> Hi,
>
> >
> >
> > On Sat, 2017-02-11 at 10:39 -0500, Paolo Bonzini wrote:
> > >
> > > >
> > > >
> > > >
> > > > >
> > > > >
> > > > > On 10/02/2017 10:31, Gonglei (Arei) wrote:
> > > > > >
> > > > > >
> > > > > > But We tested th
Hi,
>
> On Sat, 2017-02-11 at 10:39 -0500, Paolo Bonzini wrote:
> > >
> > >
> > > >
> > > > On 10/02/2017 10:31, Gonglei (Arei) wrote:
> > > > >
> > > > > But We tested the same cases on Xen platform and VMware, and
> > > > > the guest booted successfully.
> > > >
> > > > Were these two also test
On Sat, 2017-02-11 at 10:39 -0500, Paolo Bonzini wrote:
> >
> >
> > >
> > > On 10/02/2017 10:31, Gonglei (Arei) wrote:
> > > >
> > > > But We tested the same cases on Xen platform and VMware, and
> > > > the guest booted successfully.
> > >
> > > Were these two also tested with enlightenments
>
> > On 10/02/2017 10:31, Gonglei (Arei) wrote:
> > > But We tested the same cases on Xen platform and VMware, and
> > > the guest booted successfully.
> >
> > Were these two also tested with enlightenments enabled? TCG surely isn't.
>
> About TCG, I just remove ' accel=kvm,' and 'hy_releaxed'
Hi Paolo,
>
>
> On 10/02/2017 10:31, Gonglei (Arei) wrote:
> > But We tested the same cases on Xen platform and VMware, and
> > the guest booted successfully.
>
> Were these two also tested with enlightenments enabled? TCG surely isn't.
>
About TCG, I just remove ' accel=kvm,' and 'hy_releaxe
On 10/02/2017 10:31, Gonglei (Arei) wrote:
> But We tested the same cases on Xen platform and VMware, and
> the guest booted successfully.
Were these two also tested with enlightenments enabled? TCG surely isn't.
Paolo
> Today I also tested on tcg, the guest also boots successfully.
>
> BTW,
Hi,
> Behalf Of Yan Vugenfirer
>
> Hi,
>
> First off all to use more than 64 CPUs on Windows you should use CPU grouping.
> Each group can contain maximum 64 CPUs. Here is a good article explaining
> possible configurations:
> https://msdn.microsoft.com/en-us/windows/hardware/drivers/devtest/boo
Hi,
First off all to use more than 64 CPUs on Windows you should use CPU grouping.
Each group can contain maximum 64 CPUs. Here is a good article explaining
possible configurations:
https://msdn.microsoft.com/en-us/windows/hardware/drivers/devtest/boot-parameters-to-test-drivers-for-multiple-pro
Dear QEMU community,
the website for the QEMU Advent Calendar 2016 is now online:
http://www.qemu-advent-calendar.org/2016/
(thanks to Jeff Cody and Stefan Hajnoczi for the help with getting started!)
Note that we still need some more disk images to be able to complete the
calendar this year,
"zhun...@gmail.com" writes:
> Hello，recently I study qemu source code ,and I have some questions ,can you
> help me ?
>
>> 1、what is the meaning of queues in structure NICConf ? I think it is the
>> number of queues to a NIC,and I do not where it is.
NICConf captures some configuration inf
Hi All,
As discussed before, upstream are working about PCIE instead of PCI in
AArch64.
Thanks for your efforts about this on AArch64 :-)
If it convenient, could you tell me when we plan to finish this task ?
and which qemu version will support this functions in the future?
Big Thanks
Great ~ Thanks for your valuable information~
I will try with the xml and any update I will post here.
On 18 August 2016 at 21:51, Andrea Bolognani wrote:
> On Thu, 2016-08-18 at 20:43 +0800, Kevin Zhao wrote:
> > What's the minimum version of Qemu that support virito-1.0?
> > Does Qemu 2.6 wor
On 08/19/2016 11:43 AM, Andrea Bolognani wrote:
On Thu, 2016-08-18 at 08:38 +0200, Andrew Jones wrote:
Finally, FWIW, with a guest kernel of 4.6.4-301.fc24.aarch64. The
following qemu command line works for me.
(notice the use of PCIe), and my network interface gets labeled enp0s1.
$QEMU -ma
On Thu, 2016-08-18 at 08:38 +0200, Andrew Jones wrote:
> > > Finally, FWIW, with a guest kernel of 4.6.4-301.fc24.aarch64. The
> > > following qemu command line works for me.
> > > (notice the use of PCIe), and my network interface gets labeled enp0s1.
> > >
> > > $QEMU -machine virt-2.6,accel=kv
On 08/18/2016 08:43 AM, Kevin Zhao wrote:
Hi Laine,
Thanks :-) I also has a little questions below.
On 18 August 2016 at 01:00, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
Now I'm investigatin
On 08/18/2016 08:10 AM, Marcel Apfelbaum wrote:
On 08/17/2016 08:00 PM, Laine Stump wrote:
What I'm not sure about is whether we should always auto-add an extra
pcie-*-root to be sure a device can be hotplugged, or if we should admit
that 1
available slot isn't good enough for all situation
On 08/18/2016 03:41 AM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 01:00:05PM -0400, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
AArch64.
On Thu, 2016-08-18 at 20:43 +0800, Kevin Zhao wrote:
> What's the minimum version of Qemu that support virito-1.0?
> Does Qemu 2.6 works?
2.6 definitely has virtio 1.0 support, however libvirt does
not yet allow you to control whether a device uses 0.9, 1.0
or both. The default for 2.6 should be
Hi All,
Thanks for your all kindly response. Really Great and helpful :-)
On 18 August 2016 at 20:30, Kevin Zhao wrote:
> Hi Jones:
>Thanks~It is great that Qemu has been working on that :-)
>
> On 18 August 2016 at 00:13, Andrew Jones wrote:
>
>> On Wed, Aug 17, 2016 at 08:08:11PM +080
On 08/17/2016 08:00 PM, Laine Stump wrote:
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
[...]
Hi,
1) If we want to support both PCIe devices and PCI, then things are messy.
Currently we propose dropping PCI support. mac
Hi Laine,
Thanks :-) I also has a little questions below.
On 18 August 2016 at 01:00, Laine Stump wrote:
> On 08/17/2016 12:13 PM, Andrew Jones wrote:
>
>> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
>>
>>> Hi all,
>>> Now I'm investigating net device hot plug and disk
Hi Jones:
Thanks~It is great that Qemu has been working on that :-)
On 18 August 2016 at 00:13, Andrew Jones wrote:
> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > Hi all,
> > Now I'm investigating net device hot plug and disk hotplug for
> > AArch64. For virtio , the d
On Wed, Aug 17, 2016 at 01:00:05PM -0400, Laine Stump wrote:
> On 08/17/2016 12:13 PM, Andrew Jones wrote:
> > On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > > Hi all,
> > > Now I'm investigating net device hot plug and disk hotplug for
> > > AArch64. For virtio , the default
On Wed, Aug 17, 2016 at 06:41:33PM +0200, Andrea Bolognani wrote:
> On Wed, 2016-08-17 at 18:13 +0200, Andrew Jones wrote:
> > On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> > >
> > > Hi all,
> > > Now I'm investigating net device hot plug and disk hotplug for
> > > AArch64. Fo
On 08/17/2016 12:13 PM, Andrew Jones wrote:
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
Hi all,
Now I'm investigating net device hot plug and disk hotplug for
AArch64. For virtio , the default address is virtio-mmio. After Libvirt
1.3.5, user can explicitly specify the addr
On Wed, 2016-08-17 at 18:13 +0200, Andrew Jones wrote:
> On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> >
> > Hi all,
> > Now I'm investigating net device hot plug and disk hotplug for
> > AArch64. For virtio , the default address is virtio-mmio. After Libvirt
> > 1.3.5, user c
On Wed, Aug 17, 2016 at 08:08:11PM +0800, Kevin Zhao wrote:
> Hi all,
> Now I'm investigating net device hot plug and disk hotplug for
> AArch64. For virtio , the default address is virtio-mmio. After Libvirt
> 1.3.5, user can explicitly specify the address-type to pci and so libvirt
> will pa
Hi Claudio,
Could you tell me what host and guest OS are you using? And the
hardware is 96board or other Hisilicon Server?
I use SoftIron. 8 cores AArch64 servers.
On 5 August 2016 at 18:32, Claudio Fontana
wrote:
> On 05.08.2016 12:27, Claudio Fontana wrote:
> > Hi,
> >
> > On 05.08.20
On 05.08.2016 12:27, Claudio Fontana wrote:
> Hi,
>
> On 05.08.2016 10:28, Daniel P. Berrange wrote:
>> On Fri, Aug 05, 2016 at 10:23:58AM +0800, Kevin Zhao wrote:
>>> Hi All,
>>> I have a problem may about Qemu and kindly need your help. Does
>>> qemu-system-aarch64 support virtio-9p ?
>>>
Hi,
On 05.08.2016 10:28, Daniel P. Berrange wrote:
> On Fri, Aug 05, 2016 at 10:23:58AM +0800, Kevin Zhao wrote:
>> Hi All,
>> I have a problem may about Qemu and kindly need your help. Does
>> qemu-system-aarch64 support virtio-9p ?
>> Recently I have tried to use qemu remapped the file
Hi Daniel && Peter && All,
Thanks for your help. I've changed to 9p2000.u but also met the
problem. The qemu of booting the guests is here:
http://paste.openstack.org/show/550382/
After booting *Debian 8* OS, enter into the guests and run the
command( changed to 9p2000.u):
[image: Inline
Hi Peter,
Thanks~
I will try newest version of Qemu 2.7.0 to see how it well
On 5 August 2016 at 16:13, Peter Maydell wrote:
> On 5 August 2016 at 03:23, Kevin Zhao wrote:
> > Hi All,
> > I have a problem may about Qemu and kindly need your help. Does
> > qemu-system-aarch64 suppo
On Fri, Aug 05, 2016 at 10:23:58AM +0800, Kevin Zhao wrote:
> Hi All,
> I have a problem may about Qemu and kindly need your help. Does
> qemu-system-aarch64 support virtio-9p ?
> Recently I have tried to use qemu remapped the file from host to
> guest. As I know, Qemu has supported this
On 5 August 2016 at 03:23, Kevin Zhao wrote:
> Hi All,
> I have a problem may about Qemu and kindly need your help. Does
> qemu-system-aarch64 support virtio-9p ?
virtio-9p isn't guest architecture specific so in theory it
should. However I've never tried it.
> The Qemu version is QEMU
On Thu, 05/26 14:50, m13767433329 wrote:
> question 2: What does the architecture of Qemu like ?
To begin with, this is a nice overview:
http://blog.vmsplice.net/2011/03/qemu-internals-big-picture-overview.html
Fam
On Thu, 05/26 14:50, m13767433329 wrote:
> question 3:how can I develop a kind of software like Qemu which can run on
> Windows?
QEMU _can_ run on Windows:
https://qemu.weilnetz.de/
Fam
> How can I add a kind of new device support in Qemu and What is the steps
to do so?
https://github.com/rafilia/qemu_example_virtual_pcidev
--
Dongli Zhang (张东立)
finallyjustice.github.io
On Mar 30, 2016, at 11:51 AM, Eric Blake wrote:
> On 03/30/2016 09:10 AM, Programmingkid wrote:
>> I just git pull'ed today and now have this problem:
>>
>> .../scripts/qapi.py", line 1726, in maybe_open
>>return open(name, opt)
>> IOError: [Errno 1] Operation not permitted: './qapi-types.h'
On 03/30/2016 09:10 AM, Programmingkid wrote:
> I just git pull'ed today and now have this problem:
>
> .../scripts/qapi.py", line 1726, in maybe_open
> return open(name, opt)
> IOError: [Errno 1] Operation not permitted: './qapi-types.h'
What are the file permissions on ./qapi-types.h? That
hi，I have read 2015-qcow2-expanded.pdf and qcow2.txt，
so I understand how to convert the offset in the virtual disk to the
offset into the image file（qcow2).
but I wish to know how to convert the block using ext4 to the offset in
the virtual disk. Please help me.
the file block information is
1 - 100 of 279 matches
Mail list logo
