Port-xen archive

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

Re: Unable to create HVM or PV domUs with Xen 4.1

On 04/15/11 11:35, Manuel Bouyer wrote:
> On Thu, Apr 14, 2011 at 07:51:53PM +0100, Hugo Silva wrote:
>> root@dom0:/usr/pkgsrc/sysutils/xentools33# grep bridge Makefile
>> XEND_SCRIPTS=           block vif-bridge vif-ip qemu-ifup xen-subr
>> root@dom0:/usr/pkgsrc/sysutils/xentools33# cd ../xentools41/
>> root@dom0:/usr/pkgsrc/sysutils/xentools41# grep bridge Makefile
>> root@dom0:/usr/pkgsrc/sysutils/xentools41#
>> root@dom0:/usr/pkgsrc/sysutils/xentools41# grep vif-bridge PLIST
>> root@dom0:/usr/pkgsrc/sysutils/xentools41# grep vif-bridge
>> ../xentools33/PLIST
>> share/examples/xen/vif-bridge
>> # ls /usr/pkg/etc/xen/scripts/
>> hotplugpath.sh
>> Hmmm....
>> Should the scripts have been placed in scripts/ ? I find it hard to
>> believe that the others who have reported success with running HVM would
>> not have found this.
> OK, the install target did install these scripts directly in etc/xen/scripts
> (which is wrong) and didn't record them in the package.
> now that USE_DESTDIR is the default, the files are in ${DESTDIR}
> but not installed on the system.
> I fixed the package.

Uninstalled xentools41, updated pkgsrc tree:

=> Applying pkgsrc patches for xentools41-4.1.0nb1
Ignoring patch file /usr/pkgsrc/sysutils/xentools41/patches/patch-ak:
invalid checksum
ERROR: Patching failed due to modified or broken patch file(s):
ERROR:  /usr/pkgsrc/sysutils/xentools41/patches/patch-ak
*** Error code 1

I double checked: removed the xentools41 directory and then cvs update'd

>> Related question: is PV working?
> Yes, but with xm only.

Out of curiosity, could you elaborate on what's not working with xl+PV?
(is it a NetBSD problem, what is needed to fix it, etc)

Will this condition break automatic startup of PV domains
(xendomains="...") ?

Oh, another thing: I noticed the following:

# /etc/rc.d/xencommons stop
/etc/rc.d/xencommons: WARNING: $xend is not set properly - see rc.conf(5).
$xend is not enabled - see rc.conf(5).
Use the following if you wish to perform the operation:
  /etc/rc.d/xencommons onestop

Is this by design? I'm still getting up to speed with the 4.1
differences, but my impression so far is that xend is not required in
4.1 (unless using xm - which as you explained above is needed, for now)

Is that correct? Say whatever problem affecting xl+PV guests is fixed;
Would one still be required to run xend with 4.1?

Regarding my problem with being unable to start HVM/PV guests, it seems
it may be related to
http://mail-index.netbsd.org/port-xen/2011/04/04/msg006586.html. I have
cc'd Sverre, maybe he has something to add to the discussion.

As usual, thank you for taking the time to read my many questions :)


Home | Main Index | Thread Index | Old Index