Hi.
When I try to create a new Windows XenU I get these error:
guineapig:/etc/xen# xm create win1.cfg
Using config file "./win1.cfg".
VNC= 1
Unexpected error: exceptions.OSError
Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
File "/usr/sbin/xm", line 10, in ?
main.main(sys.argv)
File "//usr/lib64/python/xen/xm/main.py", line 2453, in main
_, rc = _run_cmd(cmd, cmd_name, args)
File "//usr/lib64/python/xen/xm/main.py", line 2477, in _run_cmd
return True, cmd(args)
File "<string>", line 1, in <lambda>
File "//usr/lib64/python/xen/xm/main.py", line 1266, in
xm_importcommand
cmd.main([command] + args)
File "//usr/lib64/python/xen/xm/create.py", line 1309, in main
dom = make_domain(opts, config)
File "//usr/lib64/python/xen/xm/create.py", line 1054, in
make_domain
os.kill(vncpid, signal.SIGKILL)
OSError: [Errno 3] No such process
I''m using Xen 3.1.0 on a Dual Opteron 2212. The AMD-V technology is
enabled by BIOS.
This is the win1.cfg file:
kernel = ''/usr/lib/xen/boot/hvmloader''
builder = ''hvm''
memory = ''512''
device_modem = ''/usr/lib/xen/bin/qemu-dm''
root = ''/dev/sda1 ro''
disk = [ ''phy:vserver/win1-disk,sda1,w'',
''file:/home/mattia/win2003stdita.iso,ioemu:hda:cdrom,r'' ]
name = ''win1''
vif = [ ''ip=192.168.1.55'' ]
boot = ''d''
vnc=1
vncviewer=1
sdl=0
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
All other Linux virtual machines works without any problems.
Where is the problem?
Thank you very much!
Bye.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
At 17:18 30/07/2007, shacky wrote:>Hi. >When I try to create a new Windows XenU I get these error: > >guineapig:/etc/xen# xm create win1.cfg >Using config file "./win1.cfg". >VNC= 1 >Unexpected error: exceptions.OSError > >Please report to xen-devel@lists.xensource.com >Traceback (most recent call last): > File "/usr/sbin/xm", line 10, in ? > main.main(sys.argv) > File "//usr/lib64/python/xen/xm/main.py", line 2453, in main > _, rc = _run_cmd(cmd, cmd_name, args) > File "//usr/lib64/python/xen/xm/main.py", line 2477, in _run_cmd > return True, cmd(args) > File "<string>", line 1, in <lambda> > File "//usr/lib64/python/xen/xm/main.py", line 1266, in xm_importcommand > cmd.main([command] + args) > File "//usr/lib64/python/xen/xm/create.py", line 1309, in main > dom = make_domain(opts, config) > File "//usr/lib64/python/xen/xm/create.py", line 1054, in make_domain > os.kill(vncpid, signal.SIGKILL) >OSError: [Errno 3] No such process > >I''m using Xen 3.1.0 on a Dual Opteron 2212. The AMD-V technology is >enabled by BIOS. > >This is the win1.cfg file: > >kernel = ''/usr/lib/xen/boot/hvmloader'' >builder = ''hvm'' >memory = ''512'' >device_modem = ''/usr/lib/xen/bin/qemu-dm'' >root = ''/dev/sda1 ro'' >disk = [ ''phy:vserver/win1-disk,sda1,w'', >''file:/home/mattia/win2003stdita.iso,ioemu:hda:cdrom,r'' ] >name = ''win1'' >vif = [ ''ip=192.168.1.55'' ] >boot = ''d'' >vnc=1 >vncviewer=1 >sdl=0 >on_poweroff = ''destroy'' >on_reboot = ''restart'' >on_crash = ''restart'' > >All other Linux virtual machines works without any problems.I still don''t think the HVM BIOS supports booting from SCSI/SATA drives. Try using "hda" instead of "sda" (and of course change your "hda" for the CDROM to perhaps "hdb"). You don''t need a "root" in HVM domains. You also can''t set the IP address in a HVM domain, you need to do that inside windows using the control-panel (I find it easiest to use DHCP - but that depends on if you have a suitably configured DHCP-server or not). -- Mats>Where is the problem? > >Thank you very much! >Bye. > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> I still don''t think the HVM BIOS supports booting from SCSI/SATA > drives. Try using "hda" instead of "sda" (and of course change your > "hda" for the CDROM to perhaps "hdb").Ok, thank you. I changed "sda1" to "hda" and now the VM is booting up. But windows installation doesn''t start, it hangs at "Windows starting". If I change "hda" to "hda1" the Windows installation starts, but it doesn''t recognise any hard disk drive. Another problem is that if I try to connect to Xen with UltraVNC Viewer it doesn''t work (the vncviewer.exe process is at 99% of CPU on my Windows client) and it hangs. If I use RealVNC it works.> You also can''t set the IP address in a HVM domain, you need to do > that inside windows using the control-panel (I find it easiest to use > DHCP - but that depends on if you have a suitably configured > DHCP-server or not).Yes, I have a DHCP server in my network... Thank you very much! Bye. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
At 18:12 30/07/2007, shacky wrote:> > I still don''t think the HVM BIOS supports booting from SCSI/SATA > > drives. Try using "hda" instead of "sda" (and of course change your > > "hda" for the CDROM to perhaps "hdb"). > >Ok, thank you. >I changed "sda1" to "hda" and now the VM is booting up. >But windows installation doesn''t start, it hangs at "Windows starting". >If I change "hda" to "hda1" the Windows installation starts, but it >doesn''t recognise any hard disk drive."hda1" isn''t a valid option for HVM domains, so I don''t see why that would work better.>Another problem is that if I try to connect to Xen with UltraVNC >Viewer it doesn''t work (the vncviewer.exe process is at 99% of CPU on >my Windows client) and it hangs. >If I use RealVNC it works.I guess that means that UltraVNC is broken for this particular use - but I know nothing about different VNC servers - I''ve mostly been using SDL over X-windows. -- Mats _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> "hda1" isn''t a valid option for HVM domains, so I don''t see why that > would work better.Ok. Now I''m using "hda" but it isn''t recognise any hard disk al all. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
At 18:21 30/07/2007, shacky wrote:> > "hda1" isn''t a valid option for HVM domains, so I don''t see why that > > would work better. > >Ok. >Now I''m using "hda" but it isn''t recognise any hard disk al all.Any error message(s) in "xend.log"? How about if you specify the full path to the disk-image in the config file? -- Mats _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> How about if you specify the full path to the disk-image in the config file?It works! :-) Thank you!! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Now my Windows VM works. In the hardware manager of Windows Server 2003 it shows 3 unrecognised devices, a PCI device and a unknown device. Do you know what devices they could be? And the serial port (COM3) isn''t working (it shows me the "error 10, impossible to startup the device"). Do you know whehere the problem could reside? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> In the hardware manager of Windows Server 2003 it shows 3 unrecognised > devices, a PCI device and a unknown device. > Do you know what devices they could be?Well, there''s probably the Xen Platform Device in there, which you wouldn''t have the driver for unless you were running paravirtualised drivers (and there aren''t any for Windows unless you''re using some flavour XenEnterprise or Novell''s new / upcoming Windows driver package). It doesn''t do any harm, you don''t need the platform device to be recognised in order for everything to work.> And the serial port (COM3) isn''t working (it shows me the "error 10, > impossible to startup the device"). Do you know whehere the problem > could reside?Wouldn''t the first serial port be COM1 in Windows terminology, or am I being confused? AFAIK, you can only have one virtual serial port at the moment. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> Well, there''s probably the Xen Platform Device in there, which you wouldn''t > have the driver for unless you were running paravirtualised drivers (and > there aren''t any for Windows unless you''re using some flavour XenEnterprise > or Novell''s new / upcoming Windows driver package). It doesn''t do any harm, > you don''t need the platform device to be recognised in order for everything > to work.So I can''t find the drivers in any place?> Wouldn''t the first serial port be COM1 in Windows terminology, or am I being > confused? AFAIK, you can only have one virtual serial port at the moment.Yes, the first serial port is COM1, but it is recognised as COM3... _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel