similar to: uuid of DomU from DomU.

Hello! My Dom0 config: Xubuntu 8.10 + "Xen-3.3.1 and kernel-2.6.18-xen.hg" I have Nexenta CP2 RC1 (Opensolaris b104) on ZFS file system. I installed this OS in HVM. For PV i used pygrub. My config file: ''ncp2.pygrub'' bootloader = "/usr/bin/pygrub" boot = "c" memory = 512 name = "NexentaPV" uuid =

Hello! I installed NexentaOS (Opensolaris kernel b104+). First booting system is true. Before first rebooting system updates boot_archive. It''s false. Computer is freeze and CapsLock and ScrollLock is blinking. Helps only RESET button. My system is Ubuntu 8.10, kernel-2.6.30-rc3-tip, Xen-3.4-Stable with debug options enabled. My hardware: AMD Athlon64X2 5400+, RAM 4GB. For DomU: mem=1024,

Hi, I am posting my question to both storage-discuss and zfs-discuss as I am not quite sure what is causing the messages I am receiving. I have recently migrated my zfs volume from b104 to b134 and upgraded it from zfs version 14 to 22. It consist of two zvol''s ''vol01/zvol01'' and ''vol01/zvol02''. During zpool import I am getting a non-zero exit code,

Distro: debian unstable Xen version: 4.0.0-2 This is the config: #HVM #still no qemu-dm in debian #kernel = "/usr/lib/xen-4.0/boot/hvmloader" #builder = ''hvm'' #memory = 2048 #name = "webserver" #vif = [''bridge=eth0''] #disk = [''tap:tapdisk:aio:/srv/xen/webserver.img,xvda,w'',''phy:/dev/cdrom,xvdb:cdrom,r'']

I have NexentaCP2 (Opensolaris b104+). Parameters for the kernel: ''zfs-bootfs=syspool/rootfs-nmu-000,bootpath=/xpvd/xdf@0:a'' Pygrub returns: ''zfs-bootfs=syspool/30,bootpath=/xpvd/xdf@0:a'' Result: Boot with pygrub don''t work. What is "30" in syspool/30 ? _______________________________________________ Xen-users mailing list

Forwarding to you original patch requested. It works for me. Boris --- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote: From: eXeC001er <execooler@gmail.com> Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) To: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, July 11, 2010, 9:18 AM 1. Bug fix for error: "Error: Device

Folks, The tag 4.0.1-rc3 has been added to http://xenbits.xensource.com/xen-4.0-testing.hg Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello. Is it available a communication interface between Dom0 and DomU to get some parameteres about DomU without connection via ssh? For example i need to get information about IP addresses that are allocated in DomU. I found following mail-thread: http://xen.1045712.n5.nabble.com/How-to-get-domU-IP-address-td2510278.html Keir Fraser said about xenstore, but as i understand to use xenstore

Announcing new direction of Open Source NexentaOS development: NexentaCP (Nexenta Core Platform). NexentaCP is Dapper/LTS-based core Operating System Platform distributed as a single-CD ISO, integrates Installer/ON/NWS/Debian and provides basis for Network-type installations via main or third-party APTs (NEW). First "unstable" b65-based ISO with ZFS/Boot-capable installer available as

I see in NexentaStor''s announcement of Community Edition 3.0.3 they mention some backported patches in this release. Aside from their management features / UI what is the core OS difference if we move to Nexenta from OpenSolaris b134? These DeDup bugs are my main frustration - if a staff member does a rm * in a directory with dedup you can take down the whole storage server - all with

Can i using pv-grub for loading OpenSolaris on zfs volume? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Are these the current functional procedures for dropping a dom0 on a jaunty 64 bit server? xen-tools: http://bderzhavets.wordpress.com/2009/08/14/attempt-of-prevu-xen-3-4-1-hypervisor-on-ubuntu-jaunty-server-64-bit/ kernel: http://bderzhavets.wordpress.com/2009/07/07/building-xenified-2-6-30-1-kernel-via-xen-patches-2-6-30-2-tar-bz2/ Regarding the patches used in the above procedure from here:

Hi All, I am trying to attach floppy virtual image to Windows domU. Either it is not attaching or domU is not showing floppy drive? domU config: 1. disk = [ ''file:/root/xenwin.img,hda,w'', ''file:/opt/Windows-Xp.iso,hdc:cdrom,r'', ''file:/root/win-boot.img,fd:floppy,r'' ] boot = "cda" In above format the window domU is booting but

Hello all, I''ve patched pv-grub to allow it to boot a Solaris PV domU using an unmodified menu.lst. The attached patch has been tested with various Solaris versions (Solaris 11 Express, OpenIndiana 151a, OpenSolaris 134, Nexenta Core 3.0.1; all 64-bit). I appreciate your feedback. The patch consists mainly of Oracle''s grub modifications, which add ZFS support and

When I try to virt-install a PV instance of F11, I''m getting an ''invalid kernel'' message, as if it''s not a Xen kernel. I have tried both the i386 and x86_64 versions. Is there any weirdness with this distro that I''m not aware of?

Hi all, I installed a paravirt CentOS 5.4 domU on a CentOS 5.4 dom0 environment. I compiled the domU kernel with framebuff console. But I couldn’t using VNC to connect to the domU console. The kernel boot message could print on the vnc console. But after the boot process, the console appears on the text console in dom0 again. The configfile is as follows: vfb = [

Hi list, I setup on 2 Xen Dom0s drbd/gfs a logical volume, this works as primary/primary so both DomUs will be able to write on them at the same time. But I dont know how to mount them from my domUs, I can see them with fdisk -l. The partition is /dev/xvdb1 SHould I install gfs on domUs and mount them on each as gfs partitions? [root@p3x0501 ~]# fdisk -l Disk /dev/xvda: 5368 MB, 5368709120

Hello, I''ve got a big problem when I try to install Zimbra on a xen debian etch vm. Eeek! page_mapcount(page) went negative! (-1) page pfn = 7141 page->flags = 4000083c page->count = 2 page->mapping = cd946510 vma->vm_ops = 0x0 ------------[ cut here ]------------ kernel BUG at mm/rmap.c:669! invalid opcode: 0000 [#1] SMP Pid: 7717, comm: java Not tainted

Hi. I need more space on my domU server, so i create a file image to attach it to the domU. But when i load that image in the domU, show a size very different to the create. I create the file with this command dd if=/dev/zero of=/xen/domains/SRV03/opt-disk.img bs=1024k seek=30720 count=30720 (The idea is create an image disk with 30GB, but when i check the disk on the domU show 64GB.)

Hi Everyone, Can anyone confirm if a xen based domU can be used for snort setup? It is not for commercial use, rather just SOHO use. Regards, dot.yet _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users