Re: [Xen-users] My failures so far. Or qemu-stable or upstream?

[Casey DeLorme <cdelorme@xxxxxxxxx>]

Xen 4.2 compiled from source should include both traditional and upstream qemu.

Upstream does not have complete passthrough support, if you are doing anything of that nature best to stick to traditional.

The Xen Man Pages have the most up to date configuration:

http://wiki.xen.org/wiki/Xen_4.2_Man_Pages

The flag to set per HVM Configuration is `device_model_version`, its values are "qemu-xen" and "qemu-xen-traditional", the traditional being the default. ÂKey benefits are alternative BIOS, though the UEFI BIOS has to be specified to build when compiling Xen.

On Fri, Dec 7, 2012 at 8:17 PM, ShadesOfGrey <shades_of_grey@xxxxxxxxxxxxx> wrote:

During my first two attempts to install Xen and create a Debian based DomU, I got the following error:

xl create /etc/xen/debian.cfg
Parsing config from /etc/xen/debian.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
 Loader: 0000000000100000->0000000000175488
 TOTAL: 0000000000000000->000000001f800000
 ENTRY ADDRESS: 0000000000100608
xc: info: PHYSICAL MEMORY ALLOCATION:
 4KB PAGES: 0x0000000000000200
 2MB PAGES: 0x00000000000000fb
 1GB PAGES: 0x0000000000000000
libxl: error: libxl_dm.c:1086:libxl__spawn_local_dm: device model /usr/lib/xen-4.2/bin/qemu-dm is not executable: No such file or directory
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: (null): spawn failed (rc=-3)

With my first attempt, Plan A, I compiled xen-unstable and after tweaking my config file I did something to 'fix' the error. Don't remember exactly what I did, but I fear I just commented out the "builder" line, which makes sense. A short time later though, I did something that broke the xenstore and xenconsole daemons. In a fit of frustration, I went to Plan B.

To execute Plan B, I decided to restart from scratch and use Xen 4.2 from Debian's experimental repositories. Things went smoothly until I tried to create my first DomU. The same error message again. This time I went searching and found a reference to it in Debian's bug tracking system. Although, it did not offer a clear solution. So, I figured I'd try to install qemu from the Debian repositories. Sadly, I got a similar error about qemu missing, though this time not "qemu-dm"... I think it was "qemu-system-i386" but I can't recall exactly. I thought I captured the error message, but either I didn't or I misplaced the text file. Anyway, the result was the same.

Now I'm on Plan C. Which is just revisiting Plan A. Re-installing from scratch and compiling Xen and the linux kernel from source. This time however, I plan to snapshot my Dom0's LV after I compile and before I install so I can easily revert to a 'clean' system. So, I'm about to compile the latest xen-unstable per the instructions here. However, I'm unsure if I should build xen with qemu-upstream as mentioned on this page, or go with vanilla qemu-stable-1.0? Which I gather should be built during the compilation of Xen... though given the error messages, I wonder about that.

Advice, please?

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users