Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Sun, Jan 30, 2011 at 11:52:56PM +, M A Young wrote: On Sun, 30 Jan 2011, W. Michael Petullo wrote: I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. With the exception that xl doesn't support embedded python code in the cfgfiles. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. With the exception that xl doesn't support embedded python code in the cfgfiles. I am able to boot a DomU kernel using xl with xen-4.1.0-0.1.rc2.fc14.x86_64 and kernel-2.6.38-0.rc2.git3.2.xendom0.fc15.x86_64. Both block and network devices work. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
] usbcore: registered new interface driver hiddev [ 0.169115] usbcore: registered new interface driver usbhid [ 0.169122] usbhid: USB HID core driver [ 0.169145] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 0.169290] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use [ 0.169304] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or [ 0.169312] sysctl net.netfilter.nf_conntrack_acct=1 to enable it. [ 0.169376] ip_tables: (C) 2000-2006 Netfilter Core Team [ 0.169395] TCP cubic registered [ 0.169401] Initializing XFRM netlink socket [ 0.169411] NET: Registered protocol family 17 [ 0.169536] registered taskstats version 1 [ 0.169557] XENBUS: Device with no driver: device/vbd/51712 [ 0.169563] XENBUS: Device with no driver: device/vif/0 [ 0.169578] Magic number: 1:252:3141 [ 0.169597] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 0.169614] Initalizing network drop monitor service [ 0.169776] Freeing unused kernel memory: 944k freed [ 0.170033] Write protecting the kernel read-only data: 10240k [ 0.174701] Freeing unused kernel memory: 1576k freed [ 0.175744] Freeing unused kernel memory: 1836k freed [9;0][8] Greetings. anaconda installer init version 14.22 starting mounting /proc filesystem... done (process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed creating /dev filesystem... done starting udev...done mounting /dev/pts (unix98 pty) filesystem... done mounting /sys filesystem... done (process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed anaconda installer init version 14.22 using /dev/hvc0 as console trying to remount root filesystem read write... done mounting /tmp as tmpfs... done (process:1): GLib-CRITICAL **: g_hash_table_lookup_extended: assertion `hash_table != NULL' failed running install... running /sbin/loader detecting hardware... waiting for hardware to initialize... Boris. --- On Mon, 1/31/11, W. Michael Petullo m...@flyn.org wrote: From: W. Michael Petullo m...@flyn.org Subject: Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2 To: xen@lists.fedoraproject.org Date: Monday, January 31, 2011, 8:40 AM I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. With the exception that xl doesn't support embedded python code in the cfgfiles. I am able to boot a DomU kernel using xl with xen-4.1.0-0.1.rc2.fc14.x86_64 and kernel-2.6.38-0.rc2.git3.2.xendom0.fc15.x86_64. Both block and network devices work. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, 27 Jan 2011, W. Michael Petullo wrote: When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Sun, Jan 30, 2011 at 6:17 PM, W. Michael Petullo m...@flyn.org wrote: I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. You can pull examples for the Xen test suite, for example, take a look at one of the tests: http://www.chiark.greenend.org.uk/~xensrcts/logs/5501/ The syntax is rather similar, and we'll need to formally document it on the xen wiki soon. Hope that helps, Todd -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Sun, 30 Jan 2011, W. Michael Petullo wrote: I have finally got a domU to boot in this sort of situation, having found a few bugs in 4.1.0-rc2 on the way when trying to use pygrub as a bootloader. Note that you may have to use xl rather than xm because they are deprecating xm and xm may not have support for qemu block backends. Does anyone know where I can find documentatin on domain configuration for xl? There does not seem to be a man page and a review of the Xen Wiki did not find authoritative documentation. I am trying to figure out how to write an xl configuration, i.e., rewrite xmexample1 to work with xl. It is supposed to be a direct replacement for xm, the idea being for configuration files for xm to work for xl, though not necessarily the other way around. In practice, you can still find stuff that doesn't yet work. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, Jan 27, 2011 at 05:03:57PM -0600, W. Michael Petullo wrote: Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. I have written the following domain config (to try to force the QEMU block backend): kernel = '/tmp/openwrt-x86-xen_domu-vmlinuz' memory =32 # NOTE: Generated with qemu-img convert -f raw -O qcow2 input.img output.qcow2 disk = [ 'tap:qcow2:/tmp/openwrt-x86-xen_domu-rootfs-ext2.qcow2,xvda,r', ] vif = [ 'bridge=virbr0' ] name = '2.6.38-DomU-Test' root = '/dev/xvda1' on_crash = 'destroy' When I boot, I get: [...] NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear gree...@candelatech.com All bugs added by David S. Miller da...@redhat.com Using IPI No-Shortcut mode XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 Just making sure.. you're running Xen 4.1 ? The userspace qemu blkback implementation is *only* in Xen 4.1 .. And it should get used automatically if dom0 kernel blkback is not available. -- Pasi -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. I have written the following domain config (to try to force the QEMU block backend): kernel = '/tmp/openwrt-x86-xen_domu-vmlinuz' memory =32 # NOTE: Generated with qemu-img convert -f raw -O qcow2 input.img output.qcow2 disk = [ 'tap:qcow2:/tmp/openwrt-x86-xen_domu-rootfs-ext2.qcow2,xvda,r', ] vif = [ 'bridge=virbr0' ] name = '2.6.38-DomU-Test' root = '/dev/xvda1' on_crash = 'destroy' When I boot, I get: [...] NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear gree...@candelatech.com All bugs added by David S. Miller da...@redhat.com Using IPI No-Shortcut mode XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 Just making sure.. you're running Xen 4.1 ? The userspace qemu blkback implementation is *only* in Xen 4.1 .. Yes. I am using Michael's Xen 4.1 package. And it should get used automatically if dom0 kernel blkback is not available. That was my understanding, but I have not yet been able to get this to work. -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
On Thu, 27 Jan 2011, W. Michael Petullo wrote: Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] 2.6.38-rc dom0 kernel and xen 4.1.0-rc2
Now, the last issue remaining for me is the backend drivers. My understanding is that, in the absence of backends being accepted upstream, we can use QEMU-based drivers. This would be acceptable for our work. Has anyone been using these with Fedora 15? In theory the block driver should work in 4.1.0, though I am not sure about the net driver. In practise I have failed so far to get the block driver working so far. This post today http://lists.xensource.com/archives/html/xen-devel/2011-01/msg01847.html talks about what block driver configurations should work. I have written the following domain config (to try to force the QEMU block backend): kernel = '/tmp/openwrt-x86-xen_domu-vmlinuz' memory =32 # NOTE: Generated with qemu-img convert -f raw -O qcow2 input.img output.qcow2 disk = [ 'tap:qcow2:/tmp/openwrt-x86-xen_domu-rootfs-ext2.qcow2,xvda,r', ] vif = [ 'bridge=virbr0' ] name = '2.6.38-DomU-Test' root = '/dev/xvda1' on_crash = 'destroy' When I boot, I get: [...] NET: Registered protocol family 17 802.1Q VLAN Support v1.8 Ben Greear gree...@candelatech.com All bugs added by David S. Miller da...@redhat.com Using IPI No-Shortcut mode XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s... When I try to use: disk = [ 'file:/tmp/openwrt-x86-xen_domu-rootfs-ext2.img,xvda,r', ] I get: [No boot] Error: Device 51712 (vbd) could not be connected. Path closed or removed during hotplug add: backend/vbd/13/51712 state: 1 -- Mike :wq -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen