Trouble installing Windows HVM on 3.1
by Johnson, Tony M
All,
Whether I utilize the DVD or ISO image, once the initial setup is
completed, rebooted and restarted,
I get the following pop-up:
"The file 'asms' on Windows XP Professional Service Pack 2 CD is needed"
Has anyone experienced and solved this problem using x64?
Tony
16 years, 9 months
Re: [Fedora-xen] Trouble installing Windows HVM on 3.1
by Ronald Warsow
Johnson, Tony M wrote:
> Installing windows XP professional on a core duo with
> Fedora x64 installed. Thanks for the pointer I will give
> it a try. I assume you have not encountered this issue
> because of embedding the asms with NLite.
to your above question:
up to now i was under the impression that nlite among other things
deletes some stuff, esp. asms dir, also.
but this is not the case for my lastly created iso.
i install that xp (x86) iso's under f7 (x64) with qemu-kvm !
and i believe the internal "mechanics" to do a xp installation with
virt-manager under a xen kernel makes not diff. to me.
maybe i'm wrong ?
but i tried it now and it leads me to your initial question:
do you mean the xp installation prompts you for file asms from
*GLOBALROOT\DEVICE\CDROM\I386*
???????????
if so then it's described/discussed here:
https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf
page 5...
let me know if that was your question !
>
> Tony
>
> -----Original Message-----
> From: Ronald Warsow [mailto:rwarsow@online.de]
> Sent: Tuesday, July 10, 2007 11:21 AM
> To: Johnson, Tony M
> Cc: fedora-xen(a)redhat.com
> Subject: Re: [Fedora-xen] Trouble installing Windows HVM on 3.1
>
> Johnson, Tony M wrote:
>> All,
>> Whether I utilize the DVD or ISO image, once the initial setup is
>> completed, rebooted and restarted, I get the following pop-up:
>> "The file 'asms' on Windows XP Professional Service Pack 2 CD is
> needed"
>> Has anyone experienced and solved this problem using x64?
>
> windows x64 ?
> or
> linux x64 and windows x86 ?
>
> i compose win iso's with nlite
> http://en.wikipedia.org/wiki/NLite
>
> - unattend installs,
> - all sp's/updates,
> - no unneeded grap,
> - no hassle with asms files/dir's
> - small iso's
> - ...
>
>> Tony
>>
>
--
Ronald
16 years, 9 months
CentOS 5 guest sees only one CPU
by Kyle Tucker
Hi,
We have set up Xen on Fedora Core 5 Domain0 with a CentOS 5 HVM.
This is a Dell Poweredge SC1430 system. We've set vcpus=2 and it will
only see one CPU. I've also tried setting cpus="1,2" or "6,7" to no avail.
Here's what xm reports when I've set cpus="6,7".
# xm vcpu-list
Name ID VCPUs CPU State Time(s) CPU Affinity
Domain-0 0 0 6 -b- 3304.1 any cpu
Domain-0 0 1 1 -b- 245.0 any cpu
Domain-0 0 2 0 -b- 198.5 any cpu
Domain-0 0 3 5 -b- 901.3 any cpu
Domain-0 0 4 4 -b- 192.6 any cpu
Domain-0 0 5 2 -b- 236.0 any cpu
Domain-0 0 6 0 r-- 240.8 any cpu
Domain-0 0 7 3 -b- 200.9 any cpu
vm2 67 0 7 -b- 45.2 6-7
vm2 67 1 - --p 0.0 6-7
The following is in vm2's dmesg output, and I suspect the line about not
detecting a SMP motherboard begins to point at the issue. Any thoughts on
what's up? Thanks.
CPU: After generic identify, caps: 8fa9f9bf 00100000 00000000 00000000 0000e215 00000000 00000000
CPU: After vendor identify, caps: 8fa9f9bf 00100000 00000000 00000000 0000e215 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: After all inits, caps: 8fa9f1bf 00100000 00000000 00000140 0000e215 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
CPU0: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
--
- Kyle
---------------------------------------------
kylet(a)panix.com http://www.panix.com/~kylet
---------------------------------------------
16 years, 9 months
guest domain couldn't be started
by taoj2＠cs.rpi.edu
Hi,
I install a guest Fedora inside the host Fedora. When I use the
service xend status
to check the status of xend. It shows xend is running.
However when I use
xm create xen1
to start the guest domain xen1, it failed. The corresponding file xen1 is
in /etc/xen/xen1. The error msg is as follows:
[root@phillis xen]# xm create xen1
Using config file "./xen1".
Going to boot Fedora Core (2.6.19-1.2911.6.5.fc6xen)
kernel: /vmlinuz-2.6.19-1.2911.6.5.fc6xen
initrd: /initrd-2.6.19-1.2911.6.5.fc6xen.img
Error: Device 0 (vif) could not be connected. Could not find bridge device
xenbr1
I found the following line in file /etc/xen/xen1,
vif = [ 'mac=00:16:3e:5c:5c:31, bridge=xenbr1', ]
Why device 0 couldn't be connected? I don't know the usage of the bridge
device, xenbr1.
Anybody has similar problem ? Or know how to slove this problem? THanks.
Best
Angel
16 years, 9 months
ups connected to serial port, but can't communicate via ttyS0
by Ranbir
Hi,
I tried to use ttyS0 in dom0 for a serial interface UPS, but apcupsd
complains that it can't talk to ttyS0. I look through /var/log/messages,
and sure enough, xen is using it:
Jul 3 09:45:22 xenmaster kernel: Xen virtual console successfully
installed as ttyS0
Can that be turned off, so that ttyS0 isn't used by Xen? I tried to do
this several months ago, but back then I was told Fedora was working
towards fixing the serial port access problems.
Regards,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 2.6.20-1.2962.fc6 i686 GNU/Linux
08:15:36 up 5 days, 20:58, 3 users, load average: 0.35, 0.18, 0.17
16 years, 9 months
Not seeing all RAM
by Ranbir
Hello,
I'm running a FC6 dom0, with kernel version,
kernel-xen-2.6.19-1.2895.fc6 on a Dell PowerEdge 1600SC. I just
upgraded it from 1 GB (2 x 512 MB modules) to 3 GB (2 x 1 GB + 2 x 512
MB). The BIOS sees all of the ram, but kernel does not. All I see when
I run free is this:
total used free shared buffers
cached
Mem: 2454528 207876 2246652 0 11032
47380
-/+ buffers/cache: 149464 2305064
Swap: 524280 0 524280
It looks like 512 MB is missing.
Here's a bit more detail from dmesg:
Memory: 2874124k/2987900k available (2166k kernel code, 104532k
reserved, 1100k data, 184k init, 2242436k highmem)
So, what happened to the rest of the RAM? I should add that the server
is updated with the latest firmware and BIOS.
BTW, I appear to be having problems with one of my domUs now too (after
the ram upgrade). A PCI device I was handing to the domU is now causing
the domU kernel to panic, crashing the domU. I'll try to get a copy of
the error message.
Any help appreciated.
Regards,
Ranbir
--
Kanwar Ranbir Sandhu
Linux 2.6.20-1.2944.fc6 i686 GNU/Linux
00:17:27 up 10:25, 2 users, load average: 0.68, 0.43, 0.26
16 years, 9 months
Xen kernel doesn't boot for me
by Doug Eubanks
I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running Fedora 7.
Each time, it seems to hang during or perhaps right after the SCSI hardware is initialized. It doesn't panic, although it sometimes prints messages about USB devices not accepting new addresses (but not always).
I am attaching my SCSI and CPU info, if anyone has a suggestion to fix or troubleshoot this I would appreciate any information.
[root@DMZServer /]# ls /proc/scsi/
aic7xxx device_info gdth scsi sg
[root@DMZServer /]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.76
clflush size : 32
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
16 years, 9 months
HVM bridge not working any more
by Weismueller, Jonas
Hi,
I am using xen on F7. My guest config looks like this:
*********************************************
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
name = "scp231"
vcpus=2
pae=1
acpi=1
vif = [ 'type=ioemu, bridge=virbr0' ]
dhcp="off"
disk = [ 'phy:/dev/aida/scp-231,hda,w', ',hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="cda"
vnc=1
vncdisplay=1
vncpasswd=''
stdvga=0
serial='pty'
localtime=1
*********************************************
[root@csli9 ~]# /etc/xen/scripts/network-bridge status
============================================================
8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 00:30:48:31:97:49 brd ff:ff:ff:ff:ff:ff
inet 172.16.1.37/16 brd 172.16.255.255 scope global eth2
inet6 fe80::230:48ff:fe31:9749/64 scope link
valid_lft forever preferred_lft forever
8: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 00:30:48:31:97:49 brd ff:ff:ff:ff:ff:ff
inet 172.16.1.37/16 brd 172.16.255.255 scope global eth2
inet6 fe80::230:48ff:fe31:9749/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
eth2 8000.003048319749 no peth2
virbr0 8000.3a7b564bbcda no tap0
vif1.0
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
172.16.0.0/16 dev eth2 proto kernel scope link src 172.16.1.37
default via 172.16.1.16 dev eth2
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0
virbr0
172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2
0.0.0.0 172.16.1.16 0.0.0.0 UG 0 0 0 eth2
============================================================
[root@csli9 ~]# ifconfig
eth2 Link encap:Ethernet HWaddr 00:30:48:31:97:49
inet addr:172.16.1.37 Bcast:172.16.255.255 Mask:255.255.0.0
inet6 addr: fe80::230:48ff:fe31:9749/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15230 errors:0 dropped:0 overruns:0 frame:0
TX packets:3692 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:897539 (876.5 KiB) TX bytes:2761958 (2.6 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6171 errors:0 dropped:0 overruns:0 frame:0
TX packets:6171 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:51022608 (48.6 MiB) TX bytes:51022608 (48.6 MiB)
peth2 Link encap:Ethernet HWaddr 00:30:48:31:97:49
inet6 addr: fe80::230:48ff:fe31:9749/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:240988 errors:0 dropped:0 overruns:0 frame:0
TX packets:3730 errors:0 dropped:0 overruns:0 carrier:0
collisions:539 txqueuelen:100
RX bytes:65841255 (62.7 MiB) TX bytes:2780370 (2.6 MiB)
Base address:0x4020 Memory:d8420000-d8440000
tap0 Link encap:Ethernet HWaddr 3A:7B:56:4B:BC:DA
inet6 addr: fe80::387b:56ff:fe4b:bcda/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:7544 (7.3 KiB) TX bytes:510 (510.0 b)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:32
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
virbr0 Link encap:Ethernet HWaddr 3A:7B:56:4B:BC:DA
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:110 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6004 (5.8 KiB) TX bytes:510 (510.0 b)
I would like to use the guest within the subnet of eth2, so 172.16.0.0 .
But it doesn't work for any reason? It looks like, that I only can use a
192.168.122.X address in the guest. Any glue how to bridge the interface
to be able access the 172.16.0.0 network directly?
Regards Jonas
--
---------------------------------------------------------------------------
Jonas Weismueller Phone: +49 721 9497-163
COMSOFT GmbH Fax: +49 721 9497-129
Wachhausstrasse 5a http://www.comsoft.de
76227 Karlsruhe, Germany mailto:jonas.weismueller@comsoft.de
Geschäftsführer: Manfred Jlg, Manfred Schmid
Sitz der Gesellschaft: Karlsruhe, Handelsregister: Mannheim HRB 102488
Help save paper - do you really need to print this e-mail?
--- Disclaimer ---
This mail contains private or confidential information for the eyes of the addressee(s) named within this mail only.
Any distribution or usage, in whole or in part, is strictly prohibited.
If the context of this message indicates that you may have received this mail by error, please immediately contact and notify
the sender and delete this mail from your computers as well as from your mail server. Thank you!
---------------------------------------------------------------------------
16 years, 9 months
Xen kernel doesn't boot for me
by Doug Eubanks
I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running Fedora 7.
Each time, it seems to hang during or perhaps right after the SCSI hardware is initialized. It doesn't panic, although it sometimes prints messages about USB devices not accepting new addresses (but not always).
I am attaching my SCSI and CPU info, if anyone has a suggestion to fix or troubleshoot this I would appreciate any information.
[root@DMZServer /]# ls /proc/scsi/
aic7xxx device_info gdth scsi sg
[root@DMZServer /]# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.76
clflush size : 32
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 0
cpu MHz : 701.640
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1403.02
clflush size : 32
16 years, 9 months
How to shutdown a hvm guest gracefully?
by Felix Schwarz
Hi,
sometimes I forget to shutdown my hvm guests before restarting the host machine.
I want to prevent this/automatically shutdown the guests gracefully (as if I
typed 'poweroff' on the guest's console)
http://fedoraproject.org/wiki/FedoraXenQuickstartFC6:
> To gracefully power off a guest use:
> # virsh shutdown <virtual machine (name | id | uuid)>
On my FC6 (x86_64) machine this is only works for pv guests. Unfortunately, I
use several hvm guests (e.g. 32 bit guests for FC{5,6,7} which can not be run
under the current 64 bit xen in FC7 - AFAIK).
However, all these guests are linux machines which can be powered off by sending
"Ctrl+Alt+Del". Is there any possibility to gracefully shut down linux hvm guests?
fs
16 years, 9 months
