[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Re: Re: [Xen-devel] Updating Xen 4.1.x xmexamples files (vfb line required for HVM guests)



> Thus, there is only one other person I know benefited from that advice -    
> bderzhavets. However, I'll repeat the list of other threads in Xen-users of
> people with hvm problems:

No i didn't. There was long thread regarding GCC 4.6 problem when
building "hvmloader" ( F15, U 11.10 both has 4.6)

1. Stefano noticed that problem was GCC 4.6 when building "hvmloader"
2. Official fix was in the same thread
   http://xenbits.xen.org/hg/staging/xen-4.1-testing.hg/rev/1976adbf2b80.
Been back ported to 4.1.1 is resolves the issue.

There is build (PPA on Oneiric) and i believe xen-4.1.1-(X).fc16.src.rpm
already has this patch as well. Pasi knows it better.
Regarding Ubuntu 11.10 :-

https://launchpad.net/~bderzhavets/+archive/xen-4.1.1

Boris

--- On Mon, 8/1/11, jim burns <jim_burn@xxxxxxxxxxxxx> wrote:

From: jim burns <jim_burn@xxxxxxxxxxxxx>
Subject: [Xen-users] Re: Re: [Xen-devel] Updating Xen 4.1.x xmexamples files (vfb line required for HVM guests)
To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Date: Monday, August 1, 2011, 7:06 PM

Pasi said:
(sorry - my new kmail is having trouble quoting text)
> Interesting. Have others seen this problem?

In the thread I mention at the head of this thread - '[Xen-devel] Failure to
create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2)' -
I summarize several threads from people that have had problems starting hvm
domu's on xen 4.1.x. They all have similar log output to mine, namely:

qemu-dm:

xen be: console-0: xen be: console-0: initialise() failed

& hypervisor.log (xm dmesg) reports an MMIO error. The fix was either to
upgrade to xen 4.2 unstable, or downgrade to 4.0.x - at least until Konrad
proposed adding the vfb= line, in that same thread in Xen-users. This made 
4.1.x usable, and made the MMIO error go away (but not the 'xen be:' error).
Thus, there is only one other person I know benefited from that advice -    
bderzhavets. However, I'll repeat the list of other threads in Xen-users of
people with hvm problems:

> According to several threads, such as mine last month - '[Xen-users]
> Working with Fedora 15 & systemd' - and  '[Xen-users] Problems
> with HVM after upgrade from 4.0.1 to 4.1.1', and a private communication
with
> t.wagner in '[Xen-users] XEN-4.1.1 and linux kernel 3.0-rc5', and finally
> '[Xen-users] Re: Trouble starting HVM domU with Linux 3.0.0 and Xen 4.1.1',

and one I omitted, from the beginning of July: '[Xen-users] Starting basic HVM
-- where am I going wrong?' from Sam Mulvey.

> I don't think vfb-line is supposed to be needed with HVM guests..

It hasn't been needed since xen 3.2.x (maybe even 3.0.x) until 4.1.x, and
again reportedly not needed for 4.2 unstable ( I haven't worked with it, yet).

Thank you for continuing to take an interest in this.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.