Displaying 7 results from an estimated 7 matches for "f3001000".
Did you mean:
f3000000
2010 Jun 10
1
Re: Xen-users Digest, Vol 64, Issue 52
...nfo.destroy: domid=14
> > [2010-06-06 21:31:38 4034] DEBUG (XendDomainInfo:2207) Destroying device
> > model
> > [2010-06-06 21:31:38 4034] INFO (image:556) mkts device model terminated
> > qemu-dm-mkts.log:
> > region type 1 at [c100,c200).
> > region type 0 at [f3001000,f3001100).
> > squash iomem [f3001000, f3001100).
> > reset requested in cpu_handle_ioreq.
> > Issued domain 15 reboot
> >
> > This is very frustrating, because the server is a live server, and reboot
> is
> > not preferred just randomly. And I must say that P...
2012 Aug 01
2
Bug report about Windows 7 pro 64 bit domU on xen-unstable dom0 with qemu traditional
2011 May 18
3
XCP jumbo frames in vm
...op- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 177
Region 0: I/O ports at c100 [size=256]
Region 1: Memory at f3001000 (32-bit, non-prefetchable) [size=256]
Kernel driver in use: 8139cp
Kernel modules: 8139too, 8139cp
If I am doing something wrong, please let me know. Or, if it is just
plain not possible. I am pulling my hair out.
Thanks,
Greg
_______________________________________________
Xen-users mailing l...
2011 Sep 16
2
Ubuntu 11.04 64-bit HVM on xen-unstable 23842
...mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.
Unknown PV product 3 loaded in guest
PV driver build 1
region type 1 at [c100,c200).
region type 0 at [f3001000,f3001100).
squash iomem [f3001000, f3001100).
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2012 Jul 24
1
Problems with HVM S3
...size 02000000: f0000008
(XEN) HVM14: pci dev 03:0 bar 14 size 01000000: f2000008
(XEN) HVM14: pci dev 02:0 bar 14 size 00001000: f3000000
(XEN) HVM14: pci dev 03:0 bar 10 size 00000100: 0000c001
(XEN) HVM14: pci dev 04:0 bar 10 size 00000100: 0000c101
(XEN) HVM14: pci dev 04:0 bar 14 size 00000100: f3001000
(XEN) HVM14: pci dev 01:2 bar 20 size 00000020: 0000c201
(XEN) HVM14: pci dev 01:1 bar 20 size 00000010: 0000c221
(XEN) HVM14: Multiprocessor initialisation:
(XEN) HVM14: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ...
done.
(XEN) HVM14: Testing HVM environment:
(XEN) HVM14: - REP...
2008 Aug 29
12
stubdom problem
Hello all Xen devels,
I''m writing howto''s in brazilian portuguese language about Xen-3.3.0
stubdom, pv-grub and others configurations. Following what is written
in xen-3.3.0/stubdom/README, I tried start a HVM but without success.
When I start the virtual machine calling ''xm create hvmtest'' command,
in a few seconds the virtual machine is dead (see
2008 Jan 23
13
Xen 3.2 and Big Real Mode support?
Hello,
I read in the announce of Xen 3.2.0 released that it has "preliminary
support for a wider range of bootloaders in fully virtualised (HVM)
guests, using full emulation of x86 ''real mode''" .
I''d like to know what is the level of the emulation of x86 ''real
mode''? I ask that because I tried to install OpenSuse 10.3 (I used
the iso file