libvirt users - Feb 2020 - Re: guest-fsfreeze-freeze freezes all mounted block devices

Link? 

-----Original Message-----
Sent: 21 February 2020 11:50
To: Marc Roos
Cc: pkrempa; libvirt-users
Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices

On Mon, Feb 17, 2020 at 01:52:02PM +0100, Marc Roos
wrote:
>  
> Hmmm, using 'virsh domfsinfo testdom' gives me a crash in win2008r2
> (using software from virtio-win-0.1.171.iso)
> 
> Fault bucket , type 0
> Event Name: APPCRASH
> Response: Not available
> Cab Id: 0
> 
> Problem signature:
> P1: qemu-ga.exe
> P2: 100.0.0.0
> P3: 5c473543
> P4: KERNELBASE.dll
> P5: 6.1.7601.24545
> P6: 5e0eb6bd
> P7: c0000005
> P8: 000000000000c4d2
> P9: 
> P10: 
> 
> Attached files:
> 
> These files may be available here:
> C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_qemu-ga.exe_
> bd 2e6535bdb93328680e0285e89e08f2866db83_0b0deada
> 
> Analysis symbol: 
> Rechecking for solution: 0
> Report Id: 3d82596e-517c-11ea-b213-525400e83365
> Report Status: 0
That's not good!  Could you report this problem to the QEMU bug tracker.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    
https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            
https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    
https://www.instagram.com/dberrange :|

On Fri, Feb 21, 2020 at 04:35:46PM +0100, Marc Roos
wrote:
> Link?
> 
> That's not good!  Could you report this problem to the QEMU bug
tracker.
https://www.qemu.org/support/

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

I have been asking at technet about if I could snapshot an exchange db 
volume[1]. But it looks like that windows server backup is sort of doing 
the same. Creating vs image, and backup that one. However they truncated 
the exchange db log files after a succesful procedure. 

I was wondering if someone is doing this already. How does the guest 
freeze work exactly in windows (In linux it is quite clear no io is 
done). I assume that if the guest is invoking the vss service, and then 
you snapshot on the host environment. You have a snapshot with a vss 
image? So if you want to recover, you first need to 'roll back' to that 
internal vss image on the snapshot?


[1]
https://social.technet.microsoft.com/Forums/office/en-US/7818e7a5-3c09-4f36-9158-e423d0c0a705/mailbox-database-disk-snapshot?forum=Exch2016GD

https://social.technet.microsoft.com/Forums/office/en-US/922ff22a-73d6-4b86-b718-b6300754a467/wsbexchangeexe-how-to-use-how-does-it-work-with-wbadmin-and-vssfull-fixing-external?forum=Exch2016GD

I am doing a virsh detach-interface and an attach-interface. Is it 
possible to automatically bring the interface up after attaching it?

On 8/8/20 11:26 PM, brent s. wrote:
> On 8/8/20 9:42 AM, Marc Roos wrote:
>>   
>> I am doing a virsh detach-interface and an attach-interface. Is it
>> possible to automatically bring the interface up after attaching it?
>>
> 
> By coincidence, I was just playing with this with the python API.
> 
> The interface being brought up automatically, if I understand your
> question correctly, depends on the OS of the guest having hotplug
> support for the NIC you have selected for it.
> 
> It takes a couple seconds, but I can generally detach and re-attach an
> interface in CentOS Linux, for instance, with only about a 2-5 second
> hiccup in network traffic.
Yes, by default any hotplugged interface will be online when it's 
attached. You need to modify the XML of the interface to have it plugged 
in with an offline status. If it's not coming up in the guest, then 
that's something in the guest OS, not the emulated interface's online 
status, and will need to be taken care of in the guest OS.