* [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
@ 2013-11-21 20:46 Martin van den Nieuwelaar
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
` (4 more replies)
0 siblings, 5 replies; 9+ messages in thread
From: Martin van den Nieuwelaar @ 2013-11-21 20:46 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a separate
machine and run the script and it will display the '2 second' issue, but
as soon as you move the mouse pointer constantly in the VNC console
window the script starts behaving normally with updates every second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD host.
Running an OpenBSD VM on a Linux host does not exhibit the problem for
me. I also belive (am told) that a Linux VM running on an OpenBSD host
does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue - going
back to OpenBSD distros from two years ago still have the problem. This
is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set command
line option, but I've since gone through many of the options in the man
page simply trying different values (eg. different CPU types ( -cpu) ,
different emulated PC (-M)) but so far the problem remains.
I'm quite happy to run tests in order to track this bug down better. We
use qemu running on OpenBSD extensively and find it very useful!
** Affects: qemu
Importance: Undecided
Status: New
** Tags: openbsd sleep time
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
@ 2013-11-27 12:58 ` Paolo Bonzini
2013-11-27 20:42 ` Martin van den Nieuwelaar
2013-11-27 22:16 ` Martin van den Nieuwelaar
2014-01-28 3:12 ` Martin van den Nieuwelaar
` (3 subsequent siblings)
4 siblings, 2 replies; 9+ messages in thread
From: Paolo Bonzini @ 2013-11-27 12:58 UTC (permalink / raw)
To: qemu-devel
Hi, please test qemu 1.7.0-rc. There were several changes to the timer
machinery that can help this bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
@ 2013-11-27 20:42 ` Martin van den Nieuwelaar
2013-11-27 22:16 ` Martin van den Nieuwelaar
1 sibling, 0 replies; 9+ messages in thread
From: Martin van den Nieuwelaar @ 2013-11-27 20:42 UTC (permalink / raw)
To: qemu-devel
I'll have a look at it now.
Regards,
-Martin
On 28/11/13 01:58, Paolo Bonzini wrote:
> Hi, please test qemu 1.7.0-rc. There were several changes to the timer
> machinery that can help this bug.
>
--
R A Ward Ltd. | We take the privacy of our customers seriously.
Christchurch | All sensitive E-Mail attachments MUST be encrypted.
New Zealand
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
2013-11-27 20:42 ` Martin van den Nieuwelaar
@ 2013-11-27 22:16 ` Martin van den Nieuwelaar
1 sibling, 0 replies; 9+ messages in thread
From: Martin van den Nieuwelaar @ 2013-11-27 22:16 UTC (permalink / raw)
To: qemu-devel
I downloaded 1.7.0-rc2 and compiled it. Running it, I see the version
number reported as 1.6.92!?
In any case, I don't see any improvement, ie. the bug is still there.
Regards,
-Martin
On 28/11/13 01:58, Paolo Bonzini wrote:
> Hi, please test qemu 1.7.0-rc. There were several changes to the timer
> machinery that can help this bug.
>
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
@ 2014-01-28 3:12 ` Martin van den Nieuwelaar
2016-11-10 1:16 ` [Qemu-devel] [Bug 1253777] Fix included in openstack/python-tripleoclient 0.0.10 OpenStack Infra
` (2 subsequent siblings)
4 siblings, 0 replies; 9+ messages in thread
From: Martin van den Nieuwelaar @ 2014-01-28 3:12 UTC (permalink / raw)
To: qemu-devel
Hadn't heard any news on this bug so decided to check the latest source.
1.7.0 now available so downloaded it and compiled it. No mean feat in
itself for OpenBSD. FWIW it seemed a lot more difficult than for
earlier (1.6.x) versions. 1.7.0 now reports its version as 1.7.0 - a
good start. Alas the "2 second" bug still appears to be there.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Qemu-devel] [Bug 1253777] Fix included in openstack/python-tripleoclient 0.0.10
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
2014-01-28 3:12 ` Martin van den Nieuwelaar
@ 2016-11-10 1:16 ` OpenStack Infra
2017-01-23 19:32 ` [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Thomas Huth
2017-03-25 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 9+ messages in thread
From: OpenStack Infra @ 2016-11-10 1:16 UTC (permalink / raw)
To: qemu-devel
This issue was fixed in the openstack/python-tripleoclient 0.0.10
release.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
New
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
` (2 preceding siblings ...)
2016-11-10 1:16 ` [Qemu-devel] [Bug 1253777] Fix included in openstack/python-tripleoclient 0.0.10 OpenStack Infra
@ 2017-01-23 19:32 ` Thomas Huth
2017-01-23 21:00 ` Martin van den Nieuwelaar
2017-03-25 4:17 ` Launchpad Bug Tracker
4 siblings, 1 reply; 9+ messages in thread
From: Thomas Huth @ 2017-01-23 19:32 UTC (permalink / raw)
To: qemu-devel
What does comment #5 mean? Is this issue now fixed with the latest
version of QEMU?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
Incomplete
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2017-01-23 19:32 ` [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Thomas Huth
@ 2017-01-23 21:00 ` Martin van den Nieuwelaar
0 siblings, 0 replies; 9+ messages in thread
From: Martin van den Nieuwelaar @ 2017-01-23 21:00 UTC (permalink / raw)
To: qemu-devel
I hadn't seen comment #5. Not sure how that affects qemu.
Unfortunately I'm not in a position to set up a system any time soon
with the latest versions of everything to see if the bug is still present.
On 24/01/17 08:32, Thomas Huth wrote:
> What does comment #5 mean? Is this issue now fixed with the latest
> version of QEMU?
>
> ** Changed in: qemu
> Status: New => Incomplete
>
--
R A Ward Ltd. | We take the privacy of our customers seriously.
Christchurch | All sensitive E-Mail attachments MUST be encrypted.
New Zealand
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
Incomplete
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
` (3 preceding siblings ...)
2017-01-23 19:32 ` [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Thomas Huth
@ 2017-03-25 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 9+ messages in thread
From: Launchpad Bug Tracker @ 2017-03-25 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1253777
Title:
OpenBSD VM running on OpenBSD host has sleep calls taking twice as
long as they should
Status in QEMU:
Expired
Bug description:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constantly in the VNC window, the script runs normally with updates
every second! Note that the script doesn't have to be running on the
VM's console - it's also possible to (say) ssh to the VM from a
separate machine and run the script and it will display the '2 second'
issue, but as soon as you move the mouse pointer constantly in the VNC
console window the script starts behaving normally with updates every
second.
I have only seen this bug when running an OpenBSD VM on an OpenBSD
host. Running an OpenBSD VM on a Linux host does not exhibit the
problem for me. I also belive (am told) that a Linux VM running on an
OpenBSD host does not exhibit the problem.
I have been using the OpenBSD 5.4 64 bit distro which comes with qemu
1.5.1 in a package, however I tried compiling qemu 1.6.1 and that has
the same bug. In fact older OpenBSD distros have the same issue -
going back to OpenBSD distros from two years ago still have the
problem. This is not a 'new' bug recently introduced.
Initially I wondered if it could be traced to an incorrectly set
command line option, but I've since gone through many of the options
in the man page simply trying different values (eg. different CPU
types ( -cpu) , different emulated PC (-M)) but so far the problem
remains.
I'm quite happy to run tests in order to track this bug down better.
We use qemu running on OpenBSD extensively and find it very useful!
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1253777/+subscriptions
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-03-25 4:30 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-21 20:46 [Qemu-devel] [Bug 1253777] [NEW] OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Martin van den Nieuwelaar
2013-11-27 12:58 ` [Qemu-devel] [Bug 1253777] " Paolo Bonzini
2013-11-27 20:42 ` Martin van den Nieuwelaar
2013-11-27 22:16 ` Martin van den Nieuwelaar
2014-01-28 3:12 ` Martin van den Nieuwelaar
2016-11-10 1:16 ` [Qemu-devel] [Bug 1253777] Fix included in openstack/python-tripleoclient 0.0.10 OpenStack Infra
2017-01-23 19:32 ` [Qemu-devel] [Bug 1253777] Re: OpenBSD VM running on OpenBSD host has sleep calls taking twice as long as they should Thomas Huth
2017-01-23 21:00 ` Martin van den Nieuwelaar
2017-03-25 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.