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

Re: [Xen-devel] COLO Xen patch v12 - Unable to start virtual machine



Hello, I've CC COLO authors for you.

Please be aware that COLO is still under development -- the interfaces
aren't stable yet.

On Thu, Mar 24, 2016 at 11:22:33AM +0100, Alexis RIES wrote:
> I have managed to compile Xen, the kernel, COLO, following the information
> in this thread.
> http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg03507.html
> 
> Github branche : changlox/colo_v12
> https://github.com/Pating/xen/tree/changlox/colo_v12
> 
> Xen (COLO version) is now compiled and installed, the kernel patched and
> network cards are configured as in the documentation below:
> http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
> 
> 
> When I try to start a virtual machine, I receive this error message:
> 
> [root@xen1 ~]# xl create /var/virtualStore/test/test.cfg
> Parsing config from /var/virtualStore/test/test.cfg
> libxl: warning: libxl_dm.c:1447:libxl__build_device_model_args_new: Could
> not find user xen-qemuuser-shared, starting QEMU as root
> libxl: error: libxl_device.c:963:device_backend_callback: unable to add
> device with path /local/domain/0/backend/vif/3/0
> libxl: error: libxl_create.c:1443:domcreate_attach_vtpms: unable to add nic
> devices
> libxl: error: libxl_device.c:963:device_backend_callback: unable to remove
> device with path /local/domain/0/backend/vif/3/0
> libxl: error: libxl.c:1638:devices_destroy_cb: libxl__devices_destroy failed
> for 3
> libxl: error: libxl.c:1565:libxl__destroy_domid: non-existant domain 3
> libxl: error: libxl.c:1523:domain_destroy_callback: unable to destroy guest
> with domid 3
> libxl: error: libxl.c:1452:domain_destroy_cb: destruction of domain 3 failed
> 
> When I commented the network line in the virtual machine configuration file,
> it works correctly.
> 
> I tried with or without COLO in the virtual machine configuration file,
> without success.
> 
> Attached, the virtual machine configuration file.
> 
> Someone an idea for this problem?

> builder='hvm'
> memory = 2048
> vcpus=2
> cpus=["2", "3"]
> name = "hvm_nopv_colo"
> 
> #disk = [ 
> 'format=raw,devtype=disk,acces=w,vdev=hda,backendtype=qdisk,colo,colo-params=10.0.2.2:9000:exportname=qdisk1,active-disk=/mnt/ramfs/active_disk.img,hidden-disk=/mnt/ramfs/hidden_disk.img,target=/var/virtualStore/test/XenGuest1.img'
>  ]
> disk = [ 'file:/var/virtualStore/test/XenGuest1.img,hda,w', 
> 'file:/var/virtualStore/iso/windows7.iso,hdc:cdrom,r' ]
> 
> vif = [ 'mac=00:16:4f:00:00:11, bridge=br0, model=virtio-net, 
> forwarddev=eth1' ]
> #vif = [ 'mac=00:16:4f:00:00:11, bridge=br0' ]
> 
> #-----------------------------------------------------------------------------
> # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d)
> # default: hard disk, cd-rom, floppy
> boot="c"
> sdl=0
> vnc=1
> vnclisten='0.0.0.0'
> vncunused = 1
> stdvga = 0
> serial='pty'
> apic=1
> apci=1
> pae=1
> extid=0
> keymap="en-us"
> localtime=1
> hpet=1
> usbdevice='tablet'
> xen_platform_pci=0

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


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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.