similar to: xen serial port access for domu?

Hello I use xen and I am trying to use the parallel port of Centos 5.2 host from a Windows XP (HVM) guest. I have tried to transfer control of the port by blacklisting lp, parport and parport_pc + adding: ioports = [ "0378-037a" ] to the xen configuration file. However, in the presence of this line, xm create replies with: Error: function takes exactly 4 arguments (3

Hi all, I''m trying to get a pci card working on a guest os (ast01) on dum0 I hided the pci card w/: # modprobe pciback hide=''(0b:08.0)'' then added this line to the guest os config file (/etc/xen/ast01) pci = [ "0000:08:0e.0" ] Whenever I try to start it fails w/: # xm create ast01 Using config file "/etc/xen/ast01". Error: function takes exactly 4

I have been playing with Xen 3.0.1 for some days now, using debian sarge for dom0 and domU''s, and it works like a charm. But, I have a problem with rebooting domU''s. Here is the output from /var/log/xend.log [2006-03-30 13:44:58 xend.XendDomainInfo] INFO (XendDomainInfo:823) Domain has shutdown: name=vmintraweb1 id=5 reason=reboot . [2006-03-30 13:44:58 xend.XendDomainInfo]

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When starting (or migrating in) a domain, sometimes I get the following exception: [2014-04-01 10:58:08 4821] ERROR (XendDomainInfo:2927) XendDomainInfo.initDomain: exception occurred Traceback (most recent call last): File "/usr/lib/xen-4.1/bin/../lib/python/xen/xend/XendDomainInfo.py", line 2914, in _initDomain

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

This is a repost of sorts, and for that I am sorry; I do not think my original posting subject was very clear, and I have more data about the problem. I'm experiencing lots of kernel errors when reading or writing to a disk that is part of an mdadm softraid-5 array. Since originally detecting this problem, I have isolated it to one disk, but I'm not sure what the cause of the error is. I

Hello List, i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working. Here is my config: ---------------------------------------------- kernel = ''/boot/vmlinuz-2.6.18.8-xenU'' memory = ''128'' root = ''/dev/sda2 ro'' disk = [ ''drbd:pgone-disk,sda2,w'' ] name

This patch fixes IO deadlocks in the vtpm hotplug scripts. Signed off by: Matthew Fioravante matthew.fioravante@jhuapl.edu --- Changed since previous: * rebased off of latest xen stable * replaced instances of gawk with awk diff --git a/tools/hotplug/Linux/vtpm b/tools/hotplug/Linux/vtpm --- a/tools/hotplug/Linux/vtpm +++ b/tools/hotplug/Linux/vtpm @@ -1,22 +1,18 @@ #!/bin/bash +export

Yes, I saw that problem and removing the vif line or changing it to vif0 fixed it for me. Aravindh > -----Original Message----- > From: wei huang [mailto:huanwei@cse.ohio-state.edu] > Sent: Friday, November 04, 2005 12:14 PM > To: Puthiyaparambil, Aravindh > Cc: Mark Williamson; xen-users@lists.xensource.com; ewan@xensource.com > Subject: RE: [Xen-users] Error "Device 0

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

I decided to simplify every that I was doing. I noticed that I had begun to overthink things, and I decided that KISS, is still the best way to go. This has turned out to be something like this; *** File xenmaster.testdomain.com.pp node xenmaster.testdomain.com { include xen } Where xen has been defined as a class in File testdomain.classes.pp class xen { package { xen: ensure =>

I am trying to start a large number of SMP domains (> 50). However, I am unable to create more than 7 domains. When I try creating the 8th domain, I get this error: Using config file "myconf7". VIRTUAL MEMORY ARRANGEMENT: Loaded kernel: 0xc0100000->0xc0344c24 Init. ramdisk: 0xc0345000->0xc0345000 Phys-Mach map: 0xc0345000->0xc0347800 Page tables:

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains

Package: xen-hypervisor-3.0-i386 Version: 3.0.2+hg9681-1 Severity: important Have been trying to get NetBSD to run under debian unstable with the debian supplied hypervisor. Using the 3.0.2-2 hypervisor supplied by XenSource, it works just fine. Because the install process overrides other things, reverified with debian hypervisor afterwards and symptom continues. Attaching the netbsd.cfg and the

----- Forwarded message from pakrat <pakrat@private.neotoma.org> ----- Forwarding to list without attachments. From: pakrat <pakrat@private.neotoma.org> To: Debian Bug Tracking System <submit@bugs.debian.org> Subject: xen-hypervisor-3.0-i386: cannot start NetBSD-HEAD X-Neotoma-Consulting-MailScanner: Found to be clean X-Neotoma-Consulting-MailScanner-From:

Hi All, [I originally posted this message in the main CentOS users' list, but later found this list. So, I'm reposting it here since this is where it belongs.] I'm trying to install a Fedora 8 domU on a CentOS 5 dom0, but the following command fails: [root at xenmaster ~]# virt-install -p -n krs -r 512 -m 00:16:3E:66:94:5F -b xenbr0 --vnc --vncport=5910 -l

Hi everyone! I just wanted to share all the bits of information I needed while trying to get a serial modem to work under a Xen guest :) I found other howtos but every one was missing something. So, my setup consists of dom0 and domU with CentOS 5.2, kernel 2.6.18-92.1.10.el5xen and Xen 3.2.1 To get /dev/ttyS0 to work under domU: - Tell Xen to use something else for its console: in

Just something to be added: - This procedure doesn''t work with a Fedora 9 DomU - Maybe you have to blacklist some modules in the Dom0: AFAIK you have to rmmod (better: blacklist on boot using modprobe.conf) these modules: serial_core 8250 and 8250_pnp ----- Ursprüngliche Mail ---- Von: Federico Fanton <fake@panizzolo.it> An: xen-users@lists.xensource.com Gesendet: Freitag, den

Hi guys I have few problems with live migration ... and I need some professional help :) I have 2 xen servers ... CentOS 5.3 and I want to have a high available cluster Now let`s begin .... xen0: [root@xen0 ~]# fdisk -l Disk /dev/sda: 218.2 GB, 218238025728 bytes 255 heads, 63 sectors/track, 26532 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start

Hello: I just gave 3 tries at compiling a xen kernel. I managed to get the networking in the host to work ok on the third try, unfortuately xend gives me the following errors in my xend.log and will not start. Any ideas? It fails to start with the following error ---------------------------------------------------- /usr/sbin/xend [root@localhost ~]# /usr/sbin/xend start Traceback (most recent