Am 29.05.2016 um 08:37 schrieb Sameeh Jubran:
> Since mit_delay can never be 0 this if statement is
> superfluous.
>
> Signed-off-by: Sameeh Jubran
> ---
> hw/net/e1000.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/hw/net/e1000.c b/hw/net/e1000.c
> index 8e79b
Since mit_delay can never be 0 this if statement is
superfluous.
Signed-off-by: Sameeh Jubran
---
hw/net/e1000.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/hw/net/e1000.c b/hw/net/e1000.c
index 8e79b55..eb903a9 100644
--- a/hw/net/e1000.c
+++ b/hw/net/e1000.c
@@
I have 2 running virtual machines.
1. Ubuntu Server 16.04 acting as a headless game server
2. Windows 10 Pro used for gaming and other daily activities
I too can start/stop the Win 10 vm for a period of time after a cold boot but
if it is logged in for a certain period of time, when I go to sh
I am having the exact same issue!
My Setup:
Model: unRaid 6.2 Beta
M/B: ASUSTeK Computer INC. - Z8P(N)E-D12(X)
CPU: Intel® Xeon® CPU X5690 @ 3.47GHz
HVM: Enabled
IOMMU: Enabled
Cache: 384 kB, 1536 kB, 12288 kB
Memory: 32768 MB (max. installable capacity 96 GB)
Network: bond0: fault-tolerance (act
Well, now we finally know that it isn't the i7-5820K's or X99 chipset's
or LGA 2011 socket's faults.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1580459
Title:
Windows (10?) guest freezes entire
Signed-off-by: Wei Wang
---
Benefits | 8
1 file changed, 8 insertions(+)
create mode 100644 Benefits
diff --git a/Benefits b/Benefits
new file mode 100644
index 000..7d10485
--- /dev/null
+++ b/Benefits
@@ -0,0 +1,8 @@
+The vhost-pci design provides KVM with a faster and more scal
Signed-off-by: Wei Wang
---
FutureWorks | 21 +
1 file changed, 21 insertions(+)
create mode 100644 FutureWorks
diff --git a/FutureWorks b/FutureWorks
new file mode 100644
index 000..210edcd
--- /dev/null
+++ b/FutureWorks
@@ -0,0 +1,21 @@
+The vhost-pci design is curren
Signed-off-by: Wei Wang
---
Results | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 Results
diff --git a/Results b/Results
new file mode 100644
index 000..7402826
--- /dev/null
+++ b/Results
@@ -0,0 +1,18 @@
+We have built a fundamental vhost-pci based inter-VM
Signed-off-by: Wei Wang
---
Introduction | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 Introduction
diff --git a/Introduction b/Introduction
new file mode 100644
index 000..8774676
--- /dev/null
+++ b/Introduction
@@ -0,0 +1,31 @@
+Current vhost-u
This RFC proposes a design of vhost-pci, which is a new virtio device type.
The vhost-pci device is used for inter-VM communication. Please read the RFC
patches for details.
Wei Wang (6):
Vhost-pci RFC: Introduction
Vhost-pci RFC: Modification Scope
Vhost-pci RFC: Benefits to KVM
Vhost-pc
Signed-off-by: Wei Wang
---
ModificationScope | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 ModificationScope
diff --git a/ModificationScope b/ModificationScope
new file mode 100644
index 000..ea949ee
--- /dev/null
+++ b/ModificationScope
@@ -0,0 +1,3 @@
+Changes to: QEMU, Gue
Signed-off-by: Wei Wang
---
Details | 324
1 file changed, 324 insertions(+)
create mode 100644 Details
diff --git a/Details b/Details
new file mode 100644
index 000..4ea2252
--- /dev/null
+++ b/Details
@@ -0,0 +1,324 @@
+1 De
On Sat, 28 May 2016 18:14:18 +
"Aviv B.D." wrote:
> Hi,
> As far as I tested the disabled code (call to memory_region_iommu_replay)
> hangup
> QEMU on startup if IOMMU is enabled (scaning 64 bit address space takes
> more
> than an hour on modern hardware) , at least on x86 hardware. So the c
OK, I figured out how to delete it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1580459
Title:
Windows (10?) guest freezes entire host on shutdown if using PCI
passthrough
Status in QEMU:
Ne
Whoops, I clicked the wrong button and added the wrong thing for Arch
Linux, and I don't know how to delete it. (new to launchpad here)
** Also affects: archlinux-lp
Importance: Undecided
Status: New
** Also affects: archlinux
Importance: Undecided
Status: New
** Changed in:
On 25/05/16 04:13, Emilio G. Cota wrote:
> Reviewed-by: Richard Henderson
> Signed-off-by: Emilio G. Cota
Acked-by: Sergey Fedorov
> ---
> tests/.gitignore | 1 +
> tests/Makefile | 6 +-
> tests/test-qdist.c | 369
> +
> 3 files
I see, it's definitely the same issue then.
Could it be something to do with our hardware unbinding and binding pci
devices or something of the sort? I sort of doubt it but it is strange
someone else with a more different CPU/mobo combo hasn't reported this
problem yet.
That being said, we have a
On 25/05/16 04:13, Emilio G. Cota wrote:
> diff --git a/util/qdist.c b/util/qdist.c
> new file mode 100644
> index 000..3343640
> --- /dev/null
> +++ b/util/qdist.c
> @@ -0,0 +1,386 @@
(snip)
> +
> +void qdist_add(struct qdist *dist, double x, long count)
> +{
> +struct qdist_entry *entry =
Hi,
As far as I tested the disabled code (call to memory_region_iommu_replay)
hangup
QEMU on startup if IOMMU is enabled (scaning 64 bit address space takes
more
than an hour on modern hardware) , at least on x86 hardware. So the code is
not 100%
correct for any context. Maybe it just should be dis
** Also affects: debian
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1580459
Title:
Windows (10?) guest freezes entire host on shutdown if using PCI
p
Signed-off-by: Wei Wang
---
Details | 324
1 file changed, 324 insertions(+)
create mode 100644 Details
diff --git a/Details b/Details
new file mode 100644
index 000..4ea2252
--- /dev/null
+++ b/Details
@@ -0,0 +1,324 @@
+1 De
On Sat, 28 May 2016 16:10:55 +
"Aviv B.D." wrote:
> On Sat, May 28, 2016 at 7:02 PM Alex Williamson
> wrote:
>
> > On Sat, 28 May 2016 10:52:58 +
> > "Aviv B.D." wrote:
> >
> > > Hi,
> > > Your idea to search the relevent VTDAddressSpace and call it's notifier
> > > will
> > > probab
I think this is what's happening to me on my windows 8.1 vm although it
might be slightly different.
Just about everything you guys talked about applies except I don't have
to shutdown for it to freeze up in my case(although if it's on for long
enough and I shut it off it freezes). It freezes up o
Signed-off-by: Wei Wang
---
Results | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 Results
diff --git a/Results b/Results
new file mode 100644
index 000..7402826
--- /dev/null
+++ b/Results
@@ -0,0 +1,18 @@
+We have built a fundamental vhost-pci based inter-VM
Signed-off-by: Wei Wang
---
Introduction | 31 +++
1 file changed, 31 insertions(+)
create mode 100644 Introduction
diff --git a/Introduction b/Introduction
new file mode 100644
index 000..8774676
--- /dev/null
+++ b/Introduction
@@ -0,0 +1,31 @@
+Current vhost-u
This RFC proposes a design of vhost-pci, which is a new virtio device type.
The vhost-pci device is used for inter-VM communication. Please read the RFC
patches for details.
Wei Wang (6):
Vhost-pci RFC: Introduction
Vhost-pci RFC: Modification Scope
Vhost-pci RFC: Benefits to KVM
Vhost-pc
Signed-off-by: Wei Wang
---
Benefits | 8
1 file changed, 8 insertions(+)
create mode 100644 Benefits
diff --git a/Benefits b/Benefits
new file mode 100644
index 000..7d10485
--- /dev/null
+++ b/Benefits
@@ -0,0 +1,8 @@
+The vhost-pci design provides KVM with a faster and more scal
Signed-off-by: Wei Wang
---
ModificationScope | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 ModificationScope
diff --git a/ModificationScope b/ModificationScope
new file mode 100644
index 000..ea949ee
--- /dev/null
+++ b/ModificationScope
@@ -0,0 +1,3 @@
+Changes to: QEMU, Gue
Signed-off-by: Wei Wang
---
FutureWorks | 21 +
1 file changed, 21 insertions(+)
create mode 100644 FutureWorks
diff --git a/FutureWorks b/FutureWorks
new file mode 100644
index 000..210edcd
--- /dev/null
+++ b/FutureWorks
@@ -0,0 +1,21 @@
+The vhost-pci design is curren
I doubt you have a different issue. My VM has randomly hanged my
computer without a shut down a few times during the life of this bug,
and there are two very possible ways it could happen: the VM suddenly
crashed, making a situation similar to it shutting down, or something in
your host caused some
- Original Message -
> From: "Peter Maydell"
> To: "Paolo Bonzini"
> Cc: "QEMU Developers"
> Sent: Friday, May 27, 2016 6:38:10 PM
> Subject: Re: [Qemu-devel] [PULL v3 00/31] Misc changes for 2016-05-27
>
> On 27 May 2016 at 17:11, Paolo Bonzini wrote:
> > The following changes since
From: Wei Xu
Field 'coalesced' is to indicate how many packets are coalesced and field
'dup_ack' is how many duplicate acks are merged, guest driver can use these
information to notify what's the exact scene of original traffic over the
networks.
Signed-off-by: Wei Xu
---
hw/net/virtio-net.c
From: Wei Xu
All the data packets in a tcp connection will be cached to a big buffer
in every receive interval, and will be sent out via a timer, the
'virtio_net_rsc_timeout' controls the interval, the value will influent the
performance and response of tcp connection extremely, 5(50us) is a
From: Wei Xu
Most stuffs are like ipv4 2 differences between ipv4 and ipv6.
1. Fragment length in ipv4 header includes itself, while it's not
included for ipv6, thus means ipv6 can carry a real '65535' payload.
2. IPv6 header does not need calculate header checksum.
Signed-off-by: Wei Xu
---
From: Wei Xu
Changes in V6:
- Sync upstream code
- Split new fields in 'virtio_net_hdr' to a seperate patch
- Remove feature bit code, replace it with a command line parameter 'guest_rsc'
which is turned off by default.
Changes in V5:
- Passed all IPv4/6 test cases
- Add new fields in 'virtio_ne
Build on top of Marcel's -device for IOMMUs patches, add a device property.
Sorry, no reference at hand.
Jan
Mit TouchDown von meinem Android-Telefon gesendet (www.symantec.com)
-Original Message-
From: Aviv B.D. [bd.a...@gmail.com]
Received: Samstag, 28 Mai 2016, 18:12
To: Kiszka, Jan
What is the best way to add this configuration option?
Aviv.
On Tue, May 24, 2016 at 12:25 PM Jan Kiszka wrote:
> On 2016-05-24 10:14, Jason Wang wrote:
> > On 2016年05月22日 00:19, Aviv B.D wrote:
> >> From: "Aviv Ben-David"
> >>
> >> This flag tells the guest to invalidate tlb cache also after
On Sat, May 28, 2016 at 7:02 PM Alex Williamson
wrote:
> On Sat, 28 May 2016 10:52:58 +
> "Aviv B.D." wrote:
>
> > Hi,
> > Your idea to search the relevent VTDAddressSpace and call it's notifier
> > will
> > probably work. Next week I'll try to implement it (for now with the
> costly
> > sca
On Sat, 28 May 2016 10:52:58 +
"Aviv B.D." wrote:
> Hi,
> Your idea to search the relevent VTDAddressSpace and call it's notifier
> will
> probably work. Next week I'll try to implement it (for now with the costly
> scan
> of each context).
I think an optimization we can make is to use pci_f
On Fri, 27 May 2016 22:43:54 +
"Tian, Kevin" wrote:
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Friday, May 27, 2016 10:55 PM
> >
> > On Fri, 27 May 2016 11:02:46 +
> > "Tian, Kevin" wrote:
> >
> > > > From: Alex Williamson [mailto:alex.william...@redhat.c
Just a small note:
It's more like RFC. I don't think 8 bits would be enough for all possible
policies and I don't know whether it is possible to maintain backward
compatibility by keeping VMSD .minimum_version_id. "loadvm" refused to accept
old ptimer VMState, I haven't looked at it much.
--
On 25/05/16 04:13, Emilio G. Cota wrote:
> For some workloads such as arm bootup, tb_phys_hash is performance-critical.
> The is due to the high frequency of accesses to the hash table, originated
> by (frequent) TLB flushes that wipe out the cpu-private tb_jmp_cache's.
> More info:
> https://lis
On 25/05/16 04:13, Emilio G. Cota wrote:
> This will be used by upcoming changes for hashing the tb hash.
>
> Add this into a separate file to include the copyright notice from
> xxhash.
>
> Reviewed-by: Richard Henderson
> Signed-off-by: Emilio G. Cota
Reviewed-by: Sergey Fedorov
> ---
> inc
On 28/05/16 00:10, Emilio G. Cota wrote:
> On Fri, May 27, 2016 at 23:53:01 +0300, Sergey Fedorov wrote:
>> On 25/05/16 04:13, Emilio G. Cota wrote:
>>> Taken from the linux kernel.
>>>
>>> Reviewed-by: Richard Henderson
>>> Reviewed-by: Alex Bennée
>>> Signed-off-by: Emilio G. Cota
>>> ---
>>>
On Fri, 05/27 17:37, Paolo Bonzini wrote:
>
>
> On 27/05/2016 17:30, Peter Maydell wrote:
> > This version fails on the "retypedefing a typedef" clang warning:
> >
> > /home/petmay01/linaro/qemu-for-merges/hw/scsi/scsi-disk.c:73:3: error:
> > redefinition of typedef 'SCSIDiskClass' is a C11 feat
On 05/28/2016 11:52 AM, David Gibson wrote:
> On Fri, May 27, 2016 at 09:56:32AM +0200, Cédric Le Goater wrote:
>> On 05/27/2016 05:38 AM, David Gibson wrote:
>>> On Tue, May 03, 2016 at 06:03:29PM +0200, Cédric Le Goater wrote:
From: Benjamin Herrenschmidt
We use an env. flag which
Hi,
Your idea to search the relevent VTDAddressSpace and call it's notifier
will
probably work. Next week I'll try to implement it (for now with the costly
scan
of each context).
I still not sure if populating the MemoryRegion will suffice for hot plug
vfio
device but i'll try to look into it.
As
On Fri, May 27, 2016 at 09:56:32AM +0200, Cédric Le Goater wrote:
> On 05/27/2016 05:38 AM, David Gibson wrote:
> > On Tue, May 03, 2016 at 06:03:29PM +0200, Cédric Le Goater wrote:
> >> From: Benjamin Herrenschmidt
> >>
> >> We use an env. flag which is set to the initial value of MSR_HVB in
> >>
Public bug reported:
I give a host usb device to guest in the way of passthrough,use "virsh
attach-device" cmd. In guest os,use "lsusb" cmd I can see two devices have been
added,one is usb device and the other is usb-hub(0409:55aa NEC Corp. Hub).
when I use "virsh detach-device" detach the usb d
Public bug reported:
I give a host usb device to guest in the way of using "virsh attach-device"
cmd. In guest os,use "lsusb" cmd I can see two devices have been added,one is
usb device and the other is usb-hub(0409:55aa NEC Corp. Hub).
when I use "virsh detach-device" detach the usb device,in g
50 matches
Mail list logo