1: is it possible to use ioemu:sda instead of ioemu:hda ? 2: is ioemu keyword optionnal ? conf seems to work without 3: why d i need to put vfb = [ "type=vnc,vncunused=1,keymap=fr" ] line ? seperate vnc = 1 + vncunused = 1 look identical to me, but are ignored. have the conf parser changed ? 4: during dom0 startup:> * Starting Xen control daemon ... > * Error: either "local" is duplicate, or "192.168.0.80/32" is agarbage. [ ok ] before I do <<many things with my conf>>, it used to complain about inet6. So, it seems the problem is not really IPv6 support, but something else. This may be Gentoo specific issue, or even kernel specific. 192.168.0.80 is an alias for eth0; after Xend, all my IPs are removed, and I have to re-declare all of them manually. any idea ? 5: when i start a/any domU, syslog get filled of messages: May 19 18:46:29 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=8950 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6900 comm="/usr/sbin/hald)) May 19 18:46:29 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=8950 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6900 comm="/usr/sbin/hald)) May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/40/0 May 19 18:46:29 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=8950 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6900 comm="/usr/sbin/hald)) May 19 18:46:29 uranus dbus-daemon: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.9" (uid=1000 pid=8950 comm="/usr/lib/enlightenment/utils/enlightenment_fm) interface="org.freedesktop.Hal.Device" member="QueryCapability" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=6900 comm="/usr/sbin/hald)) May 19 18:46:29 uranus kernel: device tap40.0 entered promiscuous mode May 19 18:46:29 uranus kernel: eth0: port 2(tap40.0) entering forwarding state May 19 18:46:29 uranus kernel: device vif40.0 entered promiscuous mode May 19 18:46:29 uranus kernel: eth0: port 3(vif40.0) entering forwarding state May 19 18:46:29 uranus kernel: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: iptables setup failed. This may affect guest networking. May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif40.0, bridge eth0. May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/40/0/hotplug-status connected to xenstore. May 19 18:46:31 uranus avahi-daemon[6611]: Joining mDNS multicast group on interface vif40.0.IPv6 with address fe80::fcff:ffff:feff:ffff. May 19 18:46:31 uranus avahi-daemon[6611]: New relevant interface vif40.0.IPv6 for mDNS. May 19 18:46:31 uranus avahi-daemon[6611]: Registering new address record for fe80::fcff:ffff:feff:ffff on vif40.0.*. May 19 18:46:31 uranus avahi-daemon[6611]: Joining mDNS multicast group on interface tap40.0.IPv6 with address fe80::xxxx:74ff:fe82:xxxx. May 19 18:46:31 uranus avahi-daemon[6611]: New relevant interface tap40.0.IPv6 for mDNS. May 19 18:46:31 uranus avahi-daemon[6611]: Registering new address record for fe80::xxxx:74ff:fe82:xxxx on tap40.0.*. May 19 18:46:38 uranus avahi-daemon[6611]: Interface tap40.0.IPv6 no longer relevant for mDNS. May 19 18:46:38 uranus avahi-daemon[6611]: Leaving mDNS multicast group on interface tap40.0.IPv6 with address fe80::xxxx:74ff:fe82:xxxx. May 19 18:46:38 uranus avahi-daemon[6611]: Withdrawing address record for fe80::xxxx:74ff:fe82:xxxx on tap40.0. May 19 18:46:38 uranus kernel: eth0: port 2(tap40.0) entering disabled state May 19 18:46:38 uranus kernel: device tap40.0 left promiscuous mode May 19 18:46:38 uranus kernel: eth0: port 2(tap40.0) entering disabled state May 19 18:46:38 uranus halevt: Running: halevt-umount -u /org/freedesktop/Hal/devices/net_6e_a7_74_82_dd_17; halevt-umount -s May 19 18:46:38 uranus logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vkbd/40/0 May 19 18:46:38 uranus logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/40/0 May 19 18:46:38 uranus logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vfb/40/0 May 19 18:46:38 uranus avahi-daemon[6611]: Interface vif40.0.IPv6 no longer relevant for mDNS. May 19 18:46:38 uranus avahi-daemon[6611]: Leaving mDNS multicast group on interface vif40.0.IPv6 with address fe80::fcff:ffff:feff:ffff. May 19 18:46:38 uranus avahi-daemon[6611]: Withdrawing address record for fe80::fcff:ffff:feff:ffff on vif40.0. May 19 18:46:38 uranus kernel: eth0: port 3(vif40.0) entering disabled state May 19 18:46:38 uranus kernel: eth0: port 3(vif40.0) entering disabled state May 19 18:46:38 uranus logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/40/0 May 19 18:46:38 uranus logger: /etc/xen/scripts/vif-bridge: brctl delif eth0 vif40.0 failed May 19 18:46:38 uranus logger: /etc/xen/scripts/vif-bridge: ifconfig vif40.0 down failed May 19 18:46:38 uranus kernel: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. May 19 18:46:38 uranus logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif40.0, bridge eth0. May 19 18:46:38 uranus halevt: Running: halevt-umount -u /org/freedesktop/Hal/devices/net_fe_ff_ff_ff_ff_ff_3; halevt-umount -s May 19 18:46:38 uranus logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/40/0 ATM it works, and domU have network, but I wonder about those ones, that could induce problems in the future: May 19 18:46:29 uranus kernel: physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for non-bridged traffic is not supported anymore. May 19 18:46:29 uranus logger: /etc/xen/scripts/vif-bridge: iptables setup failed. This may affect guest networking. Thank you. -- Gentoo stable with many instable components Linux uranus 2.6.32-xen-r1-Gentoo-uranus-1-15 #2 SMP Tue May 4 23:46:21 CEST 2010 x86_64 AMD Phenom(tm) II X4 965 Processor AuthenticAMD GNU/Linux uranus ~ # xm info host : uranus release : 2.6.32-xen-r1-Gentoo-uranus-1-15 version : #2 SMP Tue May 4 23:46:21 CEST 2010 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 3415 hw_caps : 178bf3ff:efd3fbff:00000000:00000310:00802001:00000000:000037ff:00000000 virt_caps : hvm total_memory : 3965 free_memory : 820 node_to_cpu : node0:0-3 node_to_memory : node0:820 xen_major : 3 xen_minor : 4 xen_extra : .2 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.3.4 (Gentoo 4.3.4 p1.0, pie-10.1.5) cc_compile_by : root cc_compile_domain : cc_compile_date : Fri Jan 15 04:03:11 CET 2010 xend_config_format : 4 uranus ~ # _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 25, 2010 at 11:43 PM, Doublehp <doublehp-xen@doublehp.org> wrote:> 1: is it possible to use ioemu:sda instead of ioemu:hda ?I assume this is a HVM domU? On new version of Xen anyway, yes, it''s possible (I''ve used hda, sda, xvda). But in most cases it won''t matter. First, I''m not sure if you should put ioemu: in the first place. It does harm in the past (prevents GPLPV from working), and the domU works just fine without it. Second, on non xen-aware HVM domU (like Windows, or Linux without PV drivers), it would still detect the same thing (first disk on primary IDE controller). For PV domU, you should never put ioemu. As for which disk (hda, sda, xvda), older kernel version (like 2.6.18-xen) used to respect them and present it as-is to domU. Newer kernels (like pv_ops) will silently change it to xvda no matter what you put in domU config file. So why do you want to put sda instead of hda?> > 2: is ioemu keyword optionnal ? conf seems to work without>From what I understand, it started out to mean something, usingemulated device (i.e. using qemu) instead of PV device. It has been somewhat useless for a long time (and could even cause harm, like I mentioned earlier). Perhaps others can give a better explanation about this. The short version is I don''t see a reason why you should still put ioemu.> > 3: why d i need to put vfb = [ "type=vnc,vncunused=1,keymap=fr" ] line ? > seperate vnc = 1 + vncunused = 1 look identical to me, but are ignored. > have the conf parser changed ?Historically, the virtual frame buffer (vfb) which is accessible via vnc/sdl is only available for HVM domU. vfb for domU was added later, using a different syntax (vfb line). So there are two different syntax, one for HVM, and one for PV. If you ask "why not make the syntax the same since the functionality is the same", then you have to ask the developers.> > 4: during dom0 startup: >> * Starting Xen control daemon ... >> * Error: either "local" is duplicate, or "192.168.0.80/32" is a > garbage. [ ok ] > > before I do <<many things with my conf>>, it used to complain about > inet6. So, it seems the problem is not really IPv6 support, but > something else. This may be Gentoo specific issue, or even kernel specific. > > 192.168.0.80 is an alias for eth0; after Xend, all my IPs are removed, > and I have to re-declare all of them manually.It might be related to the fact that xen''s default network bridge script does some interface renaming and ip address/route transfer. In your case it doesn''t work so well. I suggest you create bridges manually using your OS config files, and comment out network-script line on xend-config.sxp. Note that this approach requires some basic knowledge on how Linux bridging works. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 25/06/10 19:14, Fajar A. Nugraha wrote:> On Fri, Jun 25, 2010 at 11:43 PM, Doublehp <doublehp-xen@doublehp.org> wrote: >> 1: is it possible to use ioemu:sda instead of ioemu:hda ? > So why do you want to put sda instead of hda?Once, i wanted to install Debian in a domU using install CD, and, I wanted to force the installer to detec the virtual disk as being SCSI instead of P-ATA/IDE. I was wondering if putting :sda would make qemu understand I wanted any kind of SCSI ... I had not phrased my first email properly.>> 4: during dom0 startup: >>> * Starting Xen control daemon ... >>> * Error: either "local" is duplicate, or "192.168.0.80/32" is a >> garbage. [ ok ] >> >> before I do <<many things with my conf>>, it used to complain about >> inet6. So, it seems the problem is not really IPv6 support, but >> something else. This may be Gentoo specific issue, or even kernel specific. >> >> 192.168.0.80 is an alias for eth0; after Xend, all my IPs are removed, >> and I have to re-declare all of them manually. > > It might be related to the fact that xen''s default network bridge > script does some interface renaming and ip address/route transfer. In > your case it doesn''t work so well. I suggest you create bridges > manually using your OS config files, and comment out network-script > line on xend-config.sxp. Note that this approach requires some basic > knowledge on how Linux bridging works. >http://bugs.gentoo.org/show_bug.cgi?id=258378 proposed patch does not work for me. I have good knowledge in iptables, but, not in Xen related routing and bridging. What i know is, as I change anything in the Xen conf, domU looses networking. After a long chat on IRC, I just ... don''t understand how Xen plays with interfaces; I finally gave up trying to understand. Things in my host do not work like explained in tutos, and, not as the IRC peopled explained me. I wonder if Gentoo is hiding somewhere some if-rename call so that eth0 and peth0 are *NOT* inverted as they should be after xend have started ... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users