Hi drew，Thanks for your reply.
I agree this patch remains insufficient. Regardless, Guest Interrupt Files
represent a new and critical resource type that upper layers currently
lack awareness of, and significant work is still needed to fully integrate them.
> From: "Andrew Jones"
> Date: Thu, Ju
Hi Markus,
On 4/23/24 6:39 AM, Markus Armbruster wrote:
Gustavo Romero writes:
Hi Markus,
Thanks for interesting in the ivshmem-flat device.
Bill Mills (cc:ed) is the best person to answer your question,
so please find his answer below.
On 2/28/24 3:29 AM, Markus Armbruster wrote
Of all the gin joints in all the towns in all the world, Andrey Smirnov had to
walk into mine at 12:11 on Thursday 15 March 2018 and say:
> Add support for "TX complete"/TXDC interrupt generate by real HW since
> it is needed to support guests other than Linux.
>
> Base
Of all the gin joints in all the towns in all the world, Bill Paul had to walk
into mine at 13:45 on Thursday 15 March 2018 and say:
> Of all the gin joints in all the towns in all the world, Andrey Smirnov had
> to
>
> walk into mine at 12:11 on Thursday 15 March 2018 and say:
>
As I said before:
"I'm not submitting this as a patch to the development list as I'm not
fully certain it complies with the hardware spec and doesn't break any
other functionality."
What I'm trying to say here is that while I may have been able to cobble
together a hack to make the UART nominally
> > }
> >
> > }
> >
> > (For ENET_INT_MAC events, just signal both s->irq[0] and s->irq[1]).
>
> Now this is an excellent idea.
>
> > This of course means signaling spurious events on vector 151, but you're
> > doing that now any
Of all the gin joints in all the towns in all the world, Bill Paul had to walk
into mine at 10:53 on Friday 09 March 2018 and say:
> Of all the gin joints in all the towns in all the world, Guenter Roeck had
> to
>
> walk into mine at 10:20 on Friday 09 March 2018 and say:
> &
Of all the gin joints in all the towns in all the world, Guenter Roeck had to
walk into mine at 10:20 on Friday 09 March 2018 and say:
> On Fri, Mar 09, 2018 at 05:47:16PM +, Peter Maydell wrote:
> > On 8 March 2018 at 18:28, Bill Paul wrote:
> > > Anyway, this means th
now they would never get interrupts on either vector, unless you fudge things
so that the ENET module triggers both vector 150 and the vector for GPIO6 in
the GIC or patch them to back out the erratum 6678 workaround as later kernels
do.
Later kernels that register vectors 150 and 151 would w
"4.14+: Both versions of qemu (as-is and interrupts reverted) work fine"
Hm. I really wonder how it can be possible that Linux works with the
interrupt vectors reversed, though to be fair I have not looked at the
Linux i.MX6 ENET driver code. I suppose it's possible that the driver is
binding the
Public bug reported:
The imx_serial.c driver currently implements only partial support for
the i.MX6 UART hardware. (I understand it's a work in progress and
that's fine.) dIn particular, it does not implement support for the
Transmit Complete Interrupt Enable bit in the UCR4 register. The VxWorks
Public bug reported:
The sabrelite machine model used by qemu-system-arm is based on the
Freescale/NXP i.MX6Q processor. This SoC has an on-board ethernet
controller which is supported in QEMU using the imx_fec.c module
(actually called imx.enet for this model.)
The include/hw/arm/fsm-imx6.h file
until you press a key at the serial console, which causes an RX
interrupt that unjams in).
Also once a character has been written, it waits for a TXEIE interrupt
before sending the next character in a string. With these two fixes, it can
now write to the serial port sucessfully.
Signed-off-by: Bil
Of all the gin joints in all the towns in all the world, Peter Maydell had to
walk into mine at 12:51:04 on Monday 29 August 2016 and say:
> On 29 August 2016 at 13:59, Bill Paul wrote:
> > Unfortunately it's been a frustrating experience because there seem to be
> > seve
Of all the gin joints in all the towns in all the world, Liviu Ionescu had to
walk into mine at 12:19:42 on Monday 29 August 2016 and say:
> > On 29 Aug 2016, at 20:59, Bill Paul wrote:
> >
> > I recently started tinkering with ChibiOS as part of a small personal
> >
hibiOS/RT seems to support an alternate preemption scheme that uses the
PendSV interrupt instead of NMI, and if I compile it to use that mode, then
the example works with the Stellaris machine model. That feels like a hack
though: shouldn't a software NMI just work?
-Bill
--
=
e with the ioapic.c implementation either.
Signed-off-by: Bill Paul
CC: Paolo Bonzini
CC: Richard Henderson
CC: Eduardo Habkost
---
hw/timer/hpet.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/hw/timer/hpet.c b/hw/timer/hpet.c
index 78140e6..a2c18b3 100644
---
Of all the gin joints in all the towns in all the world, Paolo Bonzini had to
walk into mine at 06:20:05 on Tuesday 05 April 2016 and say:
> On 04/04/2016 23:42, Bill Paul wrote:
> > I'm testing some of the HPET handling code in VxWorks using QEMU 2.4.1
> > and I've en
ot; the problem with Linux by introducing some non-standard
behavior that happens to pacify Linux's particular usage model.
Can someone comment on whether or not this inversion logic is really still
necessary in Linux? Is there maybe a better way to handle this?
-Bill
--
=
guest can't clear.
To fix this, the 'efer' member of the CPUX86State structure has been moved
to an area outside the region preserved by do_cpu_init(), so that it can
be properly re-initialized by x86_cpu_reset().
Signed-off-by: Bill Paul
CC: Paolo Bonzini
CC: Richard Henders
to the above condition (the CPU starts up, but is
> unable to enable paging and dies screaming in short order).
>
> Booting with the 32-bit OVMF build and the VxWorks BOOTIA32.EFI loader
> works ok. The same VxWorks loader and kernel code also seems to run ok on
> real hardware.
>
order).
Booting with the 32-bit OVMF build and the VxWorks BOOTIA32.EFI loader works
ok. The same VxWorks loader and kernel code also seems to run ok on real
hardware.
I'm using QEMU 2.3.0 on FreeBSD/amd64 9.2-RELEASE. I'm not using KVM. It looks
like the code is
Of all the gin joints in all the towns in all the world, Laszlo Ersek had to
walk into mine at 11:20:28 on Monday 14 September 2015 and say:
> On 09/14/15 18:53, Bill Paul wrote:
> > Of all the gin joints in all the towns in all the world, Laszlo Ersek had
> > to
> >
> &
a bug in Microsoft's
ACPI implementation (both in their ASL compiler and in the AML parser)? Unless
DataTableRegion() is specified to be optional in some way (I don't know if it
is or not, but I doubt it), this sounds like an clear cut case of non-
compliance with the ACPI spec. And i
Yep, lack of interest here. The ACE-DB-3 (and probably all QCA988x)
simply does not work with Linux. No more time for this.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1471583
Title:
QCA988X Wi
Oh I see. It's because the path that was shared on the host is no
longer available, apparently causing this weird error message.
0a:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless Network
Adapter (rev ff) (prog-if ff)
!!! Unknown header type 7f
So even earlier than P
I've figured out how to compile ElRepo's kernel-ml and make the change to pci's
quirks. But now the KVM's VM won't even boot. It gives a popup with:
"Error starting domain: Unable to read from monitor: Connection reset by peer
Traceback (most recent call last):
File "/usr/share/virt-manager/v
Oh this is not good. The current kernel (3.10.0-229.7.2.el7.x86_64)
that comes with the current CentOS (7.1) does not have in quirks.c the
preceeding or succeeding stanzas in the patch here:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/quirks.c?id=c3e59ee4e766
I see. And now I also understand that the patch is to the *PCI* driver,
not the ath10k driver.
I was busily trying to get the SRPM for ElRepo's 4.1 kernel to recompile
for the guest, but it is not there. He has something called "kernel-
ml-4.1.1-1.el7.elrepo.nosrc.rpm" which is incomplete, and s
You mean 'a patch and recompile to the -guest- kernel'? Otherwise I'm
confused.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1471583
Title:
QCA988X Wifi Card Not PCI Passing Through
Status in QE
Actually my card locks up *on* boot of the guest, not after its reboot.
This generation of Atheros cards requires firmware files:
https://wireless.wiki.kernel.org/en/users/Drivers/ath10k/firmware
So kernel 3.10 (default with CentOS 7.1) is not an option; 3.11 is the
minimum, and that doesn't
It does sound exactly like what I'm seeing.
>From http://www.gossamer-threads.com/lists/linux/kernel/2054846
"Yes. If you *re*start the VM . ... The first start (after reboot) was
not a problem."
It seems clear that this problem began with kernel 3.13. I tried
applying the backports ath10k to
Public bug reported:
CPU: Intel(R) Xeon(R) CPU E3-1265L v3 @ 2.50GHz
KVM: qemu-kvm-1.5.3-86.el7_1.2.x86_64
Kernel: 4.1.1-1.el7.elrepo.x86_64, and kernel-3.10.0-229.7.2.el7.x86_64
Host & Guest: CentOS 7.1
Using virt-manager-1.1.0-12.el7.noarch to create, configure, and start guest
I am trying t
.0 on FreeBSD/amd64 9.1-RELEASE.
-Bill
Signed-off-by: Bill Paul
---
target-i386/seg_helper.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-i386/seg_helper.c b/target-i386/seg_helper.c
index fa374d0..2bc757a 100644
--- a/target-i386/seg_helper.c
+++ b/target-i386/
Of all the gin joints in all the towns in all the world, Stefan Weil had to
walk into mine at 15:23:36 on Monday 09 March 2015 and say:
> Hi Bill,
>
> sending text only e-mails might help. Usually git send-email is better
> than using KMail or other mail software.
You know, I t
crash on QEMU, unless I apply the patch below.
Can someone confirm that this is in fact a real bug? The Intel architecture
manual seems quite clear about the SYSRET behavior. The bug seems to have been
around as far back as QEMU 0.10.5.
I am using QEMU 2.2.0 on FreeBSD/amd64 9.1-RELEASE.
-Bill
simple. I'm attaching a patch which worked for me.
Using this fix, the code that I'm testing now behaves the same on the
QEMU virtual machine as on real hardware.
- Bill (wp...@windriver.com)
** Affects: qemu
Importance: Undecided
Status: New
** Attachment added:
king that maybe
I'm missing something. I'm pretty sure this is wrong though.
I'm including a patch to fix this below. It seems to fix the problem quite
nicely on my QEMU 2.2.0 installation. I'm also attaching a separate copy in
case my mai
is there too (in target-i386/op_helper.c). I'm puzzled
as to how it's gone unnoticed for so long, which has me thinking that maybe
I'm missing something. I'm pretty sure this is wrong though.
I'm attaching a patch for this below. It'
Of all the gin joints in all the towns in all the world, Michael S. Tsirkin
had to walk into mine at 13:44:38 on Wednesday 09 January 2013 and say:
> On Wed, Jan 09, 2013 at 09:30:43AM -0800, Bill Paul wrote:
> > Of all the gin joints in all the towns in all the world, Michael S.
&g
tup method -- for the older non-PCI LANCE chips that was the only way
to configure them but PCI devices starting with the am97c970 can be configured
just by setting up registers).
Honestly I'm surprised I still have all my hair and that it's still the same
color.
-Bill
--
===
he hardware
either, but that doesn't mean they don't exist.
So pretty please, with sugar on top, leave this code alone.
-Bill
> Tested with windows and linux guests.
>
> Cc: Bill Paul
> Reported-by: Yan Vugenfirer
> Signed-off-by: Michael S. Tsirkin
> ---
>
section 9 of the GPL. The reason why some software projects can not
automatically update to GPL 3, is some authors deliberately remove the
", or (at your option) any later version." clause.
Bill
M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> &qu
dragoran wrote:
> Bill C. Riemers wrote:
>> You don't need to compile kqemu into the kernel. When I install
>> dkms-kqemu from freshrpms, I do NOT rebuild my kernel. I am fairly
>> certain with Fedora's new policy for extras, there would not be much
>> of
d into the
new Enterprise Extra's repository as well. However, someone would need to
volunteer to maintain the package.
Bill
On 8/4/07, dragoran <[EMAIL PROTECTED]> wrote:
>
>
>
> On 8/4/07, Ricardo Almeida <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
I would suggest just the opposite, under commit your ram. If your base operating system is Linux, you can create your swap partitions under a host linux tmpfs directory. You can then safely over commit the amount of tmpfs swap space. The guest linux system will expect he swap to be slow, so it
About a month ago, I used 'fetchmail' to copy mail from an IMAP folder to gmail. I accidently used the wrong flags, and about 100 messages were redelivered... Perhaps someone else has accidently done the same thing with messages from this mailing list?
BillOn 8/21/06, Bruno Abinader <[EMAIL PROT
Fails to compile on Linux with glibc 2.2.5. CLOCK_MONOTONIC isn't
defined in glibc 2.2.5. The following patch is a workaround:
--- qemu-0.8.2/vl.c 2006-07-22 13:23:34.0 -0400
+++ ../qemu-0.8.2/vl.c 2006-07-26 11:37:34.0 -0400
@@ -541,7 +541,7 @@
static void init_get_clock(
I was talking to a friend at Red Hat. He says what they suggest using ext3, but putting the journal file small separate internal SCSI drive If you do so you will get far better performance and reliability than from reiserfs.
BillOn 8/7/06, R. Armiento <[EMAIL PROTECTED]> wrote:
Jens Axboe wro
Just to throw in my two cents, I notice that on the namesys website, they claim reiser4 is completely safe in the event of a power failure, while reiserfs 3 still requires some recovery. Apparently in reiser4 they somehow design writes to happen in sequences that create atomic events. So the whol
How about compromising, and making the patch a run time option. Presumably this is only a problem when the virtual machine is not properly shutdown. For those ho want the extra security of knowing the data will be written regardless of the shutdown status they can enable the flag. By default it
It seems to me you missed the most important qemu feature. That is qemu will emulate different processors. Just try running an PPC version of Linux on an x86 with VMWARE. To my knowledge the only other programs that can do this are either very expensive or extremely slow.
BillOn 7/28/06, Udo 'Ro
e in
qemu-0.8.1 version. It has nothing to do with recompiling glibc, or downloading different kernel source, or any other such non-sense.BillOn 7/17/06,
Damien Mascord <[EMAIL PROTECTED]> wrote:
Bill C. Riemers wrote:> Good guess, SuSE makes many modifications to the standard kernel. H
System: SuSE 10.1gcc version: 3.4.6CPU: Amd Athlon(tm) Processor 3200+Bill
On 7/8/06, Jim C. Brown <[EMAIL PROTECTED]> wrote:
The issue is with your linux kernel headers.On Sat, Jul 08, 2006 at 11:07:57AM -0400, Doctor Bill wrote:> At first I thought the problem was that I was using gc
At first I thought the problem was that I was using gcc-4, so I installed gcc-3.4.6, but I still get the same errors:gcc-3.4 -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/tmp/qemu-0.8.1/target-i386 -I/tmp/qemu-0.8.1
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/tmp/qemu-0.8.1/fpu -DH
to kill the virtual machine.
The only thing that will kill the process is a hard power down on the
host machine. Without KQemu enabled, the virtual machine works.
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman
he proc filesystem. Some consider this a security
hole, others consider it a very useful feature.
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
I would do:
chmod -R ugo+w /cygdrive/q
I can than modify \\docbill002\Data as guest as much as I want.
Maybe someone on the list can specify the non-cygwin equivalent of this command.
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
y, this usually only done for runtime error
detection and sometimes thread saftey. Pretty much all modern
operating systems do copy on write. However, this is completely
beyond the scope of our discussion.
Bill
___
Qemu-devel mailing li
constant, you do not need to reference how
there values are changing in a debugger...
Probably more important is to make sure none constant data structures
are done on the stack. There is no good reason why any code page
should be read-write.
Bill
On 8/23/05, Andreas Mohr <[EMAIL PROTECTED]>
o I do use QEMU to host other Windows operating systems, but I would
only use it for Linux system when coLinux is unusable.
Bill
On 7/28/05, Christian MICHON <[EMAIL PROTECTED]> wrote:
> found out why :)
>
> On 7/28/05, 姚春林 wrote:
> (...)
> > debian + gnome 2.1
> > g
exact same problem on a real PC. I did not have
time to try and resolve thi problem, so I ended up installing XP Home
edition on that particular computer.
Bill
On 7/27/05, Antony Gelberg <[EMAIL PROTECTED]> wrote:
> Christian MICHON wrote:
> > 1) have you tried using qemu-im
have not experienced this slow
down problem with any other guest OS's.
Bill
On 7/26/05, Christian MICHON <[EMAIL PROTECTED]> wrote:
> On 7/26/05, Mike Tremoulet wrote:
> > Outstanding work! I've been a fan of QEMU as a free emulator for some time.
> >
> >
Just out of curiousity, I verified Norton Ghost Floppies still produce
the same error. I was hoping the patch I saw a few weeks ago to allow
self modifing x86 code would fix the problem...
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http
networking problems with SAMBA. However, I am
not convinced those are bug. It could just be I am making some bad
guesses on how to configure samba due to lack of documentation. So I
will try not to take up peoples time on this list until I know if it
is user errors or so
On 6/30/05, Doctor Bill <[EMAIL PROTECTED]> wrote:
> The first problem I noticed is that with the 0.70 version, keys are
> not mapped correctly. For example, if I try to type in a URL as soon
> as I press the letter e explorer opens. As soon as I type the letter
> m, the window
er than my G3.
Bill
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
67 matches
Mail list logo
