Reporting a traceback

Reporting a traceback

[Marc Patino Gómez]

Hi list,

this is my first post to devel list, so... if I make a mistake... please 
tell me.

XEN version: 3.1.0, compiled from sources

I am trying to boot a HVM FreeBSD (migrate via Linux dd), this is the 
domU config file:


kernel = "/usr/lib/xen/boot/hvmloader"
builder = 'hvm'
memory = 1024
name = "galileo"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'phy:/dev/mapper/vg00-galileo,ioemu:da0s,w' ]
cpus = "0"
device_model = '/usr/lib/xen/bin/qemu-dm'
ne2000=0
boot='c'
sdl=0
# enable VNC library for graphics, default = 1
vnc=1
# enable spawning vncviewer(only valid when vnc=1), default = 1
vncviewer=1
vncdisplay=5


and this is the issue

riemann:/home/install# xm create /etc/xen/galileo-config.sxp

Using config file "/etc/xen/galileo-config.sxp".
VNC= 1
Unexpected error: exceptions.OSError

Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "//usr/lib/python/xen/xm/main.py", line 2453, in main
    _, rc = _run_cmd(cmd, cmd_name, args)
  File "//usr/lib/python/xen/xm/main.py", line 2477, in _run_cmd
    return True, cmd(args)
  File "<string>", line 1, in <lambda>
  File "//usr/lib/python/xen/xm/main.py", line 1266, in xm_importcommand
    cmd.main([command] + args)
  File "//usr/lib/python/xen/xm/create.py", line 1309, in main
    dom = make_domain(opts, config)
  File "//usr/lib/python/xen/xm/create.py", line 1054, in make_domain
    os.kill(vncpid, signal.SIGKILL)
OSError: [Errno 3] No such process

The problem, in my opinion is located in the following line:

disk = [ 'phy:/dev/mapper/vg00-galileo,ioemu:da0s,w' ]

If I sustitute da0s by hda this traceback is not shown, but then BTX 
(the FreeBSD boot loader) hangs when it try to boot the kernel.

Any ideas? Can I send more usefull information?

Regards,

Marc

Re: Reporting a traceback

[Keir Fraser]

On 27/9/07 08:08, "Marc Patino Gómez" <mpatino@es.clara.net> wrote:

> The problem, in my opinion is located in the following line:
> 
> disk = [ 'phy:/dev/mapper/vg00-galileo,ioemu:da0s,w' ]
> 
> If I sustitute da0s by hda this traceback is not shown, but then BTX
> (the FreeBSD boot loader) hangs when it try to boot the kernel.
> 
> Any ideas? Can I send more usefull information?

I believe that vmxassist doesn't work with the FreeBSD bootloader. The only
reports of success that I've seen have been running FreeBSD as an HVM guest
on AMD processors.

 -- Keir

Re: Reporting a traceback

[Marc Patino Gómez]

Hi Keir,

you was write, after testing with an AMD processor all works like a 
charm, so.. the same problem that I had with an HVM Solaris 10.

 In my modest opinion... I think that will be interesting to put in the 
official documentation the advantages and dissadvantages about Intel and 
AMD processors.

Cheers,

Marc


Keir Fraser wrote:
> On 27/9/07 08:08, "Marc Patino Gómez" <mpatino@es.clara.net> wrote:
>
>   
>> The problem, in my opinion is located in the following line:
>>
>> disk = [ 'phy:/dev/mapper/vg00-galileo,ioemu:da0s,w' ]
>>
>> If I sustitute da0s by hda this traceback is not shown, but then BTX
>> (the FreeBSD boot loader) hangs when it try to boot the kernel.
>>
>> Any ideas? Can I send more usefull information?
>>     
>
> I believe that vmxassist doesn't work with the FreeBSD bootloader. The only
> reports of success that I've seen have been running FreeBSD as an HVM guest
> on AMD processors.
>
>  -- Keir
>
>
>   

Re: Reporting a traceback

[John Levon]

On Mon, Oct 01, 2007 at 03:53:59PM +0200, Marc Patino Gómez wrote:

> you was write, after testing with an AMD processor all works like a 
> charm, so.. the same problem that I had with an HVM Solaris 10.
> 
> In my modest opinion... I think that will be interesting to put in the 
> official documentation the advantages and dissadvantages about Intel and 
> AMD processors.

Again, this is not really about Intel versus AMD. It's just software
that's missing some fixes. Those fixes will come about at some point.

john