I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The device can not find enough free resources to use. I get that same message for the vga adapter and an unrecognized pci device. Any body have any ideas of what to disable or try to make this work? Thanks Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Greetings, I would like to use unionfs for my Virtual Machines, and I would like to use initramfs instead of an initrd. But I am not sure how to accomplish this. I have read over the HOWTO section for Copy of Write, but haven''t really found the solution I want. I do not know much about initramfs or initrd for that matter, but I do know initramfs is suppose to replace the initrd so I would like to use it. Ultimately what I want is to have a read only partition on LVM2 that contains the virtual machine image, and this would be readonly. Then I would have another partition that would be read write. I am familiar with unionfs, but not too much with Xen, so if any can provide assistance please do! Thanks, James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
________________________________ From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike Fremont Sent: 02 November 2006 22:30 To: xen-users@lists.xensource.com Subject: [Xen-users] windows 2003 I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The device can not find enough free resources to use. I get that same message for the vga adapter and an unrecognized pci device. Any body have any ideas of what to disable or try to make this work? Thanks Mike Are you saying that your REAL network card is an Intel one, or that you''ve set your vm configuration file to say it''s an Intel network adapter? There is three (I think) options for network devices within QEMU, which is what your Windows installation will see - Windows don''t see your REAL HARDWARE, just what QEMU tells it there is, and the network card by default is a RealTek 8139, but you can select another one in the config for your VM. I would try another network card, something like: vif = [ ''type=ioemu, model=ne2k_pci'' ] I believe that QEMU supports (that''s what qemu-doc.html says): ne2k_pci _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
________________________________ From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Mike Fremont Sent: 02 November 2006 22:30 To: xen-users@lists.xensource.com Subject: [Xen-users] windows 2003 I have finally gotten one version of windows 2003 r2 x64 installed as a guest. The bad news is no network. The network tab says it''s a realtek 8139 when I know it is a intel. I tried downloading the intel drivers and they wont install says it''s the wrong hard ware. Is this common that it uses a 8139 as a generic network card? Also the network card shows The device can not find enough free resources to use. I get that same message for the vga adapter and an unrecognized pci device. Any body have any ideas of what to disable or try to make this work? Thanks Mike Are you saying that your REAL network card is an Intel one, or that you''ve set your vm configuration file to say it''s an Intel network adapter? There is three (I think) options for network devices within QEMU, which is what your Windows installation will see - Windows don''t see your REAL HARDWARE, just what QEMU tells it there is, and the network card by default is a RealTek 8139, but you can select another one in the config for your VM. I would try another network card, something like: vif = [ ''type=ioemu, model=ne2k_pci'' ] I believe that QEMU supports (that''s what qemu-doc.html says): ne2k_pci, rll8139, smc91c111 and lance So, it may be that the 64-bit driver for rtl8139 isn''t working right - try another one and see if that works any better... -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats schrieb:> > ------------------------------------------------------------------------ > *From:* xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] *On Behalf Of *Mike > Fremont > *Sent:* 02 November 2006 22:30 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] windows 2003 > > I have finally gotten one version of windows 2003 r2 x64 installed > as a guest. > > > > The bad news is no network. >Same with me.> > The network tab says it’s a realtek 8139 when I know it is a > intel. I tried downloading the intel drivers and they wont > install says it’s the wrong hard ware. Is this common that it > uses a 8139 as a generic network card? > > > > Also the network card shows > > > > The device can not find enough free resources to use. > > > > I get that same message for the vga adapter and an unrecognized > pci device. > > > > Any body have any ideas of what to disable or try to make this work? > > > > > > Thanks > > Mike > > > > > > Are you saying that your REAL network card is an Intel one, or that > you''ve set your vm configuration file to say it''s an Intel network > adapter? There is three (I think) options for network devices within > QEMU, which is what your Windows installation will see - Windows don''t > see your REAL HARDWARE, just what QEMU tells it there is, and the > network card by default is a RealTek 8139, but you can select another > one in the config for your VM. > > > > I would try another network card, something like: > > vif = [ ''type=ioemu, model=ne2k_pci'' ] > > I believe that QEMU supports (that''s what qemu-doc.html says): > ne2k_pci, rll8139, smc91c111 and lance >Not all of them are available in Xen, the supported ones are: ne2k_pci,rtl8139,pcnet> > So, it may be that the 64-bit driver for rtl8139 isn''t working right - > try another one and see if that works any better... >I''ve tried all of the above, rtl8139 is the only one that gets a driver, but cannot be used (due to resource problems).> > Mats >Marcel _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 11/3/06, Otter <OtterzStuff@bellsouth.net> wrote:> > Greetings, > > I would like to use unionfs for my Virtual Machines, and I would like to > use initramfs instead of an initrd. But I am not sure how to accomplish > this. I have read over the HOWTO section for Copy of Write, but haven''t > really found the solution I want. I do not know much about initramfs or > initrd for that matter, but I do know initramfs is suppose to replace > the initrd so I would like to use it. Ultimately what I want is to have > a read only partition on LVM2 that contains the virtual machine image, > and this would be readonly. Then I would have another partition that > would be read write.Just configure two disks in the VM config file. They are available as partitions inside the domU then. Then, I guess the definition how they should be used to achieve you goal is some config in the initrd, right? I am familiar with unionfs, but not too much with> Xen, so if any can provide assistance please do!Your question is very generic, and multiple questions at once. Better describe different problems in different mail (or, forgive me if I don''t know enough abput initramfs and unionfs to understand they belong together). What did you try already, and what were your problems? What is "the solution you want" you didn''t find in the HOWTO''s? Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am having problems with the initrd/initramfs. I am not really sure of what needs to be done inside the init script for a VM. Since I have never used a ramdisk with a VM. And I have never created an initrd/initramfs before ( aside from using the generic mkinitrd/mkinitfamfs ). Meaning I have no idea how to implement this in the init script. I have placed all needed partitions in the Xen config something like: <lvm volume with VM image> as hda ro <lvm volume to contain the changes> as hdb w <lvm volume that contains swap> as hdc w I am not near the machine with the exact Xen config, but I can post it in about 12 hours. Inside the init script, do I need to leave all of the script that is generated by the mkinitrd/mkinitramfs? I have tried just modifying the section of the script where it configures the root file system. I mount hda, hdb in directories in the initrd, and then mount the union of the two to another directory in the initrd. I then try and make the union directory the root filesystem. Then it all dies, with a kernel panic ''trying to kill init''. I can post the script later today as well. I just don''t know enough about init scripts to begin tracing my error =\ Thanks for the reply! Henning Sprang wrote:> On 11/3/06, *Otter* <OtterzStuff@bellsouth.net > <mailto:OtterzStuff@bellsouth.net>> wrote: > > Greetings, > > I would like to use unionfs for my Virtual Machines, and I would > like to > use initramfs instead of an initrd. But I am not sure how to > accomplish > this. I have read over the HOWTO section for Copy of Write, but > haven''t > really found the solution I want. I do not know much about > initramfs or > initrd for that matter, but I do know initramfs is suppose to replace > the initrd so I would like to use it. Ultimately what I want is to > have > a read only partition on LVM2 that contains the virtual machine image, > and this would be readonly. Then I would have another partition that > would be read write. > > > > Just configure two disks in the VM config file. They are available as > partitions inside the domU then. Then, I guess the definition how they > should be used to achieve you goal is some config in the initrd, right? > > I am familiar with unionfs, but not too much with > Xen, so if any can provide assistance please do! > > > Your question is very generic, and multiple questions at once. > Better describe different problems in different mail (or, forgive me > if I don''t know enough abput initramfs and unionfs to understand they > belong together). > > What did you try already, and what were your problems? What is "the > solution you want" you didn''t find in the HOWTO''s? > > Henning > > ------------------------------------------------------------------------ > > _______________________________________________ > 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
I tried those settings and I can not get the guest to boot. Great ideas any others? M -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Marcel Ritter Sent: Friday, November 03, 2006 5:59 AM To: xen-users@lists.xensource.com Subject: Re: [Xen-users] windows 2003 Petersson, Mats schrieb:> >------------------------------------------------------------------------> *From:* xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] *On Behalf Of *Mike > Fremont > *Sent:* 02 November 2006 22:30 > *To:* xen-users@lists.xensource.com > *Subject:* [Xen-users] windows 2003 > > I have finally gotten one version of windows 2003 r2 x64 installed > as a guest. > > > > The bad news is no network. >Same with me.> > The network tab says it''s a realtek 8139 when I know it is a > intel. I tried downloading the intel drivers and they wont > install says it''s the wrong hard ware. Is this common that it > uses a 8139 as a generic network card? > > > > Also the network card shows > > > > The device can not find enough free resources to use. > > > > I get that same message for the vga adapter and an unrecognized > pci device. > > > > Any body have any ideas of what to disable or try to make this work? > > > > > > Thanks > > Mike > > > > > > Are you saying that your REAL network card is an Intel one, or that > you''ve set your vm configuration file to say it''s an Intel network > adapter? There is three (I think) options for network devices within > QEMU, which is what your Windows installation will see - Windows don''t > see your REAL HARDWARE, just what QEMU tells it there is, and the > network card by default is a RealTek 8139, but you can select another > one in the config for your VM. > > > > I would try another network card, something like: > > vif = [ ''type=ioemu, model=ne2k_pci'' ] > > I believe that QEMU supports (that''s what qemu-doc.html says): > ne2k_pci, rll8139, smc91c111 and lance >Not all of them are available in Xen, the supported ones are: ne2k_pci,rtl8139,pcnet> > So, it may be that the 64-bit driver for rtl8139 isn''t working right - > try another one and see if that works any better... >I''ve tried all of the above, rtl8139 is the only one that gets a driver, but cannot be used (due to resource problems).> > Mats >Marcel _______________________________________________ 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
Hi, On 11/3/06, Otter <OtterzStuff@bellsouth.net> wrote:> > I am having problems with the initrd/initramfs. I am not really sure of > what needs to be done inside the init script for a VM.Nothing special. You don''t create a VM specific init script. In most cases you just use you distro of choice''s deafult init script. Since I have> never used a ramdisk with a VM. And I have never created an > initrd/initramfs before ( aside from using the generic > mkinitrd/mkinitfamfs ). Meaning I have no idea how to implement this in > the init script.Depending on your distribution you just have to run something like mkinitrd, mkinitramfs, whatever. You should read appropriate docs to learn more, but, as I said, there''s nothing Xen specific - you only use a spcial Kernel, and define it in the VM config instead of some grub config. (apart of the fact that some distro''s Xen support even use grub config files with pygrub). I have placed all needed partitions in the Xen config something like:> <lvm volume with VM image> as hda ro > <lvm volume to contain the changes> as hdb w > <lvm volume that contains swap> as hdc wMost often I don''t configure full disks but single partition to be used by the VM, at least in paravirtual mode. so I mount lvm partitions as hda1, hdb1, ... Never tried if inserting the whole block device into a paravirtual VM works. I am not near the machine with the exact Xen config, but I can post it> in about 12 hours. > > Inside the init script, do I need to leave all of the script that is > generated by the mkinitrd/mkinitramfs?Why do you want to remove them? You have to try which ones you can leave out. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''ve never played much with unionfs, but I have done a bit of initrd tinkering to get ocfs2 working with diskless xen nodes sharing a common xen install. There''s a few reasons why its easier to leave modular support only for file systems you need to boot .. the biggest one (in the case of ocfs2 and others) is that the init scripts and controls that come stock with them want to be able to load and unload modules to function. The most efficient way to do it is not use the initrd, and build support for the FS directly into the kernel.. then go modify all of the init scripts and controls so they no longer load / unload modules to work. I don''t like doing that because I like everything to be the same. If you mount your initrd : mkdir /tmp/init && mount -o loop -t cramfs /boot/my-initrd.img And edit the file "linuxrc" , you''ll see where its appropriate to toss in some more lines of code to do things. In my case, I wanted to put all nics in an up state, initialize AoE, aoe-ping and verify some ATA device ID''s, run a few smart commands, fetch a cluster config, then load the ocfs2 modules. This let me pass an AoE root to the kernel so I could boot from nas storage. modprobe is copied to the initrd by default when you make it, however I''m not so sure about insmod (for user modules or otherwise not included when you run depmod). If you add any binaries just be sure you copy over any shared objects needed, treat it as if you were populating a chroot. It sounds like you could accomplish everything you want to do simply by adding some code in linuxrc (its just a shell script). linuxrc is run just prior to the system calling pivot_root to switch to the root file system passed to the kernel as a paramater. I think if you just look at the file, a "light bulb" should go on for you. My experience may not solve your problem but should help get you a little closer to a solution. If all you need to do is load unionfs at boot before the dom-u pivots to the VBD you specified in its config - this should be all you need. I''m also sure there''s a much easier way of going about it, did you try just running a depmod in the dom-u after manually installing the modules, making a ramdisk within it and copying it over to dom-0 for use? Sorry for the rather lengthy reply .. but as Henning also indicated .. I''m not 100% sure what you want to accomplish. Hope this helps. Best, -Tim On Fri, 2006-11-03 at 07:58 -0600, Otter wrote:> I am having problems with the initrd/initramfs. I am not really sure of > what needs to be done inside the init script for a VM. Since I have > never used a ramdisk with a VM. And I have never created an > initrd/initramfs before ( aside from using the generic > mkinitrd/mkinitfamfs ). Meaning I have no idea how to implement this in > the init script. > > I have placed all needed partitions in the Xen config something like: > <lvm volume with VM image> as hda ro > <lvm volume to contain the changes> as hdb w > <lvm volume that contains swap> as hdc w > > I am not near the machine with the exact Xen config, but I can post it > in about 12 hours. > > Inside the init script, do I need to leave all of the script that is > generated by the mkinitrd/mkinitramfs? > > I have tried just modifying the section of the script where it > configures the root file system. I mount hda, hdb in directories in the > initrd, and then mount the union of the two to another directory in the > initrd. I then try and make the union directory the root filesystem. > Then it all dies, with a kernel panic ''trying to kill init''. I can post > the script later today as well. I just don''t know enough about init > scripts to begin tracing my error =\ > > Thanks for the reply! > > > > Henning Sprang wrote: > > On 11/3/06, *Otter* <OtterzStuff@bellsouth.net > > <mailto:OtterzStuff@bellsouth.net>> wrote: > > > > Greetings, > > > > I would like to use unionfs for my Virtual Machines, and I would > > like to > > use initramfs instead of an initrd. But I am not sure how to > > accomplish > > this. I have read over the HOWTO section for Copy of Write, but > > haven''t > > really found the solution I want. I do not know much about > > initramfs or > > initrd for that matter, but I do know initramfs is suppose to replace > > the initrd so I would like to use it. Ultimately what I want is to > > have > > a read only partition on LVM2 that contains the virtual machine image, > > and this would be readonly. Then I would have another partition that > > would be read write. > > > > > > > > Just configure two disks in the VM config file. They are available as > > partitions inside the domU then. Then, I guess the definition how they > > should be used to achieve you goal is some config in the initrd, right? > > > > I am familiar with unionfs, but not too much with > > Xen, so if any can provide assistance please do! > > > > > > Your question is very generic, and multiple questions at once. > > Better describe different problems in different mail (or, forgive me > > if I don''t know enough abput initramfs and unionfs to understand they > > belong together). > > > > What did you try already, and what were your problems? What is "the > > solution you want" you didn''t find in the HOWTO''s? > > > > Henning > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the reply Tim,
I expanded the initrd, but I do not see a linuxrc.
Here is my Xen config, and init script from the initrd
Xen Config:
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.16-xen"
# Optional ramdisk.
ramdisk = "/root/Desktop/initrd_t1.img"
#vif = [ ''mac=00:00:00:00:00:01, bridge=xenbr0'' ]
disk = [
''phy:/dev/VolGroup00/VM_IMAGE,hda,r'',''phy:/dev/VolGroup00/VM_DELTA,hdb,w'',''phy:/dev/VolGroup00/VM_SWAP,hdc,w''
]
# Set root device.
root = "/VM_UNION"
for the root portion of the config I had originally used /dev/hda ro.
Init:
#!/bin/nash
mount -t proc /proc /proc
setquiet
echo Mounting proc filesystem
echo Mounting sysfs filesystem
mount -t sysfs /sys /sys
echo Creating /dev
mount -o mode=0755 -t tmpfs /dev /dev
mkdir /dev/pts
mount -t devpts -o gid=5,mode=620 /dev/pts /dev/pts
mkdir /dev/shm
mkdir /dev/mapper
echo Creating initial device nodes
mknod /dev/null c 1 3
mknod /dev/zero c 1 5
mknod /dev/systty c 4 0
mknod /dev/tty c 5 0
mknod /dev/console c 5 1
mknod /dev/ptmx c 5 2
mknod /dev/rtc c 10 135
mknod /dev/tty0 c 4 0
mknod /dev/tty1 c 4 1
mknod /dev/tty2 c 4 2
mknod /dev/tty3 c 4 3
mknod /dev/tty4 c 4 4
mknod /dev/tty5 c 4 5
mknod /dev/tty6 c 4 6
mknod /dev/tty7 c 4 7
mknod /dev/tty8 c 4 8
mknod /dev/tty9 c 4 9
mknod /dev/tty10 c 4 10
mknod /dev/tty11 c 4 11
mknod /dev/tty12 c 4 12
mknod /dev/ttyS0 c 4 64
mknod /dev/ttyS1 c 4 65
mknod /dev/ttyS2 c 4 66
mknod /dev/ttyS3 c 4 67
echo Setting up hotplug.
hotplug
echo Creating block device nodes.
mkblkdevs
echo "Loading jbd.ko module"
insmod /lib/jbd.ko
echo "Loading ext3.ko module"
insmod /lib/ext3.ko
echo "Loading dm-mod.ko module"
insmod /lib/dm-mod.ko
echo "Loading dm-mirror.ko module"
insmod /lib/dm-mirror.ko
echo "Loading dm-zero.ko module"
insmod /lib/dm-zero.ko
echo "Loading dm-snapshot.ko module"
insmod /lib/dm-snapshot.ko
echo "Loading unionfs.ko module"
insmod /lib/unionfs.ko
echo Making device-mapper control node
mkdmnod
mkblkdevs
#echo Scanning logical volumes
#lvm vgscan --ignorelockingfailure
#echo Activating logical volumes
#lvm vgchange -ay --ignorelockingfailure VolGroup00
echo "Resuming VM swap hdc"
resume /dev/hdc
echo "Mounting Read Only device"
mount -t ext3 /dev/hda /VM_RO
echo "Mounting Read Write device"
mount -t ext3 /dev/hdb /VM_RW
echo Creating root device.
mkrootdev -t unionfs -o dirs=/VM_RW:/VM_RO=ro /UNION
echo Mounting root filesystem.
mount /sysroot
echo Setting up other filesystems.
setuproot
echo Switching to new root and running init.
switchroot
Sorry for the delay in getting this info posted,
And thanks for all pointers so far!
James
Tim Post wrote:> I''ve never played much with unionfs, but I have done a bit of
initrd
> tinkering to get ocfs2 working with diskless xen nodes sharing a common
> xen install.
>
> There''s a few reasons why its easier to leave modular support only
for
> file systems you need to boot .. the biggest one (in the case of ocfs2
> and others) is that the init scripts and controls that come stock with
> them want to be able to load and unload modules to function.
>
> The most efficient way to do it is not use the initrd, and build support
> for the FS directly into the kernel.. then go modify all of the init
> scripts and controls so they no longer load / unload modules to work. I
> don''t like doing that because I like everything to be the same.
>
> If you mount your initrd :
>
> mkdir /tmp/init && mount -o loop -t cramfs /boot/my-initrd.img
>
> And edit the file "linuxrc" , you''ll see where its
appropriate to toss
> in some more lines of code to do things.
>
> In my case, I wanted to put all nics in an up state, initialize AoE,
> aoe-ping and verify some ATA device ID''s, run a few smart
commands,
> fetch a cluster config, then load the ocfs2 modules.
>
> This let me pass an AoE root to the kernel so I could boot from nas
> storage.
>
> modprobe is copied to the initrd by default when you make it, however
> I''m not so sure about insmod (for user modules or otherwise not
included
> when you run depmod). If you add any binaries just be sure you copy over
> any shared objects needed, treat it as if you were populating a chroot.
>
> It sounds like you could accomplish everything you want to do simply by
> adding some code in linuxrc (its just a shell script).
>
> linuxrc is run just prior to the system calling pivot_root to switch to
> the root file system passed to the kernel as a paramater.
>
> I think if you just look at the file, a "light bulb" should go on
for
> you. My experience may not solve your problem but should help get you a
> little closer to a solution.
>
> If all you need to do is load unionfs at boot before the dom-u pivots to
> the VBD you specified in its config - this should be all you need.
I''m
> also sure there''s a much easier way of going about it, did you try
just
> running a depmod in the dom-u after manually installing the modules,
> making a ramdisk within it and copying it over to dom-0 for use?
>
> Sorry for the rather lengthy reply .. but as Henning also indicated ..
> I''m not 100% sure what you want to accomplish.
>
> Hope this helps.
>
> Best,
> -Tim
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users