Tony Su wrote:
> Re -reading my post, there are some small language issues which might
> make the post unclear, hoping with the following alterations the post
> might be more clear...
>
> Hello,
>
> Am hoping to get experienced eyes on this to evaluate how much of what
> I'm seeing is expected and what is not.
>
> System: openSUSE 12.2
> Desktop: KDE 4.8
> Virtualization: QEMU-KVM
> Also using graphical virt-manager
>
> Hardware: Laptop with occasionally available WiFi
>
> - I have found that anything configured for bridged networking still
> requires a wired connection, usually binding to eth0.
>
> - I have found that when any real connection to a Network exists
> (wireless or wired), if a Host Only network does not exist, then the
> Guest will be automatically configured to use User Mode Networking
> <only when the NIC is created>. If any network <is> available, then
> User Mode Networking no longer is an option initially or later and the
> virtual NIC is configurable for any available virtual network.
>   

Maybe you should try the "default" virtual network provided by libvirt. 
For more details, see

http://wiki.libvirt.org/page/VirtualNetworking

The NAT mode works well for me in similar scenarios.

Regards,
Jim

> - If a Guest is initially created with User Mode Networking and then
> the Host is disconnected from any and all real physical networks, User
> Mode
> Networking will fail with an error "service unavailable, port 5900"
> which likely means that a VNC connection cannot be made.
>
> - Curiously, working from the previous unbootable Guest(no service
> unavailable, port 5900 error), if a Host Only network is created and a
> second virtual network for the new Host Only network is added to the
> Guest described previously, the Guest VM will
> boot up and can even be
> viewed using virt-viewer. But, on closer inspection running ifconfig
> in the Guest reveals only one working NIC configured with an IP
> address for the User Mode Network while running ifconfig on the Host
> reveals that only the Host Only network is running and available. So,
> of course, Host and Guest cannot communicate using TCP/IP with each
> other except using virt-viewer (should not work?).
>
> - Have not tried, but am considering the idea of configuring the Host
> Only network to share the same networkID as the User Mode Network
> (10.0.2.0/24) but make sure the DHCP ranges are different.
> Theoretically I think this workaround might work but shouldn't be
> required.
>
> TIA,
> Tony
>
> On Mon, Nov 26, 2012 at 8:33 AM, Tony Su <[email protected]> wrote:
>   
>>  Hello,
>>
>>  Am hoping to get experienced eyes on this to evaluate how much of what I'm
>>  seeing is expected and what is not.
>>
>>  System: openSUSE 12.2
>>  Desktop: KDE 4.8
>>  Virtualization: QEMU-KVM
>>  Also using graphical virt-manager
>>
>>  Hardware: Laptop with occasionally available WiFi
>>
>>  - I have found that anything configured for bridged networking still
>>  requires a wired connection, usually binding to eth0.
>>
>>  - I have found that when any real connection to a Network exists (wireless
>>  or wired), if a Host Only network does not exist, then the Guest will be
>>  automatically configured to use User Mode Networking <only when the NIC is
>>  created>.
>>
>>  - When a physical connection does not exist for a Guest previously created
>>  using a NIC configured for User Mode Networking, User Mode Networking will
>>  fail with an error "service unavailable, port 5900" which likely means that
>>  a VNC connection cannot be made.
>>
>>  - Curiously, even with no physical network connection, if a Host Only
>>  network is created and a second virtual network for the new Host Only
>>  network is added to the Guest described previously, the Guest VM will boot
>>  up (no service unavailable, port 5900 error) and can even be viewed using
>>  virt-viewer. But, on closer inspection running ifconfig in the Guest
>>  reveals only one working NIC configured with an IP address for the User
>>  Mode Network while running ifconfig on the Host reveals that only the Host
>>  Only network is running and available. So, of course, Host and Guest cannot
>>     
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to