[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MirageOS-devel] error when i create hvm guest
I thought that with this hvm allow me to emulate another architecture, but if this feature did not work on arm, I do not know how. you know a program, allowing me to do that? without losing too much power compared to the host machine.
> Message du 07/08/14 11:58
> De : "Anil Madhavapeddy" <anil@xxxxxxxxxx>
> A : "Gilles DALMAS" <gdalmas@xxxxxxxxxx>
> Copie à : "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
> Objet : Re: [MirageOS-devel] error when i create hvm guest
>
>Hi Gilles,
>
It looks like you are trying to install an x86_64 virtual machine image onto an ARM Xen host. ÂThis will not work...
>
-anil
>
> nobody knows where this error come from?
>
>
>
>
>
> Message du 06/08/14 10:53
> > De : "Anil Madhavapeddy" <anil@xxxxxxxxxx>
> > A : "Gilles DALMAS" <gdalmas@xxxxxxxxxx>
> > Copie à : "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
> > Objet : Re: [MirageOS-devel] error when i create hvm guest
> >
> >
This mode doesn't exist on ARM: it's an option to run x86 guests in hardware virtualisation mode. ÂAre you trying to boot an x86 guest on ARM?
> >
-anil
> > the guest system can only be started in this mode. there is a problems with this mode ?
> >
> >
> >
> >
> >
> Message du 06/08/14 10:21
> > > De : "Anil Madhavapeddy" <anil@xxxxxxxxxx>
> > > A : "Gilles DALMAS" <gdalmas@xxxxxxxxxx>
> > > Copie à : "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
> > > Objet : Re: [MirageOS-devel] error when i create hvm guest
> > >
> > >
Why are you trying to create an HVM guest on Xen/ARM? ÂYou should just be using the default PV mode on ARM to launch guests.
> > > my xl file :
> > > # =====================================================================
> > > # Example HVM guest configuration
> > > # =====================================================================
> > > #
> > > # This is a fairly minimal example of what is required for an
> > > # HVM guest. For a more complete guide see xl.cfg(5)
> > >
> > > # This configures an HVM rather than PV guest
> > > builder = "hvm"
> > >
> > > # Guest name
> > > name = "Xp"
> > >
> > > # 128-bit UUID for the domain as a hexadecimal number.
> > > # Use "uuidgen" to generate one if required.
> > > # The default behavior is to generate a new UUID each time the guest is started.
> > > #uuid = "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
> > >
> > > # Enable Microsoft Hyper-V compatibile paravirtualisation /
> > > # enlightenment interfaces. Turning this on can improve Windows guest
> > > # performance and is therefore recommended
> > > #viridian = 1
> > >
> > > # Initial memory allocation (MB)
> > > memory = 512
> > >
> > > # Maximum memory (MB)
> > > # If this is greater than `memory' then the slack will start ballooned
> > > # (this assumes guest kernel support for ballooning)
> > > #maxmem = 512
> > >
> > > # Number of VCPUS
> > > vcpus = 2
> > >
> > > # Network devices
> > > # A list of 'vifspec' entries as described in
> > > # docs/misc/xl-network-configuration.markdown
> > > vif = [ 'bridge=br0' ]
> > >
> > > # Disk Devices
> > > # A list of `diskspec' entries as described in
> > > # docs/misc/xl-disk-configuration.txt
> > > disk = [ '/dev/vg0/guest-linux-1,raw,xvda,rw' ]
> > >
> > > # Guest VGA console configuration, either SDL or VNC
> > > sdl = 1
> > > #vnc = 1
> > >
> > >
> > > Â
> Message du 06/08/14 10:03
> > > > De : "Gilles DALMAS" <gdalmas@xxxxxxxxxx>
> > > > A : "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
> > > > Copie à :
> > > > Objet : [MirageOS-devel] error when i create hvm guest
> > > >
> > > >
> > > > hello,
> > > > I have this error when i execute :
> > > > Â
> > > > mirage@cubietruck:/$ sudo xl -vvv create /etc/xen/xl.conf
> > > Parsing config from /etc/xen/xl.conf
> > > libxl: debug: libxl_create.c:1342:do_domain_create: ao 0x31f00: create: how=(nil) callback=(nil) poller=0x32578
> > > libxl: verbose: libxl_create.c:134:libxl__domain_build_info_setdefault: qemu-xen is unavailable, use qemu-xen-traditional instead: No such file or directory
> > > libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=unknown
> > > libxl: error: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=xvda failed to stat: /dev/vg0/guest-linux-1: No such file or directory
> > > libxl: error: libxl_dm.c:1467:kill_device_model: unable to find device model pid in /local/domain/9/image/device-model-pid
> > > libxl: error: libxl.c:1421:libxl__destroy_domid: libxl__destroy_device_model failed for 9
> > > libxl: debug: libxl_event.c:1591:libxl__ao_complete: ao 0x31f00: complete, rc=-3
> > > libxl: debug: libxl_create.c:1356:do_domain_create: ao 0x31f00: inprogress: poller=0x32578, flags=ic
> > > libxl: debug: libxl_event.c:1563:libxl__ao__destroy: ao 0x31f00: destroy
> > > xc: debug: hypercall buffer: total allocations:26 total releases:26
> > > xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
> > > xc: debug: hypercall buffer: cache current size:2
> > > xc: debug: hypercall buffer: cache hits:22 misses:2 toobig:2
> > > > Â
> > > > i have a cubietruck arm and i have installed qemu-system-arm and qemu-system-x86
> > > > Â
> > >
> > >
> > > _______________________________________________
> > > MirageOS-devel mailing list
> > > MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> > > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
> > >
> > >
> _______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
|
