similar to: How do I get rid of vfb?

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

/usr/lib/xen/bin/qemu-system-i386 doesn''t exist on ARM. We need to check if the file exists/is executable and starts it. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- tools/hotplug/Linux/init.d/xencommons | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/tools/hotplug/Linux/init.d/xencommons b/tools/hotplug/Linux/init.d/xencommons index

Hello! I was asking for help on the Freenode channel, and I was pointed here. I have a situation where, using xl, I can create a functional PV domU, with or without pv-grub, but I cannot access the console. Firing up xend and using xm works without trouble. Since xend and company is being deprecated, I would like to transition to using the xl toolstack. The system is an Arch Linux system

Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- docs/man/xl.cfg.pod.5 | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 3b227b7..ecdc816 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -1007,6 +1007,9 @@ drivers are available for various Operating Systems including HVM Linux

$ git checkout RELEASE-4.2.2 $ git clean -ffdx [do a build, install, reboot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there

Hi- I am trying to pass an LSI SAS2008-based HBA (IBM M1015) through to an HVM Solaris VM, using Xen 4.2 unstable and the qemu-traditional device model. On boot I see the following error: MPT BIOS Fault 09h encountered at adapter PCI(00h,05h,00h) A list search yielded (http://comments.gmane.org/gmane.comp.emulators.xen.devel/128172), however there was no solution for an HVM VM. I''ve

Processing commands for xen@bugs.xenproject.org: > create ^ Created new bug #20 rooted at `<1571692646.20131009000945@eikelenboom.it>'' Title: `Re: [HVM} xen_platform_pci=0 doesn''t prevent platform device creation and disk and nic take over by PV drivers.'' > title it xen_platform_pci=0 doesn''t work with qemu-xen Set title for #20 to

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

This patch series provides the facility to eject and insert a cdrom when the used device-model is qemu-xen. The only difference between both device-model is a call to a QMP command as `xl cd-insert ...` will still update xenstore, even if it''s not used by QEMU. Anthony PERARD (3): libxl_qmp, Introduce libxl__qmp_insert_cdrom. libxl_dm: Set an id to cdrom drives with qemuu. libxl:

Hi, List, I''m trying xl create a pv guest with qcow/qcow2 image, it always fails at libxl_device_disk_local_attach. #xl create pv_config_file libxl: error: libxl.c:1119:libxl_device_disk_local_attach: cannot locally attach a qdisk image if the format is not raw libxl: error: libxl_create.c:467:do_domain_create: failed to run bootloader: -3 disk configuration is: disk=[

Package: xen-utils-common Version: 4.1.2-1 Severity: normal Hi, I was doing some experiments today with XL TOOLSTACK, and found few problems when trying to do PV domU boot. I was trying to run kfreebsd9 or linux-3.2 kernel in qemu using PV i386, and with simple configuration without any disks, nics or virtual framebuffer, kernel boots (and then kernel itselfs correctly fails with information

Hello All, After a few months of hiatus, we have resumed working on mips port of Xen. We are at the point of booting dom0 userland (init process and its children). The init process gets spawned and in turn forks off processes to run commands in /etc/rc.d/init.d/rcS. However, the getty process does not seem to run subsequently and hence the login prompt is not displayed. Dom 0 does not use the

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

Hello, I build and installed Xen (4.1.3) from source, and I think I have got it working. Well, almost. I am using unmodified kernel of Fedora16 as my dom0 kernel. So this is what happened. I am able to boot into Xen, but the "xl info" failed with the standard error message mentioned in the tutorial. "libxl: error: libxl.c:56:libxl_ctx_init Is xenstore daemon running? failed to

Hi, Here is a little patch that attempt to fix the issue regarding xen_platform_pci=0 not been handled. There is one patch left from the previous version. The patch that was adding qemu_machine_override have been removed as it is unnecessary. If someone wants to change the -machine, it can always add it to device_model_args_hvm, as QEMU appear to use the last one. Regards, Anthony PERARD (1):

Wednesday, October 9, 2013, 2:00:02 PM, you wrote: > create ^ > title it xen_platform_pci=0 doesn''t work with qemu-xen > owner it Anthony Perard <anthony.perard@citrix.com> > thanks Perhaps in general looking at the libxl and xend .. and .. qemu-xen and qemu-xen-traditonal compatibility shoud be added too. Perhaps i''m a bit blunt .. but for users

Hey, I just started noticing it today - with qemu-xen (tip is commit b97307ecaad98360f41ea36cd9674ef810c4f8cf xen_disk: mark ioreq as mapped before unmapping in error case) when I try to pass in a PCI device at bootup it blows up with: char device redirected to /dev/pts/2 (label serial0) qemu: hardware error: xen: failed to populate ram at 40050000 CPU #0: EAX=00000000 EBX=00000000

Document a per-disk cache option in the xl config file to allow users to select the cache mode that the backend should use to open the disk file or device. Document backend options that are part of the vbd xenstore interface. The existing "mode" and "device-type" as well as the new "cache". Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>