nesredin mahmud
2013-Jun-14 13:46 UTC
Re: DomU: piix:not 100% native mode: will probe irq later
Hello wei,
I dont have the ip address for it. The interface configuration looks like
this:
eth0 Link encap:Ethernet HWaddr 88:51:fb:7d:3d:ae
inet6 addr: fe80::8a51:fbff:fe7d:3dae/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128696 errors:0 dropped:0 overruns:0 frame:0
TX packets:39448 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:50345545 (50.3 MB) TX bytes:8203273 (8.2 MB)
Interrupt:20 Memory:f7c00000-f7c20000
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:8513 errors:0 dropped:0 overruns:0 frame:0
TX packets:8513 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1116727 (1.1 MB) TX bytes:1116727 (1.1 MB)
tap14.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:16776 (16.7 KB)
vif14.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
UP BROADCAST RUNNING 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 fe:ff:ff:ff:ff:ff
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:405 (405.0 B)
xenbr0 Link encap:Ethernet HWaddr 88:51:fb:7d:3d:ae
inet addr:10.10.15.81 Bcast:10.10.15.255 Mask:255.255.255.0
inet6 addr: fe80::8a51:fbff:fe7d:3dae/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:123406 errors:0 dropped:0 overruns:0 frame:0
TX packets:38623 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:47494627 (47.4 MB) TX bytes:7935997 (7.9 MB)
Thank you,
//nas
On Fri, Jun 14, 2013 at 1:09 PM, Wei Liu <wei.liu2@citrix.com> wrote:
> On Fri, Jun 14, 2013 at 12:32:01PM +0200, nesredin mahmud wrote:
> > hello again,
> >
> > I did the same the procedure with xen-4.2.2, the guest machine booted
> > successfully. But I wana do it on xen-4.1.2 because virt-manager seems
to
> > work very well in this version and also is default ubuntu distribution
> > support.
> > I hope am not pushing so hard...but i have reproduced similar problem
on
> > xen-4.1.2 from the guest machine and it seems a console problem. But i
ve
> > no clue what to do next.
>
> Can you ssh into the guest even if the console is stuck? Serial console
> freezing doesn''t necessary means the guest is crashed / stuck. If
the
> guest is still working, can you use ssh instead?
>
>
> Wei.
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users