Todd Deshane ([info]deshantm) wrote,
@ 2008-05-12 19:25:00
Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Xen + Ubuntu 8.04 Howto
NOTE: This is a work in progress

For details that I might be missing a good resource is:
http://howtoforge.com/ubuntu-8.04-server-install-xen-from-ubuntu-repositories

Another useful link related to HVM and Solaris/OpenSolaris:
http://blogs.sun.com/breakdown/entry/ubuntu_8_04_and_xen

I will clean this up and do more testing when I have time

Any problems, questions leave a comment or post to the xen-users mailing list

Also, this is just proof of concept, in production I would recommend things like
LVM and network storage solutions like AoE, iSCSI, and DRDB.

Another NOTE: this is for amd64, there are also packages for i368


sudo apt-get remove network-manager
sudo gedit /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp


sudo /etc/init.d/network restart
sudo apt-get install ubuntu-xen-server
wget http://downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories/linux-headers-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb
wget http://downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories/linux-image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb
sudo dpkg -i linux-headers-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb linux-image-2.6.24-16-xen_2.6.24-16.30zng1_amd64.deb

Restart into Xen

sudo xm list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  3888     2     r-----     57.7

sudo mkdir -p /xen/images
sudo dd if=/dev/zero of=/xen/images/para.partition bs=1M seek=10240 count=1
ls -lh /xen/images/
sudo mkfs.ext3 -F /xen/images/para.partition
sudo mkdir /mnt/para
sudo mount -o loop /xen/images/para.partition /mnt/para
sudo debootstrap hardy /mnt/para
sudo cp -a /lib/modules/`uname -r` /mnt/para/lib/modules/
echo para | sudo tee /mnt/para/etc/hostname

fix /etc/hosts, /etc/fstab, /etc/network/interfaces etc.

sudo umount /mnt/para
sudo gedit /etc/xen/para

kernel="/boot/vmlinuz-2.6.24-16-xen"
ramdisk="/boot/initrd.img-2.6.24-16-xen"
disk=['tap:aio:/xen/images/para.partition,xvda1,w']
memory=512
vif=['']
root="/dev/xvda1"
extra='xencons=tty'

sudo xm create -c para


sudo dd if=/dev/zero of=/xen/images/hvm.disk bs=1M seek=10240 count=1
sudo gedit /etc/xen/hvm

kernel="/usr/lib64/xen/boot/hvmloader"
builder="hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/<cdrom device>,hdc:cdrom,r']
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/loop0,hdc:cdrom,r']
sdl=1
boot="dc"
memory=512
vif=['type=ioemu,bridge=eth0']

Note that it if you want to use an ISO, just run the command:
sudo losetup `sudo losetup -f` The_ISO_file.iso

sudo xm create hvm

after the hvm install, you can do:

kernel="/usr/lib64/xen/boot/hvmloader"
builder="hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/dvdrw1,hdc:cdrom,r']
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/loop0,hdc:cdrom,r']
disk=['phy:/xen/images/hvm.disk,hda,w']
sdl=1
boot="dc"
memory=512
vif=['type=ioemu,bridge=eth0']
#stdvga=1

NOTES:
UPDATE 1: add sudo in front of `losetup -f` so not it reads `sudo losetup -f`
UPDATE 2: change phy: to tap:aio: in the cases referring to image files (in the HVM config file examples)
UPDATE 3: added note at the top to state specific to amd64, but that i386 packages are available.
UPDATE 4: add another link towards the beginning related to HVM and Solaris/OpenSolaris



(Post a new comment)

Install Solaris (Nevada build 87) DomU at Ubuntu 8.04 Xen 3.2 Server Dom0 (amd64)
[info]dbaxps
2008-05-14 08:12 pm UTC (link)
http://lxer.com/module/newswire/view/102955/index.html

(Reply to this)

Re: Xen + Ubuntu 8.04 Howto
(Anonymous)
2008-05-15 06:04 am UTC (link)
Two things strike me here. First and foremost, the links you give get the AMD64 versions (not stated up front). I run an 32bit Intel system. Second, you assume eth0 on the target system. I would need to move the system to use eth0; ath0 or wifi0 apply otherwise. Now, maybe it is silly to consider installing xen on a wifi based home network, but I've run other virt sw on these machines with no problem other than their natural limitations irrespective of wifi.

Finally, why remove network manager to begin with?

--Gary (sorry, no contact info)

Gary Greene

(Reply to this) (Thread)

Re: Xen + Ubuntu 8.04 Howto
[info]deshantm
2008-05-15 01:53 pm UTC (link)
I added a note about the amd64-specific instructions. Thanks :)

I use eth0 since that is the common case and most people will know if they have special network needs.

I think it is great that people are trying with wireless cards and home networks. That is just not the common case (yet).

Removing network manager was just the easy way to go. There are surely better more complicated ways. A purely desktop/laptop oriented howto is something that people could benefit from, it is just not something that I had time to include at this time.

Thanks for the comments.

(Reply to this) (Parent)(Thread)

Re: Xen + Ubuntu 8.04 Howto
[info]jtriedl
2008-05-21 04:52 pm UTC (link)
Todd:

Thanks very much for this tutorial. Very helpful.

I've been carefully following the HOWTO Forge tutorial you link to, and I have been unable to get my network to work correctly. I notice two things you do differently:

- turn off network-manager
- install the updated linux kernel headers from Japan

I'm assuming the kernel headers don't matter if I'm not building a kernel. The network-manager is interesting. Can you say a few more words about why you turn that off?

My symptoms are that my dom0 boots fine, and can start domUs with no problem -- as long as bridging is turned off! When I turn bridging on, the dom0 has no networking. (Of course, with bridging off, the domUs have no networking, so that's an imperfect solution.) I'm wondering if switching to your style of editing the interface I want up into /etc/network/interfaces and disabling network-manager would work, and if so, why.

I discovered the problem by accident, since I have two interfaces on my box, eth0 and eth1. When I switched to eth1 because eth0 was not working for dom0, networking worked for dom0, but not domU. I found that the problem was that the network-bridge script was still operating on eth0. When I fixed that problem, networking broke for dom0 as well! I've now been able to switch between eth0 and eth1, and have networking work on either one, as long as I have network bridging incorrectly on the other one (or commented out).

Thanks!
John

(Reply to this) (Parent)(Thread)

Re: Xen + Ubuntu 8.04 Howto
[info]jtriedl
2008-05-22 02:26 pm UTC (link)
Todd:

I just want to follow-up on my previous note to say that the network-manager advice in your HOWTO was the savior for me. I uninstalled network-manager, and networking works great, both in DomO and DomU.

I had previously read many pages all over the net, and yours and one other are the only ones that mention network-manager, which is odd given my experience. I wonder if the problem only occurs in systems with more than one ethernet NIC, so most people don't have to worry about it(?).

Thank you!
John

(Reply to this) (Parent)(Thread)

Re: Xen + Ubuntu 8.04 Howto
[info]deshantm
2008-05-22 02:46 pm UTC (link)
There are some tricks to get around these problems I am sure. It is basically on incompatibility of the Xen networking scripts and the Ubuntu network manager scripts.

I am trying to get time to get Xen working on my laptop with and without wireless and with network manager installed. If/when I get around to it I will post any tips or tricks that I find, possibly a new destop/laptop oriented howto

Thanks for posting your experiences.

(Reply to this) (Parent)

Windows DomU
(Anonymous)
2008-05-15 10:33 am UTC (link)
Has anyone been able to get Windows DomU's running? I'm able to show a Xen PDL window, but it's blank and eventually fails giving the following error:

Error: Device 768 (vbd) could not be connected. losetup /dev/loop11 /xen/images/WinXP.img failed

(Reply to this) (Thread)

Re: Windows DomU
[info]deshantm
2008-05-15 01:42 pm UTC (link)
use tap:aio instead of file:/

(Reply to this) (Parent)(Thread)

Re: Windows DomU
(Anonymous)
2008-05-15 04:33 pm UTC (link)
I have similar problems with x86_64 Windows Exchange 2k7.

my config (hvm.conf):
kernel="/usr/lib64/xen/boot/hvmloader"
builder="hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/,hdc:cdrom,r']
disk=['tap:aio:/srv/domus/exchange/win.disk,hda,w','phy:/dev/loop0,hdc:cdrom,r']
sdl=0
vnc = 1
vnclisten = "0.0.0.0"
boot="dc"
memory=512
vif=['type=ioemu,bridge=eth0']

before xm create hvm.conf I execute:

losetup -f /srv/images/Exchange_Server_2007_Enterprise_Edition_Deutsch_X12-98678.iso

BUT the domU doesn't start. After xm create hvm.conf the ramsize is reduced but domU not started.

by the way: i got an error msg when I try to install the modified linux-headers ...

(Reply to this) (Parent)(Thread)

Re: Windows DomU
[info]deshantm
2008-05-15 06:19 pm UTC (link)
I think you are mis-understanding the losetup command.

Read the howto again for that part.

losetup loop_device iso_file

then try the following to make sure it was associated correctly
losetup -a

I think posting to the xen-users list (if my explanation here is not sufficient for you to see your problem) would be a good idea

I have had good luck booting Windows, Linux, and Xen Server, iso files so far. Others have reported opensolaris working as well.

(Reply to this) (Parent)(Thread)

Re: Windows DomU
(Anonymous)
2008-05-16 02:56 pm UTC (link)
Hello.

First, thanks for this fantastic tutorial.

I have xen installed and working on ubuntu 8.04.

I tried to install another ubuntu guest on dom1, but after i do xm create ubuntu.cfg, boot cd start well but after is impossible to do installation.

Do you have any similar problem?

Thanks

(Reply to this) (Parent)(Thread)

Re: Windows DomU
[info]deshantm
2008-05-18 06:04 pm UTC (link)
Install in safe graphics mode (use F4 at LiveCD boot prompt)

(Reply to this) (Parent)

Re: Windows DomU
(Anonymous)
2008-05-17 02:14 pm UTC (link)
okay - Windows 32Bit HVM and the Gentoo 2008.0 beta2 64bit HVM boots well.

BUT i have problems with 64Bit M$ Exchange!

root@xenpc:/srv/domus/exchange# xm create xchange.hvm
Using config file "./xchange.hvm".
Started domain xchange.hvm
root@xenpc:/srv/domus/exchange# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 1476 1 r----- 40.0

losetup -a lists that Exchange.iso is mounted to loop0
config like above

as you can see the xm list shows the reduced 2gb ram ... o_O

(Reply to this) (Parent)(Thread)

Re: Windows DomU
[info]deshantm
2008-05-18 06:05 pm UTC (link)
there might be some 64bit MS Exchange-specific thing. You could try posting to the xen-users list for advice.

(Reply to this) (Parent)

Raul
(Anonymous)
2008-05-19 12:11 pm UTC (link)
Hello.

I install xen on ubuntu desktop 64 bits.

I have a question, is necesary star ubuntu in graphical mode to star xen guest?

Thanks.

(Reply to this) (Thread)

Re: Raul
[info]deshantm
2008-05-19 02:38 pm UTC (link)
You can start guests from the command line.

For HVM guests, don't use the sdl option, instead use vnc=1 and setup the vnc options in the xend config and you can vnc to the HVM guests.

PV guests you can ssh or console into, or also also use vnc if you install X of course.

(Reply to this) (Parent)

i386 64bit ?
(Anonymous)
2008-05-20 12:22 am UTC (link)
Is there a i386 64bit intel version of a working kernel and package I can get. It seems I can only find AMD64 with no mention of Intel 64 anywhere.
I need 64bit version since I have 8Gb RAM on my box.

Thanks,
Xen

(Reply to this) (Thread)

Re: i386 64bit ?
[info]deshantm
2008-05-20 12:24 am UTC (link)
take a look here:
http://downloads.howtoforge.com/ubuntu_8.04_server_xen_from_repositories/

the packages are in the same place as the amd64 ones.

(Reply to this) (Parent)(Thread)

Re: i386 64bit ?
(Anonymous)
2008-05-21 04:36 pm UTC (link)
Todd: I think the last guy is asking about i386 *64 bit*. My understanding is that that's the same as AMD 64 bit. (I think the naming convention is unfortunate, but that's how ubuntu does it.)

On the ubuntu web site if I choose to download "Intel or AMD 64 bit" I get the following ISO:

Download URL: http://ubuntu-releases.cs.umn.edu/hardy/ubuntu-8.04-desktop-amd64.iso
Ubuntu Edition: Ubuntu 8.04 desktop
Computer Platform: amd64
Download Location: http://ubuntu-releases.cs.umn.edu/

John

(Reply to this) (Parent)(Thread)

Re: i386 64bit ?
[info]deshantm
2008-05-21 05:19 pm UTC (link)
amd64 is the same (for most all intents and purposes) as x86_64 from Intel. amd64 came first and Intel copied the amd64 spec (for the most part and the differences have been argued out by now I would assume)

I run amd64 on both Intel-based and AMD-based machines without any problems.

(Reply to this) (Parent)

pciback
[info]jcs19570124
2008-05-25 06:05 pm UTC (link)
Very good note !
but how can i use pciback with hardy ?
I am beginner and i do not find pciback in this distro

Thanks.
Bye.
(excuse my english)

(Reply to this) (Thread)

Re: pciback
[info]deshantm
2008-05-25 06:15 pm UTC (link)
I haven't tried PCI passthrough on hardy yet, at least not in quite awhile.

Give it a try and report any problems on xen-users.

(Reply to this) (Parent)(Thread)

Re: pciback
[info]jcs19570124
2008-05-25 08:18 pm UTC (link)
Thanks for answer.
I'll try like this

(Reply to this) (Parent)

Re: pciback
[info]chivas143
2009-05-02 03:05 am UTC (link)
Todd: Hi, its Ron of DDSI. I just got Xen 3.3.1 running on test server with 8 Gigabit Nics and was fiddling around with this.

This is how I have managed to hide two PCI Nics from Dom0 and have it dedicated in a DomU:

First thing is to identify the PCI device you want to hide from Dom0:
# lspci
The output will be in similar to this format:
0a:00.0 Ethernet controller: Intel Corporation 82575GB Gigabit Network Connection (rev 02)
10:00.0 Ethernet controller: Intel Corporation 82575GB Gigabit Network Connection (rev 02)

From the above example the PCI device id is 0a:00.0 and 10:00.0
Add the following:
pciback.permissive pciback.hide=(0a:00.0)(10:00.0)
To the following "menu.lst" as shown below:
################
title Xen 3.3.1 / Ubuntu 8.04.2, kernel 2.6.24-23-xen
root (hd0,0)
kernel /xen-3.3.1.gz
module /vmlinuz-2.6.24-23-xen root=/dev/mapper/vg--os-lv--root ro console=tty0 pciback.permissive pciback.hide=(0a:00.0)(0a:00.1)
module /initrd.img-2.6.24-23-xen
quiet
################
Save and reboot and log back in:
# dmesg | more
Output should not show the devices, the two NICs. The two are now not seen by your Dom0 and can be allocated to a DomU as dedicated pci devices.
You'll also notice that the pci id(s) are in the following format:
[ 7.878770] igb 0000:0b:00.0: Intel(R) Gigabit Ethernet Network Connection

The preceeding "0000" in 0000:0b:00.0 identifies the domains, in this case its "0000" Dom0.

Edit your domU's configuration file and add a "pci=" line as shown below:
#vim domu.cfg
vif = [ 'ip=192.168.1.108,mac=00:16:3E:E4:14:96' ]
pci = ['0a:00.0','0a:00.1']

Save and Quit
Boot up the domU and do a "lspci" and you should see the two devices.
You can comment the "pci=" line and reboot your DomU to verify.

Hope this helps.

Ronald Arenas



(Reply to this) (Parent)(Thread)

Re: pciback
[info]deshantm
2009-05-02 05:08 pm UTC (link)
Thanks Ron!

Does your hardware have an IOMMU (Intel VT-d or AMD IOMMU - the new one)?

If not, be aware that passing devices to guest opens up a potential security hole in which the guest that has a device passed to it could DMA to memory that it doesn't own.

(Reply to this) (Parent)(Thread)

Re: pciback
[info]chivas143
2009-05-04 01:36 pm UTC (link)
Todd:

After after a relentless search to answer your question above, I would conclude "Yes, my hardware supports VT-d which is a DELL Poweredge 2900-III with Quad-Core Xeon 5405 CPU(s)", I finally found some enlightenment on "VT-d" (See below):


FROM: http://software.intel.com/en-us/forums/virtualization-software-development/topic/56802/

########################### Excerpt from the forum ##############################

The only current server chipset which supports VT-d is the successor of the 5000p (server)chipset (by the codename Blackford), codenamed Seaburg or 5400 chipset (http://www.intel.com/products/chipsets/5400/index.htm).

The Intel 5400 chipset is designed for systems based on the Intel processors Dual Core Intel Xeon Processor 5100 series, Quad-Core Intel Xeon Processor 5300 series, Quad-Core Intel Xeon Processor 5400 series, and Dual-Core Intel Xeon Processor 5200 series

So, watch out, there is an Intel 5400 series chipset (aka Seaburg) AND there is a Intel Xeon Processor 5400 series (aka Harpertown). Intel just wants to confuse us :-)

Here is a site with all the Intel Processors listed which support VT (VT-d is NOT specifically referred to!!):
http://compare.intel.com/pcc/default.aspx?familyid=5&culture=en-US&iid=products_xeon5000+body_compare

This link compares the 5000p server chipset (no VT support!) and the 5400 server chipset (with VT support):
http://compare.intel.com/pcc/showchart.aspx?mmID=24664,28047&familyID=9&culture=en-US

So, virtually all current Xeon processors support VT, but currently only one chipset (5400 aka Seaburg) support VT-d. It should be noted, that the BIOS also should allow it to enable VT. And even then, when all three conditions are met, there is no guarantee that it will work flawlessly.

The equivalent of the Seaburg (5400) server chipset for the desktop PCs is the Q35 chipset aka Bearlake-Q, with VT-d support. All other Bearlake variants in the 3-Series chipset do NOT support VT-d, as far as I know.

This is what I understand after I dug into this. I may be wrong, so anyone who can amend my above deliberations, please do so.

To respond to your question: no I don't think your server board with 3210 chipset supports VT-d.
########################################################################################

(Reply to this) (Parent)(Thread)

Re: pciback
[info]deshantm
2009-05-04 03:54 pm UTC (link)
You may also want to look into:
http://wiki.xensource.com/xenwiki/VTdHowTo

Since I am not sure if VT-d is on by default in the version of Xen you have.

Also, it gives some information on chipsets/systems that support VT-d

(Reply to this) (Parent)(Thread)

Re: pciback
[info]chivas143
2009-05-05 12:55 am UTC (link)
Todd:

I am using Xen 3.3.1 on Ubuntu 8.04.2 Server where Xen 3.3.1 was compiled and installed after doing backport of Xen 3.3.0. When compiling, I was prompted to enable pciback.., pcifront..., etc.. as well as support for several NIC(s) where I have answered "Y" and "m" respectively and "N" to the 10GigE. It is still unclear even from the wiki what VT-d enable truly is as it implies a combination of CPU + Motherboard requirements. OEM they only mention the Dell optiplex 755 on the Dell line, but on the Intel forums they mention all Xeon 5400 series are VT-d capable and usually, support is on Server Boards. One might therefore conclude that any Server Class Motherboard running 5400 series Xeon Chips would be VT-d enabled.

As far as my testing, I have not run accross the following error from the wiki on Dell's 2900 III servers (5405+ Xeon CPU(s)):

##################################################
If the device model has been compiled without pass-through support, the following error will show up in xend.log at run-time when pass-through is attempted.

ERROR (XendDomainInfo:581) Device model didn't tell the vslots for PCI device

##################################################

And have identical results when implementing the "simplest way to make PCI devices available for VT-d pass-through is to use the pciback.hide kernel parameter" as described from the wiki and I am also able to "Boot-Time VT-d Device Pass-Through" as described by the wiki with no errors. DomU loads as expected with the PCI devices.

Todd: I really want to believe my test environment is VT-d, and I think it is, but are there any other indications that might positively confirm VT-d on a running Xen System. No flag indications in "/proc/cpuinfo" or "xm dmesg".

(Reply to this) (Parent)(Thread)

Re: pciback
[info]deshantm
2009-05-05 11:36 pm UTC (link)
Looks like you are right. I can't find anything on that wiki that would indicate that you don't have it.

I guess one way to really test it, is to try an HVM guest. HVM guests don't support passthrough without VT-d.

So, if you can passthrough to an HVM guest, that would mean you for sure have VT-d support enabled.

(Reply to this) (Parent)

Problem installing/running xen on kubuntu 8.04 64bit
[info]itrush
2008-08-22 03:31 am UTC (link)
Hi everybody,

Could you help me in correct installation of xen?
I checked everything and performed process many times but failed at the same position - I install xen 3.2 successfully, kernels as well,
but when I try booting xen hypervisor fails with page fault trap and gives stack dump.
If someone met this issue and knows workaround,help,pls.
OS: Kubuntu AMD 64bit 8.04
MB: ASUS M2N
CPU: AMD AM2 6000+
RAM: 6GB

(Reply to this) (Thread)

Re: Problem installing/running xen on kubuntu 8.04 64bit
[info]deshantm
2008-08-22 01:51 pm UTC (link)
You should ask your question on the xen-users list

You should also give more details into the exact version of the kernel and how you installed it. Also give the error message etc.

These directions are now slightly dated, since the latest Ubuntu Xen kernel has the fixes, and you can simply install them from apt.

(Reply to this) (Parent)

Re: Problem installing/running xen on kubuntu 8.04 64bit
[info]itrush
2008-08-22 02:22 pm UTC (link)
Hi,
I tried as exactly described in your blog as from others.
checked all kernel including 2.6.24-16,2.6.24-19 standard and 2.6.24-16zng
I always get same result-trap
However, xen 3.0 starts(but not start guests).
I think it is not kernel but hypervisor start level
Initially I thought of hardware problem but in Fedora everything works fine

(Reply to this) (Thread)

Re: Problem installing/running xen on kubuntu 8.04 64bit
[info]deshantm
2008-08-22 02:26 pm UTC (link)
I don't know of this problem.

Could you post your problem as a bug on Ubuntu (if it doesn't exist already) and also on the xen users list?

Maybe someone can help you debug it or figure out a work around.

(Reply to this) (Parent)


[info]great_fantom
2008-09-11 12:12 pm UTC (link)
hi
i have ubuntu 8.04 server on hp proliant 380 g5
my version of kernel is Linux webmyos 2.6.24-19-xen #1 SMP Wed Aug 20 21:08:51 UTC 2008 x86_64

config of hvm module:

kernel="/usr/lib64/xen/boot/hvmloader"
builder="hvm"
device_model = "/usr/lib64/xen/bin/qemu-dm"
disk=['tap:aio:/xen/images/hvm.disk,hda,w','tap:aio:/home/fantom/ubuntu.iso,hdc:cdrom,w']
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/,hdc:cdrom,r']
#disk=['tap:aio:/xen/images/hvm.disk,hda,w','phy:/dev/loop0,hdc:cdrom,r']
sdl=1
boot="dc"
memory=512
vif=['type=ioemu,bridge=eth0']

so and after
fantom@webmyos:~$ sudo xm create hvm
Using config file "./hvm".
Started domain hvm

and
fantom@webmyos:~$ sudo xm console hvm

i get this:
xenconsole: Could not read tty from store: No such file or directory

my last xend.log is:

DEBUG (XendDomainInfo:1637) XendDomainInfo.constructDomain
DEBUG (balloon:151) Balloon: 546560 KiB free; need 2048; done.
DEBUG (XendDomain:443) Adding Domain: 5
DEBUG (XendDomainInfo:1722) XendDomainInfo.initDomain: 5 256
DEBUG (XendDomainInfo:1754) _initDomain:shadow_memory=0x0, memory_static_max=0x20000000, memory_static_min=0x0.
DEBUG (balloon:151) Balloon: 545268 KiB free; need 538112; done.
DEBUG (image:514) domid = 5
DEBUG (image:515) image = /usr/lib64/xen/boot/hvmloader
DEBUG (image:516) store_evtchn = 2
DEBUG (image:517) memsize = 512
DEBUG (image:518) vcpus = 1
DEBUG (image:519) acpi = 1
DEBUG (image:520) apic = 1
DEBUG (DevController:119) DevController:
DEBUG (DevController:119) DevController:
DEBUG (DevController:117) DevController:
DEBUG (DevController:119) DevController:
DEBUG (XendDomainInfo:2211) Storing VM details:
DEBUG (XendDomainInfo:1027) Storing domain details: {'console/port': '3', 'name': 'hvm', 'console/limit': '1048576', 'store/port': '2', 'vm': '/vm/c61c15bb-953f-aea5-83b4-4a8a314d1fe9', 'domid': '5', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '524288', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '131070', 'console/type': 'ioemu'}
DEBUG (DevController:117) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/5/0'} to /local/domain/5/device/console/0.
DEBUG (DevController:119) DevController: writing {'domain': 'hvm', 'protocol': 'vt100', 'uuid': '1b3319ea-4860-777a-71d7-c497750a5b1a', 'frontend': '/local/domain/5/device/console/0', 'state': '1', 'location': '3', 'online': '1', 'frontend-id': '5'} to /local/domain/0/backend/console/5/0.
DEBUG (XendDomainInfo:1111) XendDomainInfo.handleShutdownWatch
DEBUG (DevController:150) Waiting for devices vif.
DEBUG (DevController:155) Waiting for 0.
DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status.
DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/5/0/hotplug-status.
DEBUG (DevController:608) hotplugStatusCallback 1.
DEBUG (DevController:150) Waiting for devices vbd.
DEBUG (DevController:150) Waiting for devices irq.
DEBUG (DevController:150) Waiting for devices vkbd.
DEBUG (DevController:150) Waiting for devices vfb.
DEBUG (DevController:150) Waiting for devices console.
DEBUG (DevController:155) Waiting for 0.
DEBUG (DevController:150) Waiting for devices pci.
DEBUG (DevController:150) Waiting for devices ioports.
DEBUG (DevController:150) Waiting for devices tap.
DEBUG (DevController:155) Waiting for 768.
DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/tap/5/768/hotplug-status.
DEBUG (DevController:608) hotplugStatusCallback 1.
DEBUG (DevController:155) Waiting for 5632.
DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/tap/5/5632/hotplug-status.
DEBUG (DevController:608) hotplugStatusCallback 1.
DEBUG (DevController:150) Waiting for devices vtpm.
INFO (XendDomain:1165) Domain hvm (5) unpaused.

can yuo help me?
best regards from russia :)

(Reply to this) (Thread)


[info]great_fantom
2008-09-11 12:19 pm UTC (link)
PS
I try to insyall on xen-server anither ubuntu server-8.04-amd64
and before this post i tried two or three another your configs

(Reply to this) (Parent)


[info]deshantm
2008-09-11 01:21 pm UTC (link)
You can't easily console into the guest.

Are you running the xm create in a graphical enviroment?

If so, there is like a problem with sdl on your system, one alternative is to set sdl=0 and vnc=1 and use the command
vncviewer localhost
(note you may need to enable vnc* options in /etc/xen/xend-config.sxp)

If those don't help I would suggest posting to xen-users explaining what you tried and you should be able to more help there.

(Reply to this) (Parent)


Create an Account
Forgot your login?
Login w/ OpenID
English • Español • Deutsch • Русский…