Yes I am
French. I saw your post on ubuntu-fr. So welcome to Xen world
:)
That should
be a pretty long message so take a coffee and read it
entirely. I will make errors here while writting :)
Let do everything
step by step hoping to reply to all your questions. Here is
the plan
0) Did you have a
good PC for Xen? I will try to reply
1) about PV
domU and xen-create-image
2) about
HVM domU
3) to reply
to your mail
PV domU? HVM domU?
(This is my own point of view!)
* PV domU:
xen-create-image installs only a simple base Ubuntu machine
(no desktop :) ). You have to install it yourself. Typically
PV domU are usefull it you want a machine dedicated for a
server only like a Web Server, a FTP server etc....
A graphical
desktop can be installed by you have to do it yourself. You
can access this throuhg a console (see #1 below).
* HVM domU:
Usefull for desktop. But you have to do the installation
yourself from an ISO :( . To improve performance you need to
be sure that your CPU has the expected features for this.
0) Your CPU
is Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
If you have
a look at
Then you
will see
Technologie de
virtualisation Intel® (VT-x) Yes
Technologie de virtualisation Intel® pour les E/S répartis
(VT-d) Yes
So it means
that you are lucky your CPU is good for Xen :). That is the
first good new.
In human
language
Vt-x means
that you should be able to set up HVM domU (you should get
good performance)
Vt-d means
that you should be able to access real "parts" of your PC
through your HVM domU. By "parts" I mean graphical card, usb
etc....I will not explain this here
Now you have
to check if your MB is OK.
Your MB is
H97M-G43(MS-7924)
Virtualization
is available for this MB :) . You have to check if it is
available in your current BIOS version
-
Boot your PC
-
Go to your BIOS by pressing a button (here I can't tell you
which one)
-
Try to find "virtualization". If there is something about
"virtualization" then enable it.
-
Reboot your PC.
If
you don't find anything in your BIOS then it just means that
you are currently using a BIOS version without this feature.
But it does not mean that your MB didn't support it. It just
means that you have to upgrade your own BIOS version.
The
only way to know it is to go on the manufacture of your MB and
to check which one is available with "virtualization".
I will not
explain here how to upgrade a BIOS for Linux (it should take
another mail if needed! )
IMPORTANT
NOTICE BEFORE GOING AHEAD : Don't try any command that you
find on internet about
grep 'vmx
'/proc/cpuinfo'.
Because if
you boot your PC on a kernel with Xen then grep command above
will return nothing. Check it yourself by doing steps below.
Command above will work only but a kernel booted without Xen
if "virtualization" is enabled in your BIOS.
1) For your post on
ubuntu-fr xen-create-image will only set up a new PV domU .
That's all. So there is no graphical server. You have to
install it yourself.
xen-create-image
installs only a simple available domU (= no graphical desktop)
When you start your PV
domU to get the console (add -c option)
xl create
/path/to/your/configuration/file -c
Then you will be on
the PV domU console. If SSH is not installed then install it
(sudo apt-get install openssh-server). After that you should
be able to log through SSH.
To log out from the
console, press ""shift" + "5" ("5" from button where there is
both "(" and "5" character not the pad number)
Later you
should be able to SSH on your PV domU and you should be able
to install a X server plus KDE or LXDE etc. So you have to do
this yourself.
2) For HVM and only
for HVM
Since you set 'vnc=1'
in your configuration file and since you have LXDE on your
dom0 start by installing vncviewer. Ok let me explain :)
vnc=1 means
that your domU will start with VNC available so you shoul be
able to access GRAPHICALLY to your domU through any vnc
client. You just need a VNC client on your dom0
a) sudo
apt-get install xtightvncviewer
That should
install vncviewer. This is a VNC client. This one should be
usefull
b) Update
your configuration file for HVM domU to point to a Ubuntu iso
for installation. I am speaking here about the line '
file:/path/to/your/iso,xvdc:cdrom,r''.
If you don't have a Ubuntu iso then download one
c) Start
your domU (xl create /path/to/your/configuration/file)
e) Open a
Linux terminal and run
vncviewer IP_of_your_dom0
You should
be able to see your graphical Ubuntu domU and do a normal
installation
3) It is
doable to acces a HVM domU when it is not started so you can
copy/move files on one of the devices used by this domU. This
is doable since you are using LVM. To do this you need to
install kpartx (But here please be carefull since your
experience with LVM is quite new if you do something wrong
that it can break your system)
sudo apt-get
install kpartx
kpartx -va
/dev/vg/mydomU
(-v and -a
options will list all "parts" inside the disk used for volume
/dev/vg/domU)
You should
get something like as output
/dev/vg/domU1....
/dev/vg/domU2...
etc
You just
need to use command 'mount' to mount one of the devices you
need
mount ....
Once it is
done then umount and
use
kpartx -vd
/dev/vg/mydomU
David TECHER
[...]
dom
tt depends
french isn't it :) ?
"'xl console' are for PV domU not for HVM domU."
ah ok I had not seen this difference.
My Xen host config (new PC) :
- MB : H97M-G43(MS-7924)
- CPU : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz
- Dom0 OS : Ubuntu 14.04 LTS 64 bits with LXDE
desktop manager and X server
- Xen : 4.4.2
And my old remote PC. I use Remmina tool to access
graphicaly to Dom0 and SSH to administrate Dom0.
I want accessing DomU VM in the same way.
I just found this, but it implies that I can access
inside the DomU VM :
http://wiki.linuxservertech.com/index.php?action="">
Le 12/10/2015 17:06, David TECHER a écrit :
'xl
console' are for PV domU not for HVM domU.
To
get graphical acces to a HVM dom tt depends if
you set up a X server on your dom0 or not ( X
server with KDE, Gnome or whatever you want).
There are two cases
1)
No X server on dom0
The
VNC commands (= GUI access) should not be used
on the dom0 itself but on a remote PC through
your own network.
In
a nutshell install a VNC client on a remote PC
(not the dom 0).
If
your remote PC is Ubuntu with (a X server
installed of course) then install vncviewer.
After than on the remote PC
vncviewer
hostname_of_your_dom0
or
vncviewer
IP_of_your_dom_0
You
should be able to access graphically your new
HVM domU.
2)
X server on your dom0
Install
vncviewer and run the same commands as above
Ok, it is confusing... I will try to
clarify.
When following tutorials I managed to run
PV DomU guest (successfull
tests with Ubuntu, Debian), but for this
moment I did not managed to run
HVM DomU guest (no Windows and no Ubuntu).
So in the first time, I
suspected a CPU incompatibility but this
is not the case.
So, I can create an Ubuntu HVM DomU, but a
simple terminal access, shows
me that is does not work completely.
root@lnj-ubu64:/home/lnj#
xl -vvv vncconsole xen-domu-ubuntu
command not implemented
xc: debug: hypercall buffer: total
allocations:6 total releases:6
xc: debug: hypercall buffer: current
allocations:0 maximum allocations:1
xc: debug: hypercall buffer: cache current
size:1
xc: debug: hypercall buffer: cache hits:5
misses:1 toobig:0
I have no 'vncconsole' parameter in xl
tool. Wrong version ?
Le 12/10/2015 13:02, Ian Campbell a
écrit :
> On Mon, 2015-10-12 at 12:55 +0200,
estebann@xxxxxxxxx
wrote:
>> [...]
>> So, because Windows HVM did not
work, I wanted first to attest that
>> Ubuntu HVM DomU with graphical
access, works. But that is not the case
>> neither.
> If you want serial (AKA xl console)
from Ubuntu I think that would need
> manually configuring too. Since you
mention Ubuntu graphical and are aiming
> for Windows I'll ignore that
possibility though.
>
>> "xl console gets you access to
the virtual serial device. I don't think
>> Windows would attach anything
to that at least not by default. Try
>> connecting to the VNC and you
should see the Windows GUI. "
>> OK for Windows but for Ubuntu
graphical access this will work, no ?
>>
>> With VNC this do not work
neither !
> Please can you give details of what
goes wrong.
>
> The output of:
>
> xl -vvv vncconsole <domain>
>
> Would likely be useful.
>
> Ian.
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
