search for: ssidrefs

...ump: ============ POLICY REFERENCE = example.client_v1. PolicyVer = 0. XML Vers. = 1.0 Magic = 1debc. Len = 198. Primary = CHINESE WALL (c=1, off=40). Secondary = SIMPLE TYPE ENFORCEMENT (c=2, off=b8). Chinese Wall policy: ==================== Policy version= 0. Max Types = 4. Max Ssidrefs = 7. Max ConfSets = 1. Ssidrefs Off = 24. Conflicts Off = 5c. Runing T. Off = 64. C. Agg. Off = 6c. SSID To CHWALL-Type matrix: ssidref 0: 00 00 00 00 ssidref 1: 00 00 00 01 <-- Domain-0 ssidref 2: 00 01 00 00 ssidref 3: 01 00 00 00 ssidref 4: 00 00 01 00 ssidref 5...

- This minor patch implements the missing stub function security_label_to_details in the dummy module. This stub function is necessary to create domains with network interfaces for modules that do not implement the security_label_to_details function. Signed-off-by: George Coker <gscoker@alpha.ncsc.mil> _______________________________________________ Xen-devel mailing list

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, I have Xen (unstable) on two Debian Sarge 2.4.27 systems, one of which is an nfs server and the other the nfs client. I am trying to set up NFS root so that I can live migrate my domains from one to another. My /etc/exports on N1(10.5.144.29) /myfs1/foo 10.5.144.27(rw,sync,no_root_squash) 10.5.144.29(rw,sync,no_root_squash) 10.5.144.30(rw,sync,no_root_squash) My /hosts.allow on N1

hi, I am trying to start a new domainU but got the error: Error: Device 0 (vif) could not be connected. Hotplug scripts not working I have struggled with it for a long time. I found somebody else report this but can not find a solution. The xen version is xen-3.0 latest version. I do not have a initrd. Domain0 works fine but when I create a new domain, it always gives an error as above. Thanks,

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and

I''m running Xen 3.0.2 on a system that''s based on Slackware 10.2 as Dom0. DomU is also slackware 10.2. Am using the kernel that came with 3.0.2 - no custom config, just a "make world", etc.. Did have to add grub of course. When I start up xend, I get the following on /var/adm/messages: Apr 23 21:04:11 rc25 kernel: Bridge firewalling registered Apr 23 21:04:11 rc25

- The patch does away with the autogenerated xsm.py file and introduces a config parameter in xend-config.sxp to determine the security module. The parameter is (xsm_module_name {acm, dummy, flask}). The default setting/option is dummy. .hgignore is also updated to stop ignoring xsm.py on commits. - The patch has created an xsconstant for XS_POLICY_FLASK and updated the toolchain to check the

This is patch 2of2 of an eighth cut of the patch of the proposed XENMEM_claim_pages hypercall/subop, taking into account feedback from Jan and Keir and IanC and Matthew Daley. As requested by Jan, this is a separate post of the tools part of the patch. NOTE: This patch must be applied after the hypervisor part of the patchset or otherwise may break the build! v5->v8: - no change in this

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]

I''ve installed a Fedora Core 5 2054 and Xen 3.0.4.1 on a Intel 945 mainboard with xen3.0 user manual, everything seemed fine then. After I rebooted and chosed to enter into xen kernel , I find xend doesn''t run . when I try to run manually by input: /etc/init.d/xend start there some dot(indicating time maybe) appeared, and then nothing happened, the xend jun didn''t get

Hello again, now my xen works. But a strange thing: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 2514 4 r----- 76.2 vx1 1 256 1 -b---- 6.1 vx2 2 256 1 -b---- 5.8 vx3 3 256 1 -b---- 5.3 vx4

Hi all, I have recently installed FC5 along with xen via yum. I''ve successfully rebooted using the dom0 (2.6.16-1.2133_FC5) kernel, started xend, and trying to start my first domU after following the instructions in the user guide. However, I keep receiving a kernel panic and an error about XENBUS timeout. Any help greatly appreciated as I am stumped. Should I be using the provided

Hi, I have compiled xen-unstable (using hg clone http://xenbits.xensource.com/xen-unstable.hg). I have successfully booted into the dom0 kernel. output of xm list: Name ID Mem VCPUs State Time(s) Domain-0 0 932 1 r----- 591.2 But whenever I xm create, I get: # xm create /etc/xen/domu1 Using config file

I''ve got a system with 3 nics. eth0 is down, eth1 is external and eth2 is internal. (This is in a "lab" so the "external" is a 10.x.x.x address.) Before starting xen, the broadcast for eth2 is 192.168.1.255, after starting it becomes 0.0.0.0 - which sure doesn''t look right to me - plus I''m getting networking problems. Been digging for a while and

Hi, I''m trying to use a Gentoo whit Xem 4.0, but I try: xm create windows2008r2.hvm I get the error: Error: coercing to Unicode: need string or buffer, NoneType found. Does anybody knows how to solve that? windows2008r2.hvm: kernel = "hvmloader" builder=''hvm'' memory = 512 name = "Windows2008R2" vcpus=2 acpi=1 apic=1 disk = [

I am working on FC5 [root@blrkec38274d ~]# xm list Error: Error connecting to xend: No such file or directory. Is xend running? THE LOG FILE xend.log is below.... [2006-06-28 18:22:59 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-06-28 18:22:59 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-06-28 18:23:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:201)

Hi. I am trying get use xen vmx, it shows only black window. I attach my config and logs. config: import os, re arch = os.uname()[4] if re.search(''64'', arch): else: kernel = "/usr/lib/xen/boot/vmxloader" builder=''vmx'' memory = 128 name = "bluszcz" vif = [ ''type=ioemu, bridge=xenbr0'' ] disk = [