From mboxrd@z Thu Jan 1 00:00:00 1970 From: soapcn Subject: Re: Xen4.7 unable to get domain type for domid Date: Tue, 29 Sep 2015 19:45:40 -0400 Message-ID: <560B22A4.1020102@gmail.com> References: <56096505.3040109@gmail.com> <5609F64F.80609@gmail.com> <20150929220653.GF4243@bitfolk.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0438507319865840421==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Meng Xu , Andy Smith Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0438507319865840421== Content-Type: multipart/alternative; boundary="------------000700010609010800010106" This is a multi-part message in MIME format. --------------000700010609010800010106 Content-Type: text/plain; charset=utf-8; format=flowed Content-Length: 2273 Content-Transfer-Encoding: quoted-printable On 9/29/2015 7:19 PM, Meng Xu wrote: > HI Andy, > > 2015-09-29 18:06 GMT-04:00 Andy Smith >: > > Hi Tianyang, > > On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote: > > I keep getting this error about not being able to get domain type > > when I try to create a domU. > > Xen-4.7, Ubuntu 12.04 > > I also had this problem recently with regard to some Ubuntu 12.04 > domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on > earlier versions of Xen. I searched around a lot and found a few > other people with the same problem, but no answers. > > In the end I discovered that these domUs were using the > linux-image-virtual kernel package instead of the more usual > linux-image-generic. I installed linux-image-generic and > uninstalled linux-image-virtual, and then the affected domUs would > boot. > > I note also that I have some domUs with Ubuntu 12.04.01 using > linux-image-virtual and these are okay. So I assumed whatever > problem there was with that kernel was rectified by the time of the > 12.04.01 release. > > I hope that helps you. > > > Thank you very much for your suggestions! =E2=80=8B > > =E2=80=8BAfter Tianyang changed the netboot image used to =E2=80=8Bboot the domU, the > error disappears. > So it is likely that the linux-image provided by the ubuntu archive > that he uses is kind of broken. > > It is glad to know that it is not Xen's problem. :-) > > =E2=80=8BBest regards,=E2=80=8B > > =E2=80=8BMeng=E2=80=8B > > > > ----------- > Meng Xu > PhD Student in Computer and Information Science > University of Pennsylvania > http://www.cis.upenn.edu/~mengxu/ Andy, I really appreciate for your suggestions. Like Meng said, there is something wrong with the netboot image(precise) from archive.ubuntu.com. I downloaded one couple weeks ago and it worked. It's the most recent one that's broken and it's not Xen's problem. For the record, I didn't do further testing but images from these two won't work. http://mirror.pnl.gov/ubuntu/... http://archive.ubuntu.com/ubuntu/... Tianyang --------------000700010609010800010106 Content-Type: text/html; charset=utf-8 Content-Length: 4925 Content-Transfer-Encoding: quoted-printable On 9/29/2015 7:19 PM, Meng Xu wrote:

HI Andy,

2015-09-29 18:06 GMT-04:00 Andy Smith <andy@strugglers.net>:

Hi Tianyang,

On Mon, Sep 28, 2015 at 10:24:15PM -0400, soapcn wrote:
> I keep getting this error about not being able to get domain type
> when I try to create a domU.
> Xen-4.7, Ubuntu 12.04

I also had this problem recently with regard to some Ubuntu 12.04
domUs, but on Xen 4.4.1, Debian jessie. These domUs worked fine on
earlier versions of Xen. I searched around a lot and found a few
other people with the same problem, but no answers.

In the end I discovered that these domUs were using the
linux-image-virtual kernel package instead of the more usual
linux-image-generic. I installed linux-image-generic and
uninstalled linux-image-virtual, and then the affected domUs would
boot.

I note also that I have some domUs with Ubuntu 12.04.01 using
linux-image-virtual and these are okay. So I assumed whatever
problem there was with that kernel was rectified by the time of the
12.04.01 release.

I hope that helps you.

Thank you very much for your suggestions! =E2=80=8B
=C2=A0

=E2=80=8BAfter Tianyang changed the netboot image used to =E2=80=8Bboot the domU, the error disappears.=C2=A0

So it is likely that the linux-image provided by the ubuntu archive that he uses is kind of broken.=C2=A0

It is glad to know that it is not Xen's problem. :-)

=E2=80=8BBest regards,=E2=80=8B

=E2=80=8BMeng=E2=80=8B

-----------
Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania
http://www.cis.upenn.edu/~mengxu/

Andy,

I really appreciate for your suggestions. Like Meng said, there is something wrong with the netboot image(precise) from archive.ubuntu.com. I downloaded one couple weeks ago and it worked. It's the most recent one that's broken and it's not Xen's problem.

For the record, I didn't do further testing but images from these two won't work.

http://mirror.pnl.gov/ubuntu/...
http://archive.ubuntu.com/ubuntu/...

Tianyang

--------------000700010609010800010106-- --===============0438507319865840421== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0438507319865840421==--