Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Failed to create domU HVM Linux guest with Xen 3.3



Is the procedure really difficult? Do you have any howto/manual so I
can give it a try under 4.1.1?

Now I prefer to install a virtual machine with Debian and
xen-image-create and use it to create Ubuntu/Debian PV machines.

2011/6/23 John Jaser <john%jaser.net@localhost>:
>
> FWIW,  I've been able to install and run Ubuntu 11.04 under Xen 3.3 with
> HVM, but have not tried Xen 4.x yet.
>
> ________________________________
> From: "Roger Pau Monné" <roger.pau%entel.upc.edu@localhost>
> To: "Manuel Bouyer" <bouyer%antioche.eu.org@localhost>
> Cc: port-xen%netbsd.org@localhost
> Sent: Thursday, June 23, 2011 2:24:42 AM
> Subject: Re: Failed to create domU HVM Linux guest with Xen 3.3
>
> Hello,
>
> I've asked the same question on the Xen-users lists, here is the topic:
>
> http://permalink.gmane.org/gmane.comp.emulators.xen.user/67825?set_blog_all=yes
>
> Just in case someone faces the same problem.
>
> 2011/6/22 Manuel Bouyer <bouyer%antioche.eu.org@localhost>:
>> On Wed, Jun 15, 2011 at 04:28:06PM +0200, Roger Pau Monné wrote:
>>> Hello,
>>>
>>> Im' trying to create a Linux HVM guest in Xen 3.3 using raw files as
>>> disks, but there seems to be some problem with the devices and the
>>> machine crashes, the config fle I'm using:
>>> (ubuntu.img created with 'dd if=/dev/zero of=ubuntu.img bs=1m
>>> count=4096')
>>>
>>> kernel = '/usr/pkg/lib/xen/boot/hvmloader'
>>> builder = 'hvm'
>>> memory = '2048'
>>> device_model='/usr/pkg/libexec/qemu-dm'
>>>
>>> disk = [ 'file:/home/xen/ubuntu.img,ioemu:hda,w',
>>>           'file:/home/xen/ubuntu.iso,ioemu:hdb:cdrom,r', ]
>>>
>>> # Hostname
>>> name = "ubntu11"
>>>
>>> vif = [ 'type=ioemu, bridge=bridge1' ]
>>>
>>> boot= 'd'
>>> vnc = 1
>>> usbdevice = 'tablet' # Helps with mouse pointer positioning
>>>
>>> The output from qemu is the following:
>>>
>>> domid: 13
>>> qemu: the number of cpus is 1
>>> Watching /local/domain/0/device-model/13/logdirty/next-active
>>> Watching /local/domain/0/device-model/13/command
>>> qemu_map_cache_init nr_buckets = 10000 size 3145728
>>> shared page at pfn 7fffe
>>> buffered io page at pfn 7fffc
>>> Time offset set 0
>>> Register xen platform.
>>> Done register platform.
>>> I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
>>>
>>> And xm dmesg output the following:
>>>
>>> (XEN) realmode.c:133:d13 Failed to emulate insn.
>>> (XEN) realmode.c:175:d13 Real-mode emulation failed @ 0020:0000a82b:
>>> 0f 00 d0 b0 28 8e
>>> (XEN) domain_crash called from realmode.c:176
>>> (XEN) Domain 13 (vcpu#0) crashed on cpu#23:
>>> (XEN) ----[ Xen-3.3.2  x86_64  debug=n  Not tainted ]----
>>> (XEN) CPU:    23
>>> (XEN) RIP:    0028:[<000000000000a82b>]
>>
>> I guess this kernel uses instructions not understood by the Xen 3.3
>> x86 emulator. If this is a kernel you built yourself, try less
>> aggressive gcc flags.
>> The RIP looks like an instruction before the MMU is on, so this may be
>> in some assembly file.
>>
>> Maybe try Xen 4.1 ?
>>
>> --
>> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>>     NetBSD: 26 ans d'experience feront toujours la difference
>> --
>>
>
>


Home | Main Index | Thread Index | Old Index