xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Marcin Cieslak <saper@saper.info>
To: "Roger Pau Monné" <royger@FreeBSD.org>
Cc: freebsd-xen@FreeBSD.org, freebsd-virtualization@freebsd.org,
	xen-devel@lists.xenproject.org
Subject: Re: HEADS UP: Imported Xen 4.7: no blkback
Date: Mon, 13 Jun 2016 09:44:35 +0000	[thread overview]
Message-ID: <alpine.BSF.2.11.1606130941440.2130__19654.5783700005$1465811152$gmane$org@z.fncre.vasb> (raw)
In-Reply-To: <20160613091003.cejnbuqepp25zanc@mac>

On Mon, 13 Jun 2016, Roger Pau Monné wrote:

> Since you mention that the console is very slow, if you run 'top' on Dom0, 
> do you see any process (eg: qemu) taking a lot of CPU time?
> 
> Also, do you see Dom0 consuming a lot of CPU if you run 'xentop'?

Just quick info regarding console problem at the mountroot prompt:

- it was also very slow and behaving strange with older kernel
and 4.5.2.

- it works better when I use dual console - one can type on the 
serial console and see the results immediately, vidconsole
is slower but thins seem to work (at least I get no panics
due to "cannot mount root" anymore).

- will check top

Marcin

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-06-13  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160603120921.y5l362zgrhf4fdcb@mac>
2016-06-08 22:18 ` HEADS UP: Imported Xen 4.7 and blkback changes Marcin Cieslak
     [not found] ` <alpine.BSF.2.11.1606082204080.2130@z.fncre.vasb>
2016-06-08 22:35   ` HEADS UP: Imported Xen 4.7 and blkback changes - domU respawning on_crash Marcin Cieslak
2016-06-09  7:40   ` HEADS UP: Imported Xen 4.7 and blkback changes Roger Pau Monné
     [not found]   ` <alpine.BSF.2.11.1606082229190.2130@z.fncre.vasb>
2016-06-09  7:44     ` HEADS UP: Imported Xen 4.7 and blkback changes - domU respawning on_crash Roger Pau Monné
     [not found]   ` <20160609074021.uqtjio2vn7wo5h4m@mac>
2016-06-10 21:41     ` HEADS UP: Imported Xen 4.7 and blkback changes Marcin Cieslak
     [not found]     ` <alpine.BSF.2.11.1606102140290.2130@z.fncre.vasb>
2016-06-13  9:22       ` Roger Pau Monné
2016-06-09  0:16 ` HEADS UP: Imported Xen 4.7: no blkback Marcin Cieslak
     [not found] ` <alpine.BSF.2.11.1606090010280.2130@z.fncre.vasb>
2016-06-09  8:03   ` Roger Pau Monné
     [not found]   ` <20160609080343.44rvpda4hskiy3ge@mac>
2016-06-09  9:07     ` Wei Liu
2016-06-10 21:38     ` Marcin Cieslak
     [not found]     ` <alpine.BSF.2.11.1606102124330.2130@z.fncre.vasb>
2016-06-13  9:10       ` Roger Pau Monné
     [not found]       ` <20160613091003.cejnbuqepp25zanc@mac>
2016-06-13  9:44         ` Marcin Cieslak [this message]
2016-06-13 19:26         ` Marcin Cieslak
     [not found]         ` <alpine.BSF.2.11.1606131922240.2130@z.fncre.vasb>
2016-06-16 15:29           ` Roger Pau Monné
     [not found]           ` <20160616152919.3nelncwerh3nir27@mac>
2016-06-16 17:05             ` Marcin Cieslak

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='alpine.BSF.2.11.1606130941440.2130__19654.5783700005$1465811152$gmane$org@z.fncre.vasb' \
    --to=saper@saper.info \
    --cc=freebsd-virtualization@freebsd.org \
    --cc=freebsd-xen@FreeBSD.org \
    --cc=royger@FreeBSD.org \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: HEADS UP: Imported Xen 4.7: no blkback' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).