I''m attempting to boot a domU with a NFS Root filesystem. I''ve configured by domU with a network interface, the DHCP option set correctly, and the necessary nfs root options. The domU is supposed to run openSuSE 11.3. I''ve also used mkinitrd to generate the necessary initrd image with xennet, nfs, etc., and have this configured correctly in my domU configuration. However, every time I try to boot it, it seems to just hang. Here is the last of the output: [ 0.271143] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 0.271369] TCP cubic registered [ 0.271510] NET: Registered protocol family 10 [ 0.271876] lo: Disabled Privacy Extensions [ 0.272102] registered taskstats version 1 [ 0.272135] PCI IO multiplexer device installed. [ 0.272147] Magic number: 1:252:3141 [ 0.272158] XENBUS: Device with no driver: device/vif/0 [ 0.272163] /usr/src/packages/BUILD/kernel-xen-2.6.34.4/linux-2.6.34/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 12.824902] Freeing unused kernel memory: 352k freed [ 12.825043] Write protecting the kernel read-only data: 7104k [ 12.863444] netfront: Initialising virtual ethernet driver. [ 12.971358] udev: starting version 157 [ 13.052730] NET: Registered protocol family 17 [ 14.172028] RPC: Registered udp transport module. [ 14.172035] RPC: Registered tcp transport module. [ 14.172043] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 14.177726] Slow work thread pool: Starting up [ 14.177851] Slow work thread pool: Ready [ 14.177911] FS-Cache: Loaded [ 14.188728] FS-Cache: Netfs ''nfs'' registered for caching So, it looks like xennet loads correctly, and, in fact, looking at my DHCP server logs, I see that the domU picks up an IP address. However, this is as far as it gets - it never contacts the NFS server, and there''s no further output on the console. Any hints would be greatly appreciated - I''ve tried increasing verbosity of the boot process, doing TCP dumps, etc., but I''m not able to figure out what the domU is attempting to do and what''s holding up the boot process. Thanks, Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
When i boot via NFS I specify NFS root in DomU''s config file: root = "/dev/nfs" nfs_root = "/mnt/root" nfs_server = "10.0.0.1" Probably root=/dev/nfs is important... Regards, Felix Am 13.09.2010 23:47, schrieb Nick Couchman:> I''m attempting to boot a domU with a NFS Root filesystem. I''ve configured by domU with a network interface, the DHCP option set correctly, and the necessary nfs root options. The domU is supposed to run openSuSE 11.3. I''ve also used mkinitrd to generate the necessary initrd image with xennet, nfs, etc., and have this configured correctly in my domU configuration. However, every time I try to boot it, it seems to just hang. Here is the last of the output: > > [ 0.271143] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 > [ 0.271369] TCP cubic registered > [ 0.271510] NET: Registered protocol family 10 > [ 0.271876] lo: Disabled Privacy Extensions > [ 0.272102] registered taskstats version 1 > [ 0.272135] PCI IO multiplexer device installed. > [ 0.272147] Magic number: 1:252:3141 > [ 0.272158] XENBUS: Device with no driver: device/vif/0 > [ 0.272163] /usr/src/packages/BUILD/kernel-xen-2.6.34.4/linux-2.6.34/drivers/rtc/hctosys.c: unable to open rtc device (rtc0) > [ 12.824902] Freeing unused kernel memory: 352k freed > [ 12.825043] Write protecting the kernel read-only data: 7104k > [ 12.863444] netfront: Initialising virtual ethernet driver. > [ 12.971358] udev: starting version 157 > [ 13.052730] NET: Registered protocol family 17 > [ 14.172028] RPC: Registered udp transport module. > [ 14.172035] RPC: Registered tcp transport module. > [ 14.172043] RPC: Registered tcp NFSv4.1 backchannel transport module. > [ 14.177726] Slow work thread pool: Starting up > [ 14.177851] Slow work thread pool: Ready > [ 14.177911] FS-Cache: Loaded > [ 14.188728] FS-Cache: Netfs ''nfs'' registered for caching > > So, it looks like xennet loads correctly, and, in fact, looking at my DHCP server logs, I see that the domU picks up an IP address. However, this is as far as it gets - it never contacts the NFS server, and there''s no further output on the console. Any hints would be greatly appreciated - I''ve tried increasing verbosity of the boot process, doing TCP dumps, etc., but I''m not able to figure out what the domU is attempting to do and what''s holding up the boot process. > > Thanks, > Nick > > > > -------- > This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Buckminster Katt
2010-Sep-14 09:54 UTC
[Xen-users] Windows Vista Home Basic guest (XCP, but not necessarily limited to XCP)
Note: I''d like to thank everyone who helped get me started in my last message. Turned out I was able to get the OpenXenManager running on Slackware 13.1 64 bit with only a couple a few installed bits. So, I need to install Windows and the only thing I have hanging around is Vista Home Basic. Blah. I realize this isn''t exactly supported. So it runs, so far pretty reliably, but I''m having one strange problem and I''m not sure if its related to it being Home Basic... I can''t seem to run the Xen-tools install. It asks to reboot the system... does so, but on reboot, it seems to not actually do anything. I looked through the Event Log for any sign of whats going wrong, but nothing is there. I''m more of a Linux guy, so I need a little insight into what the xen-tools do upon bootup after installation. Thanks. BK _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > CONFIG_X86_64_XEN=y > CONFIG_XEN_BLKDEV_FRONTEND=y > CONFIG_XEN_NETDEV_FRONTEND=y > CONFIG_NFS_FS=y > CONFIG_ROOT_NFS=y > CONFIG_IP_PNP=y > CONFIG_IP_PNP_DHCP=y >Thanks for the response, Steve. I guess I assumed that, since the openSuSE mkinitrd supported the addition of NFS features, this would support root over NFS. Perhaps this is not the case and the NFS support in initrd is intended for something else. In any case, I''m compiling a new kernel with the options similar to what you specified above and I''ll see if that works. It''ll have the side benefit of being a much leaner kernel, and of not requiring an initrd, but I much prefer to stick with the vendor-provided, stock kernel when possible. Anyway, I''ll see where this gets me. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> On 2010/09/13 at 15:55, Felix Kuperjans <felix@desaster-games.com> wrote: > When i boot via NFS I specify NFS root in DomU''s config file: > > root = "/dev/nfs" > nfs_root = "/mnt/root" > nfs_server = "10.0.0.1" > > Probably root=/dev/nfs is important... > > Regards, > Felix >Thanks for the suggestions, Felix - I do, indeed, have all of these options specified in my domU config file. I believe the root cause may be the lack of CONFIG_ROOT_NFS support in my kernel, so I''m compiling a purpose-specific kernel with this option enabled and will give that a try. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > Thanks for the response, Steve. I guess I assumed that, since the openSuSE > mkinitrd supported the addition of NFS features, this would support root over > NFS. Perhaps this is not the case and the NFS support in initrd is intended > for something else. In any case, I''m compiling a new kernel with the options > similar to what you specified above and I''ll see if that works. It''ll have > the side benefit of being a much leaner kernel, and of not requiring an > initrd, but I much prefer to stick with the vendor-provided, stock kernel when > possible. Anyway, I''ll see where this gets me. > > -Nick >Tracked it down to two silly problems: - First, my DHCP server had a root server/path option specified, which, apparently overwrites anything you pass to Linux on the command line. I''m assuming this is done intentionally and is sort of a security feature as it prevents folks from messing around with the root paths passed by DHCP and pointing the system off on some other path, but it did throw me a little. I ended up doing a tcpdump and looking at the traffic, and saw the system looking for the wrong DHCP server. I removed that option from the DHCP server and, what do you know, it started mounting the correct root FS! - The second problem was the one with the CONFIG_ROOT_NFS not being compiled into the kernel. So, I compiled a custom kernel with CONFIG_ROOT_NFS enabled and removed a bunch of other stuff that I''ll never use in a xen domU (pretty much all the device drivers :-). - The final issue was that, apparently I needed to explicitly pass the "console=xvc0" option in the extra parameter of the domU config. I still haven''t figured out exactly why this was necessary, but it was, and it works fine, now. On to the next challenge - using AUFS2 so that I can have a common, read-only NFS base for all the domUs, with individual NFS shares for the configuration files, etc., for the domUs. If anyone has hints on this or would like to point me in the direction of some documentation from someone who''s already done it, I''d certainly appreciate it! I took the opportunity recompiling the kernel to patch it with AUFS2 and compile it in, so that piece is taken care of - just have to figure out all the magic initrd stuff that needs to happen to make it work properly. -Nick -------- This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users