From: Wakko Warner <wakko@animx.eu.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Issue with KVM under 4.10 and above
Date: Thu, 14 Dec 2017 20:21:46 -0500 [thread overview]
Message-ID: <20171215012146.GA17818@animx.eu.org> (raw)
In-Reply-To: <20171207021929.GA29924@animx.eu.org>
Anyone ?
Wakko Warner wrote:
> Starting with 4.10-rc1, I'm seeing an issue with a VM that boots an old
> kernel. The VM uses kernel 3.3.0 and is booted directly by qemu. This VM
> is a copy of a physical machine.
>
> During boot, it hangs for several seconds on "Using IPI No-Shortcut mode".
> The next line shows something about ata5 link down. According to the kernel
> timing, the difference is less than .3 seconds, however many seconds had
> actually passed. During boot, after fsck finishes, nothing happens, it's
> like it's hung. When I issue "sleep 1", it takes way longer than 1 second
> to complete.
>
> I made a copy of another system that has an old kernel (2.6.36.2). It
> boots, but it hangs for a few seconds after TCP cubic registered then prints
> ata4 link down. Issueing "sleep 1" takes a long time. I also noticed that
> issueing date several times shows the same date each time, even several
> minutes later.
>
> This worked with 4.9.65 and 67 (and older).
>
> If I change the qemu command line to not use KVM, it works fine, although
> it runs slower.
>
> I tested some other VMs that use newer kernels (like 4.4.4). They work OK.
> with the host being 4.10. I tested linuxmint 18.1 without problems.
> Issueing date several times shows the time incrementing as expected.
--
Microsoft has beaten Volkswagen's world record. Volkswagen only created 22
million bugs.
prev parent reply other threads:[~2017-12-15 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 2:19 Wakko Warner
2017-12-15 1:21 ` Wakko Warner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171215012146.GA17818@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®