| how install windows xen [message #96733] |
Sat, 17 March 2012 12:35  |
|
i have server with xen
and i have iso
and i greated vps with windows-lxblank.img
what the next step
i want install win 2003 in xen
regards
|
|
|
|
|
|
|
| Re: how install windows xen [message #98938 is a reply to message #97921] |
Fri, 29 June 2012 17:34  |
|
It woks fine under xen as long as your server supports it, you need to enable it in the BIOS of the server, if not it will not work.
What to do:
1- copy your ISO on the hypervm server @ /home
2- rename the ISO to wincd.img (you can also link it to /home/wincd.img)
3- go to the hypervm control panel and make a new VPS using the windows-lxblank.img
thats it now you can VNC to it in hypervm control panel (VNC does not work so good so use it to install then turn on remote desktop after you install it)
|
|
|
| Re: how install windows xen [message #99222 is a reply to message #98938] |
Sun, 08 July 2012 12:16 |
|
troylight wrote on Sat, 30 June 2012 04:34It woks fine under xen as long as your server supports it, you need to enable it in the BIOS of the server, if not it will not work.
What to do:
1- copy your ISO on the hypervm server @ /home
2- rename the ISO to wincd.img (you can also link it to /home/wincd.img)
3- go to the hypervm control panel and make a new VPS using the windows-lxblank.img
thats it now you can VNC to it in hypervm control panel (VNC does not work so good so use it to install then turn on remote desktop after you install it)
Have similar issue, i managed to boot up the win 2003 server but fail to connect to VNC via the vnc client on Hypervm. Error message could not connect to server : port 5903.
On the lxlabs tutorial never mention about this, so i expect this should be automatically configured. but i stuck in this phase.
any suggestion ?
|
|
|
|
| Re: how install windows xen [message #99230 is a reply to message #99226] |
Sun, 08 July 2012 23:56 |
|
[root@ZZZZZZZ bayu]# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vifwin201
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
it seem ok.
Here are my qemu log.
------------------------------------------------------------ -----
[root@GATOTKACA xen]# tail -n 200 qemu-dm.2909.log
domid: 34
qemu: the number of cpus is 1
Using file in read-only mode
Using file in read-write mode
Watching /local/domain/34/logdirty/next-active
Watching /local/domain/0/device-model/34/command
qemu_map_cache_init nr_buckets = 10000
shared page at pfn ffff
buffered io page at pfn fffd
xs_read(/vm/9536cb2a-ecf7-cb75-650f-1e62a9d9dae4/rtc/timeoff set): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
gpe_sts_write: addr=0x1f6a, val=0x0.
gpe_sts_write: addr=0x1f6b, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
gpe_en_write: addr=0x1f6c, val=0x0.
gpe_en_write: addr=0x1f6d, val=0x0.
gpe_en_write: addr=0x1f6e, val=0x0.
gpe_en_write: addr=0x1f6f, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
------------------------------------------------------------ ----
|
|
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
. 
