Message-ID: <1348830659.21090.19.camel@df1844j>
Subject: Re: [alpine-devel] Xen: first experiments
From: Leonardo <rnalrd@gmail.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: alpine-devel <alpine-devel@lists.alpinelinux.org>
Date: Fri, 28 Sep 2012 13:10:59 +0200
In-Reply-To: <50656E8C.6070206@citrix.com>
References: <1348823298.21090.14.camel@df1844j>
	 <50656E8C.6070206@citrix.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-J8UlXFt1URlJq0HrbRhW"
Precedence: list
Mime-Version: 1.0


--=-J8UlXFt1URlJq0HrbRhW
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2012-09-28 at 10:31 +0100, Roger Pau Monne wrote:
> Leonardo wrote:
>=20
> Hello!
>=20
> Thanks for trying Xen with Alpine!
>=20
> > Hi,
> >=20
> > I've just started to play with alpine-xen-2.4.5-x86_64 iso + libvirt,
> > and I've hit the first issues.
> >=20
> > So far I've followed http://wiki.alpinelinux.org/wiki/Xen_LiveCD, setup
> > my local storage, installed and started libvirt.
>=20
> So I assume you are running it from RAM? If you are interested in this
> kind of setup, I would recommend that you create a new ISO/USB with the
> dom0_mem command line option [1], something like dom0_mem=3D512M or maybe
> dom0_mem=3D1024M, since you seem to have quite a lot of memory. This will
> prevent errors from the ballon driver, which as far as I know can be a
> little slow and I'm not sure if it plays well with ramfs.

I've added "dom0_mem=3D512M,max:512M" and this fixed the problem.

>=20
> Could you also paste the output from `free -m` and `df -h`?

# free -m
             total         used         free       shared      buffers
Mem:           425          252          172            0            3
-/+ buffers:                249          175
Swap:            0            0            0

# df -h
Filesystem                Size      Used Available Use% Mounted on
mdev                      1.0M         0      1.0M   0% /dev
shm                     212.8M         0    212.8M   0% /dev/shm
/dev/usbdisk              3.7G    105.9M      3.6G   3% /media/usb
tmpfs                   212.8M    115.5M     97.3M  54% /
tmpfs                   212.8M    176.0K    212.6M   0% /run
rc-svcdir                 1.0M     72.0K    952.0K   7% /lib/rc/init.d
cgroup_root              10.0M         0     10.0M   0% /sys/fs/cgroup
/dev/loop0               46.1M     46.1M         0 100% /.modloop
/dev/sda2                68.1G      1.4G     63.4G   2% /var


>=20
> Anyway, I would recommend making sure that everything works with xl, and
> then try to use libvirt (I've never used it, so I'm not sure of how well
> it works).

Yeah. That's why I want to use "xl". And I'm also interested in fixing
libvirt.

>=20
> > When creating a new domain via libvirt, it reports this error:
> >=20
> > xc: detail: Failed allocation for dom 2: 2048 extents of order 0
> > xc: error: Could not allocate memory for HVM guest. (16 =3D Device or
> > resource busy): Internal error
> >=20
> > Googling around I've found this:
> >=20
> > "Sufficient memory was not reserved for fully virtualized guests when
> > creating new guests. Memory listed as available by the xm info command
> > could not be fully allocated to the guest. When attempting create a
> > fully virtualized guest with more than or equal to the maximum availabl=
e
> > memory value, the following error message would appear:=20
> > Error: (1, 'Internal error', 'Could not allocate memory for HVM guest.\=
n (16 =3D Device or resource busy)')
> > This issue has been resolved by improving the memory balloon driver to
> > correctly allocate memory for fully virtualized guests and fully
> > virtualized guests using the Intel VT-d extensions for PCI passthrough.
> > (BZ#512041)"
> >=20
> > (from http://www.centos.org/docs/5/html/5.5/Technical_Notes/xen.html
> > )
> >=20
> > This is what "xl info" reports:
> >=20
> > kvbn1:~# xl info
> > host                   : kvbn1
> > release                : 3.3.8-grsec
> > version                : #4-Alpine SMP Tue Jul 17 13:08:00 UTC 2012
> > machine                : x86_64
> > nr_cpus                : 8
> > nr_nodes               : 2
> > cores_per_socket       : 4
> > threads_per_core       : 1
> > cpu_mhz                : 2128
> > hw_caps                :
> > bfebfbff:28100800:00000000:00003b40:009ce3bd:00000000:00000001:00000000
> > virt_caps              : hvm hvm_directio
> > total_memory           : 8179
> > free_memory            : 909
> > free_cpus              : 0
> > xen_major              : 4
> > xen_minor              : 1
> > xen_extra              : .2
> > xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
> > hvm-3.0-x86_32p hvm-3.0-x86_64=20
> > xen_scheduler          : credit
> > xen_pagesize           : 4096
> > platform_params        : virt_start=3D0xffff800000000000
> > xen_changeset          : unavailable
> > xen_commandline        :=20
> > cc_compiler            : gcc version 4.6.3 (Alpine 4.6.3-r0)=20
> > cc_compile_by          : buildozer
> > cc_compile_domain      : alpinelinux.org
> > cc_compile_date        : Fri Jun 22 14:59:04 UTC 2012
> > xend_config_format     : 4
> >=20
> >=20
> > I'd like also to try creating a domain without libvirt, and I tried
> > following this http://wiki.xen.org/wiki/Xen_Beginners_Guide. However I
> > cannot find on Alpine a xen-tools package to run "xen-create-image", fo=
r
> > creating a config file to feed to "xl" in order to create a domain.
>=20
> xen-create-image is a Debian tool, which is not present in Alpine. If
> you wish, you can try creating a Alpine Linux DomU [2] or a Debian DomU
> with NetInstall [3].

Sorry, I've missed the wiki doc about AL PV DomU.

Thank you!

- leonardo

--=-J8UlXFt1URlJq0HrbRhW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAABAgAGBQJQZYXDAAoJELAPckZGG2T6+dcH/3mc2XYujK9WmZicSUTK0hBd
YyQDh67OTxBty68ejlbiwjfWO/Uh+stzeJ471MVrAd+cf/8lr5o0dwjwTIpJ4H2S
Z+0qfv/GgyTJ1RtYB7/bs+Lm+NP05srbZOvyLSsH86/x3ulb+dMtI7+4ewFK8q+X
kbNtTgsbiKx1pswDK9yoEtk38JmGENXhtG5JWi/+iQjSseaf/g3fjbiW95DsTQyW
lYt3ISkF603jWlaE7cT+IApu2ZQx5GoBRaBBlQc9qt+vLORw26TcLpadGq34bJLz
c4YmS9iOq7gKJ8coJ6oWOJ42xqafke6feiDHRU/DP/XXJQxoqlhVWc40hbiqrog=
=VY8+
-----END PGP SIGNATURE-----

--=-J8UlXFt1URlJq0HrbRhW--



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---