search for: emptydomain

...pport really there in xen-3.2 ? I tried but was not successful in booting even xen-3.2 from xen.org. Did anyone have a success? Or any help on what extra config options I need to pass while compiling a domain0 from xen sources? Thanks, -- Pradeep Singh Rautela http://eagain.wordpress.com http://emptydomain.googlepages.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...00.207.11. Even attaching an ip alias eth0:0 10.0.1.1 netmask 255.255.255.0 does not helps. Shouldn''t vif1.0 be atleast reachable from HVM domain with NAT? Any help, corrections or pointers are welcome. Thanks, --Pradeep -- Pradeep Singh Rautela http://eagain.wordpress.com http://emptydomain.googlepages.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...00.207.11. Even attaching an ip alias eth0:0 10.0.1.1 netmask 255.255.255.0 does not helps. Shouldn''t vif1.0 be atleast reachable from HVM domain with NAT? Any help, corrections or pointers are welcome. Thanks, --Pradeep -- Pradeep Singh Rautela http://eagain.wordpress.com http://emptydomain.googlepages.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

hello, I would like to map (Read/Write) pages owned by a HVM guest from my Dom0 Linux kernel module. I have access to the "machine frame numbers" of these pages. 1. What is the right interface to do this? kmap needs ''struct page'' ptrs which I doubt exist for pages owned by a HVM guest. Is there a hypercall to do this then? 2. Do I need to modify the HVM behavior in

Hello, I am trying to boot a FC6 domU on Xen 3.2 (compiled on a FC6 system). After compiling Xen 3.2 successfully on FC6 and making the ramdisk, I modified the conf.grub as shown below. With this, I was able to boot xen. ------------------------------ --------------------------------------------------------------------------------- # grub.conf generated by anaconda # # Note that you do not have