[Fedora-xen] Probems installiing windows under xen in FC6

[Denis Forveille]

Ian,

Did you check the thread called "Win Xp 32 bit as guest in..."? (I 
missed the ..in x86_64 FC6 dom0)
I had (and others too, it seems...) some problems to install Win XP fp2 
on my  FC6 x86_64 dom0...
I finally installed it with qemu...and now I run it directly with xen
Maybe the answer is in this thread...
(BTW thanks to David Parsley for his help...)

Denis



Ian Brown wrote:
> Hello,
> I am trying desperately to install windows under xen in FC6 on x86_64;
> my processor has virtulaization extensions (as can be seen from flags of
> /proc/cpuinfo).
> The kernel I have is the one from the FC6 DVD, 2.6.18-1.2798.fc6xen.
>
>
> I had prepared a configuration file , windows.hvm, which is
> given fully in the end of this message.
> When I ran :
> xm create windows.hvm , there is some window on the screen for a 
> second then
> it is closed.
>
> On the console I see
> xm create windows.hvm
> Using config file "/etc/xen/windows.hvm".
> Started domain ExampleHVMDomain
> and that's it.
>
>
> I am not sure about this line :
>  disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]
>     
> I am not sure about something: I do indeed have a sata disk; which is 
> sda;
> but when using qemu, should it also be sda?
>
> I see in the kernel log the following:
>
> rh kernel: device tap0 entered promiscuous mode
> rh kernel: audit(1163952063.221:41): dev=tap0 prom=256 old_prom=0
> auid=4294967295
> rh kernel: xenbr0: port 3(tap0) entering learning state
> rh kernel: xenbr0: topology change detected, propagating
> rh kernel: xenbr0: port 3(tap0) entering forwarding state
> rh kernel: device vif10.0 entered promiscuous mode
> rh kernel: audit(1163952063.589:42): dev=vif10.0 prom=256 old_prom=0
> auid=4294967295
> rh kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready
> rh kernel: xenbr0: port 4(vif10.0) entering disabled state
> rh kernel: device vif10.0 left promiscuous mode
> rh kernel: audit(1163952064.309:43): dev=vif10.0 prom=0 old_prom=256
> auid=4294967295
> rh kernel: xenbr0: port 4(vif10.0) entering disabled state
> rh kernel: xenbr0: port 3(tap0) entering disabled state
> rh kernel: device tap0 left promiscuous mode
> rh kernel: audit(1163952064.469:44): dev=tap0 prom=0 old_prom=256
> auid=4294967295
> rh kernel: xenbr0: port 3(tap0) entering disabled state
>
> and this is windows.hvm:
>
> #  -*- mode: python; -*-
>
> import os, re
> arch = os.uname()[4]
> if re.search('64', arch):
>    arch_libdir = 'lib64'
> else:
>    arch_libdir = 'lib'
>
> #---------------------------------------------------------------------------- 
>
> # Kernel image file.
> kernel = "/usr/lib/xen/boot/hvmloader"
>
> # The domain build function. HVM domain uses 'hvm'.
> builder='hvm'
>
> # Initial memory allocation (in megabytes) for the new domain.
> #
> # WARNING: Creating a domain with insufficient memory may cause out of
> #          memory errors. The domain needs enough memory to boot kernel
> #          and modules. Allocating less than 32MBs is not recommended.
> #memory = 128
> memory = 384
>
> # Shadow pagetable memory for the domain, in MB.
> # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
> shadow_memory = 8
>
> # A name for your domain. All domains must have different names.
> name = "ExampleHVMDomain"
>
> # 128-bit UUID for the domain.  The default behavior is to generate a 
> new UUID
> # on each call to 'xm create'.
> #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
>
> #----------------------------------------------------------------------------- 
>
> # the number of cpus guest platform has, default=1
> #vcpus=1
> vcpus=1
> # enable/disable HVM guest PAE, default=0 (disabled)
> #pae=0
>
> # enable/disable HVM guest ACPI, default=0 (disabled)
> #acpi=0
>
> # enable/disable HVM guest APIC, default=0 (disabled)
> #apic=0
>
> vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
>
> #---------------------------------------------------------------------------- 
>
> # Define the disk devices you want the domain to have access to, and
> # what you want them accessible as.
> # Each disk entry is of the form phy:UNAME,DEV,MODE
> # where UNAME is the device, DEV is the device name the domain will see,
> # and MODE is r for read-only, w for read-write.
>
> disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]
> cdrom='/dev/hdb'
> on_poweroff  = 'destroy'
> on_reboot   = 'restart'
> on_crash    = 'restart'
> #on_reboot    = 'destroy'
> #on_crash     = 'destroy'
> ne2000=0
>
> #============================================================================ 
>
>
> # New stuff
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
>
> #----------------------------------------------------------------------------- 
>
> # boot on floppy (a), hard disk (c) or CD-ROM (d)
> # default: hard disk, cd-rom, floppy
> #boot from cdrom
> boot="d"
> sdl=1
> vnc=0
>
> #---------------------------------------------------------------------------- 
>
> # enable stdvga, default = 0 (use cirrus logic device model)
> stdvga=0
>
> #----------------------------------------------------------------------------- 
>
> #   serial port re-direct to pty deivce, /dev/pts/n
> #   then xm console or minicom can connect
> #serial='pty'
>
>
> #----------------------------------------------------------------------------- 
>
> #    set the real time clock to local time [default=0 i.e. set to utc]
> #localtime=1
>
>
> #----------------------------------------------------------------------------- 
>
> #    start in full screen
> #full-screen=1
>
>
> #----------------------------------------------------------------------------- 
>
> #   Enable USB support (specific devices specified at runtime through the
> #            monitor window)
> usb=1
>
> #   Enable USB mouse support (only enable one of the following, 
> `mouse' for
> #                  PS/2 protocol relative mouse, `tablet' for
> #                  absolute mouse)
> usbdevice='mouse'
>
>
> any ideas what can cause the problem?
> Regards,
> Ian
>
> -- 
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>