Will this fix make it into 6.2?
On 11/12/2021 3:51 PM, Igor Mammedov wrote:
On Fri, 12 Nov 2021 17:53:42 +
Daniel P. Berrangé wrote:
On Fri, Nov 12, 2021 at 12:35:07PM -0500, Brian Rak wrote:
In 6.1, a guest with 15 empty pcie-root-port devices will not boot properly
- it just hangs on
In 6.1, a guest with 15 empty pcie-root-port devices will not boot
properly - it just hangs on "Guest has not initialized the display
(yet).". As soon as I remove the last pcie-root-port, the guest begins
starting up normally. My qemu command line:
/usr/libexec/qemu-kvm -name guest=xxx,debug
We ran into this as well, using qemu 2.11.0. We're not using the "-k
en-us" command line flag, and we're using noVNC as a client (which
supports the QEMUExtendedKeyEvent encoding)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https
he drop counter incrementing)
On 1/19/2018 3:28 PM, Brian Rak wrote:
We've been running into a fairly persistent issue where virtio_net
adapters will suddenly stop sending packets when running under KVM.
This has persisted through several qemu versions, and a large number
of guest ker
We've been running into a fairly persistent issue where virtio_net
adapters will suddenly stop sending packets when running under KVM.
This has persisted through several qemu versions, and a large number of
guest kernel upgrades.
What we end up seeing is the guest continuing to receive packet
Public bug reported:
Since 2.9 / 07e95cd529af345fdeea230913f68eff5b925bb6 , whenever the VNC
websocket server finds an error with the incoming connection request, it
just closes the socket with no further information.
This makes figuring out what's wrong with the request nearly impossible.
I wou
On 2/10/2017 3:35 AM, Brad Campbell wrote:
On 03/02/17 01:14, Brian Rak wrote:
We recently upgraded to qemu 2.8.0, and noticed a bunch of issues with
various non-linux operating systems.
I was able to bisect this down to
83d768b5640946b7da55ce8335509df297e2c7cd being the commit that breaks
We recently upgraded to qemu 2.8.0, and noticed a bunch of issues with
various non-linux operating systems.
I was able to bisect this down to
83d768b5640946b7da55ce8335509df297e2c7cd being the commit that breaks
things (0687c37c5eeef8580b31cc6e1202d874833ae38a which is immediately
prior still
On 1/30/2017 5:51 AM, Daniel P. Berrange wrote:
On Fri, Jan 27, 2017 at 06:08:20PM +, Daniel P. Berrange wrote:
On Fri, Jan 27, 2017 at 09:35:38AM +, Daniel P. Berrange wrote:
On Tue, Jan 24, 2017 at 05:02:25PM -0500, Brian Rak wrote:
We've been considering switching over to
We've been considering switching over to using qemu's built in
websockets support (to avoid the overhead of needing websockify
running). We've been seeing very poor performance after the switch (it
takes the console 4-5 seconds to update after pressing a key). So far,
I haven't been able to f
On 9/14/2016 12:35 AM, Michael S. Tsirkin wrote:
On Tue, Sep 13, 2016 at 11:09:27PM +0200, Laszlo Ersek wrote:
Hi,
(CC Michael and Cornelia,)
On 09/13/16 21:10, Brian Rak wrote:
I have some KVM hosts that I just upgraded to qemu 2.7.0. When the host
is running a kernel newer then 3.19
},
+{ SCMP_SYS(getrusage), 245 },
{ SCMP_SYS(set_tid_address), 245 },
{ SCMP_SYS(statfs), 245 },
{ SCMP_SYS(unlink), 245 },
--
2.8.2
On 9/13/2016 4:12 AM, Eduardo Otubo wrote:
On Wed, Sep 7, 2016 at 9:55 PM, Brian Rak wrote:
--- src_clean/qemu-seccomp.c2016-09-02 11:34:22.0
I have some KVM hosts that I just upgraded to qemu 2.7.0. When the host
is running a kernel newer then 3.19, everything works fine.
If the host is running on something lower then 3.19, some guests fail to
start. I noticed this on a Ubuntu 16.04 guest, it fails to find the
virtio NIC, and thi
18:41 Brian Rak <mailto:b...@gameservers.com>> wrote:
I've been testing out 2.7.0 with seccomp support. Whenever I
connect to
the VNC console, the process gets killed by the kernel. dmesg shows:
audit: type=1326 audit(1473175350.674:2): auid=0 uid=107 gid=107
ses=42
I've been testing out 2.7.0 with seccomp support. Whenever I connect to
the VNC console, the process gets killed by the kernel. dmesg shows:
audit: type=1326 audit(1473175350.674:2): auid=0 uid=107 gid=107
ses=423110 pid=32202 comm="qemu-kvm" exe="/bin/qemu-system-x86_64"
sig=31 arch=c03
I have two Ubuntu 14.04 KVM instances (kernel version
3.16.0-29-generic). (Running under qemu 2.2.0) They're connected using
qemu's 'multicast' network type, and basic connectivity works fine. I
can ping between the guests, they can transfer data, etc.
I'll refer to them this way:
guest1 -
I'm trying to track down some CPU usage issues we're having with some
virtual machines. Basically, when we run our application under KVM, we
see about 2x the CPU usage that we would see if we were running it on
bare metal.
kvm_stat shows me the following:
efer_reload 0
17 matches
Mail list logo
