Re: [Xen-devel] Does Xen-4.0 + pvops kernel still supports PV guest?

[Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>]

On Fri, 2010-12-17 at 14:51 +0000, Zhiyuan Shao wrote:
> On 12/17/2010 10:36 PM, Ian Campbell wrote:
> > On Fri, 2010-12-17 at 14:23 +0000, Zhiyuan Shao wrote:
> >> hi all,
> >>
> >> I had installed Xen-4.0 in my Ubuntu desktop (Maverick Meerkat, 10.10)
> >> according to https://help.ubuntu.com/community/Xen
> >>
> >> although, I had to replace grub 2.0 with old version to make everything
> >> work.
> >>
> >> After rebooting, I want to create a PV guest with old method I had used
> >> in Xen 3.4.2. However, I got the following messages, and the creation
> >> failed.
> >>
> >> zhiyuan@zhiyuan-ThinkPad-R400:~/xen_work/images/rhel51-pv$ sudo xm cr -c
> >> 1-pv.cfg
> >> [sudo] password for zhiyuan:
> >> Using config file "./1-pv.cfg".
> >> Error: (4, 'Out of memory', 'xc_dom_alloc_segment: segment ramdisk too
> >> large (0x11575>  0x4000 - 0x1b8f pages)\n')
> > 0x11575 pages is a 277M ramdisk, which, as the message says, is really
> > quite large. Especially compared with the 64M of RAM which you have
> > configured the guest with.
> >
> > Ian.
> >
> >
> OK, I changed the "memory" line to 800, but, seems it does not work also:
> 
> zhiyuan@zhiyuan-ThinkPad-R400:~/xen_work/images/rhel51-pv$ sudo xm cr -c 
> 1-pv.cfg
> Using config file "./1-pv.cfg".
> zhiyuan@zhiyuan-ThinkPad-R400:~/xen_work/images/rhel51-pv$ Error: Device 
> 2049 (vbd) could not be connected. Path closed or removed during hotplug 
> add: backend/vbd/1/2049 state: 1
> 
> and quite silently .....
> 
> But I am very sure the disk image path is correct. And tried also to 
> change "sda" to "hda" the result is the same.

pvops kernels require you to use xvda not sd* or hd*.

Ian.



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